Building Automation Knowledge Base

Issue When tunneling through a UNC (R2) or ENC (G3) to an ASD bus with XPSI, set the baud rate to 1200 to eliminate communications timeout errors. Environment PSI/XPSI software, any version. I/A Series UNC (R2) or ENC(G3) with an ASD bus connected. All versions. Serial tunnel client, R2 or G3. Cause Delays introduced by the Internet between the PSI/XPSI computer and the remote tunnel client can result in communications timeout errors. Setting the PSI/XPSI baud rate = 1200 can help minimize or eliminate the effects of these delays. Resolution Set the baud rate of PSI/XPSI to 1200, per the TAC I/A Series Enhanced ASD Driver Engineering Guide, F-27429, Chapter 5, Table 5.1, "Site Setup Configuration", excerpt below:

Issue This tool will help calculate the required M&B conversion coefficient for a given analog value in I/NET. Product Line TAC INET Environment All I/NET Controllers I/NET Resident Point Editor Cause Need to calculate an I/NET Conversion Coefficient (M&B) for a special sensor Resolution Click here to download an Excel spreadsheet that has several functions for calculating the correct M&B.

Issue After replacing an older revision MNL controller with a new one, WorkPlace Tech is unable to download the existing application file into the new controller reporting an error "The selected device is Invensys IA(x) ... controller, the application requires Invensys IA(y) ... controller".  In this error message the controller type info (...) will be the same in both parts of the message but the IA(x) and IA(y) part of the message is different.  Environment MNL-50 MNL-100 MNL-110, MNL-130, MNL-150, MNL-200, MNL-Vx Cause Replacement controller is of the same type but of a different version. This issue occurs any time a version 2 controller is replaced with a version 3 controller. for example, this error will occur if a MNL-V2RV2 controller is replaced by the newer version, MNL-V2RV3.   Resolution Open application in the WorkPlace Tech Tool. Open the Hardware Wizard and click the [Back] button to open the Controller Selection page. When the Controller Selection page has been opened, you will note that the [Older] tab has been displayed with the existing controller type displayed. Select the tab corresponding to the controller type, for example if replacing a MNL-V2RV2 controller, select the MNL-VAV tab. Select the model of the replacement controller, for example when replacing a MNL-V2RV2, the replacement is the MN-V2 [MNL-V2RV3]. Click the [Next] button to complete the selection of the replacement controller type then click the [Finish] button to close the Hardware Wizard. Recompile the application and download it to the replacement controller. If the controller is part of a LON network that has been commissioned by a LON Network Management tool, it will be necessary to replace the existing device object and commission the new controller.

Issue After a CX99xx is updated for SNMP option enabled, the hyper terminal screen does not show the SNMP option setting button when the hyper terminal PC is indirectly connected to the target CX99xx via other local CX99xx. Environment NetController (CX9900, CX9940) Cause This issue happens when the hyper terminal PC is indirectly connected to the target CX99xx via other local CX99xx. Resolution After successful update the CX OS file for SNMP, connect the hyper terminal PC directly to the target CX99xx.

Issue Upgraded Site to Continuum 2.01, now get %N and %D in Alarm Message as seen in the message field in the snapshot below: Product Line Andover Continuum Environment Cyberstation Keywords %D %N Cause This is caused by the Enhanced Alarm Logging and Enhanced Alarm Delivery being unchecked Resolution This can be resolved by using the following steps: Close all the cyberstations Initialise the database making sure you have Enhanced Alarm Logging and Enhanced Alarm Delivery ticked as shown below:  

Issue If the result of a divide by zero is sent to a physical AO, Vista Workstation will display this value as -2. The physical output, however, will be sending out the maximum specified voltage (default 10V). In Menta simulation mode, if a divide by zero scenario is simulated, the following error will pop up: tam32 Division by zero Connected to a controller viewing live Menta, a divide by zero equation will result in a displayed value of 1.#QNAN. All subsequent equations using this value will also output 1.#QNAN. Environment Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta Cause Division by zero results in an invalid value that is interpreted differently by the controller's physical outputs, the Menta application, and the Vista Workstation. The application will continue to run, but any output affected by the invalid value will not act as expected. Division by zero is not usually intentional (there's no equation that says "A/0"). Instead, it is usually the result of an unforeseen sequence of events where complex equations result in a 0 in the denominator of an equation, and simulations did not ever produce this unique situation. Resolution To troubleshoot whether a divide by zero is occurring: The best solution is to connect live to the controller with a serial cable and watch the live Menta. Look for any values that read 1.#QNAN and trace it back to the source. If live Menta is no available, the simulation mode can be helpful. Recreate the scenario as best as possible with all inputs set to the real life instance. To prevent a divide by zero error: Never allow an equation to write to the denominator of a division equation without programming divide by zero prevention. Add an expression block prior to the division equation that says "if the value is zero, then output a safe value" Add a max block to the input that compares the value with 0.0001, so that a zero will never pass through.

Issue It may be useful to have logic in Menta programs trigger an event in Vista so that it can be recorded and stored in the event log. Environment Vista Workstation Menta Cause Alarms that have the Priority parameter set to 0 are used for info purposes only and only show in the event viewer and not the alarm viewer (queue). Resolution Events can be triggered by a Menta program by creating an Alarm block in Menta and setting the Priority parameter to zero. This causes the alarm to only function as an event and keeps it from showing up in the alarm queue. The following is taken from the Menta Technical Manual: The alarm priority is specified with the Priority parameter. There are 10 levels, 1 to 9 and 0, where 1 is the highest. Events with priority 0 (Information messages) have the lowest priority. They are not placed in the alarm database of TAC Vista and do not appear in the alarm overview. An example where using a priority zero alarm might be useful is to record as an event whenever an air handler enables and disables its economizer. This would be done as follows: 1. An ALARM block is created and named EVENTS\ECONOMIZER_ENBL. The Priority parameter is set to 0. Alarm Control is set to the standard alarm control object which is $Alr_Cntrl. The Tripped Alarm text is set as "ECONOMIZER ENABLED" and the Reset Alarm text is set as "ECONOMIZER DISABLED". 2. The ALARM block is then connected to the Economizer function. Now an event will be generated each time the economizer is enabled and disabled but an alarm will never pop up in the alarm viewer. An Events Viewer object could now be created to make it easier to view just economizer events without everything else. This is done as follows: In Vista Workstation right click the Root object and select New > Object > Viewer - Events. Type in a description and enter the Object ID of the economizer event that has been created. This can be found by locating an instance of the economizer event in the standard event viewer and copying the Object ID from there. The event viewer could be set up to display all priority 0 alarms instead of one specific event type by entering a 0 in Priorities in the Alarms section under the Event Specifics tab. The amount of time displayed in the event viewer can be filtered under the Date and Time tab. It may be useful to remove unneeded columns from the new event viewer so that only the relevant information will be displayed. In this example everything is unselected except Time, Object ID and Text under the Select Column(s) tab. The event viewer will automatically update and could be used for real-time monitoring of whatever event(s) it has been configured to display.

Issue Security Expert database size increasing rapidly and getting large. SecurityExpert Database size From the screen capture below, it can be seen that the Security Expert transaction log file SecurityExpert.ldf has increased to a large size. SecurityExpert database log file Product Line EcoStruxure Security Expert Environment Security Expert Microsoft SQL Server Cause The Recovery model of the Security Expert database is set to FULL and the database has not been maintained. When using the Full recovery model, regular backups of the transaction log should be performed to prevent the transaction log file size from growing out of proportion to the database size.   New user databases are created with the same recovery model as the model database. The default recovery model for the model database depends on the edition of SQL Server you have installed. Editions targeted at test and development environments (SQL Server Express) set the recovery model of the model database to SIMPLE. Other editions set the recovery model of the model database to FULL. Resolution For Security Expert, it is recommended that the Recovery model be set to the default of SIMPLE.   You can reduce the size of the logs and also prevent them from getting too large again by changing the recovery model of the database from FULL to SIMPLE. The databases are then shrunk to free up drive space.   Refer to the following steps: Take a backup of both the SecurityExpert and SecurityExpertEvents databases and store them in a safe location Change the Recovery Model of the SecurityExpert database from Full to Simple in SQL Server Management Studio. To do this, right click on the SecurityExpert database and go to its properties. Select 'Options'. Change the Recovery Model setting to Simple. Recovery Model Simple Right click on the SecurityExpert database and select Tasks > Shrink > Files Shrink In the Shrink File - Security Expert window, change the File type to Log. Shrink File Type Log Click OK Repeat steps 2-5 for the SecurityExpertEvents database   It is recommended that regular scheduled backups be configured when using the SIMPLE recovery model. In SIMPLE recovery mode, changes since the most recent backup are unprotected.

Issue BACnet controller objects that have not been overridden are displayed on I/A Series R2 graphic screens in the purple color as if they were overridden. Environment I/A Series R2 (Niagara) Graphic screens displaying values representing physical BACnet controller inputs. Cause Purple BACnet values (I/A Series R2 graphic override color) are internal BACnet points that can not be modified (display only).  This behavior is normal and began to appear in MNB controller firmware versions 1.2 and higher.  Per the BACnet specification, read-only type points must be set to indicate an override condition.  The root cause is a design change required by the BACnet specification to bring the controllers into compliance for BTL certification.  The ASHRAE BACnet Specification 135-2004 specifies that the "read-only" type objects (e.g. Analog Value, Binary Value, etc.) OVERRIDDEN flag is: Logical TRUE (1) if the point has been overridden by some mechanism local to the BACnet device.  In this context "overridden" is taken to mean that the Present Value property is not changeable through BACnet services. In this case, the override is meant to indicate to Niagara that the point is locally overridden (by the controller) and cannot be changed by the Niagara BACnet service (or user). Resolution There are several approaches that can be used to display these objects without the background showing the purple color. One approach is to use a native Niagara AI object to buffer the value where the override condition is not transferred.  In addition, if the BACnet points and Analog Input objects reside in a poll-on-demand container, the BACnet points will not be polled unless a gx type object is added and directly attached to the BACnet point.  The graphic page will have a gx type object linked to the Analog Input object (displaying the value without the override) and another gx type object (invisible) linked to the BACnet point to start the point polling. A second approach is to configure the GxText object so that the object property "statusColorEnabled" is false. 

Issue Requirement for a number of users to be able to access Security Expert using Web Client at the same time. Product Line EcoStruxure Security Expert Environment Security Expert Web Client Cause Unsure how many Web Client users are licensed with the standard license or how to add additional user licenses. Resolution Included with the base SX-SRVR license is an allowance for having three (3) concurrent Web Client operators.  Additional operator licenses (SX-WEB-OPR) must be purchased to allow Web Client logins beyond the licensed amount of three, purchase as many of these as is required.

Issue WorkPlace Tech 5.8.x, 5.9.x, 5.10.x, and 5.11.x Operating System and Microsoft Visio Compatibility Product Line TAC IA Series Environment WorkPlace Tech Tool Software release 5.8.x, 5.9.x, 5.10x, and 5.11.x Microsoft Windows and Microsoft Office Visio requirements, see the "Resolution" section, below. Visio 2010, 2013, 2016, 2019, 2021(.msi install)  Visio 2013, 2016, 2019, 2021 (subscription "Click to Run", Plan 2) Office 2010, 2013, 2016 (.msi install) Office 2013, 2016, 365 (subscription "Click to Run", Plan 2) Support for Workplace Tech 5.10 / previous and Workplace Tech Editor Note: Visio 2019 and Visio 2021 are not supported in 5.9.4 or EBO versions before EBO 2022.  Visio 2019 and Visio 2021 are supported when using Workplace Tech 5.10.x and EBO 2022. Cause What Microsoft Windows operating systems and what versions of Microsoft Visio are compatible with the WorkPlace Tech Tool version 5.8.x, 5.9.x, 5.10.x, and 5.11.x? Resolution Microsoft Windows WorkPlace Tech Tool releases 5.8 through 5.8.6 are certified to run on the following versions of Microsoft Windows: Microsoft Windows XP Professional with Service Pack 2 or Service Pack 3 Microsoft Windows Vista 32-bit Business, Ultimate or Enterprise Microsoft Windows 7 32-bit Professional Microsoft Windows 7 64-bit Professional WorkPlace Tech Tool release 5.8.7 is certified to run on the following versions of Microsoft Windows: Microsoft Windows 7 32-bit Professional Microsoft Windows 7 64-bit Professional Microsoft Windows 8.1 32-bit Pro or Enterprise Microsoft Windows 8.1 64-bit Pro or Enterprise Microsoft Windows Server 2012 64-bit WorkPlace Tech Tool releases 5.9.1 to 5.9.4 are certified to run on the following versions of Microsoft Windows: Microsoft Windows 7   32-bit Professional Microsoft Windows 7   64-bit Professional Microsoft Windows 8.1   32-bit Pro or Enterprise Microsoft Windows 8.1   64-bit Pro or Enterprise Microsoft Windows 10    32-bit Professional Microsoft Windows 10    64-bit Professional Microsoft Windows Server 2012   64-bit WorkPlace Tech Tool release 5.10.0 to 5.10.x is certified to run on the same as WorkPlace Tech 5.9.x and the following versions of Microsoft Windows: Microsoft Windows Server 2016 64-bit Microsoft Windows Server 2019 64-bit Microsoft Windows Server 2022 64-bit Microsoft Windows 11 Professional (Workplace Tech 5.10.4 only) WorkPlace Tech Tool release 5.11.0 is certified to run on the following versions of Microsoft Windows: Microsoft Windows 10 64-bit Professional Microsoft Windows Server 2022 64-bit Microsoft Windows 11 Professional Microsoft Visio Microsoft Windows 7 32-bit Professional Microsoft Windows 7 64-bit Professional Microsoft Windows 8 32-bit Pro or Enterprise Microsoft Windows 8 64-bit Pro or Enterprise Microsoft Windows 8.1 32-bit Pro or Enterprise Microsoft Windows 8.1 64-bit Pro or Enterprise Microsoft Windows Server 2012 64-bit WorkPlace Tech Tool releases 5.8 through 5.8.6 require one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2003 with Service Pack 3 (officially supported for WPT 5.8.0, WPT 5.8.1, no known issues with WPT 5.8.2 through 5.8.5) Microsoft Office Visio 2007 with Service Pack 1 or Service Pack 2 Microsoft Office Visio 2010 with or without Service Pack 1 NOTE: Standard or Professional edition of Microsoft Visio may be used. WorkPlace Tech Tool release 5.8.7 requires one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2007 with Service Pack 3 Microsoft Office Visio 2010 with Service Pack 2 NOTE: Standard or Professional edition of Microsoft Visio may be used. WorkPlace Tech Tool release 5.9.1 through 5.9.4 requires one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2010 with Service Pack 2 Microsoft Office Visio 2013 with Service Pack 1 Microsoft Office Visio 2016 NOTE: Standard or Professional edition of Microsoft Visio may be used. WorkPlace Tech Tool releases 5.10.0 through 5.10.x requires one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2016 Microsoft Office Visio 2019 Microsoft Office Visio 2021 Microsoft Office Visio Office 365 Subscription Plans 2 WorkPlace Tech Tool releases 5.11.x requires one of the following versions of Microsoft Visio (64-bit version ONLY) Microsoft Office Visio 2019 64-bit Microsoft Office Visio 2021 64-bit Microsoft Office Visio Office 365 Subscription 64-bit Plans 2 Warning: WorkPlace Tech 5.11 is not compatible with EBO WorkPlace Tech Editor. Do not install WP Tech 5.11 on a PC that has EBO WorkPlace Tech Editor installed. Continue to use WP Tech 5.10 on PCs where EBO WorkPlace Tech Editor is required.   Note: Workplace Tech Tool 5.10.0 and later releases require .NET Framework 4.8 to support Open LDV 5.1 which is included in the installer.  .NET Framework 3.5 Sp1 is no longer required.   Follow the instructions in the article link for the security updates required. Workplace Tech 5.10.x and previous / Workplace Tech Editor (EBO) Microsoft Security Updates required for Visio and Office For the Visio requirements for earlier versions of the WorkPlace Tech Tool software, see What versions of Visio are required for WorkPlace Tech?.

Issue How can a communication heartbeat time be detected in Menta? Can you detect if a value has not changed for more then a specified time period? Environment Menta Cause There are multiple methods to detect a timeout scenario and which method to use will likely depend on the specific criteria of your application. The included examples are intended to indicate some of the options available that can be built upon to customize your application. Resolution These methods can be used to detect if another device has stopped communicating or if another portion of your process logic is stuck. Timeout Simple (Click image for AUT file) This macro block will output a value of one when the input value has not changed for the DelayOn time period and you do not require the previous value for processing. Timeout Complex (Click image for AUT file) This macro block will preserve the last value for use in your process logic if that is necessary.

Issue Getting the error message “Can not access controller” when downloading to an MNB-300 controller with WorkPlace Tech 5.7.7. Environment WorkPlace Tech 5.7.7 Cause Corrupt database Resolution   Use backup copy of application or create a new application.

Issue If a database is downloaded to the controller after the box has been balance will it lose the balance data? Product Line TAC IA Series Environment All versions of MNB VAV controllers MNB-V1 MNB-V2 Cause In MNB VAV controllers the flow balance data is preserved in a different area of EEPROM than the application data. Resolution Balance data in an MNB VAV controller is not affected by the downloading of its database.

Issue Niagara R2 is installed on a computer but the HostId is not known.  Aside from viewing the details of the license.properties file, how can the HostId be determined? Environment Niagara R2 Cause No access to the license.properties file Resolution Open the Niagara Console (located in the Program Group), and type the following: nre -hostid This will display the HostId to the screen (see the screenshot below) The  nre command can also display other information.  The screenshot below shows the other options.

Issue Running an ActivityEvent ListView with filter longer than one week (example - One MonthToNow).  Listview returns 13621 events. When trying to page down the list,  CyberStation locks up. There are 3 popup windows that occur in this order: Error: Continuum has detected an internal error. If you continue experiencing problem, it is recommended that you shutdown and restart Continuum. Reason Code: 4 ListView: It is illegal to call out while inside message filter. CONTIN~1: The RPC Server is unavailable. At this point CyberStation must be shut down via ContinuumProcesses.exe and then restarted. Environment CyberStation v. 1.81 Windows XP   Cause RPC error occurs and CyberStation locks up when running a large listview. Resolution Increase Windows virtual memory for the workstation from the default value (set by Windows) to a custom size. The "Initial Size (MB)" should be set to a minimum of 1000MB (per the CyberStation Installation Guide). For fastest performance do not set the Maximum Size (MB) to more than the amount of RAM. This will avoid using the hard disk for the virtual memory and RAM is faster than disk drives. If necessary to run the task, increase this setting beyond the amount of RAM. To change the virtual memory settings open Control Panel. Then System>>Advanced tab>>Performance Settings>>Advanced tab>> Virtual Memory Change.

Issue When trying to log into Workstation you get "Access is denied". Environment Vista Workstation Windows 10 (not supported) Cause First verify that the licensing is installed and working properly on the machine. If running Vista on a Windows 10 machine and the message "Access is denied" still appears when logging in to Workstation then there may have been Windows updates applied to the PC causing the issue. Microsoft has identified an issue with their updates and have plans to correct them in future updates.  Note: Windows 10 is not a supported operating system for TAC Vista.  Resolution If using Windows 10 with TAC Vista, then check to make sure that the following updates have not been installed (updates depend on the Windows 10 build being used).  If one of these builds have been identified then remove the Windows Update and restart the PC. After the reboot, the operator should now be able to log in to Workstation.   Windows 10 1709: KB4056892 Windows 10 1703: KB4056891 Windows 10 1607: KB4056890 Windows 10 1511: KB4056888 Windows 10 1507: KB4056893   Note: There has been a couple of instances where the Windows Upload and blocked access on a Window 8 PC as well.  If the same error is seen in Windows 8 then check for recent Windows updates. Click Here if you are having issues with the updates coming back.

Issue Do Xenta controllers support PT100/PT1000 sensors for measuring the temperature? Environment Xenta Controller TAC Menta PT100/PT1000 Temperature sensors Cause Requirement to measure the temperature using PT100/PT1000 Temperature sensors. Resolution PT100/PT1000 sensors are not supported within any of the Xenta controllers.  The following is a method to achieve this using Menta: When using PT100/PT1000 to connect to a thermistor input, Menta Logic is required to add a polynom using the expression block. It is also strongly recommended to implement some calibration software in Menta to allow for fluctuations in resistance for every input that PT100/PT1000 is connected to. If a sensor is replaced / changed, re-calibration will be required. Sample experiment results and Menta Logic's are available here.

Issue Locating the IC3-Modbus documentation Environment Sigma IC3 Modbus Documentation Cause Unable to locate documentation. Resolution To download the IC3-Modbus Gateway.txt file click HERE. To download the IC3 configuration guide click HERE. To download the IC3 data sheet click HERE.

Issue Is it possible to run TAC Vista 5.X.X in Windows XP compatibility mode (When TAC Vista Installed on Windows Vista, Windows 7, Server 2003/2008) Product Line TAC Vista Environment TAC Vista 5.X.X Windows XP Windows Vista Windows 7 Windows Server 2003/2008 Cause If TAC Vista 5.x.x is Installed on Windows 7, Windows Vista, or Windows Server 2003/2008, is it possible to run the Vista Workstation on Windows XP using Compatibility mode. Resolution TAC Vista has several other applications that work together with Vista. These applications do not support compatibility mode. Upgrade to Vista 5.1.4 or later which support Windows 7. If the operating system is a 64-bit version, upgrade to Vista 5.1.5 or later. For the compatibility matrix see Software and Firmware compatibility matrix for older versions of the traditional product lines.