Building Automation Knowledge Base

Issue Failed to initialize view, access denied or type mismatch when logging in to workstation with some users. Environment TAC Vista Cause When you log in to TAC Vista workstation a default alarmview is always opened (if you are using user profiles you can specify other alarm views. All users that are using the default alarm view have to have at least read rights to $AlarmColumns, $AlarmView and $DisabledView Resolution Log in with a system user Right click on the $AlarmColumns and select authority. If everyone is not in the access control list with at least read rights drag everyone from the Group/users list. Repeat for $AlarmView and $DisabledAlarms

Issue Does the operation/accuracy of the 4-20mA Humidity sensor deteriorate over time? Environment SHR100 SHD100 Cause Accuracy deterioration over time? Resolution The documented deterioration/inaccuracy after 5 years is < ± 3% RH. For more details, see the data sheet for each sensor model respectively.

Issue Vista reports running on EXCEL 2010 do not save the date format correctly. Environment Microsoft EXCEL 2010 Vista 5.1.5 and below Cause Excel 2010 is not supported on Vista 5.1.5 and below Resolution To get the date and time format to work correctly with Vista uninstall Excel 2010 and install Excel 2007. The other option is to upgrade to Vista 5.1.7 which supports Excel 2010 A possible  workaround  is to insert your trends into the Work Area of the report. That is the area to the right of the main page. Then you can copy this information to the main page and format the cells on the main page.    

Issue Is SysManSMS Server and VISTA 5.1.7 tested on Windows 2008 R2 running in a Marathon EverRun Level 3 Solution? Environment TAC Vista 5.1.7 SysManSMS Server Cause  The Server software is running on any Windows platform and release, including Embedded Windows.. Resolution The SysManSMS Server is written is C and has no special requirements for the Windows platform. The Server software is running on any Windows platform and release, including Embedded Windows. The software has been certified by Microsoft for Windows 7, and tested for Windows 2008 R2.It will run in both 32-bits and 64-bits (compatibility mode) environments. The compatibility with TAC/Vista is no issue at all. The clean interface between Vista (writing Alert Files) and SysMan picking up the files to process will always work, We have more than 500 TAC/Schneider installations used with Vista. No reported problems. Marathon EverRun Level 3 we do not know at all. As long as this software does not alter the above environments, it will for sure run.

Issue Is trend logs saved in the SQL server or Vista database? Environment TAC vista 4.3.0 and later versions. Cause All trend log values are sent from the Vista server to the $queue folder in the Vista database and then a service called TAC DSSwriter is taking the trend log from the $queue folder and transfer them in to the SQL database.  Resolution All trend logs and events are stored in a SQL database.

Issue Monitor the communication integrity of sub-LAN smoke control points Environment sub-LAN controllers Smoke Control Cause Smoke control systems must maintain communication with the sub-LAN controllers at all time. Interruptions in communication must be immediately known and responded to. Resolution Create a single point that will go OLD if communication is lost to any of the smoke control sub-LAN controllers. Refer to TCON 231, Smoke Control Systems, Manual, sub-LAN monitoring for more information.

Issue Trendlog Server is busy. Please try viewing the page again later Diagram The error looks like a java popup with error "Server is busy. Please try viewing the page again later" Environment Xenta webserver Cause It may take up to 15 minutes before a trendlogs actually starts (Depending on how many trendlogs that are available in the Xenta) after a restart of a Xenta webserver. During this time a Java error might appear if you try to call something including values from a trendlog i.e. Diagram Resolution The server is trying to startup all the trendlogs so please wait up to 15 minutes and try to view the page again.

Issue xP expansion module is not being recognized. Environment BCX 9640 ACX 57xx xp DI8 Cause Controller that the module was added to needs to be cold started before it will recognize the module Resolution Adding xP expansion modules to either an ACX57xx or a BCX9640 states in the module reference guide that the modules can be added to controllers while the power is applied EXCEPT for the ACX57xx or the BCX96xx models. Power down the ACX57xx or the BCX96xx Add module to the ACX57xx or the BCX96xx Re-apply power to the controller Green CPU light on module should blink, if not follow next step. Re-load of controller.

Issue Is the LCMA-103 (UIO board) interchangeable with the GCMA-106 (SIO board)? Environment LCM-84110, LCM-84210, LCMA-103 GCM-84111, GCM-84121, GCM-84211, GCM-84221, GCMA-106 Cause Not applicable Resolution No, the LCMA-103 is not interchangeable with the GCMA-106.

Issue User account with read rights have admin access to all Xenta web pages webserver access thru Vista Environment Vista Xenta   Cause When the default settings are used, all users in TAC Vista Workstation have full access to all pages in Xenta Server regardless of their rights in Vista. This is due to the fact that the Vista Workstation user uses the root account to access Xenta Server. The root account always has full permissions to objects in Xenta Server. Resolution Enable Enhanced Xenta Server web access Under Vista server right click on $system object and choose properties (Need to have admin rights) Enable "Enhanced Xenta Server web access" Click ok and log in the user that should only have read rights.

Issue What is the best way to retrieve Logged data. Environment Logged data Logging Log retrieval Cause Sigma logged data is not always available to view, what is the best way to retrieve logged data from the Sigma controllers? Resolution Sigma controllers and IC's have the ability to upload logged data to the Sigma server when required, this is carried out when the controller data tracks are a certain percentage full. This is the best way of retrieving logged data. However this can be random and there will be occasions when a user wishes to see data that has not yet been uploaded. If the user wishes to retrieve logged data from the controllers, there are two methods that can be used. 1 -The first method is to manually instruct the controller to upload its logged data. Using "System Diagnostics" select the required controller, and from the "Options" menu choose to upload "All Logged data" or "Selected Logged data". This action will return the data, which can then be reviewed. 2 - The second method is to create a scheduled retrieval. Enter "System Setup" and choose "Scheduled Actions".  This option allows you to set the time that action occurs and can specify which controllers are affected. Select "Actions" and add a new one. The screen shot below shows that "Retrieve Controller Logs" has been selected, and this will apply to "All Controllers" Depending on the number of controllers present on this site, it may be better to retrieve the logs from groups of controllers at a time. The screen shot below shows the configuration for controllers 1-20. Having created the action, a schedule must be added. If a number of schedules are created it is suggested that they are timed to run at least 15 minutes apart.

Issue Sigma Server failure Environment Sigma Site Cause Sigma has worked OK previously but now the Sigma server fails every time and quickly after starting. Resolution A new anti-virus definitions file has been downloaded either manually or automatically and has detected that a Sigma file may be suspect, this will normally be a fault of the definitions file. There will be a report in the Windows event viewer that Sigma services has failed. Anti-Virus software is often set to move suspect files into a "quarantined" directory.  There will be a log to show this. Check these for any Sigma files quarantined. Anti-Virus software can also be set to automatically delete suspect files.  There will be a log to show this. Check this for any Sigma files shown as deleted. 1. Disable the Anti-Virus software on either the whole of c:\sigma\data or c:\sigma\bin. Note: The site IT may need to be involved and approval may be required. 2. Either re-instate the files from the quarantined folder or re-install Sigma.

Issue What is the temperature reading range for the STP500? Environment All Continuum controllers STP500 range STX500 range STD500 range Cause Clarification on read range required. Resolution When connected to a Continuum controller the operating temperature range is: -30°F to +230°F, -34°C to +110°C For readings outside this range, an active sensor with a 4-20mA or 0-10V output should be used.

Issue Is the Niagara G3 Floating License Repository (FLR) available for purchase? The FLR is a licensed feature that runs as a service in a Niagara station to provide licenses to other Niagara Runtime Environment (NRE) applications. Available licenses are 'leased' by authorized NRE applications at startup and 'returned' when the application shuts down. Environment Niagara G3 (version 3.5 and higher) Cause Field question Resolution The FLR was introduced with version 3.5 and discontinued shortly thereafter by Tridium. It is no longer available for purchase.

Issue Are there any limits on the number of entries for Path Permissions? Environment AS ES Cause Documentation Resolution There are no hard limits on how many entries can be added in the software permissions, the limit is only determined by the availability of resources such as memory.

Issue What visual indication is present when I/O server is running? Environment I/NET I/O Server Windows operating systems Cause Use the Windows system tray to determine if I/NET's companion program, I/O Server is running. This must be running to facilitate communications. Resolution The I/NET host workstation needs to communicate with many external devices, including other host workstations, NPRs, Taps and controllers. I/NET uses a companion program, I/O Server, to facilitate efficient communication functions. I/O Server must be running for most I/NET communication functions to occur. Each time it is started, I/NET launches I/O Server, which runs in the background. By default, I/O Server continues to run as a background task even after I/NET is shut down. This enables your host software to continue to receive I/NET data even if the host software is not operating. Should you need to disable the I/O Server temporarily, you can shut it down manually. You can also instruct I/NET to shut down all I/NET-related background tasks automatically. When I/O Server is running, an icon is visible in the Windows system tray. The specific icon loaded will depend upon whether the workstation is directly connected to a Tap. Right-clicking on the icon allows you to manually shut down I/O Server or to start the configuration program.

Issue In XPSI 4.1 Terminal Mode, there is a noticeable delay in the action of the “Escape” key when backing out of a Current Status or VEO group display screen. Environment XPSI rev 4.1, Windows XP SP3, Windows Vista Pro, Network 8000 GCM, Network 8000 LCM Cause Serial communications are slower with the Microsoft port controls used with XPSI version 4.1. Resolution The “Escape” key will work, it just takes a few seconds longer in version 4.1 than it did in earlier versions, such as 3.13.

Issue Replacement stuffing boxes for V392 Environment V392 Spare stuffing boxes: DN15 type V: 0804343005 DN15 type X: 0804362005 (glycol) DN20-50 type T: 0802064005 DN20-50 type Q: 0804724005 (glycol) Cause Replacement parts for obsolete valve V392 Resolution Spare stuffing boxes for DN15 was withdrawn in 20101231. For DN20-50, they will be withdrawn in 20141231. Please contact your Orders Dept for more details and availability.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue SevenReports Error when attempting to open report directly from Windows Explorer or Graphics link Error received: Error in command line parameters: Report Type: 255 Duration: 255 Error Text: C:\INETSevenData\Reports\xxxxxxxx.rpt   The Icon for SevenReports is incorrect: Environment SevenReports Windows7 Cause File association has some how become corrupt or it has been associated with the SevenReport.exe file after installing the SetupCrystalReportsXI.exe. Resolution In most cases the file association will occur automatically and there is no need to manually do this.  Best practice is to restart the computer after installation, this should stop this error from occurring. Should this error still occur then this will require manually repairing the .rpt file association within the registry. Edit the following Registry keys so they appear as shown below: 1. HKEY_CURRENT_USERS\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.rpt If there is an additional sub-key (folder) under the .rpt entry called UserChoice; then delete this key. 2. HKEY_CURRENT_USERS\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.rpt\OpenWithList If there are any other entries here they should be removed and this entry must match exactly as shown in this screen. 3. HKEY_CURRENT_USERS\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.rpt\OpenWith\Progids 4. Close the registry editor and Windows Explorer (if opened) 5. Re-open Windows Explorer, browse to the INET Seven Reports folder (default "C:\INET Seven Data\Reports") and see that the ICON has changed back to the correct type and that double clicking on any of the reports now opens correctly.  If not please contact Product Support.

Issue When an alarm comes into Active Alarm View the wav file keeps playing after the alarm has been silenced. Environment Alarm Enrollment Event Notification Wave File Cause The wave file location has been moved. Alarm Enrollment or Event Notification wave file association has been lost. Resolution Re-point the Alarm Enrollment or Event Notification to the wave file and retest.