Building Automation Knowledge Base

Issue A BACnet/MSTP network will run longer than 4000 feet. Can the ASD or MicroSmart repeater be used? Environment ASD repeater MicroSmart repeater BACnet/MSTP network Cause ASD or MicroSmart repeater won't extend communication distances on a BACnet/MSTP. Resolution Both repeaters were tested and neither worked on a MSTP network.

Issue A Niagara R2 station listed under localhost won't open.  In the fui.exe console window, this message appears: Requestclient.handshake [serverSessionId=3] Station=josh [0] Station The station never opens. Environment Niagara R2 station Cause This behavior is caused by McAfee Security Centers Proxy Service. Resolution Disable the proxy service and reboot the computer. Follow the steps below to disable this service: Open the Windows services - (Click on Start - Run - then type service.msc) Scroll down to the McAfee Proxy service. Disable this service by right-clicking on the service - select properties - change the startup type to disabled. Reboot the computer. This should allow the station to run correctly on the localhost.

Issue The Vykon Alarm Client will not connect to the Niagara R2 Enterprise Server station. Environment Vykon Alarm Client Niagara R2 Enterprise Server station Cause The Vykon Alarm Client uses TCP port 4321 to communicate with the Enterprise Server. Many firewall, antivirus, and Internet security applications (e.g. Windows Firewall, antivirus & remote access software) block TCP port 4321 by default. Resolution Either disable the offending application, or create an exception policy in the application to open TCP port 4321. To view active TCP connections, open a DOS window, and type: netstat -ano. The output will look something like this: Active Connections Proto Local Address Foreign Address State PID TCP 0.0.0.0:13 0.0.0.0:0 LISTENING 956 TCP 0.0.0.0:37 0.0.0.0:0 LISTENING 956 TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 1368 TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4 TCP 0.0.0.0:3011 0.0.0.0:0 LISTENING 756 TCP 0.0.0.0:6523 0.0.0.0:0 LISTENING 3752 TCP 0.0.0.0:27700 0.0.0.0:0 LISTENING 748 TCP 10.1.146.152:139 0.0.0.0:0 LISTENING 4 TCP 10.1.146.152:2531 72.247.127.34:80 CLOSE_WAIT 3616 TCP 10.1.146.152:2532 72.5.124.55:80 CLOSE_WAIT 3560 TCP 10.1.146.152:2533 72.247.127.11:80 CLOSE_WAIT 3560 TCP 10.1.146.152:4245 10.1.146.32:4321 ESTABLISHED 216 A successful connection to the Enterprise Server will have an entry similar to the last line, where the Foreign Address (e.g. 10.1.146.32:4321) will have a state of ESTABLISHED.

Issue When using Workplace Tech, links won't create between two objects.  No matter what type of objects, the link line remains red and the application will not link the two objects. Environment Workplace Tech Cause In Microsoft Visio, the Snap & Glue feature is disabled. Resolution  To enable Snap and Glue go to Tools > Snap & Glue, then check the Snap box and the Glue box.

Issue Can Signal XP run with a limited user account in Windows XP? Environment Signal XP Limited local user account Cause The application will not run properly with limited local user account. Resolution In order to run Signal XP, the Windows user account must have local administrative privileges.

Issue Will Niagara R2 and G3 applications (ie: Workplace Pro, Workbench) run on a dual-processor/dual core/duo laptop? Environment Niagara R2 Niagara G3 Workplace Pro Workbench Dual core processor PC Cause As per Tridium sales and technical support, both applications will run on dual processor computers, though they have not been specifically tested. For more information on Workplace Pro review document F-26999 and for more information on Workbench review document F-27426. Resolution Minimum hardware requirements for Niagara applications are as follows: R2 - Workplace Pro: Intel Pentium IV 1GHz processor, 512 MB RAM, 1GB hard disk space G3 - Workbench: Intel Pentium IV 2GHz processor, 1 GB RAM, 1GB hard disk space

Issue After manually changing all the COV increments in a Niagara R2 station, the COV increment values never update. Environment Niagara R2 Cause The COV increment property is not fetched during a poll. To receive an update on this property use the Upload All command on the device object. Resolution Follow the steps below in WorkPlace Pro to perform an Upload All on the device object: Navigate to the workspace of the container where the BACnet device object exists. Right click the device object and select upload all. For further information on COV increment refer to the Niagara R2 BACnet Integration Reference manual 

Issue Is an additional license feature required for BACnet/MSTP in a Niagara R2 UNC or Niagara G3 ENC? Environment Niagara R2 UNC Niagara G3 ENC BACnet/MSTP Cause Each COM port require a license to enable BACnet/MSTP Resolution Although the BACnet driver is included with all Niagara R2 and G3 controllers, only the UNC-510-2, UNC-520, and ENC-520 controllers support BACnet/MSTP communications. For the UNC-510-2 and UNC-520, BACnet/MSTP is a license feature that must be purchased separately per COM port desired for MSTP communications (part number: IA-DRV-MST-P). For the ENC-520, BACnet/MSTP is licensed for all COM ports by default.  No additional license purchase is necessary.

Issue A Niagara R2/G3 UNC/JACE is rebooting every 15 minutes and the standard output window indicates AC Power status failed and a "Battery test failed" gets logged as well. Product Line TAC IA Series Environment I/A Series UNC, ENC or JACE chassis with Gel-cell backup battery Cause Marginal or failed battery or bad battery charging fuse Resolution The UNC automatically performs a battery load test every 15 minutes. If the voltage drops below a predefined value, the battery test indicates "battery test failed". If the voltage is higher than the predefined value, the battery test indicates "battery test passed". This message is only reported once unless the detected battery condition changes. A station alarm is generated only when the new outcome is different that the previous test. If a battery is marginal, the test may alternate between "passed" and "failed." Additionally, a bad or marginal battery has been known to cause random UNC reboots. Begin troubleshooting by checking the battery fuse (field replaceable only in the UNC-500/510 controllers), connections and voltage level.  If the battery voltage is low (less than 12 Vdc), disconnect the battery and monitor the UNC for errors or rebooting. If the errors or rebooting stops install a new battery.  After installing the new battery, measure the battery charging voltage.  The voltage reading should be between 13 and 14.5 volts DC if a good battery is connected.  If the installed battery is partially discharged, the charging voltage reading may be as low as 12.5 volts. In release 2.301.522, a change was made to how embedded controllers (UNC-410 / 500 / 510 / 520) perform the backup battery test.  Formerly, a "marginal" battery might result in continuous reboots. Now, the battery test is better coordinated with the AC power test. This prevents the scenario of repeated AC power fail shutdowns upon boot up if the battery is bad or weak.

Issue When opening an application file in Workplace Tech 5.x, the following error message appears:  "AppXMLAddon error code: -##########" "unknown error."  (where # = random numbers) Environment Workplace Tech 5.X Cause This error is caused by an illegal character in the application's nciLocation snvt. The character looks like a bold vertical line. WorkPlace Tech 4.0 did not have an issue with this character but WorkPlace Tech 5.x generates the above error. Resolution To eliminate the error: Open the application with WorkPlace Tech 5.x and continue to click OK until the drawing opens.  Locate the nciLocation snvt and check its initial value. Delete the unknown character from that entry field, and re-compile the application. 

Issue How can the Niagarad service for Niagara G3 be started? Environment Niagarad service Niagara G3 Cause There are three different ways to start the Niagarad service manually. Resolution From the Windows Start menu: click Programs > Vykon AX Supervisor 3.x.x > Install Platform Daemon Open a DOS window and type - cd\Niagara\Niagara-3.x.x\bin then type plat.exe installdaemon Create a desktop shortcut with the following: C:\niagara\niagara-3.x.x\bin\plat.exe installdaemon

Issue Daylight Savings Time changeover may not automatically occur on some Network 8000 controllers. Environment Network 8000 Cause The controllers with the "Formula Date" option selected will use the "Formula Date" information to calculate a Spring and Fall fixed date which is used to determine when the daylight savings changeover should occur. The fixed dates calculated will be for the current calendar year. This means that if a "Formula Date" recalculation is triggered on April 15, 2007 in a NW8000 controller, the controller will generate fixed dates of March 11, 2007 and November 4, 2007 corresponding to the 2nd Sunday in March and the first Sunday in November. Once the fall back date of November 4, 2007 has been processed, the NW8000 controller will not recalculate the new fixed dates for year 2008 until there is a trigger event that occurs after January 1, 2008. If no trigger event occurs between January 1, 2008 and March 9, 2008, the "spring ahead changeover" does not occur since the controller is still using the fixed date of March 11, 2007. Resolution For the daylight savings time changeover to occur, a new fixed date must be calculated each calendar year before the Spring changeover date. The changeover date calculation is made following a pre-determined trigger event. The fixed changeover dates used for comparison in the "Formula Date" Daylight Savings option currently get recalculated when: The controller’s EEPROM is cleared, The controller is reset, Any information in the INSTALLATION DATA is modified. If the "Formula Date" option is selected in a controller, the only means to insure that a controller will process the daylight savings changeover is to either reset the controller or modify the installation data. If it is unknown that either of these events has occurred during the calendar year it will be necessary to manually initiate one of these events to guarantee that the daylight savings time changeover will occur. Refer to Bulletin 01-40

Issue Where can network bandwidth utilization statistics be found for the Niagara R2 product? Environment Niagara R2 Cause Concern of bandwidth usages over a connection. Resolution There are some scenarios in which IT Managers or Network Administrators are concerned with the impact of Niagara R2 systems on their network. Some testing has been done to determine bandwidth usages and is documented in the Niagara ITManagersFAQ document.

Issue How can the default HTTP port for a Niagara R2 UNC station be changed? Environment Niagara R2 UNC station Cause The station need to change the default port 80 to a non-standard HTTP port in the httpPort text box. Resolution Do the following:  In WorkPlace Pro, open the station offline In the tree view, right-click on the offline station and select Go - Properties On the Properties sheet, click the Config tab Edit the httpPort text box, removing the default port of 80 and replacing it with your chosen port number (e.g. 8081) Click Apply In the tree view, right-click on the offline station and select Close Open the Admin Tool, and log into the UNC Right-click the station name (not the host name or address) and select Edit - Properties. This opens the station.properties file Add the following line to the station.properties file:  httpPort=[newport] (newport = port number from step 4), example httpPort=8081 From the file menu, choose File - Close. The system will prompt you to save any changes. Choose Yes. In the Admin Tool, click the Installation tab On the Installation Sheet, click Install Station Select the station from step 4, then click OK In the Confirm dialog box, click Yes In the Select Database Format dialog box, select the DB radio button, then click OK The system will load the offline database to the UNC, then re-boot the station. When finished, the message box will display "Installation Complete"

Issue The following error appears in a Niagara R2 UNC Standard Output Window: "Duplicate server sessions; kill! [station name]" Environment Niagara R2 UNC Cause This error message is usually indicative of another station running on the Enterprise Server having the same name as the UNC station. Resolution Stop the running station on the Enterprise Server via the Admin Tool.

Issue With Niagara R2 UNCs using BACnet routers, router function quits when other routers are on the network. Environment Niagara R2 UNC BACnet routers Cause Niagara R2 station detected a routing issue and has disabled its routing functionality. Resolution When Niagara R2 stations encounter a network mis-configuration, such as multiple routers on the same BACnet network, it disables its routing functionality, to avoid a packet flood when multiple routers repeatedly circulate the same request. This routing functionality cannot be re-enabled without restarting the station. In some installations, this could be bad, as the installing engineer may not be able access the station remotely, or it may be difficult to reboot the UNC. Beginning with release 2.305.516, the BACnet service can be programmed to maintain its routing functionality even with such network problems. Do this by editing the bacnet.properties file in the host with the following line:  maintainRoutingEnabled=true. Note that after editing this file, from the BACnet service, issue the menu bar command "readBACnetPropertiesFile" to make changes effective.

Issue No alarms are displayed in the Niagara R2 Alarm Console. Environment Niagara R2 Cause Generally, this condition indicates that the Alarm Console is not properly configured with the Niagara station information. Resolution To configure the Alarm Console: Open the Alarm Console From the Address menu, select Enable Edit Type the appropriate password to enable editing (by default, this password is blank) From the Address menu, select Add Address. An input dialog is displayed that allows entry of the new station address record information In the Station Name box, type the name given to the station node that will be monitored In the Host Address box, type the computer name running the station. Use either the station host name or the actual IP address of the computer In the User Name box, type the user name for a user account that exists in the station. Typically, this is the same name (user account) used to access the station in WorkPlace Pro In the Password box, type the password for the station’s user account In the Confirm Password box, type the user’s password again to confirm it Click OK Click the Stations tab to verify that the new station address record was added to the Address Book. Note that if the new station address record appears red, a restart of the station is required for alarms to be routed to the console

Issue Does Niagara R2 keep track or log the number of times a graphic page is accessed? Environment Niagara R2 Cause Graphics viewed are not store in the audit or event logs.  Resolution Accessing a graphic (GX page) does not create an entry in the audit or event logs. However, changes made to a graphics page are recorded in the audit tables.

Issue What are the System Requirements for installing MSDE or MSSQL server with a Niagara R2 Enterprise Server? Environment Niagara R2 Enterprise Server MSDE or MSSQL server Cause Hardware and Operating System (OS) must meet the minimum requirements to run MSDE or MSSQL server. Resolution These are the following minimum hardware and operating system requirements (per Microsoft’s web site) to run the MSDE database: • Pentium III, 500-MHz or higher processor. • Minimum of 512 MB of RAM, 1 GB recommended. • Minimum of 1 GB of available hard disk space, 3 GB for applications that need more archiving capacity. The following operating system configurations can run the MSDE: • Windows XP Professional • Windows NT Workstation 4.0 with Service Pack 5 or later Supported Software Supported Database Implementations • Windows NT Server 4.0 with Service Pack 5 or later • Windows NT version 4.0 Server Enterprise Edition with Service Pack 5 or later • Windows 2000 Professional • Windows 2000 Server • Windows 2000 Advanced Server Microsoft asserts that the SQL Server 2000 Driver for JDBC (required for MSDE) has been tested and certified on the following operating systems: • Microsoft Windows XP • Microsoft Windows 2000 with Service Pack 2 or higher The following versions of the JDK are supported for use with the SQL Server 2000 Driver for JDBC: • JDK 1.1.8 • JDK 1.2 • JDK 1.3 The Microsoft SQL Server 2000 Driver for JDBC is available for download from microsoft.com to all licensed SQL Server 2000 customers at no charge. Review the end-user license agreement (included with the download) for further details on users’ rights. Note:  A MSDE database can run on a machine other than the Enterprise Server and have the server station write data to the database. For information on the system requirements for a remote MSDE installation, visit http://msdn.microsoft.com/library. This configuration is not supported by Schneider-Electric. 

Issue Can the Niagara R2 UNC-410 support an ASD network? Environment Niagara R2 UNC-410 ASD network Cause The UNC-410 does not support ASD communications because the RS-485 ports are not electrically isolated. Resolution Here is a list of all the Communication ports available on the UNC-410: Communications - all Versions One 10/100 Mbit Ethernet RJ-45 connector. One non-isolated RS-485 bus (up to 76.8 Kbaud). One RS-232 port, RJ-45 connector. One LonWorks port – 78.8 Kbaud FTT-10A with Weidmuller connector (maximum of 27 devices). Options Optional UNC-410-MDM Internal Auto-dial /Auto-Answer 56k modem (p/n UNC-410-MDM); RJ-11 connector for North American applications (uses RS-232 port when installed). For further information consult F-27322