Building Automation Knowledge Base

Issue Upgraded to I/A Series G3 version 3.6.305 and now unable to successfully commission an MNL-800 controller.  Previous versions of G3 commission the same controller without issue. Environment I/A Series G3 LonWorks module version 3.6.305 Cause Issue with how the LonWorks module commissions a host-based controller. Resolution Upgrade the LonWorks module used by the I/A Series G3 station. The LonWorks 3.6.406 module can be downloaded from The Exchange Download Center.

Issue As part of a site power feed problem investigation where varistors are being blown, how are they connected to the power feed? Environment i2920, b3920, b4920. Cause When a site is experiencing power problems and the mains input varistors blow, it is required to know how the damaged varistor is connected. Resolution The 3 varistors are connected between: Live and Earth, Neutral and Earth, Live and Neutral. The attached sketch shows how  the 3 varistors are connected. The connections are the same for the i2920 and b4920.

Issue Problems adding i2 or b3 controllers to systems and causing the network to go down or devices to not learn on. Product Line Andover Continuum Environment i2 Controller b3 Controller Cause Duplicate ID's,  incorrect baud rates or faulty controller Resolution Infinet and BACnet field controllers have the capability to autobaud and auto correct duplicate ID's on a network. They do this by listening to the network on powerup and determining what Baud Rate and currently operating controller ID's are on the network. If an existing controller is on the network and the newly added controller has the same ID assigned, the new controller will zero out its own ID so as not to cause a network problem with duplicate ID's. Then learning or manually commissioning the controller will give it a unique ID. It is therefore critical that when adding a controller to a network, that the controller is connected to the network before the controller is powered up.  Failure to do so could cause network problems such as duplicate ID's or conflicting baud rates which could bring the network down. If the new controller causes these types of problems it is recommended to power down the suspect controller(s) and re-power them to eliminate these issues.  Run acctrace when the learn is being done and there will be an indication of what is happening.  Send a controller error log to PSS.   If nothing else works even with a clean database then replace the Master and if that works send the controller in to repair.

Issue Error "Continuum is already running" while trying to start Continuum. Environment Continuum 1.91 Windows XPsp3 Cause Continuum was not gracefully shut down, which left some services running. Resolution Reboot PC which will terminate all services or use Continuumprocesses.exe in the Continuum folder If this is an upgrade ensure that the database has been updated prior to starting Cyber with the transferred database Make sure the Workstation initialization was completed prior to starting Cyber.

Issue 7771 (Modbus ICI) will not keep station address after station restore. Environment I/NET Seven 7771 (Modbus ICI) Cause The cause is the EEPROM rev in that unit. Resolution Update EEPROM to version 3.32 to work correctly in I/NET Seven.

Issue Require a Lua script for using DIM modules Environment SmartStruxure Lite Cause Using a Digital Input Module and Lua script is required to view the Inputs. Resolution For Sontay's DIM4 module download the script here. For Sontay's DIM6 module download the script here. For AXIO's DIM module download the script here. For a generic DIM module download the script here. The voltage received at the AI may need tuning. Copy and paste the text into a Lua program and create the Binary Values (BV).

Issue When attempting to perform maximum or minimum Flow Balance on a MNB-V1 controller, ;an error appears: "Invalid flow setpoint values. To balance the selected flow setpoints...." Product Line TAC IA Series Environment MNB-V1 Controller Cause The MNB-V1 is a cooling only controller and does not have the Reheat properly disabled. Resolution Check the date code of the MNB-V1 controller. If it is between 0902 and 0913 see TPA-RKFD-09-0007.01 on The Exchange Download Center for details. If it is outside that date code range contact Product Support Services for assistance.

Issue TGML Graphic Alert: ReferenceError: "test" is not defined. (cmd#16) Product Line TAC Vista Environment Vista 5 TGML Graphic Cause A Javascript tag in the TGML has used a variable that has not been defined. Resolution Determine which script tag is generating the error. When did the error occur? When the page loaded?  When a value changed?  When the user clicked?  Did it happen once or multiple times?  These questions can help you narrow down which script has thrown the error. Save the graphic under a different name.  Delete portions of the graphic until the error clears.  The component that was removed holds the offending script. The cmd# syntax is indicating which line of the script has the error.  Launch the script editor by clicking the "..." button next to the script Content attribute.  In this example, go to line 16 of the code. The variable name is in quotes.  In this example, find where a variable named "test" was used. Verify that the variable has been declared and defined prior to being used. Also check out the JavaScript Essentials - Programs and Statements Quick-Help video on the Exchange.

Issue The STR-150 Wall Module with Display is not compatible with Xenta 100 controllers that are earlier than SW-version 1.2. The space temperature (nvoSpaceTemp) is displaying an invalid or default value (either 621.81 degrees Fahrenheit or 327.67 degrees Celsius). In newer versions of Vista the value will display "Invalid Value". Product Line TAC Vista Environment STR-150 Xenta 101-VF Xenta 102-ES Xenta 103-A Xenta 104-A Cause Software for Xenta 100 series controllers previous to version 1.2 is not compatible the STR-150 wall module. Resolution The STR-150 is only compatible with Xenta 100 series controllers that are software version 1.2 or later. If a wall module with display is required for a Xenta 100 controller with software that is older than version 1.2 there are two possible solutions: An identical Xenta controller can be purchased with the latest software version to replace the old controller. An STR-350 stat can be used and connected to the Xenta controller via SNVT bindings.

Issue What is LANMon and how do I use it? Product Line TAC INET Environment I/NET Controller LAN 78010 Model TAP Cause Further analysis is required to establish physical layer (LAN) issues, which may include some of the following: Abnormally large number of LAN Reconfigure messages Controllers going offline individually or in groups and sometimes all together Large numbers of Station Lost/Restore Messages Frequent problems connecting to controllers and data interruption It is strongly recommended that you look at these issues prior to using LANMon.  Refer to I/NET Physical Layer Issues for rectification and recommendations of these Physical Layer Issues. Another form of analysis is to look at your Processor and LAN loading for each of your controller LAN devices.  Refer to I/NET Configuration Status parameters: Processor Loading and LAN Loading (Percentages (%)) for further information on this. Resolution LANMon 3.0 is a utility program used to perform communications capture and analysis functions on the I/NET controller network. The LANMon utility consists of a firmware program which is executed on a 78010 Tap and a .EXE program which is run on a PC. The Tap running the LANMon firmware connects to the RS485 I/NET controller LAN and listens to the communications traffic on the LAN. The Tap receives and translates the communications to a continuous ASCII stream of data which it sends to the LANMon PC using the RS232 channel. Download TCON301 which describes the installation, configuration and operation of LANMon. Click here to download the LANMon application. EPROM is available through either your logistic channels (Australia Only) or alternatively refer to Using the LANMON 3 tool with a 78010 TAP with a MIP01 board attached on how to use a MIP01 to achieve the same function. After capturing your LANMon files, you can then send your captured files to Product Support for further analysis if required or use Decoding LANMON 3 errors to assist in decoding the capture. Below is an image showing the basic LANMon equipment:

Issue An I/A Series R2 (Niagara) station opened in the Admin Tool displays "Disabled." What does this error message mean? Product Line TAC IA Series Environment An I/A Series R2 (Niagara) UNC. Cause When a station is in the disabled mode, it indicates that the station has rebooted multiple times in a five minute period. Possible causes are rapid fluctuations in the AC power supplying the UNC, a bad battery, or a station with less than 20% idle time. Resolution Disconnect the battery, then cycle power to the UNC and see if it boots up normally. Run the system spy: in a browser, enter  http:// (ipaddress of UNC):3011/system/spy. Login with the hardware user name and password. At the bottom of the page, click on "Reset Counter", then check to see if the idle time exceeds 20%. If not, the station will need to be tuned to increase the idle time. Check battery per Niagara R2/G3 UNC/JACE reboots every 15 minutes with "Battery test failed" logged. See Batteries for the UNC-410 and UNC-520 are interchangeable for battery part numbers.

Issue Xenta Server Log Error contains the error line: Generic OS: Too Many Semaphores. 5326 02-Dec-2011 12:47:33 AM fatal  undef  httpdd           1      Generic OS: Too many semaphores.   (Error#:8202) Environment Xenta Server System Error Log Xenta 701, 711, 721, 731 Cause An Application in Xenta 700 consumes too many internal semaphores which cause a fatal error resulting in repeated coldstarts. Resolution Corrected in release 5.1.0 and documented on page 6 of TPA-MALR-08-0009.00. Upgrade to Vista version >5.1.0.

Issue Cannot register LonMaker plugins Product Line TAC Vista Environment LNS, LonMaker, NL220 Cause If you are having difficulty registering plug ins in LonMaker then you may have corrupted LNS credits. Resolution To check your LNS credit status, run the LNS Server License Wizard which is found at C:\LonWorks\bin\LnsLic.exe If you run the wizard and it displays the Max Credits at zero and Credits Available as zero as well, then your LNS credits have become corrupted. To correct this, select Next in the Wizard so that it displays the PC Key. The wizard provides a button titled "Copy to Clipboard" which when selected will allow you to paste a form letter into an email or text editor. After filling your specific contact information you will want to check the "No Charge" box and the "Replacement Use" box. Before you send the form via fax or email, you also need to provide evidence that your LNS credits have been corrupted. Select Start > Run > and type "cmd" to reach a command prompt. This command will check the status of the LNS credits: checklic nsseng.exe The output of this command should either be printed and sent with the fax or included in the email to the address or phone number shown at the top of the form letter. You should then receive instructions or an application key to correct the problem.

Issue BACnet Programs Disable on a Reload This is an issue that will be addressed, but in the meantime an explanation of how this happens and a workaround is provided below. Environment Infinity Program in a Continuum Bacnet controller Cause How this happens: Create an Infinity Program in a Continuum Bacnet controller and then right click on the folder directory located under the controller you just created it under on the Infinity side. Now make sure there are two columns in the listview named State. You will most likely have to add one or both of these columns and make one of the columns source LIVE and the others source Database Notice when you run the listview both State columns will reflect Enabled for your running program. Now, perform a find new bacnet devices if you haven't already and then perform a send to database on the controller you just created the Infinity Program under. At this point go back and either run or refresh your listview we ran earlier and notice the Infinity Programs State attribute is set to disabled in the database view. At this point if you reload your controller in the Infinity side it will disable the program. Resolution Workaround on how to avoid this issue After a newly created program has been sent to the database on the Bacnet side, immediately run the listview we created earlier and Highlight either all or only the programs that are set to disable for the State attribute where the source is set to Database. Once you have selected the rows of the programs you want to set to enable, select the Edit menu item in the listview. Now select set attributes.. and in the drop down select State for the name and enter Enabled for the value and select OK. This will allow the program's to be reloaded without being disabled.  Most sites will never see this issue, since most will load up their controllers and back up the flash on the controller before performing a find new bacnet devices and send to DB on the bacnet side After controllers repower or reset the programs are just loaded back from flash. But the sites that reload their controllers will see the reload and programs disable issue. But like any reloading, you should always check your programs and alarms before leaving the site.

Issue Renaming a Vista Server. Product Line TAC Vista Environment Vista Server Cause The Vista Server name will default to the PC name where the database is created. To rename the server to any desired name of fewer than 40 characters. This can be customer-appropriate or more generic than an individual's PC name; follow the steps below. Resolution Shut down Vista Server Open Vista Server setup and navigate to the Vista Database tab. Enter the desired server name in the text field "Rename Vista Server to"   Click OK Restart Vista Server.  Within a few seconds, the server's name shown at the top of the window will be updated to reflect the new name.  It will also show up in the folder view of the Vista Workstation. Note: Changing the Vista Server name after graphics have been created and bound will break the binding path for all points.  To fix up the binding paths for all graphics at once, use Change References, as shown in Change all bind paths for all bindings on a TGML or OGC graphic at once.

Issue How to configure Xenta 913 to talk to C-Bus devices Environment Xenta 913 C-Bus Cause C-Bus is a public protocol which is commonly used in lighting control. Xenta 913 can be configured to talk to C-Bus devices with proper settings. Resolution A. Device Preparation C-bus 5500PC (PC Interface) RS-232 port        Xenta 913 RS-232A port NOTE: Communication is between Xenta913’s RS-232A port (NOT RS-485A port) and 5500PC’s RS-232 port (NOT C-Bus port).   Communication Cable Xenta913   C-Bus 5500PC, PC Interface RS-232A    <---------------------> RS-232 3(TX) <---------------------> 5(RX) 4(RX) <---------------------> 6(TX) 5(COM) <---------------------> 4(COM) Above number are RJ45 jack (as shown below) pin numbers.   B. Configuration Configure C-Bus device with CBusToolkit. Make sure to write down the Application number and the device’s Group number which Xenta 913 needs to communicate with.   Configure Xenta 913 in Xbuilder. Set Application number to 38 (38 is the HEX value of 56).   In DeviceEditor   The Group number (Hex value) needs to be inputted. Such as ‘01’ in the figure below. Same Group number can be inputted in different lines; however the ‘IO’ type should not be the same, such as ‘R’ and ‘W’ in below figure. ON Only and OFF Only types are NOT applicable to read-only values.   C. Verification In Xbuilder, drag all C-Bus points onto Value page. Download Xbuilder project into Xenta 913. Login Xenta 913 webpage and check if all point are correct and can be modified.   D. Additional Information Since CBusToolkit communicates with 5500PC by 5500PC’s RS-232 port, and Xenta 913 also communicates with 5500PC by 5500PC’s RS-232 port. Therefore, Only ONE device can be connected to 5500PC’s RS-232 port for CBusToolkit and Xenta 913.

Issue Instructions are required, on how to set up and troubleshoot a Contact ID Reporting Service. Product Line EcoStruxure Security Expert Environment Security Expert Client SP-C-WEB Contact ID Reporting Service Cause Basic information on configuring reporting services is documented in the Security Expert Operator Manual and SP-C-WEB Programming Reference but these do not contain practical steps on configuring this specifically for Contact ID reporting. Resolution The Contact ID Service is used to send Alarms, Tests, and Events using Contact ID reporting to a 3rd Party monitoring station capable of receiving the Contact ID format.   The following steps can be used to configure a basic setup of Contact ID. Note that a modem will be required and modem events can be logged in the events window for troubleshooting.   1. Go to Programming | Phone Numbers. Add your phone numbers, usually primary and backup.   2. Go to Programming | Services. Add a new service, set Service Type to ContactID. Set Service Mode to 1 - Start With controller OS. 3. Set the Client code and select the previously created phone number 4. Select required report options. Log Modem Events to Event Buffer option will log all events. Only use this for troubleshooting.   5. Go to Programming | Areas and assign the Service to required Areas 6. Go back to Programming | Services.  Right-click the Service record, and select Start Service. Without doing this the service will not be running. It needs to be manually started the first time. Check the controller Health Status to see the status of your service if it is started or stopped. When done configuring your Services, Inputs, and Areas. Select Reports | Central Station Report. Select the Reporting Service and the output directory to generate the file. Click Generate and a CSV and HTML file will be generated. This report can be provided to the central station for their database. The HTML version is the easiest to read.   Further details on the Contact ID reporting format and outlines of the reporting and mapping options can be found in the AN 316 Security Expert - Contact ID Reporting in Security Expert and SP-CWEB - Integration Guide application note.   For Details of creating Test Reports for Reporting Services see KB Article : Creating a Trouble Input for Periodic Testing of a Reporting Service such as Contact ID

Issue I searched the Publication Zone with key word "VAV" and only found manuals for the LON controllers. Environment I/A Series BACnet Cause The Users Guide for the BACnet Flow Balance program is Workplace Commissioning Tool and Flow Balance Tool Users Guide.  Since it does not have VAV in the title the Publication Zone search did not find it. Resolution The BACnet Flow Balance manual is part of the Workplace Commissioning Tool and Flow Balance Tool Users Guide (F-27357).  It is installed with the WorkPlace Tech software and can be viewed from the Help menu or it can be found in the Publication Zone by searching with the "F" number.

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 for assistance. Issue SP-C has a valid gateway specified and it's not receiving communications Product Line EcoStruxure Security Expert Environment Security Expert Controller firmware .1248 (or higher) Security Expert 4.0.128 (or higher) Security Expert Controller w/ USB port 2.08.582 (or higher) SX-ELV-HLI-TK license to enable the integration USB to Ethernet adaptor dongle TKE Controller (American) v2r0 (only supported version) Cause It is a known issue. SP-C sends a heartbeat message to TKE but it is not being sent/received as a broadcast message. The controller still sends a heartbeat message to TKE but it is not sending it as a broadcast message with a destination of FF:FF:FF:FF:FF:FF. The gateway being valid causes it to send a Unicast message to the gateway itself (eg router) which does not pass it on to the rest of the network. (This is a known issue and has been logged with engineers). Resolution The workaround is to enable the USB Eth NIC on the SP-C and use: - The onboard NIC to connect to the Security Expert Server that requires a valid gateway to be set - The USB to ethernet adaptor (USB NIC) to connect to the TKE Network where we would set any gateway to avoid this bug Note: The USB NIC can only be configured when using OTIS elevator HLI type. The USB NIC hardcodes the required OTIS IP info to the Onboard NIC for connection to Security Expert. To enable Web UI: 1. In Security Expert, Go to Sites|Controllers|Configuration Tab. 2. Scroll down and expand the Elevator HLI section. Set Elevator HLI type to choose OTIS 3. Return to the General Tab, Scroll down and expand the Commands section and enter OTISUseUSBForMainComms = true 4. Save changes and wait for the programming to be downloaded. 5. Power cycle the SP-C. 6. Go to SP-C Web UI. The USB Eth adaptor will have the original IP. Configure both IP adresses 7. Once The NICs are configured, change the Elevator HLI type back to Thyssen Krupp, choose Cable Network type 8. Click Save and restart the SP-C.

Issue There are many BCX1 on the site. All of the BCX1s go offline when reloading the controller. Environment BCX1-CR B3 Continuum Cause Checking the system configuration and programming. The reasons listed below may cause significant traffic on the network. A lot of Polling value of points across controllers COV increment is set to zero Check all the numeric points' setpoint attribute including Runtime, DamperPosition, etc. as these change all the time. Points under b3 controllers are referenced by more than 32 devices. Device in the BACnet Device folder doesn't match the controller in infinity side.(Not deleted device from BACnet folder after replace the controller) When the special trunk with low quality cable  connect to BLink also cause this issue. Remove the problem trunk, the issue will be  gone When the heavy traffic happens on the network or some other issues , it will cause unexpected issues. Resolution Change the programs way, create a program in the BCX1 to mirror the referenced points in b3s Uncheck the setpoint attribute of all numerics except  temperature setpoint. Change the polling program flow type from looping to fall thru and trigger every minute or trigger by other digital point. Set the COV increments to a non-zero value After device replacement, delete the device from BACnet Device folder and find new BACnet device again, then send to database Remove the problem trunk from Blink or try to change the terminal resistor will  resolve this issue  After the steps above are done, the network should be stable and the BCX1 will no longer go offline when reloading.