Building Automation Knowledge Base

Issue Need to submit contents of a part of the information from the Standard Output Window to Product Support Services for troubleshooting assistance. Environment I/A Series (Niagara) R2 system (Enterprise Server or UNC), any version Cause Emailing or printing a print-screen capture of the Standard Output Window requires excessive email bandwidth or printer ink.  You may also need to do several screen captures saved as separate image files where the entire contents of the Standard Output Window could be saved to one much smaller text file. Resolution Copy the needed information from the Standard Output Window to the Windows clipboard as text and paste it into a text file or directly into the email message.  The procedure is as follows (Reference the image that follows). Click the "Pause" button to stop the information from scrolling.  Pause button is circled in green. Highlight the text to be captured.  Left click your mouse on the first line to be captured and hold the mouse button down while you drag the cursor down the window.  The window will automatically scroll if you continue to drag off the bottom of the window.  When all the required information has been highlighted, release the mouse button.  If you did not highlight the proper information, this process can be repeated. Click the "copy" button to capture the selected information to the Windows clipboard.  Copy button is circled in red. Paste the copied text into a text editor (Windows Notepad, Windows WordPad, etc.) or directly into the body of your email message.  

Issue Set the clock on an MNB-1000 Plant Controller Environment MNB-1000 Plant Controller Cause Needs to set the clock in the MNB-1000. Resolution Access the MNB-1000 controller via the WorkPlace Commissioning Tool then open the Properties page for that controller.  There are two ways to open the device properties page.  You can double click on the device in the device list or right-click on the device and select Properties.   The following window opens:   Figure-1: MNB-1000 Device Properties Window Click the [Device Clock] button (circled above).  The following pop-out menu is displayed:   Clicking the [Set Clock] selection will synchronize the clock in the MNB-1000 to the clock in the local computer.  The time and date will be updated on the screen (see highlighted section of Figure-1, above). Clicking the [Set Time Zone] selection will allow the user to specify the time-zone configuration for the MNB-1000.

Issue Cannot select LNS Database in Explorer after Browsing to the desired database. Can click on the LNS Database but it doesn't do anything. Correct way to add LNS Network to an XBuilder Project. Environment XBuilder Xenta Server LNS Network Cause Selecting an LNS network to add to an XBuilder project requires dragging and dropping the LNS network object rather than just clicking it Resolution In the Network pane of XBuilder expand the Xenta 5XX / 7XX / 9XX device to locate the LON port object. Right click the LON port object and select Insert Network from LNS... to open the TAC LNS Explorer. Drag the TAC LNS Explorer window to make the LON port object in the Network pane of XBuilder visible. In the TAC LNS Explorer select the File menu and select Open > Local LNS Networks. (This is assuming that the LNS network is on the local computer.) Identify the desired LNS network and click and drag it from the TAC LNS Explorer to the LON port object in the Network pane of XBuilder. The LNS network will then populate below the LON port object.

Issue Trying to serial tunnel with XPSI through an I/A Series G3 (Niagara) ENC, get error message: "Could not connect: tunnel unknown by server." Environment I/A Series G3 (Niagara) ENC with connected ASD bus PSI/XPSI software Cause The Tunnel Identifier in the ENC station and the Tunnel Name in the Niagara AX Serial Tunnel Client do not match. Resolution Copy the Tunnel Identifier from the ENC station and paste it into the Tunnel Name of the client to insure an exact match. Properties of the Psi Tunnel, under the AsdNetwork  

Issue How to configure Event Notification object to deliver event to BACnet client Environment CyberStation bCX4040 b3s Cause Delivery of Event Notifications to BACnet clients Resolution When adding a recipient in the Event Notification object check the BACnet Address check box then in the Recipient field specify whether the delivery will be a broadcast or sent to a specific destination. In the screen shot below, the notification will be delivered to the recipient with the MAC address 01 on the 2801 Network.

Issue Re-addressing I/A Series BACnet controllers on an existing BACnet MS/TP installation Environment I/A Series R2 BACnet integration to I/A Series Micronet BACnet Controllers Cause There are gaps in BACnet MS/TP addressing which needs to be fixed. Gaps in addressing add delays in communications. Addressing should begin with node 0 (zero) and progress through all nodes, without any gaps, for each separate MS/TP network. Refer to the I/A Series MicroNet BACnet Wiring, Networking, and Best Practices Guide (F-27360-7). Resolution The procedure to change the addresses of the MNB controllers involves the following steps. Changing the physical DIP switch address on the MNB controllers. Making sure the MAC Address of the BACnet shadow device object in the I/A Series R2 UNC reflects the change. Changing the Max Master property in each MNB controller using WorkPlace Pro. Alternatively, you can change the Max Master property using the WorkPlace Commissioning Tool. 1. Changing the physical DIP switch address on the MNB controllers Have a piece of paper ready to note down the physical DIP switch address before and after the change. DIP switch addressing should be sequential starting from ‘0’ with no gaps in between. However, the physical location of the device does not matter. For example, if we have 30 MNB controllers on the BACnet MS/TP network, the addresses should be from 0 to 29 but they do not have to be in order physically. As an example, the first MS/TP device could have an address of '0' while the second MS/TP device on the wire can have an address of '10'. The MNB-1000 should be address ‘0’ if it is the first MS/TP device. If the first MS/TP device is an UNC, the UNC should be address '0' (set in WorkPlace Pro). Use Table–2.3 to calculate the DIP switch value for physical addressing. Take, for example, that the address must be set to 16. To do so, you would set switch number 5 (value=16) to ON. If the address is to be set to 43, instead, you would set switches 1, 2, 4, and 6 to ON (value=1+2+8+32=43). The controller should reset itself about 10 seconds after the change and the new address will be in effect. 2. Check / change the MAC Address of the BACnet shadow device object in the UNC using WorkPlace Pro. After changing the physical DIP switch of the device, we will need to make sure that they change has been reflected in the corresponding BACnet shadow object device in the UNC. Using WorkPlace Pro, open the UNC station. Go to the Properties of the MNB shadow device object and go to the ‘Config’ tab. Make sure that the 'MAC Address' field is showing the new address (in HEX) of the controller. 3. Changing the Max Master property in each MNB controller using WorkPlace Pro. Each MNB controller under a particular BACnet MS/TP trunk needs to have their ‘Max Master’ setting changed. Set ‘Max Master’ to 1 or 2 higher than the highest address on the MS/TP network. If the highest addressed device is DIP switch value 50, set the Max Master to 51 or 52. In WorkPlace Pro, open the UNC station. Go to the Properties of the MNB shadow device object and go to the ‘Engineering’ tab. Change the ‘maxMaster’ to a value that is 2 higher than the highest addresses device. Click ‘Apply’.

Issue Updating a application specific controller with a later firmware version Environment NL220 Cause Enhancements in firmware version need to be implemented into existing controllers of older firmware versions Resolution Here are the steps to download a new APB or NXE file in NL220. Locate the controller you wish to update in NL220. Right mouse click and select "Copy configuration values to memory" Right click on the same controller and select  "Download Program" Browse to the new APB or NXE file you want to download Once the download is complete you can paste the configuration back into the controller. Right click on the controller again and select "Paste configuration value(s) from memory" The controller is now updated with the new application.

Issue This issue has symptoms as below: Blank page, No ID code or number displayed in login webpage and can not login to Xenta Server. Can not access Xenta Server via webpage. The following blank page is displayed: Login page is displayed, but project name and ID code or ID number are not: Environment Windows Server Environment TAC Vista 5.1.X Xenta Server Ver 5.1.X Cause Windows Server "Internet Options" Security Settings are not set properly. Resolution Need add the Xenta Server IP address into "Trusted Sites" in "Internet Options>>Security>>Trusted Sites". If didn't add the IP address into "Trusted Sites", blank page would display; If just "http://%Xenta Server IP address%" is added into the "Trusted Sites", would get login webpage which didn't include project name and ID code in the login page; Need remove "http://%Xenta Server IP address%" from "Trusted Sites", and add "https://%Xenta Server IP address%" into "Trusted Sites" list;   Then could get correct login webpage,  

Issue Is it possible to remove the folder tree and alarm pane from webstation? Environment Vista webstation 5.1.X Cause Certain users have access to graphics and nothing else. It would therefore be better to be able to maximize the graphic resolution and not see the other panes. Resolution The folder View and Alarm View can be removed by editing the DefaultPage.aspx file. The DefaultPage.aspx file can be found in the folder C:\Inetpub\wwwroot\TACVistaWeb51X.

Issue How can a setpoint programmed using a nci-type snvt, in a MNL controller, be controlled and displayed in a Niagara R2 station? Environment MNL controllers Niagara R2 Cause Site programming was done years ago and the end customer wants to now add the ability to change a setpoint in all the MNL controllers from a Niagara R2 graphic.  The setpoints were configured using a nci-type snvt (ex: nciSatConfig1). Resolution A nci-type snvt can be displayed and commanded from a Niagara R2 station. One method to provide both: In the DynamicCmd object > Config tab, set it up like this: Visual tab, set it up like this: In the UnitConversion > Config tab, set it up like this:

Issue Vista does not allow the user to edit standard graphics. Attempting to edit a standard object will result in the following error: Environment TAC Vista OGC Graphics Cause Vista does not allow the user to edit a standard graphic file within the vista database. A standard graphic is more of a shortcut to the master graphic in the root directory of TAC Vista Resolution Only make edits to the master graphic within the root directory of TAC Vista. This change will automatically be changed to all standard graphics associated to it.

Issue Host Lost Message Definition Environment I/NET Cause Host Lost messages are caused when I/NET has lost communication over the Ethernet LAN with a host workstation, Xenta 527 or NPR. Resolution Host masks are enabled or disabled by using the far left bit mask of group 1.  You can enable/disable these from showing up in AMT by: Open AMT Select Edit>Configuration Toggle the far left bit of Group 1 Click OK   Alternative Resolution Open I/NET configuration Modify the Active Profile Click Host Masks Modify Each Host Device Toggle the far left bit of Group 1

Issue How is Sigma Contingency logging enabled or disabled? Environment Sigma Contingency logging Enable Disable Cause Confusion about when Sigma Contingency logging is enabled. Resolution When a new Sigma object is created, Contingency logging is enabled automatically. Disabling Contingency logging. Ensure that the controller you are working on is online to the Sigma server. In the System manager, select the "Logging" menu and choose "Contingency Setup" The following dialogue box is displayed; Click on "Enable" to deselect Contingency logging, then choose "OK". Contingency logging is now disabled on this object. Enabling Contingency logging. Carry out the same procedure as for disabling, but when "Enable is selected the "Entries and Interval" boxes will be available. The value Entries shown are the maximum available for the interval shown, do not exceed this value. Selecting "OK" will complete the process of enabling Contingency Logging for the object.

Issue Workplace Tech error POP-UP "Server Busy.... action can't be completed because the other program is busy. Choose 'switch to' to activate the busy program and correct the problem."  when trying to configure communications.   Environment Workplace Tech Tool, revision 5.x  OpenLDV 3.40 OpenLDV 4.0 Cause Possible causes: 1. Multiple versions of Echelon drivers installed. 2. WinPcap may have been uninstalled, quarantined, or blocked. Resolution Only one version of LDV32.DLL should exist on the system and it should be the latest version.  WorkPlace Tech 5.7 and later uses OpenLDV 3.40 or OpenLDV 4.0. Verify the following: OpenLDV 3.40 or later is the only Echelon driver installed in the Windows Control Panel Add/Remove Programs dialog.  If the LonWorks PCLTA-20/PCC-10/PCLTA-10 for Windows is installed, do the following: From the Control Panel, Add/Remove programs, uninstall the OpenLDV driver Uninstall the PCLTA-20/PCC-10/PCLTA-10 for Windows driver. Reinstall the OpenLDV driver. Search the hard drive to locate all LDV32.DLL files on the pc.   Make certain all the LDV32.DLL files found are the same version as is found in the \LonWorks\Bin folder.    Verify the LON Flow Balance still communicates, if applicable. Verify winpcap 4.1.2 installed.  Use the link below to download and install WinPcap, if required.  http://www.winpcap.org/install/default.htm  UNCHECK THE FOLLOWING DURING INSTALLATION, UNLESS YOU HAVE UAC (User Account Control, in Windows 7 and Windows Vista) ENABLED!  If UAC is enabled, the checkbox should be CHECKED!

Issue I/A Series G3 Workbench unable to open platform for local host. Error indicates "Cannot display page. Workbench can only communicate with niagarad version 3 or higher." Environment I/A Series G3 Enterprise Network Server and Workbench (all versions) Cause The Niagara service for R2 is currently active. Resolution This error indicates the Niagara service for R2 is currently active. To correct, start the Niagara service for G3 by running the Install Niagara Daemon provided by the start menu for the G3 version required.

Issue After making changes to Xenta 121 in ZBuilder and clicking OK or Apply an error is returned that says: Error writing to device - Errors occurred while writing to the device. Database and device may not be synchronized. Please download values from database and restart device manually Environment Xenta 121-FC,  Xenta 121-HP Vista Workstation ZBuilder Cause This error can occur if Vista is unable to connect to the Xenta 121 controller. Resolution Ensure that the Xenta 121 controller is powered on and that there is a reliable connection to the controller. To verify that the controller is talking to Vista either right click on the controller in Vista and select properties then click on the Neuron Status tab and check that the state is Configured, online. Alternatively, this can be checked in LonMaker by right clicking the device and selecting Properties and then clicking the Attributes tab. The State should say Configured, Online.

Issue I/A Series R2 output window continuously indicates ERROR: run [DiscoverySender] - java.net.SocketException. The station appears to be running however the heartbeat LED remains on solid. ERROR: run [DiscoverySender] java.net.SocketException at java.net.PlainDatagramSocketImpl.send (Native Method) at java.net.PlainDatagramSocketImpl.send (bytecode 25) at java.net.DatagramSocket.send (bytecode 53) at tridium.foundation.prism.DiscoverySender.run (bytecode 83) at java.lang.Thread.run (line 5) Environment I/A Series R2, UNC-410, UNC-520 Cause The ERROR: run [DiscoverySender] is related to the Enable Announcement Feature that has not been implemented within R2. Resolution To correct, open station database, highlight the station name, and review the station's properties (config tab).  Set enableAnnouncement to false.  Save and restart the station (e.g. reboot the UNC).

Issue Is there an object in I/A Series R2 (Niagara) that can make Enthalpy calculations? Environment I/A Series R2 (Niagara) station, build (X, to be determined) Cause Need enthalpy calculation. Resolution Consider the following two program objects: 1. tridiumx / lib/ programObjects / hvac/ Psychrometric Calculations.sns // Psychrometric Calculations // //   This object calculates enthalpy, wetBulb and dewpoint for //   inputs of dry bulb temperature and relative humidity. // //   NOTE: This object REQUIRES the lib.jar file be present. 2. tridiumx / lib/ energyManagement / OutsideAirOptimization.sns // Outside Air Optimization // //   This object uses the two sets of temperature and humidity inputs //   to find the air supply with the least amount of heat.  The freeCooling //   output will be set to false if outside >= inside //   and set to true if outside <= inside - (abs)thresholdSpan. //   The user can select temperature or enthalpy comparisons. //   There is also a low temperature check to protect against freezing. // // Revision History:

Issue A station will not start in an I/A Series R2 (Niagara) UNC; errors similar to: "Invalid jar: /tffs/modules/coreRuntime-2.301.522.v2.jar WARNING: Module alm 2.301.522.v1 [/tffs/modules/alm-2.301.522.v1.jar]   Missing dependency: coreRuntime-2.301 WARNING: Module lib 2.301.522.v1 [/tffs/modules/lib-2.301.522.v1.jar]   Missing dependency: coreRuntime-2.301 WARNING: Module lonSiebe 2.301.522.v1 [/tffs/modules/lonSiebe-2.301.522.v1.jar]   Missing dependency: coreRuntime-2.301 WARNING: Module lonworks 2.301.522.v1 [/tffs/modules/lonworks-2.301.522.v1.jar]   Missing dependency: coreRuntime-2.301 WARNING: Module ndio 2.304.522.v1 [/tffs/modules/ndio-2.304.522.v1.jar]   Missing dependency: coreRuntime-2.301 WARNING: Module programLib 2.301.522.v1 [/tffs/modules/programLib-2.301.522.v1.jar]   Missing dependency: coreRuntime-2.301 WARNING: Module vlon 2.301.522.v1 [/tffs/modules/vlon-2.301.522.v1.jar]   Missing dependency: coreRuntime-2.301 WARNING: Module vlon 2.301.522.v1 [/tffs/modules/vlon-2.301.522.v1.jar]   Missing dependency: lonworks-2.301 WARNING: Module webUser 2.301.522.v1 [/tffs/modules/webUser-2.301.522.v1.jar]   Missing dependency: coreRuntime-2.301 FATAL: Could not load class "tridium.tools.StationMain". Environment I/A Series R2 UNC, all builds Cause The cause of this error is not known. Resolution Do a full install (upgrade) including upgrading the OS, NRE and niagarad. On the configure modules screen,  check the "Upgrade/Add" for all modules shown as installed (this forces the module to be reloaded).

Issue Is it possible to create a switch, in TGML, which has a popup dialog to confirm the action taken (Yes/No)? Environment TGML editor 5.1.X Vista workstation 5.1.X Webstation 5.1.X Cause A customer wishes to confirm changes before applying them, to avoid setting variables by mistake. Resolution In the components library in TGML editor, there is a check box component which has a confirm function. Drag & drop the component onto the workspace and study the code. This can be used as a basis for a switch component.