Building Automation Knowledge Base

Issue In many situations, customers need to integrate more than one LNS database into a single Vista database. Product Line TAC Vista Environment Vista LNS LonMaker NL220 TAC Vista System Plug-In Cause This is very common in retrofit situations where a new LonMaker or NL220 database is created for the new section of the building. Still, the existing system was programmed in a completely separate LonMaker or NL220 database. This is common for multi-building systems like school districts that expand and add schools or buildings over time and integrate into one Vista database. Resolution Some general rules must be followed when integrating multiple LNS databases into one Vista database. These rules are: You can not integrate more than 4 LNS networks to 1 Vista database when doing straight LNS server-to-Vista server communication. NOTE: If more than four networks are needed, the system must utilize the Loytec NIC852 key and the Orion stack. When using the Orion stack and 1 Loytec NIC852 key will expand Vista's capability to 8 LNS networks simultaneously. If more than 8 LNS databases are needed, then multiple Loytec NIC852 keys are needed. Vista can only communicate to 4 Loytec NIC852 keys simultaneously for a maximum of 32 LNS databases per Vista server. It is recommended never to use more than seven ports on the NIC852 for serviceability reasons, with Lonmaker or NL220 truly giving the system a 28-network limitation. The Menta file paths from the site or engineering PC will be stored within the path structure of the System Plug-In. If these files are not in the exact same path on the Vista server that the LNS database is being integrated to, all.MTA files will have to be browsed for every controller. It is recommended to save all Menta files from the engineering Vista database to a folder on the machine to ensure they are the most current files. Then copy that menta files directory to the new Vista server to ensure the System Plug-In will search and copy the same path when transferring the network to the vista database. Every LNS database integrated into the Vista server must have a unique domain ID. See the instructions and screenshots below. The screenshots and instructions below detail how to build one Vista database with two LonMaker databases. The first database will be called NETWORK1, and the second database will be called NETWORK2. Please follow these instructions: Restore and open the LonMaker database NETWORK1 on the machine running the Vista server database into which the LNS system will be integrated. The Vista server must be running and logged in to continue with the next instruction.   From the Visio menu bar, choose LonMaker and Network Properties. Set the Domain ID to a unique number within the Vista database. Systems sharing the same LNS server communicating to one Vista server must have unique Domain ID numbers.   In the NETWORK1 LonMaker database, open the TAC Vista System Plug-In and choose the toolbar menu item TAC Network, then choose settings. Click the browse button next to the Operator unit object: and browse to the local Vista server object running on the machine. The Operator unit object: entry to change to the Vista server object name currently running on the local machine.   In the TAC Network Settings menu, the Vista communication port should be set to Communication Port - LNS, and the Vista communication port name should be unique to the LNS network name.  LNS_Network Name is good practice. In the example below, it is LNS_NETWORK1. Click Apply, then OK, and close to close the TAC Network Settings window.   In the TAC Vista System Plug-In, click the Update TAC Network Icon.    Next, click the Check TAC Network Icon. Check for any errors or warnings in the output pane.   Then finally, click the Update Vista Database icon. This process will copy all of the Xenta groups, Lonworks groups, .MTA files, and .XIF files to the Vista database.   Once the Vista database has successfully updated, open Vista Workstation, and the LNS port should be created along with the physical LNS network. In the screenshot below LNS_NETWORK1 is the LNS port, and NETWORK1 is the physical LNS database.   The steps to add the second LNS database are almost identical except for steps 2 and 4  above. Follow these instructions to integrate NETWORK2 into the Vista database. Restore and open the LonMaker database NETWORK2 on the machine running the Vista server database into which the LNS database will be integrated. The Vista server must be running and logged in to continue with the next instruction.   From the Visio menu bar, choose LonMaker and Network Properties and set the Domain ID to a unique number within the Vista database. Systems sharing the same LNS server communicating to one Vista server must have unique Domain ID numbers.   In the NETWORK2 LonMaker database, open the TAC Vista System Plug-In and choose the toolbar menu item TAC Network, then choose settings. Click the browse button next to the Operator unit object: and browse to the local Vista server object running on the machine. The Operator unit object: entry to change to the Vista server object name currently running on the local machine.   In the TAC Network Settings menu, the Vista communication port should be set to Communication Port - LNS, and the Vista communication port name should be unique to the LNS network name. In the example below, it is LNS_NETWORK2. LNS_Network Name is good practice. Click Apply, then OK, and close to close the TAC Network Settings window.   In the TAC Vista System Plug-In, click the Update TAC Network Icon.    Next, click the Check TAC Network Icon. Check for any errors or warnings in the output pane.   Then finally, click the Update Vista Database icon. This process will copy all of the Xenta groups, Lonworks groups, .MTA files, and .XIF files to the Vista database.   Once the Vista database has successfully updated, open Vista Workstation, and the LNS port should be created along with the physical LNS network. In the screenshot below LNS_NETWORK2 is the LNS port, and NETWORK2 is the physical LNS database. As network 2 does not use the default Domain length of 1 and Id of 11 and uses a Domain length of 1 ID 12, any operator panel used in this system will need this domain setup to work this network.  You can adjust the OP Domain setting as described in the following article, "No Answer" on an OP when connecting to a Xenta 280/300/400

Issue How do Automation and Scripts work in Security Expert? Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert Cause Lack of understanding regarding the usage of Automation and Scripts features in Security Expert. Resolution 1. Automation Automation is used for C-Bus interface programming in Security Expert. It allows Security Expert to send signals to the C-Bus Network or change the state of Security Expert outputs based on control signals from C-Bus. Note: This integration is not currently validated or supported. 2. Programmable functions: Programmable functions in Security Expert enable you to directly monitor and display analogue values, such as those from HVAC systems, using Data values and Variables. These values can then be used to trigger functions within Security Expert. You can set up programmable functions to control logic within Security Expert, Doors, Areas, Elevators, and more. For further information, please consult the help file. 3. Scripts: Currently, Scripts are not available in Security Expert. The "Run Script" option under Events > Actions > Configuration > Type does not have any functionality.

Issue SNP I/O server and NCP I/O server dongleless software download location. Where can I download SNP I/O server and NCP I/O server dongleless software as advised in: PA-00145 - Satchwell MicroNet Range Rationalisation Product Line Satchwell MicroNet Environment MicroNet View. SNP I/O server dongleless software NCP I/O server dongleless software Cause SNP I/O server software can no longer be ordered, it is available as a free download. Resolution Download the software from The Exchange or Click here to be linked to the Monitor tool.(This link will open a new page) Click here to be linked to the SNP I/O server. .(This link will open a new page) Click here to be linked to the NCP/ARCnet I/O server. .(This link will open a new page).  

Issue MODBus XDriver is communicating with device but the data read is not what is expected. For example,  when requesting the voltage between phase 1 and neutral (StartChannel = 3926)  from a PM1200 the value received is the following: VPhase1toNeutral [1] = 17085 VPhase1ToNeutral [0] = 65890  (This last value varies constantly because it is the least significant part of reading). This value should be between 110V and 120V  or  220V and 240V depending on location. Environment CyberStation CX9900 CX9640 bCX4040 CX9680 ACX5720 ACX5740 Cause Function code used reading raw data from register(s) without conversion. Since, when you request information from a Modbus RTU device you receive the exact value that is in the register, Andover Controls has provided some special function codes that will help to convert some of the common engineering values into usable values.  The listing in the x-driver documentation shows the special function code, what is expected from the third party and the equivalent function code that is truly sent to the device.   For instance if a point is a Intel float and resides in the 40,000 range then function code 245 would be used in the Andover Controls x-driver.  This will still send out a function code 3 in the Modbus message but the x-driver will take the value sent in from the third party device and convert it into a usable float. Resolution Use Continuum special function code to convert the raw value to a readable value.

Issue What is the Network ID-UDP Setting required for and does this need to be changed when commissioning a new BACnet Continuum controller? Product Line Andover Continuum Environment bCX4040 bCX4000 Cause Require information on the Continuum BACnet Network setting (physical layer). Resolution Each network segment in a BACnet network is assigned a unique integer as an identifier for ease of routing packets between these networks. For more information see Effect on a BACnet network if the Network Id - UDP setting in bCX40x0 have been set to different values   BACnet Network ID-UDP Setting This defines the ID number of the BACnet/IP network on which this controller resides. When creating a Continuum BACnet controller the default UDP Net ID is set to 1. This setting would need to be the same for all BACnet controllers that want to communicate with each other across the network.   Why would you want to change it? You may have a site for example that already has a BACnet network running on the ethernet and not want to communicate on the same BACnet UDP Net Id as their BACnet devices do. In this case you could change the UDP Net Id for your BACnet communications but it needs to be the same for all of your BACnet devices since the routing tables in the controllers would need to know which UDP Net Id to route to. If you changed the UDP Net Id to 2 then all controllers would need to be set to 2 to make sure they were able to communicate efficiently with each other.

Issue When attempting to access the dashboard URL via the web browser or in SBO Workstation, the following message is displayed. Product Line EcoStruxure Building Operation, EcoStruxure Energy Expert Environment Power Manager 1.2 and newer Power Manager Expert 8.1 and newer Building Operation Workstation Cause A Power Manager 1.2 or newer system running a permanent license allows the user to a log into the Management Console, manual authentication URL, and through the EWS interface in SmartStruxure Workstation. After upgrading to the latest version of Power Manager this access no longer works. The Ports match in License Manager and FlexNet and this site has previously worked. The cause to this issue is that the URL being used has changed starting in PME 8.1. Resolution This issue is due to a change made in the dashboards URL starting in Power Manager 1.2 / Power Manager Expert 8.1. The URL needs to be changed by replacing "Web" with "Dashboards" in the URL found in the EWS link settings or when logging in directly with a web browser.    Example: http://XXXX/SystemDataService/Auth/LogOnWithMultiuseAuthToken?RedirectUrl=http%3a%2f%2fFS2%2fWeb%2f%3fDisplayEmbedded%3dTrue&multiuseAuthToken=11324... http://XXXX/SystemDataService/Auth/LogOnWithMultiuseAuthToken?RedirectUrl=http%3a%2f%2fFS2%2fDashboards%2f%3fDisplayEmbedded%3dTrue&multiuseAuthToken=11324...   Also in the newer versions of Power Manager, there is a limit regarding what can be accessed in PME when using a Power Manager license. In Power Manager 1.2 and on you can access: /Reporter /Dashboards /Trends /HierarchyManager /RateEditor and use the integration toolkit to get into SBO if necessary. Power Manager is now known as EcoStruxure Energy Expert.

Issue In a multi-version system, will the database schema in the PostgreSQL database be compatible with EBO servers with lower versions? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Building Operation Timescale Database Cause In a multi-version system the database schema in the PostgreSQL database needs be compatible with all servers in the system. Resolution The DB schema is backward compatible. The same schema can be used for the complete system and it can be upgraded to the latest version compatible with the top-level server. Compression is done on the PostrgreSQL/TimescaleDB side and since it’s not configured in EBO, the compression will work for EBO servers with lower versions. Compression needs at least schema version 9 for EBO2023 or schema version 13 for EBO2024 and TimescaleDB version 2.0 or higher, refer to: Compression for TimescaleDB

Issue Need replacement for AVUM4601 valve actuator Environment VEU, MEU, FEU, VZX, MZX Cause Need replacement for AVUM4601, AVUE4304, AVUE4354 or AVUX4202 valve actuator Resolution Use AVUM5601 actuator, this is the replacement for AVUM4601 230Vac actuator  Also AVUE4304 is replaced by AVUE5304 AVUE4354 is replaced by AVUE5354 AVUX4202 is replaced by AVUX5202 Click HERE for the datasheet Click HERE for the Installation Instructions

Issue Cannot Delete Personnel  Product Line Andover Continuum Environment Continuum  1.8X & 1.9X Windows XP Windows 2003 Server Continuum ACX5740 Microsoft SQL 2005 Cause Stored Procedure packPersonneldeletion failed to run Resolution Duplicate personnel.   Remove Areas from the personnel object. Delete duplicate personnel objects.

Issue Station was named incorrectly when first created.  Just copying the station folder or renaming the folder has no effect on the name of the station. Environment I/A Series R2 system (any version) Cause Station was named incorrectly when first created.  Did not realize name for the station did not match the desired naming convention used for the other stations in this facility. Resolution To rename a UNC station: Save the existing station database using the Admin Tool DbAdmin function. Use the Admin Tool DbAdmin function to get the station config.sys file and to convert it to an xml file (config.xml).  You will then have a config.sns and config.xml file in the existing station folder. Create the new named station folder under the stations folder under the current Niagara... installation folder. Copy the config.xml file from the existing station folder to the new station folder.  Copy any other folders that are under the existing station folder (graphics, etc) into the new station folder. Open the config.xml file (in the new station folder) with a TEXT or XML editor that can handle large files.  Two text editors that are know to work properly with large xml formatted text files are Notepad++ or EditPad.  These editors are both available for free via Internet. The existing station name typically first appears on lines 18 & 19 of the file.  Use the editor's Search and Replace function to globally change the existing station name to the new desired name.  Make sure that the there are no spaces or special characters in the new station name.  When specifying the existing station name, do not include the double-quote marks. Using the Admin Tool DbAdmin command, convert the edited config.xml file to config.sns. Use the Admin Tool "Install Station" function to load the edited station into the UNC.  

Issue Under different circumstances, the comm port on infinet or bacnet devices will not be assigned and will show blank in their editor. The controllers may be controlling the equipment correctly, but they can't be reloaded and communication doesn't work to and from the device. Product Line Andover Continuum Environment CyberStation Webclient Windows XP, Windows Vista, Windows 7, Windows 10 Windows Server 2003, 2008, 2012, 2016 Cause This issue can happen on an upgrade where a send to database is used if the controller didn't exist previously or under other unknown database circumstances Resolution 1. Click the link to download the following TPA1498  NOTE: the TPA indicates the following at the bottom Save the new .dmp file Right click the NetController to reattach the Infinet controllers to -> select Import Into Right click the NetController to reattach the Infinet controllers to -> select Send to Database Commports will be reattached.  (THIS SHOULD BE SEND TO CONTROLLER) (The previous line, Import into, brings the corrected comm ports into the db) 2. It may be necessary to make changes to the database in order to reassign the ports to the controllers. Backup the database and send a copy to PSS for assistance The objects can be reassigned, but the queries should be tested prior to updating in the field.

Issue Needs to know how often offline BACnet devices are polled to check if they are back online?. Product Line EcoStruxure Building Operation Environment Enterprise Server, Automation Server, AS, AS-P, AS-B BACnet Cause For troubleshooting reasons it may be good to know how often offline BACnet devices are polled (by EcoStruxure Building Operation Servers) to check if they are back online?. Resolution EcoStruxure Building Operation Servers checks once per minute, using the BACnet "who-is" service to locate the device, so even if its MAC address (or IP address) has changed, the BACnet Device will be found. A user can initiate the recheck, by selecting the "device offline" alarm and choosing "recheck" from the alarm command menu

Issue Is there surge protection available for a BACnet/MSTP or RS-485 trunk? Environment BACnet/MSTP RS-485 trunk Surge protector Cause Install surge protector to prevent devices from abnormal electrical spike, which might damage devices. Resolution In the Network 8000 Hardware Installation Practices manual (F-23061) pages 21-26, the GCMA-131-1 is used for data line surge protection in conjunction with the AS-8969-21 capacitor grounding the shields as shown. The same components and procedures apply to BACnet/MSTP or RS-485 trunks. If there are power line issues, review the PAS-29901-400 lightning arrestors. The GCMA-131-1 and its associated installation shown on pages 22-23 of the above manual can be used.  Also, the E-1001-111 transzorb shown on page 26 can be used. It is important to have a GOOD earth ground when applying these devices.

Issue PCT workstation displays message “Server version not compatible with client", when restoring a server configuration with new IDs. Product Line EcoStruxure Building Operation Environment Buildings Operation Project Configuration Tool Cause When backing up and restoring an AS-P/AS-B with a new ID in PCT at EBO 3.2.2.61, when logging back on with PCT using the installed EBO workstation,  the message “Server version not compatible with client" is displayed Resolution PCT is the offline programming tool but, it launches the workstation installed on the computer. If the workstation version on the computer is EBO 3.2.2.61, Hotfix 3.2.2.4002 (CP3) is required to be installed on the computer running PCT, taking the computer’s installed workstation version to 3.2.2.4002.

Issue Floor Plans and Camera Views that show up in the Security Expert thick client do not work in the Web Client. Instead of floor and camera images, “Floor plan not supported” and “Camera view not supported” are displayed. Product Line EcoStruxure Security Expert Environment Security Expert Web Client Cause Floor Plans and Camera Views are not displayed through the Web Client interface and will only work with the Security Expert Client. The Security Expert Web Client is not intended to support the full suite of options available through the thick client. Resolution Use the Security Expert Client as this will support Floor Plans and Camera Views.

Issue Using Schneider Electric actuators with competitors' globe valves Product Line Field Devices Environment Schneider Electric actuators (Americas field devices) 3rd party globe valves Cause To replace 3rd party / competitor valve actuators with Schneider Electric valve actuators, a linkage / adapter may be required to install the Schneider Electric actuator onto the 3rd party / competitor valve.  Resolution Refer to the AV-800 Series Competitive Globe Valve Adapters Selection Guide for a list of adapter kits, recommended Schneider Electric actuators and supported 3rd party / competitors' globe valves (Johnson Controls, Siemens, Honeywell).  The Selection Guide can also be downloaded from the Publication Zone with iPortal. If you do not have access to the iPortal, use the guest access credentials. Once you have logged on, go to 'Links' > 'Publication Zone'.  Installation instructions showing assembly drawings can be downloaded here.

Issue Continuum video integration using Pelco Endura. When video alarm comes in, Video Monitor starts up as expected and video is recorded for the specified amount of time but the recorded video does not automatically play back as expected. Product Line Andover Continuum, Pelco Environment Cyberstation Pelco Endura Cause The NVRs configuration for recorded video type has been changed from its default of continuous recording which is what the Continuum-Endura integration supports. You should ensure that your Pelco Endura system is set to continually record. While it is possible to change the recording type, continuous recording is the recommended setting from Pelco. As a result, when an alarm or event occurs, it is "marked" on the Endura system at the time of the event based on the recording time and duration. Such events are then visible from the Endura client as a marked event with details included in the comment for that mark. Resolution SOLUTION #1 If a specific recording type such as motion or schedule has been configured remove it to go back to the default continuous recording type. NOTE: As continuous video recording will utilize more storage capacity, one option for reducing the amount of storage used by all the video is to enable Pelco EnduraStor. SOLUTION #2 The other option is to leave the configuration as is and manually start playing back the recorded video by double clicking the video event. In the screen shot above, double clicking the PSS_Test_AV1 video alarm will cause the recorded video to start playing back.

Issue How many concurrent users can connect to the system Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause In the datasheet it is unclear how many concurrent users can connect to an AS without affecting performance Resolution The intent in the guidelines is to provide the concurrent user connections given that the clients are not all accessing data through the same Automation Server to the same Field Controller.  Therefore, if the load is distributed –  ES Clients viewing data from the ES (or a scattered variety of Automation Servers and below) AS Clients viewing data from that AS  Then it should be safe to add the client totals for all AS and ES clients together. The local AS connections are intended to help with scaled use of clients at a site-wide or multi-site system. The typical use case is for operators within a building, floor or tenant to connect locally to the AS, while central operators connect to the ES without impacting each other.  If all ES Clients and all clients on a single AS are all accessing data from that AS and below then the performance could drop below acceptable levels.

Issue A previous version of the client software badged SecureStruxure is installed, and needs to be upgraded to Security Expert. Product Line EcoStruxure Security Expert Environment Security Expert SecureStruxure Cause The offer had the name changed between versions and it's not straight forward how to update the software, and databases, to the newer version. Resolution SecureStruxure can be upgraded to Security Expert by following these steps: Contact Product Support to upgrade the site license to Security Expert.. Backup the SecureStruxureOperations and SecureStruxureOperationsEvents databases via SQL Server Management Studio. Uninstall SecureStruxure. Rename the SecureStruxureOperations and SecureStruxureOperationsEvents databases to SecurityExpert and SecurityExpertEvents When you run the Security Expert installer, use the new Security Expert SSN. You will need to point Security Expert at the MS SQL database instance you were previously using for SecureStruxure (this is likely "localhost\SECURESTRUXURE"). The installation wizard should pick up the databases and upgrade them, retaining all the SecureStruxure programming. Log into Security Expert and re-license the software by going to the About | License menu option.. If you are unable to connect to the license server (no internet connection), you can use the manual method for registering a license.

Issue Creating many TGML graphics that use the same or similar links and bindings can be difficult and time consuming. Environment TGML Vista Workstation Cause The copy and paste feature does not work on more than one link at a time. Resolution Whenever a Vista database export is performed on a group of TGML graphics, a .zip file is created that contains a source TGML file for each selected graphic, and one XML file describing all of the links and bindings contained in the database for those graphics. By editing this XML document and leveraging find/replace capabilities of text editors, the process of manually populating links and bindings can be sped up substantially. Warning: Always back up your database before performing any manipulation of XML files. There is a potential for your graphics to be ruined if a mistake is made, so be sure a current backup is available in this event. This is an advanced operation and should only be attempted by individuals with an understanding of Vista TGML graphics. This example shows how to populate the links on a standard menu that appears on every TGML graphic in a database. For simplicity, the database has three graphics: AHU1, AHU2, and AHU3. But the steps can be applied to hundreds of graphics just the same. A menu is created in TGML with a link to each graphic. The links are named AHU1, AHU2, and AHU3. These will correspond with the TGML objects in Vista that are also named AHU1, AHU2, and AHU3. The names do not have to match, but it is a good design standard to follow whenever possible. Right-click on the first graphic and choose Open Links Window. The first graphic should be populated manually to give a template for the rest. Populate each link using the traditional drag-and-drop. Verify the links are populated correctly. Go to File > Database > Export.... Select "Get a customized copy of the database.  This is the only option that needs to be selected. Highlight all of the graphics and drag them into the Export window. Click the green arrow in the upper-lefthand corner of the Export window and give the .zip file a name. Click Save. A message will appear stating "Vista Database Export completed" Find the resulting .zip file in the location specified in Step 4. Right-click and extract all files. Depending on the operating system and software, this step may vary. Unzip the specified file. In the resulting folder, find VistaDbImportExport.xml. Right click and open with Notepad or other text editor. Find Objects of type "TGML_LINK." If the RELREFID is populated, then this link has a destination. If it says RELREFID="" then this link is not yet populated. Time for some strategic find/replace. In this example, AHU1 has all of the links populated. But AHU2 does not. There are three links on each page that all share the same destination. Find the populated entry for AHU1 links: Object TYPE="TGML_LINK" NAME="AHU1.AHU1" DESCR="" SHCP="" SHCR="" IOLABEL="" RA="" WA="" KEYLABEL="" RELREFID="Graphics-AHU1" _PROTECTED="0" Find the non-populated entry for AHU1 links: Object TYPE="TGML_LINK" NAME="AHU2.AHU1" DESCR="" SHCP="" SHCR="" IOLABEL="" RA="" WA="" KEYLABEL="" RELREFID="" _PROTECTED="0"   Select everything after the graphic name that is not unique and perform a find replace: Find: AHU1" DESCR="" SHCP="" SHCR="" IOLABEL="" RA="" WA="" KEYLABEL="" RELREFID="" Replace: AHU1" DESCR="" SHCP="" SHCR="" IOLABEL="" RA="" WA="" KEYLABEL="" RELREFID="Graphics-AHU1"   Repeat this action for AHU2 and AHU3. When all of the edits have been made to the XML document, save and close it. Highlight the XML document as well as all of the TGML files in the unzipped folder. Right click and select Send to > Compressed (zipped) folder. This will create a modified database export file. In Workstation, go to File > Database > Import. Browse to the .zip file created in Step 12. De-select Perform alarm refresh and hit OK. A message will be displayed that says "Vista Database Import completed. All of the links on every page are now populated.