Building Automation Knowledge Base

Issue The Save to Flash exclamation point (bang) on a Controller object, does not go away even after a valid save to flash is performed on the controller. Product Line Andover Continuum Environment Continuum Controllers Cause An InfinityNumeric with its Setpoint attribute set is changing value frequently. With this Setpoint attribute set, every time the object changes value, the controller sees that the change needs to be applied to the flash as well. This changes the ObjectStatus of the Controller Device object to indicate a Save To Flash is required by  showing the exclamation point (bang) on the controller. Resolution Check if you have any InfinityNumeric points with the "Setpoint" flag set that update frequently. In ContinuumExplorer, under the controller object, right-click the InfinityNumeric default class folder and select "View". This will launch the object class listview for this controller. Add the Setpoint attribute by selecting View -> List View Configuration. Select columns tab, click "Add Column". Select the Attribute field in your new column and from the drop down select "Setpoint". Apply your Changes and refresh the ListView. The InfinityNumerics that have the Setpoint value of True are the ones you want to look at closely to determine which ones are changing value frequently and if they really need to be configured as a Setpoint.  Also, refer to Save to Flash exclamation point indicates that the controller 'requires flash backup'.

Issue View the current firmware version on a Xenta controller using the RS-232 cable Product Line TAC Vista Environment Vista 5.1.X Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B, 901 Cause While it is the best practice to match all of the firmware versions in your controllers, this is a quick and easy way to view the current version installed on your hardware.  Resolution Connect the RS-232 programming cable to your controller and your PC Open TAC Tools 5.1.X Open Download Wizard Click next Click the information button located directly above the help button For more information on how to update the firmware (.MOT file) on a Xenta controller, see Download an .MOT file into a Xenta Programmable controller. For more information on Menta Cable needed to download, see Schematic for the RS-232 cable used to direct download Menta applications and system files.

Issue Continuum reports an Unknown Model Number error. Product Line Andover Continuum Environment Controller Model number Bootloader Learn Cause Possible reasons why Continuum may report an Unknown Model Number error. Controller is in bootloader mode. Controller is not responding fast enough due to a comm issue. The controller type saved in the Continuum database is different from the controller type physically installed. The total number of controllers exceeds the maximum number of nodes allowed on the Master. The baud rate of the bLink is not correctly set for the MSTP bus. The comm bus is not stable. Problems introduced to the bus due to a bad controller or electrical interference. Resolution Communication issue must be troubleshot by using a combination of Controller error logs and LAN capture analysis. A controller can be brought out of bootloader mode by flashing the firmware.  Create the device manually. Attempt to learn the controller onto the bus with no other controllers attached Correct misaligned baud rate settings. Run an ACCTrace at the Workstation during a learn to detect duplicate IDs. Other articles that address this issue: Unknown model number error when learning I2/b3 device Learn Process stopped and get an error "Can not learn this controller, it contains an unknown model number"

Issue When adding Shadow Schedule in AS, it isn't synchronized with the Lead Schedule in ES. This issue only happens when  there is an Exception schedule assigned with another Calendar added to the Lead Schedule in ES. Error: "cannot verify lead object status" Product Line EcoStruxure Building Operation Environment SmartStruxure Lead and Shadow Cause If a Lead Schedule contains an Exception with another Calendar assigned in ES, and a Shadow Schedule needs to be pointed to this Lead Schedule in AS, both the Shadow Calendar and Shadow Schedule need to be created and pointed to corresponding Lead Calendar and Lead Schedule. If only Shadow Schedule is created, it will fail to update to Lead Schedule, or even wipe the original setting with a blank schedule. When involving Calendars the following should be considered: The only way that the lead and shadow relationship can be maintained where calendars are concerned is where the calendar has the same name and is at THE SAME RELATIVE PATH as it does with respect to the lead schedule. Consider the following examples: Example 1 - Lead Schedule is at Root and Shadow Schedule is at root and Referenced Calendar is at root. - under these conditions there is only a need for one Calendar object. The Lead Schedule has an exception that references the calendar at the root and everything works great. Example 2 - Lead Schedule and Referenced Calendar are in Folder 1 and Shadow Schedule is in Folder 2. This will not work because the Shadow Schedule is trying to reference a calendar at the same relative path, i.e., in Folder 2, and there is none there. Example 3 - Lead Schedule and LEAD Referenced Calendar are in Folder 1 and Shadow Schedule AND SHADOW CALENDAR are in Folder 2. This will work fine. In simple terms keep the names and paths within the ES and AS consistent (the same) to avoid issues. Resolution Before the steps below, ensure the communication between AS and ES is OK. Refer to Binding between ES and AS or two AS shows Unresolved and Shadow Schedule in the Automation Server is not syncing to the Lead Schedule in the Enterprise Server. If the communication is fine, continue to the following steps: Create Lead Calendar and Lead Schedule in ES, and assign the Lead Calendar to the Exception of Lead Schedule (Should already done before). Create Shadow Calendar and Shadow Schedule in AS, and point them to corresponding Lead Calendar and Lead Schedule in ES. Now the Shadow Calendar should be able to synchronized with the Lead Calendar after changes have been made to the Lead Schedule.

Issue When updating the Vista database in the TAC Vista System Pug-In an error message is displayed that says "Could not connect to Vista Server. Unable to request license." Product Line TAC Vista Environment TAC Vista System Plug-In Cause This error message is a result of not having the Vista Workstation license in the permanent license file. The licensing for the TAC Vista System Plug-In is included with the Workstation license. Resolution The license for Vista Workstation must be purchased in order for the system plug-in to work. For more information about the license packages see Vista 5.1 License Packages. 

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 After an uninstall of I/NET Seven and MS SQL, you might verify in the Windows Registry that all the items were deleted. Having issues installing I/NET what can I look for. Product Line TAC INET Environment I/NET all 2.4X versions Cause In some cases when re-installing, installing I/NET after a failed attempt or upgrading I/NET you may want to start fresh. After an uninstall of INET Seven and MSDE if items remain in the registry they will cause issues with future installations. Resolution Go to the bottom Task Bar and choose the “Start” button. Select the “Run” option and enter “Regedit” Once in the Windows registry go to “HKEY_CURRENT_USER, if the “CSI” entry is present delete this entry While still in the HKEY_CURRENT_USER look in the Microsoft File Folder for any “SQL” entries and remove them if they are present. Minimize the HKEY_CURRENT_USER folder and open up the HKEY_LOCAL_MACHINE File Folder, if the “CSI” entry is present delete this entry. While still in the HKEY_LOCAL_MACHINE, go to the Microsoft File Folder and look for any “SQL” entries. If you find any delete then from this file folder. Caution:  Before editing the SQL registry items you should ensure that no other software using SQL is still installed - all software that is installed should be uninstalled prior to modifying any registry entries. See also, MSDE and Windows 7.

Issue What badging or card creation software solutions do we support with Continuum? Product Line Andover Continuum Environment Continuum Access Control Cause Want to use a third-party badging or card creation system to create badges for a Continuum Access Control system. Resolution The only badging software that we support is EpiBuilder through the -B badging package we offer for Continuum Cyberstations. See the "Badge Manager" help topic in the Continuum on-line help for more information on EpiBuilder. See Devices that have been tested and approved by ImageWare for supported badge printers.

Issue When upgrading to 1.4, the reference system will be changed to follow newer more strict rules. Product Line EcoStruxure Building Operation Environment Device Administrator Cause With the release of 1.4, StruxureWare now has a tighter control on bindings. This is to prevent users from creating bindings which hinder system communication. When a system is upgraded from 1.3, to 1.4 any bindings that do not follow the new rule set will be dropped. Here are the 3 major items for this new rule set. See Reference Guide and References beginning with 1.4.x for a full explanation. Public Signal bindings will be dropped Multiple bindings will be restricted to one Bindings to Local Node NVIs will be dropped during the upgrade. Resolution To upgrade the Automation Servers, follow these steps: NOTE: You will need to have a copy of Workstation at 1.3 in order to make changes to the Automation Server during the upgrade process. Use 1.4 Workstation after you have completed Perform a Manual Backup of the Automation Server. This backup must include historic data. Ensure that a copy of that backup is saved to an external disk as a recovery option. Open Device Administrator 1.4 Connect to and Select an Automation Server Click Upgrade Device. Please Read the warning in this pop up message. This will upgrade the most recent backup of the Automation Server. Any changes to the system made since the last backup will be lost at the end of this process. Note that the yellow Progress bar means that you MUST review warning in the conversion log. If the progress bar is Yellow or Red, proceeding may result in irreversible system changes. Click "Open" under the conversion log column. This is very difficult to read in Notepad. Perform a Save as .txt and open this file in either Word Pad or NotePad++ for easier reading Notice the Change in display when the information is viewed in WordPad Use the notes from Reference Guide and References beginning with 1.4.x and the conversion log analysis from AS Conversion Log Analysis to make sure that all objects with WARNINGS meet the new rules. This will require making changes to the system via workstation. Repeat steps 1-8 until you are happy with the conversion log. Please note, that you must perform a new backup to get an updated log. Click on "Download updated database to devices" Click Okay in the pop up Wait for the Installation to finish successfully. If any errors occur, be sure to get a screen shot and contact Product Support Note: If the upgrade doesn't complete correctly on one of the AS, cycle power on the AS, go back to the previous version and perform the upgrade again.

Issue When trying to download a 5/7/9xx in XBuilder you get "Error code 401 - Unauthorized". Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 XBuilder Cause Password in XBuilder project does not match the password in the Xenta device. Resolution Select the 5/7/9xx in the Network panel The password is in the right hand panel of XBuilder under the TCP/IP Settings section. Change this to match the password in the 5/7/9xx. If the password is not known then refer to Receive a temporary session password for a Xenta 5/7/9xx if the password has been lost.

Issue SE7000 Series RS-485 transceiver unit load Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment SE7000 series room controllers Cause The room controller RS-485 transceiver unit load is not included in the data sheets. This information is needed to determine the number of BACnet MS/TP devices per RS-485 segment. Resolution Refer to Application Note AN05-RS485-VT7000 and Quick Guide RS485-VT7000. The links to these documents can be found in MS/TP and Modbus RS485 Communications on StruxureWare Automation Server

Issue Unexplained network and communication errors IT department may have set up IP blocking or set up IP switches incorrectly or there may be an issue with the Continuum setup Product Line Andover Continuum Environment IP network Cause Problems in the IP network, port blocking or incorrectly setup in IP switches IT departments may say their system is set up correctly, but this may need to be tested. Resolution See Router required open port numbers to run a Continuum system for IP port requirements See Continuum Controllers and IP Managed switches for other IP switch settings Get all the problematic equipment connect to a simple non managed IP switch (this will probably involve temporarily moving PCs and/or controllers) Disconnect from the site IP switches if possible (this may not be possible, depending on the site setup, eg. SQL server may be in a server room) PC and Controller settings (IP address, subnet mask, default router) may also need to be temporarily modified depending on the original site set up. Test the system with this temporary setup, if all is ok then the problem lies with the site IP network, if the problem persist then  look at the Continuum setup (Cyberstation install, database, operating systems, hardware issues)

Issue Display options now the DCX250 is no longer available Product Line Andover Continuum Environment Continuum DCX250 Touch Screen Display part number 01-0008-300 Cause The DCX250 is not available from January 2012: Discontinuation of Infinity 01-0008-300 (DCX 250) - PA-00184 Resolution There is no direct replacement for the DCX250 and there is no other display that works directly on Infinet.   The Continuum display options are- Netcontroller IO Bus - Infistat or LD-1 Direct connection to some controllers - Smart sensor or xP-Display A Continuum Cyberstation could be used if more information and input is required. Another option would be a Bacnet or Lon display. Or, the L-VIS from Loytec using bacnet MSTP may be such an option (LonWorks and BACnet Touch Panels Release - PA-00106). http://www.loytec.com/products/lvis (LON via NC2-F- port16 would also be an option, see Can LONMark Devices be used with Continuum?) NOTE - All support for this product is via Loytec. The EMX170 was a small display and keyboard available for some older Infinity Controllers (i1) This unit is obsolete, although it may be possible to repair one. There is no replacement for this unit. If the i1 controller is being replaced with an i2 unit then either a smart sensor or an xP Display plus room sensor could be used

Issue Original company sold to new company Site License needs to be updated for install/upgrade.  Computer failure and no software/license information is available. Downloaded software and during install it requests a CD Key Product Line Andover Continuum, TAC INET Environment Site Licensing for install/upgrade Cause Changes in company or computer replacement/upgrade or downloaded software and it is requesting a CD Key Resolution I/NET: 1. Original company sold to new company and Site License needs to be updated for install/upgrade: for company naming changes, contact your sales representative who in turn will contact Product Support and request a transfer of information or upgrade/purchase. Once the information has been cross referenced for validity, either a new or replacement CD Key can be generated. Please include the following when requesting transfer: User Name Site Name Site Address Serial Number Version number Build number CD Key 2. Computer failure and no software/license information is available: Send email to Product Support with the following information: User Name Site Name Site Address Serial Number version number Build number CD Key 3. CD Key for licenses on purchase of software can be ordered by contacting Contact Customer Care. Link is available on the Contact tab of this web page. Customer Care offers pricing, order placement, changes, expedites, and order status. Check Licensing of I/NET with SITE and SEAT License with License Key for issues with CD Key and Licensing information. Continuum: since Continuum only has physical security key licensing, the license is owned by the holder of the key. If you hold the key, you own the license. There is no need to contact PSS for moves, changes, restructuring. If the security key's are lost or stolen, you will need to purchase new keys to replace them. Continuum Software Licensing is available with Release 2.0. 

Issue How can the TAC Xenta OP be used with a TAC Xenta 100-series controller? How can the TAC Xenta OP know which TAC Xenta 100 controller it is communicating with? Which OP mode should be used? Product Line TAC Vista Environment Xenta OP Xenta 101 Xenta 102 Xenta 121 Xenta 122 Cause The TAC Xenta OP panel can be used to connect to a TAC Xenta 100-series controller to access input and output signals. Identifying the TAC Xenta 100 controller to configure is accomplished with a Service Pin message. If connecting directly to a TAC Xenta 100-series controller, or to a STR100-series device connected to the TAC Xenta 100-series controller, the controller sends out a Service Pin messages automatically, If this is not the case, or you connect on another location on the network, you could manually press Service Pin on the TAC Xenta 100-controller you want to connect to. For troubleshooting connectivity to a Xenta programmable controller, see "No Answer" on an OP when connecting to a Xenta 280/300/400. Resolution Configure the TAC Xenta OP Plug in the TAC Xenta OP Hold the Back and Enter button for 3 seconds to access the OP Service menu. Scroll down to option 10 for OP Mode. Change "Xenta 100" to ON with the + key. Press Enter. Change "Mode" to TAC with the + key. Press Enter twice to restart OP Connect TAC Xenta OP to a TAC Xenta 100-series device Plug TAC Xenta OP into OP jack on the TAC Xenta 100 controller, or to a STR100 device connected to the TAC Xenta 100. At prompt "Press <ENTER> to access Xenta 100", press Enter. At "Connecting to Xenta 100 ...", wait, or press the Service Pin of the Xenta 100-series  controller. Press Down. View Network Variables Select the network variable index number in the NV Index? prompt with the - and + buttons. Press Enter to view the signal. If the value is an input you can use + or - to provide a new value and press enter to accept it. If the signal is an application options set of bits then press enter to navigate between the bit number, + to change the value, and enter to accept the value.

Issue When using the DOS command Ping from a server to an ARC-net controller it fails and returns a 'Destination host unreachable' error Product Line Satchwell Sigma Environment Ethernet Network Communications Sigma RIP v1 Cause Routing has not been set-up correctly and the route to the sub-net networks is not defined Sigma DNN broadcast RIP v1 messages for the Sigma server to read, by default RIP Listener is disabled on Windows XP Resolution Enable RIP Listener on the Server.  See Sigma server communication to ARC-net/Ethernet sub-nets via a DNN failing. AND/OR   Add persistent routes to the Sigma server. See Persistent routing on the Sigma server.

Issue What is the limit of the number of Controllers that can be in a Continuum System? Product Line Andover Continuum Environment Continuum Cause Want to know the theoretical and practical limits to how many controllers can be on one system. Resolution There are certainly some logical limits to how your Netcontrollers are addressed and identified in the system but for all intents and purposes you are only restricted by the IP Address. Netcontrollers Logically, you can have Netcontrollers addressed from 1 - 190 - so the maximum you can have in a "logical" Network is 190 Netcontrollers. However, the number of Networks you can have in a Continuum Database is only restricted by the Database itself - effectively infinite. See the article below on logical Networks. How many logical networks can be created on a Continuum system? This restriction is only for Netcontrollers defined within the Infinity side of the Continuum Database and does not apply to third-party BACnet controllers. Field Controllers (b3 / i2) There is a definite limit to the number of subnet (Infinet or MSTP) controllers that can be strung off of a given bCX or Netcontroller. As a general rule, each comm port can support up to a maximum of 127 subnet devices. Of course this does depend on the device being used, the amount of nodes it is enabled for, and the physical installation. The number of nodes purchased does correspond to the total number of i2 or MSTP controllers that can be on that bus. Example: If you have a bCX1 with 32 MSTP nodes this means that a total of 32 MSTP devices can be on this MSTP network and the following architecture is valid. bCX1 with bLink; (segment1) node1 to node16. (segment2) node17 to node32. If we look at a Netcontroller or Netcontroller II, these controllers have two RS-485 comm ports that can be used to support Infinet subnet controllers, up to 127 on each port and a maximum of 254 off the one controller. Now the controller would need to have both ports enabled for 127 nodes and considerations made for the amount of traffic this number of controllers would require. Similarly, the bCX1 (BACnet) will support up to 127 nodes. One thing to note is that this also includes repeaters if they are used to extend your network or star the MSTP. The general rule for the number of devices on an MSTP segment is a maximum of 32 nodes, this dependent on the network complying with MSTP installation guidelines for termination, distance, cable type, and that each node is a full load RS-485 transceiver. In the case of our BACnet controllers, they use a 1/4 load transceiver so given perfect network conditions it is possible to have 127 b3 devices on the same MSTP network segment. Even though this is possible, it is always good practice to use a b-Link repeater and a max of 32 devices per network segment - this also helps to segregate the devices for troubleshooting as well. Total Point Limits Other than with a Cyberstation with an I/O limited Security Key, I'm not aware of any limits to the number of points that can be created in a Continuum Database; this would be limited to the size and resources of the Continuum SQL Database. Consult the following article that has a spreadsheet to help estimate the size of your Continuum Database. It could also help to estimate your SQL requirements: Continuum Database Sizing and SQL Server selection

Issue TAC Vista installations prior to TAC Vista 5.0.1 cannot be upgraded to TAC Vista 5.1.9  version directly. Product Line TAC Vista Environment TAC Vista Server TAC Vista Workstation Cause When upgrading Vista to 5.1.9, certain steps need to be followed to ensure that the process works properly. Resolution Note: If upgrading from an older version of Vista where the LNS port is at the root level of the system tree, instead of underneath the Vista Server, then you will need to follow the steps in Graphics binding were broken after a Vista upgrade to 4.5 from an earlier version to fix the binding paths of root level objects. TAC Vista installations between 4.3.0 and 5.0.0 must follow these upgrade steps in order: Upgrade to a version between 5.0.1 and 5.1.6 Upgrade to version 5.1.9   TAC Vista installations prior to 4.3.0 must follow these upgrade steps in order: Upgrade to a version between 4.3.0 and 5.0.0 Upgrade to a version between 5.0.1 and 5.1.6 Upgrade to version 5.1.9   Note: In a situation with multiple databases on a computer, make sure all are upgraded in this manner. After the upgrades have been carried out make sure the master server is started first followed by the slave servers.

Issue How can you use Loytec's LPA software with the AS as the interface Product Line EcoStruxure Building Operation Environment Automation Server Loytec LPA Cause A Loytec LPA can be a valuable troubleshooting tool to diagnose communication problems on a LON Fieldbus. Resolution As the Automation Server uses Loytec's Lon chip, it is possible to use Loytec's LPA software over the Lon port on the AS. Some Prerequisites:   A license is required to use the LPA software. Either the "LPA-IP" or the "LPA-IP-SW" package depending on your setup. LPA (loytec.com) shows a product overview.   Downloads | Software - Device Firmware and Readme (loytec.com) to download the software. Create a free login in order to download software from Loytec's home page For additional help Buying and registering the LPA software read LonTalk Protocol Analyzer Software License and Registration Steps Lonworks troubleshooting read Troubleshooting LON Network Communication Troubleshooting Lon communication with TAC Xenta's read Actions for reducing Bandwidth in a Vista network There is a limitation when using LPA through an AS. Refer to Not all traffic on a segment is captured when using the LPA through an Automation Server Please make sure that you have a LonWorks interface configured in the Automation Server before proceeding. You will also need to add a Local Node to the interface and to commission it. Make sure to set the LPA state to Enabled under the Advanced tab in the properties for the LonWorks Interface: Once the above have been checked and understood the following steps can be performed:   Start the LPA software Click on "Profile -> Network Interface..." Click on "Remote LPA Assignment" Click on "Add Device" Enter the IP address of the Automation Server, click on "Get Info" and click on "Add Device and Restart Search" Select the Automation Server device and click on "Assign/Add" Select the interface you want to assign to the Automation Server, and click "Assign" With the interface assigned, click "OK" Select the Building Operation interface and click "OK" Now the LPA software is using the Automation Server as the interface Start a new LPA log

Issue Time Synchronization in Cyberstation  Product Line Andover Continuum, EcoStruxure Building Operation Environment Multiple Cyberstation Workstations Cause Security or HVAC and want to have exact time stamp from two or more Cyberstation workstations Resolution Continuum uses the Workstation time for events and transactions which are recorded in the database. Time Synchronization with the Server is not critical since they have internal time logs with the SQL database.  Time Synchronization with the Cyberstations so they have the exact time stamp on events and transactions is done by synchronizing the Windows workstation time to either a Network Time Server (NTS) (see Public time sync Servers for the United States) or by a third party software or device. Recommended is the Windows time which automatically synchronizes with the Domain Controller when logging in. If the computer(s) is not on a domain, double click on the clock in the lower right hand corner. This opens up the time settings and has a third tab as shown in image below: Select to synchronize with the Static IP Address of a primary workstation which can be seen by this computer. Visit Google and search for "Synchronize the time with Windows Time service" for your operating system If Internet access is not available, there are 3rd party USB and PCI devices available which synchronize with the Atomic Clock via radio frequency. Check your local listing to see if available.

Issue Alarm queue in the Vista Workstation states "No license for LonWorks communication" Product Line TAC Vista Environment Vista Workstation Cause The simplest cause of the issue, and the one that should probably be checked first, is that the license for LonWorks communication was not present at the time the server was started.  Oftentimes, this is due to starting server, realizing the engineering or end user dongle was not plugged in (or license server was not started) and then plugging it in.  The server will not actively poll for this license, it must be present at startup. Resolution Stop the Vista Server Ensure the license dongle is plugged in, or the license file is activated and installed on the license server. Restart the Vista Server Related Articles: "No license for LonWorks communication" with TAC Vista Server LE "No license for LonWorks communication" error when using a non LE dongle "No license for LonWorks communication" - LonMaker Recovery Folder "No license for LonWorks communication" error message in Classic Network "No license for LonWorks communication" Error in Windows 2008 Server X64 TACOS startup delay utility