Building Automation Knowledge Base

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 When running Sigma 4.05 with a backup from a previous release of Sigma, the DeviceCnf.rec file is being over-written with a default DeviceCnf.rec file Environment Sigma 4.05 Cause The DeviceCnf.rec and gencnf.rec files use a different format in Sigma 4.05 than previous releases. Resolution When Sigma 4.05 checks these files and finds there not correctly formatted it automatically replaces the DeviceCnf.rec file with a default or blank file. Use the file C:\sigma\bin\SigUpgrade.exe to upgrade your data files to the correct formatting for Sigma version 4.05.

Issue Is it possible to replace a Xenta 400A I/O module in a LonMaker based project without a program download? Environment LonMaker Xenta 421A, 422A, 451A, 452A I/O Modules Cause There is an option in the system plug in that decides how the addressing of the I/O module is handled. If the checkbox "Xenta I/O modules commissioned with LNS" is checked (this is called preconfigured in the old NDB tool and in XBuilder), the Xenta starts communicating to the I/O module using the subnet node address it has been given by the network tool (Lonmaker).  If the Checkbox is not checked, the Xenta will communicate with the I/O module on the neuron ID first to give the module the address that it thinks it should have. Resolution If the checkbox "Xenta I/O modules commissioned with LNS" is checked in the System Plug-In, and you replace the module in LonMaker, you do not have to download the Xenta. If the checkbox is not checked (the I/O module does not need to be commissioned in LonMaker), you have to download the controller or you can add the I/O module using the OP.

Issue Copying the SHTTXT.REC file back onto a Sigma system into its correct location.. Environment Sigma server all version 4 releases. Cause Copying the SHTTXT.REC file into the incorrect location will prevent the short texts from being shown when an object is displayed. Resolution In the later versions of Sigma 4.0? there are two copies of the SHTTXT.REC file. The first SHTTXT.REC is located in the C:/Sigma/Data/Locality/English United_Kingdom (IF UK)/ folder and is used by Sigma. The second SHTTXT.REC file is located in the C:/Sigma/Data/ folder and is a copy used by SigmaX. When copying the SHTTXT.REC file back onto a Sigma system, it should be copied to both locations.

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 Does the Xenta 555 update the time on MicroNet controllers under its LAN? Environment Xenta 555 MicroNet Controller Cause Time sync to Xenta 555 Resolution Yes, the Xenta can update the controller times. The Xenta utilizes a NTP (Network Time Protocol) server. A TCP/IP protocol used to synchronize the real-time clock in computers, network devices and other electronic equipment that is time sensitive.

Issue When running Sigma 4.05 on an laptop that is also running VMware to minimize or close the application can take up to 5 seconds. Environment Sigma 4.05 VMware Cause Require to run the SetSigmaForVMware.exe Resolution The utility SetSigmaForVMware.exe has been developed to prevent the delay, but must be used on Schneider-Electric engineering laptops only. This applies to normal Windows and the VMware version where Sigma 4.05 is loaded. Download SetSigmaForVMware utility.

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 How can I see more than three property windows when programming a controller with VisiSat. Environment VisiSat MN50 Series controllers Cause The default amount of property windows allowed is set to 3. This can be changed if required in the “settings.ini” file for the project. Resolution Default = "Number of Property Forms=3" Changing this to "Number of Property Forms=9" allows you to have 9 property windows.

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 BACnet Programs Disable on a Reload This is an issue that will be addressed, but in the meantime an explanation of how this happens and a workaround is provided below. Environment Infinity Program in a Continuum Bacnet controller Cause How this happens: Create an Infinity Program in a Continuum Bacnet controller and then right click on the folder directory located under the controller you just created it under on the Infinity side. Now make sure there are two columns in the listview named State. You will most likely have to add one or both of these columns and make one of the columns source LIVE and the others source Database Notice when you run the listview both State columns will reflect Enabled for your running program. Now, perform a find new bacnet devices if you haven't already and then perform a send to database on the controller you just created the Infinity Program under. At this point go back and either run or refresh your listview we ran earlier and notice the Infinity Programs State attribute is set to disabled in the database view. At this point if you reload your controller in the Infinity side it will disable the program. Resolution Workaround on how to avoid this issue After a newly created program has been sent to the database on the Bacnet side, immediately run the listview we created earlier and Highlight either all or only the programs that are set to disable for the State attribute where the source is set to Database. Once you have selected the rows of the programs you want to set to enable, select the Edit menu item in the listview. Now select set attributes.. and in the drop down select State for the name and enter Enabled for the value and select OK. This will allow the program's to be reloaded without being disabled.  Most sites will never see this issue, since most will load up their controllers and back up the flash on the controller before performing a find new bacnet devices and send to DB on the bacnet side After controllers repower or reset the programs are just loaded back from flash. But the sites that reload their controllers will see the reload and programs disable issue. But like any reloading, you should always check your programs and alarms before leaving the site.

Issue Web Pinpoint displays different animation file(s) while Cyberstation's pinpoint displays correct animation files. Environment Cyberstation graphics Cause This issue happens when you create pinpoint graphics with different animation controls using the same animation file names. Although the files that are named the same are from different folders, Web pinpoint will not distinguish one file from the other. Resolution In order to provide faster response to Remote PC's WebPinpoint graphic, Continuum WebClient server caches animation bitmap files in a subfolder (..\Temp\Animation) under the graphic folder. As the file name is the unique key in the cache folder, it is required to use unique names for each animation bitmap file if the files contain a different animation control on a graphic. For example, first graphic displays a Fan animation with 4 bitmap files named as FAN1, FAN2, FAN3, FAN4 from below folder; C:\...\NewGraphicsFiles\ImageLibrary\Animation\FanGroup1\FAN1.bmp C:\...\NewGraphicsFiles\ImageLibrary\Animation\FanGroup1\FAN2.bmp C:\...\NewGraphicsFiles\ImageLibrary\Animation\FanGroup1\FAN3.bmp C:\...\NewGraphicsFiles\ImageLibrary\Animation\FanGroup1\FAN4.bmp And the second graphic displays a Fan animation with 4 bitmap files named as FAN1, FAN2, FAN3, FAN4 from below folder; C:\...\NewGraphicsFiles\ImageLibrary\Animation\FanGroup2\FAN1.bmp C:\...\NewGraphicsFiles\ImageLibrary\Animation\FanGroup2\FAN2.bmp C:\...\NewGraphicsFiles\ImageLibrary\Animation\FanGroup2\FAN3.bmp C:\...\NewGraphicsFiles\ImageLibrary\Animation\FanGroup2\FAN4.bmp It is required to change the file names for the second graphic to be unique as below; C:\...\NewGraphicsFiles\ImageLibrary\Animation\FanGroup2\FAN5.bmp C:\...\NewGraphicsFiles\ImageLibrary\Animation\FanGroup2\FAN6.bmp C:\...\NewGraphicsFiles\ImageLibrary\Animation\FanGroup2\FAN7.bmp C:\...\NewGraphicsFiles\ImageLibrary\Animation\FanGroup2\FAN8.bmp

Issue Problem with Continuum controller being used to poll EMon Class 3000 MODBUS RTU Meters The Controller was unable to poll all of the meters installed on the field bus. Environment Continuum controller being used to poll EMon Class 3000 MODBUS RTU Meters Cause When connecting multiple Class 3000 meters to a field bus, ONLY the last Class 3000 meter in the field bus string should have the biasing resistor pack installed. Having multiple termination resistors will load the bus down. Resolution All other biasing resistors should be removed from J17 on meters attached to the field bus. If there is still a problem Change the E-Mon "key2000" to the RS232 protocol. Using the E-Mon Repeater will provide a stronger RS-485 signal to drive their devices. Put the X-Driver on an RS-232 port of the controller.