Building Automation Knowledge Base

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 How can two controllers of different types be assigned the same program ID? Environment Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta Cause This is because of how the LonMark Standard program ID is generated. Resolution The LonMark standard for generating the Program IDs is based on what SNVTs are present in the application. Two .MTAs may have the same types and number of SNVTs included in the LonMark set, regardless of controller type, and therefore the program IDs can be generated the same. The other possibility is that two programs just happen to get the same IDs because there are only so many possible combinations of SNVTs that 255 combinations reduced the number of unique IDs. Using the check box option "XIF-Header generated according to LonMaker standard" will use only 255 (or FF in Hexadecimal) combinations of IDs. By un-checking the "Generate Program ID's according to LonMark Standards", 65535 (or FFFF in Hex) combinations can be assigned. This makes it much more likely that the IDs will not conflict. Adding a dummy SNVT to one application and regenerating the ID (leaving the LonMark option checked), is another option to resolve the conflict.

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

Issue There are multiple versions of Niagara R2 software installed on a computer (i.e. 4.31, 5.14, 5.22, 5.29).   Stations will not open with the older versions. Environment Niagara R2 Cause By default, the Niagara service for the most recent version (e.g. 5.14) will run when a computer is started. And only one instance of the Niagara service can run at a time. Resolution In order to open stations with the older versions, the Niagara service for the appropriate version must be installed and running. To install the service for an older version (i.e. 4.31): Open the Console for the desired Niagara version (Start > Programs > Niagara 2.301.431.v1 > Console In the Console window, type the following: admininstall install /start If successful, you will see the following responses: Niagara service successfully installed. Niagara service successfully started. Now, stations will open using the older releases.

Issue If there is a routing problem with a MNB-1000, how can the routing table be cleared? Environment MNB-1000 Cause The MNB-1000 controller need to relearn the network information. Resolution Anytime there is a routing loop or a network mis-configuration on a BACnet internetwork containing MNB-1000 controllers, it is possible to get a network mismatch displayed in the status column of the WorkPlace Commissioning tool. Because the MNB-1000 controller has learned the mis-configured network information, its routing tables will have incorrect information. Currently, the only way to remove this information and fix the problem is to correct the network mis-configuration and reboot the MNB-1000. Upon restarting the MNB-1000 controller, if the problem still exists the network mismatch will still appear in the status column, indicating that the problem is not resolved. If the problem is resolved this message will not display.

Issue A connection to a Niagara R2 station (UNC or Enterprise Server) using a web browser, is desired, without the pop-up window prompting for a username and password.  Is there a way to incorporate this information into the URL? Environment Niagara R2 station Web browser Cause Accessing Niagara R2 via web browser without entering username and password require \\[user]:[password]@[host]:[port] in the address bar of the web browser. Resolution In the Address Bar, type in the following: \\[user]:[password]@[host]:[port] where: [user] = the user name of the station [password] = password used to log into the station [host] = IP address or name of the desired station [port] = the http port of the station (note: if using the default port of 80, the port number is not required) NOTE: The ability to incorporate user name and passwords in a URL link is DISABLED by default in Internet Explorer versions 6 and later. In order to enable this feature, add the following to the Registry: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_HTTP_USERNAME_PASSWORD_DISABLE] "explorer.exe"=dword:00000000 "iexplore.exe"=dword:00000000 "SampleApp.exe"=dword:00000001 WARNING: Making incorrect Registry changes can cause serious problems that may require the re-installation of the operating system. If unfamiliar with making Registry changes, please contact Product Support Services for assistance.

Issue What are the default heartbeat values for the MNL controllers? Environment MNL controllers. Cause Reset heartbeat values to default values. Resolution The default values are: nciSndHrtBt=120sec nciRvHrtBt=300sec nciMinOutTm=5sec For further information on these values consult the WorkPlace Tech Tool 4.0 Engineering Guide (F-27254)

Issue What are the supported speeds for the Ethernet port on a Niagara R2 UNC? The UNC is not communicating at 100Mbps Environment UNC Cause The Ethernet port on a UNC is auto sensing - meaning it gets its speed and duplex settings from the device (hub or switch) into which it is plugged. The UNC is capable of supporting 10 or 100 Mbps, full or half duplex communication over the Ethernet port. Presently, gigabyte speed is NOT available on the UNC. Resolution If the UNC is not communicating at 100Mbps and full duplex, the most likely causes are: The hub or switch does not support 100Mbps / full duplex communications There is a problem with the wiring between the UNC and the hub / switch.

Issue What components make up the LON-TERM1 and LON-TERM2 terminators? Environment LON-TERM1 terminator LON-TERM2 terminator Cause LON-TERM1 and LON-TERM2 terminators are required for MicroNet LonWorks network topologies. Resolution The LON-TERM1 uses a capacitor in series with a resistor with each part having the following specs: Resistor E19-607 52.3 ohms, +\- 1%, 1W, MF Capacitor E13-468 47 uF, +\- 20%, 50WVDC, Elec The LON-TERM2 uses a capacitor in series with a resistor with each part having the following specs: Resistor E19-608 105 ohms, +\- 1%, 1W, MF Capacitor E13-468 47 uF, +\- 20%, 50WVDC, Elec

Issue How can it be determined if a specific LON device is supported by the Niagara R2 system? Environment Niagara R2 LON devices Cause Obtain a list of supported LON device for references. Resolution A list of all supported LON devices for a specific release of Niagara R2 can be created by performing the following steps: Open Workplace Pro and create a new local station with the default services and the "LonWorks Service". Start that new station on "localhost". Open the station "localhost" in the tree view of Workplace Pro. Right-click on the "LonWorksService" under the station you just opened and select "LonUtilitiesManager". In the "Lon Utilities" window, select the Device: LocalLonDevice, Command: reports, SubCommand: programids and click the Execute button at the bottom of the window. The displayed list shows all the devices (including program ID) supported by each manufacturer's Lon jar file.  For example, the Siebe entries in the list will display all the standard MNL series devices and their corresponding program IDs. Shadow objects for each of these devices are listed by "Class name" in the LonSiebe jar file (shown under the siebe entry in the londevices under the tridiumx local library). 

Issue When the WorkPlace Commissioning Tool browses a network or internetwork, not all controllers on the network will be found. Environment WorkPlace Commissioning Tool Cause Increase the reply timeout value in WorkPlace Commissioning Tool Resolution If controllers are missing from the list, the recommendation is to Refresh the list after the first attempt  Increase the reply timeout value in the WorkPlace Commissioning Tool to 40,000 milliseconds or greater. With large quantities of controllers (for example 80 or more), wait for the entire reply timeout value to expire for the list to stabilize.

Issue When using Link Builder in the WorkPlace Commissioning Tool, a change to the COV Client Subscription Lifetime to large minute increments (i.e. 60 minutes), is rejected. Environment WorkPlace Commissioning Tool Cause Incrementing the current values in large minute is known to create an issue, implement the below work-around to increase the lifetime value. Resolution The work-around for this issue is to change the COV Client Subscription Lifetime from its current value to the next incremental value (up one minute) and then to the desired value (i.e. 60 minutes).

Issue Miscellaneous fixes in Workplace Tech 5.5 and 1.4 controller firmware. Environment Workplace Tech 5.5 1.4 controller firmware Cause Require detail on what miscellaneous fixes in Workplace Tech 5.5 and 1.4 controller firmware. Resolution Visio 2003 generates an error and crashes when attempting to save a Visio drawing outside of the WPT environment.  In WPT, the existing application tab in the add application to project dialog area is unable to open and add an existing application drawing. The MNB-1000 will reset in response to a read or write request for the profile_name property or background BACnet object. Cannot read/write background BACnet AO, Floating Actuator or PWM object in MNB-1000. AppLED stops updating in the MNB-1000. Sometimes an unsupported property response when reading BI object name in the MNB-1000. Power up delay object did not work correctly in the MNB-1000. Single and sequence loops incorrectly calculate output.  This issue was found when single and sequence loops were set up with large throttling ranges and had a small positive deviation from setpoint. During these conditions, the output of the loop would intermittently go to 100% output and then return to normal operation. This issue applied to MNB-1000, MNB-300 and MNB-Vx controllers. Interstage delay fails after power cycle causing outputs to come on after controller power cycle of MNB-1000.  Dual delay object may be in incorrect state after controller power cycle of MNB-1000.  There was an issue found where the Dual Delay had a 50/50 chance of coming up in the correct state after a power cycle.  Control object RAM not initialized correctly after a download of an application. Floating Actuator object may oscillate at 22.22 and 66.77% output. This issue was reported in MNB-1000, MNB-300 and MNB-Vx. BACnet flow balance values except BoxFlow can sometimes show error.  COV increment property of the VAV Actuator object does not take effect. Using the MN-Sx sensor to change temperature calibration does not work when temp calibration is set to NA from WPT or a BACnet tool and can lock up S-Link communications for MNB-300 and MNB-Vx controllers Overridden and Out_Of_Service flags for PWM and momentary SS objects not previously supported in MNB-300 and MNB-Vx controllers. COV increment property not previously supported for BI count output of MNB-300 and MNB-Vx controllers.

Issue Will Niagara applications run on Dual Core / Duo Core / multiprocessor computers? Environment Niagara Computer with (Dual Core / Duo Core / multiprocessor) Cause Knowing the processor spec requirement helps assess existing computer for installing Niagara applications. Resolution Currently, Workplace Pro / Enterprise Server and Workbench / Enterprise Network Server will run on Dual Core / Duo Core  / multiprocessor computers. These programs were designed to use only one of the processors, leaving the other processor(s) available for other applications. Other software (i.e. WorkPlace Tech) has not been validated on these types of computer systems. Therefore, these systems should be avoided since there would be no way to confirm proper functionality for each application. It is recommended that dual-processor and multi-processor computers as well as computers utilizing Intel Pentium 4 processors supporting Hyper-Threading Technology (when this processor feature has been enabled in the computer BIOS) be avoided for all company software for both server and client workstation applications. For more information read Technical Bulletin TB04-07-01

Issue How to modify the setting "initString" to change the number of rings for auto answer for a Niagara R2 UNC-520 internal modem Environment Niagara R2 UNC-520 Cause The Ring to Auto-Answer can't be change. Resolution The UNC-520 is shipped with factory defaults to pick up on the first ring. The internal modem does not answer, a service answers the call.  As a result, the "Ring to Auto-Answer" parameter is NON configurable.