Building Automation Knowledge Base

Issue How can the Niagara G3 ENC platform be accessed if the user name and password have been forgotten? Environment Niagara G3 ENC Cause Forgot username and password for the Niagara G3 ENC. Resolution To connect via the serial port of the ENC you will need a UNCC-405, an Ethernet cable 7' or less, and Hyperterminal (or another terminal program). In the upper right corner of the ENC-520 is a block of four pins marked J4 Mode. Using one of the bias jumpers from the board, temporarily short the front two pins. Using the UNCC-405 and short Ethernet cable connect the laptop to serial port one of the ENC. Open HyperTerminal and configure a connection as 57600, 8, none, 1, no flow control. Reboot the ENC. When this appears: "Press ESC to restore factory default username and password...", go ahead and press the ESC key. Enter "y" when prompted to force the platform user name and password back to "tac" and "niagara". After using WorkBench to verify the user and password have been changed, remove the jumper and disconnect the serial connection.

Issue A Niagara R2 / BACnet integration station, running on a computer, can interfere with the WorkPlace Commissioning Tool. Environment WorkPlace Tech  Commissioning Tool (WPT CT), any revision I/A series R2 / BACnet integration station running on the same pc as the WPT CT Cause Communications port or driver conflict between WorkPlace Tech  Commissioning Tool  and the I/A series R2 / BACnet integration station. Resolution A Niagara R2 / BACnet integration station can interfere with the WorkPlace Commissioning Tool (WPCT), by disrupting communications between the WPCT and MNB controllers. One symptom of this interference is that while the WPCT can find some or all of the MNB controllers, their property sheets will not be fully populated with data. In such a case, the WPCT might be displaying data from a default template, rather than live data from the controller. As a best practice, check to be sure that the General tab of the device's Properties sheet is populated before going to any other tab. If the Firmware and Application fields of the General tab have not filled in, then the tool is not communicating with the controller, and the other tabs will contain default data, not current values from the controller. To insure that a Niagara R2 station is not running in the background on the computer follow these steps: Go to the Computer Management by right-clicking on My Computer Select Manage from the pull-down menu. Go to Services and Applications, then Services. Stop the Niagara service. Typically, the Niagara service will be configured to start automatically when the computer is rebooted.

Issue A Network 8000 LNC-100 cannot communicate to LON devices under it even though all the devices can be accessed with WorkPlace Tech or a LON commissioning tool. Product Line TAC IA Series Environment NETWORK 8000 LNC-100 LON devices WorkPlace Tech Cause If the LON network is known to be good and otherwise functioning, this issue indicates a problem with the LON interface in the LNC-100. This is typically caused by accidentally attempting to commission the LNC-100 using LonMaker or other LON commissioning tool. Attempting to commission the LNC-100 will result in its LON interface being set into a network state called HARD - OFFLINE. Resolution The condition can be corrected using the Echelon NODEUTIL program to set the interface network to the required CONFIGURED - ONLINE state. NodeUtil can be downloaded from The Exchange Download Center. After downloading NodeUtil to your computer, open a command prompt window and launch NodeUtil in that window.  After launching NodeUtil, perform the following steps to correct the problem. Press the F key to execute the Find function.  This will browse the connected LON network for all attached LON devices.  In the list of found devices, the LNC-100 will be identified with the program id "C 1 11.0A". Press the G key to execute the Go To Device function.  Enter the device number of the LNC-100 (program ID "C 1 11.0A") as displayed in the list of discovered devices.  The device menu will then be displayed. Press the S key to display the status of the device.  Typically 17 lines of status information are displayed followed by the "Device Status" menu.  Press Y to clear the error status.  The "Device State" line will usually show a state of either Configured, Off-line or Hard, Off-line. Press the  M key to change the device mode and state. After selecting the M command, the list of mode options is displayed.   Press the S key to select the State menu. The list of State options will be displayed.  Press the C key to set the device to the Configured state. A status message will be displayed followed by the DEVICE prompt. Press the M key again to display the Mode options then press N to set the device into the OnLine mode. A status message will be displayed followed by the DEVICE prompt. Press the S key again and verify that the Device State is now Configured, On-line. Press the D key to display the domain address table of the LNC-100.  One or two lines of device domain address information will display.  If two domain addresses were defined in the SYS: SIM block of the device, two lines of information will display, otherwise only one line will display.  Verify that the address information (Subnet, Node and Domain ID) are as set in the SYS: SIM block. The data entered for Domain0, Subnet0 and Node0 will be displayed on the Index 0 line. The data entered for Domain1, Subnet1 and Node1 will be displayed on the Index 1 line. Press the E key to exit the Device level and press the E key a second time to exit the program.

Issue The Wonderware Temporary License is out of date. How can a new one be obtained? Environment WonderWare Cause Since Schneider Electric (Rockford) is no longer a Wonderware OEM software distributor, demo licenses can no longer be provided. Resolution The 30-day temporary Wonderware demo mode license is available to the Wonderware SI selling the Wonderware software.

Issue A previously functional MNL controller is not communicating and the RED LED is on solid. Environment MNL controllers - all revisions Cause Internal hardware failure Resolution The solid RED LED indicates that the LON processor Neuron application is not running. This is a hardware failure and is not field repairable. Replace the controller.

Issue A Niagara R2 / Lonworks integration station running on a computer  can interfere with WorkPlace Tech, by preventing its access to the LON card. Environment Niagara R2 WorkPlace Tech Cause LON adapter not working with WorkPlace Tech on a pc installed with WorkPlace Pro Resolution One symptom is if attempting to download and the dialog box indicates “loading device driver”, followed by the box with the hand. The hand is not moving and is followed by an error, “waiting for service pin.” A Niagara station with autorun enabled can be running in the background without the user being aware of it. To insure that a Niagara R2 station is not running in the background on the computer, follow these steps: Go to Computer Management by right-clicking on My Computer Select Manage from the pull-down menu. Go to Services and Applications, then Services. Stop the Niagara and Niagara LON Tunnel services. Typically, the Niagara and Niagara LON Tunnel services will be configured to start automatically when the computer is rebooted.

Issue MNL-800 ramp object step change does not function if time value set greater than 164 seconds. Environment MNL-800 Cause The ramp object configured as "step change" incrementally increases or decreases the output at the level and rate defined by the step level and time values. The ramp will not perform the "step change" function if the time value setting is greater than 164 seconds. Resolution The workaround involves decreasing both the step level and time values by a common factor to obtain the overall result in the original timeframe required. For example, a step change of 1 every 1000 seconds can be performed with the same results if using a step change of 0.1 every 100 seconds.

Issue When using PSI 4.1 in direct connect mode, the baud rate is modified and saved but it will not communicate at the new rate. Environment PSI 4.1 Cause A baud rate change in PSI direct connect mode does not take affect until the PSI program is closed and restarted. Resolution Closed the PSI program and restart the program for the new baud rate to take effect.

Issue Cannot resolve WorkPlace Tech licensing problem - "License Registry is Corrupt." This applies to all versions. Environment I/A Series WorkPlace Tech Cause This issue occurs when a user that does not have "Local Administrative Rights" on the Windows operating system installed in the computer. When the license is repaired by Product Support Services and reloaded on the computer, the problem will reappear when the user attempts to start WorkPlace Tech. Resolution There are two different procedures that can be used to correct this problem: Procedure 1: If the computer is on a Windows Domain and the user has only normal user rights on the computer, an administrative user with Domain User rights can add the user's domain account to the "Local Administrators Group" on the computer.  When this is done, the user will continue to have only normal user rights on the Windows Domain but will have the privileges of an administrator on the local computer.  This allows the WorkPlace Tech (and any other software) on that computer to be run with local administrative privileges. Procedure 2:  Create a new local computer user account and place this new user account in the Administrators group. Hold down the shift key then right-click on WorkPlace Tech, either by selecting its Icon on the desktop or selecting it in the system Start menu. In the menu that is displayed after right-clicking, select "Run as Administrator". When prompted, enter the name and password for the user created in step 1.

Issue MNB controllers wired to the MSTP trunk of a MNB-1000 do not show up in the WorkPlace Commissioning Tool when connected via BACnet/IP. Environment MNB-1000 WorkPlace Commissioning Tool Cause Settings and configuration on the MNB-1000 and WorkPlace Commissioning Tool. Resolution Ensure that the MNB-1000’s MS/TP trunk is enabled. Ensure that the MNB-1000's MS/TP network number is entered.  Ensure that the Max Master count under the MSTP tab of the MNB-1000 is set with a number that is two more than the total number of controllers on the MSTP trunk. The MSTP addressing should have no gaps. Also, set the “Browse Settings” to Global. The setting is located under File > Connect > Advanced menu of the WorkPlace Commissioning Tool. When the browse setting is configured for local, not all devices on all BACnet networks will display.

Issue What is the voltage used on a universal input (UI) on a MNL-20Rx controller? Environment MNL-20Rx Controller Cause Information on the input types the MNL-20Rx Controller accepted. Resolution UI circuits output (5.0 Vdc) and are designed to process the following input types: 1K Balco RTD, 1K Platinum RTD, 10K thermistor with 11K shunt resistor, Voltage 0 to 5 VDC, Current 0 to 20 mA with external shunt, 0-1K resistance range, 0-10K resistance range, and a digital contact closure. For resistive type inputs, the microprocessor controls an internal multiplexer that switches and pulses the various current sources to the various UIs during the analog to digital (A/D) process. The circuit does not apply a constant current to the sensor on a continuous basis. A voltage value will be read across the resistive sensor.  However this reading is not accurate due to the pulse methodology. The current pulsed to the sensors depends upon the range. The 10K thermistor with 11K shunt resistor is pulsed with 0.45 mA and the 1K RTD sensors (e.g. Balco and Platinum) are pulsed with the 3.1 mA current source.

Issue Can the Echelon U10 USB interface function with the MicroNet VAV Flow Balance program (revision 3.0) for LON? Environment Echelon U10 USB MicroNet VAV Flow Balance program (revision 3.0) Cause The MicroNet VAV Flow Balance program will only function with an interface configured for LON1.  If a PCMCIA card is installed on the computer, it is probably already set up for LON1. Resolution To use the Echelon U10 USB interface: Uninstall the PCMCIA card first Ensure the Echelon OpenLDV 3.4 Driver is installed If the U10 USB interface was previously installed and it was not recognized as LON1, remove any traces of it: Disconnect the device Open the "LonWorks Interfaces" in Windows control panel On the "USB" tab, check "Show detached interfaces" to view the previous USB devices. Highlight and remove all interface instances. In the system device manager, delete any Echelon devices that may still reside under the Universal Serial Bus Controllers. When plugging in the U10 USB interface, it will be recognized as the first Lon device LON1.

Issue When using WorkPlace Tech and Niagara G3 LON tunneling through an ENC, just a few devices are found and they are displayed slowly. Environment WorkPlace Tech Niagara G3 LON Cause This is a symptom of a bandwidth issue with Lon trunk communications. The LON polling function can be a high contributor to the bandwidth, and disrupt Lon Tunnel communications. Resolution By default, the "Poll Enabled" feature in an ENC is set to true in the Poll Service (located in the Property sheet of the Lon Network). If bindings are being used, polling can be disabled, which should free up enough bandwidth for Lon Tunneling. For more details, see the Niagara LonWorks Guide "Lon Poll Service notes" page 3-6.

Issue Why is the Niagara G3 Time Sync Service not working with time.nist.gov? Environment Niagara G3 time.nist.gov Cause As of April 2007 the server time.nist.gov no longer responds to requests for time in the "Time Protocol" format defined in RFC-868. Resolution As an alternative, try time-a.nist.gov or time-b.nist.gov As of April 2007 the server time.nist.gov no longer responds to requests for time in the "Time Protocol" format defined in RFC-868. All of the other NIST servers (except for time-nw.nist.gov) will continue to respond to requests to either tcp or udp port 37 for time in the format specified in RFC-868. "Time Protocol" used by the TimeSyncService has been superseded by a more sophisticated and more accurate one known as "Network Time Protocol" (NTP for short) defined in RFC-1305 The newer protocol is supported in Niagara G3 version 3.4 and newer and it is configured through the platform service of the station.

Issue What is the current firmware revision for a Network 8000 GCM and is an upgrade kit available? Product Line TAC IA Series Environment Network 8000 GCM Cause Looking for a firmware upgrade part number. Resolution The following table lists the part number and upgrade kit part number for the system firmware installed in each version of the GCM, LCM and similar type controllers. The listing of a particular device part number, EPROM part number or Firmware Upgrade Kit part number does not guarantee that the specific item can be ordered. Update - 12/31/2011 - All firmware kits listed below are now obsolete and can no longer be purchased. GCM / LCM Model Current Version EPROM Part Number Firmware Upgrade Kit GCM-84x1x (GCS Version) 5.4 PROM-12-100/200/300 GCMA-120-054 GCM-84x2x (ASD Version) 5.41A PROM-12-120/220/330 GCMA-137-054 GCM-85x1x (GCS-CCL Version) 4.7C PROM-12-110/120/130 GCMA-132-047 GCM-85x2x (ASD-CCL Version) 4.7AC PROM-12-140/240/340 GCMA-141-047 GCMA-114 4.2 PROM-19-100 GCMA-130-042 LCM-84x1x (8k EEPROM) 5.4 PROM-23-100/200/300 LCMA-138-054 LCM-85xxx (CCL Version) 4.7C PROM-23-110/210/310 LCMA-141-047 LCM-88x1x (32k EEPROM) 5.4 PROM-23-100/200/300 LCMA-138-054 GCS-xxxxx 4.0 PROM-18-120 GCSA-103-040 GIM-2100 4.7G0 PROM-12-130/230/330 GCMA-140-047 GIM-MTECH 4.8G2 PROM-12-150/250/350 GCMA-143-048 GCM-ECH-002 (Echelon NIM) 11.1B PROM-48-204 GCMA-147-111 GCM-86x11 (GCS Version) 5.4 PROM-41-100 GCMA-145-54 GCM-86x21 (ASD Version) 5.4A PROM-41-110 GCMA-146-54 GCM-ECH-001 (Echelon NIM) 11.1B PROM-48-203 GCMA-148-111 GCM-ETH-001 (Ethernet NIM) 11.2T PROM-48-202 GCMA-149-113 LNC-100 5.4GL PROM-41-160 LNCA-100-054 SIM-CCM 5.4G3 PROM-41-120 SIM-CCN-U SIM-MTECH 5.4GM PROM-41-150 SIM-MTECH-U SIM-TRANE 5.5GT PROM-41-140 SIM-TRANE-550 SIM-YORK 5.6GY PROM-41-130 SIM-YORK-U

Issue When using WorkPlace Tech on a Windows Vista computer, the LON USB adaptor will not configure properly to work with my site. Environment WorkPlace Tech installed on a Windows Vista computer LON USB adaptor Cause The LON USB adaptor has a communication issue with both Vista and Windows 7. When configuring the LON communications via the automatic option in WorkPlace Tech, this error appears: "Error occurred in SetInterfaceDomain for domain index 0.” After this error, the LON interfaces will no longer function. Resolution A temporary work-around is to identify the domain and use the manual configuration option.  Echelon NodeUtil, Niagara R2 WorkPlace Pro, or Niagara G3 WorkBench can be used to identify the domain, if needed.  If the domain is "0", the "Default Setup" option can be used.

Issue It is possible to edit a database offline using the MNet-CI that is installed as a part of PSI 4.1? Environment PSI 4.1 MNet-CI Cause The templates and default database files are not installed by the PSI 4.1 installer.  Resolution The templates and default database files, PSIv4.10_MN-CI_Templates.zip can be downloaded from Extranet. Install the templates in the "mnetci" folder and the database folder in the PSI parent folder.

Issue Why doesn't BACnet/Ethernet work on a Niagara R2 UNC-600 or UNC-610 after upgrading to R2 version 529 (527 or higher)? ERROR: Cannot start Ethernet Packet Driver tridium.nre.DriverException: Cannot open \Device\RTL81391 [ethernet] Environment UNC-600 UNC-610 Niagara R2 version 527 or higher Cause New driver files were generated for BACnet/Ethernet to provide Vista compatibility. As a result, the driver files are unable to properly initialize the Ethernet packet driver on both the UNC-600 and UNC-610 platforms. The error can be viewed using the output window during the station start process. Resolution The solution involves the replacement of three files within the platform's R2 version 529 bin directory. File (UNC-6xx_BACnetEthernet.zip) contains the associated files and includes a readme.pdf with details on how to install on the UNC-600 and UNC-610 platforms.

Issue In Niagara G3, how can the status (up / down) of a device object be trended? Environment Niagara G3 Cause Recording a connected controller's communication status Resolution Within the Wire Sheet that contains the device shadow object: Insert a StatusDemux object (from the kitControl pallet, Util folder).  Link the "Status" from the device object to the "In Status" of the StatusDemux object Insert a Boolean Writable object.  Link the "Down" slot of the StatusDemux object to the "In10" of the Boolean Writable object Add a BooleanCov history extension to the Boolean Writable object.  This will then track the up / down status of the device.

Issue What is the preferred method of finding the MAC address of a Niagara R2 UNC? Environment Niagara R2 UNC Cause Determine the MAC address to set up the reserved IP address. Resolution The quickest and easiest method of finding the MAC address of a UNC is by way of the following: From a command window, ping the UNC using the following command: ping IP , where IP Address is the Internet Protocol Address of the known UNC.  After receiving the Ping Statistics, type the following command: arp -a The physical address will then be shown. *NOTE: All UNCs will have the following generic first four octets: 00-20-96-05. The last two octets will be specific to the Serial Number of the UNC.