Building Automation Knowledge Base

Issue Site has 75 Microsmart controllers each with a Mode Control Type 21 point doing unoccupied control of the connected fan system.  The customer has asked that the unoccupied high and low temperature setpoints be made available to adjust from a Niagara R2 graphic screen. The setpoints are assigned to a PVALU element in the point's configuration (see below). Environment Niagara R2 with Microsmart Driver Microsmart controllers (all) Cause Request for setpoint control during unoccupied hours Resolution Create the shadow object for the Mode Control Point using the Niagara Point List Manager. Move it from the Temp folder to a new container created under the controller shadow object (labeled 'Testing' in the figures below). Add two MsElement objects from the ibsMs jar file - one for the Scheduled Off High Limit and the other for the Scheduled Off Low Limit.  Note:  The MsElement objects can be created directly under the Mode Control point's shadow object or in a container (as shown in the figures below). On the config tab for each MsElement object, modify the parameters highlighted by the red box in the figures below. Link them to a graphic and a right-click will present the user with the commandString field ('New value:' was used in the figures below).

Issue How can the default graphic for the Monitor Screens be modified in SIGNAL? Environment SIGNAL (all versions) Cause A re-installation of SIGNAL from floppy restores a default graphic called _MAINMAP.SSF when clicking on the Monitor Screens. Resolution Sign onto SIGNAL with administrative privileges and click on the Edit drop-down menu.  Select Edit Button. The mouse changes to a hand with an index finger pointer.  Select the Monitor button.  The pop-up below will appear:   Change the filename _MAINMAP.SSF to the desired ssf file and click Save/Done.

Issue Trying to get a schedule working in a MNB-1000 and getting the following error message: Schedule Setup Wizard will not run: Not supported for this application's type of device. Device type: 971 Environment MNB-1000 MNL controllers Workplace Tech Cause New to programming the MNB controller line Resolution A 7-day schedule object is available for the MNB-1000 (only) and is part of the Schedule Control stencil. The Schedule Setup option under the Application drop-down menu only applies to MNL applications.

Issue The sensor in the BACnet controller is open or shorted and the value at the ENC shows "nan" but no fault is annunciated? Environment I/A Series G3 (Niagara) Cause If the analog object in question is being polled, by default only the "present value" is retrieved and therefore the "nan" is displayed but the status remains as ok.  A polled point can be made to retrieve the "statusFlag" data also by altering its "facets" as shown in the Resolution.  Resolution It is normal for the MNB controller analog input present value to change to "nan" when the sensor is shorted or open.  To annunciate a fault at the ENC: Add the "OutOfRangeAlarmExt" to the analog input object and program it to have the "fault" conditions annunciated.  If this object is defined to use COV notification the "present value" and "status flags" are reported by default.  Therefore,  the "nan" value is displayed and handled as a fault condition and annunciated.  However, if the analog object is being polled, by default only the "present value" is retrieved and therefore the "nan" is displayed but the status remains as ok.  A polled point can be made to retrieve the "statusFlag" data by altering its "facets".  With the object properties displayed on the Facets property click on >> and add a key as shown below.

Issue Using a nciState Lon network variable to set operational modes of a MNL-800 application.   Needs to be able to allow these inputs to be set from the GUI. Environment MNL-800 application program Graphical User interface built with the I/A Series (Niagara) R2 system. Cause Desire to allow a user at the graphical head end of the BMS system to configure the individual bits of a LON state type network variable. Resolution The following discussion is based on the user interface engineering work being done within the WorkPlace Pro engineering tool of the I/A Series R2 system. The "DynamicCmd" control object found in the "conversion" folder of the Lonworks jar file can be linked to a SNVT_State type Lonworks network variable.  After linking the DynamicCmd control object to the desired controller shadow object nci type network variable, the DynamicCmd object learns the configuration information for the linked network variable.  The next step in configuring this object for this type of use is to set a name for each control bit element of the network variable.  These defined names are displayed when the GUI user clicks on the control point.  The user then selects the bit field name (from the displayed list) to command and then selects the binary value (True or False)to be written to that bit field. The following is an example of this control logic where the dynamic device is the MNL-800 controller with the network variable nci_cmd as the input constant and nvo_stat as an output state variable that allows the display of 16 internal bit state variables. This image shows the configured list of boolean bits that will be configurable via this DynamicCmd_1 object: When the GUI user selects this command object, the following field list is displayed: And after selecting the "Fan2-S/S" enable selection, the following popup window is displayed allowing the user to specify the boolean state for that command bit.  The value will be written to the controller when the [OK] button is clicked.

Issue In TreeTech, can a LCM be uploaded and downloaded? Environment LCM-84000 LCM-88000 Cause On a jobsite with a Network 8000 installation dating back to the 1990s and trying to do database backups. Resolution A networked LCM can be uploaded / downloaded, with TreeTech, via a serial connection to the GCM to which it is wired.  In situations where the GCM is not easily accessible (i.e. in a locked room), a serial connection to any one of the networked LCMs will provide access to the entire network as if it was the GCM.  Uploads/downloads of any networked LCM can be done via this serial connection too. A standalone LCM can be uploaded / downloaded, with TreeTech, using a direct serial connection.  Due to limitations in TreeTech, the standalone LCM must be configured as network 1 and address 1.

Issue MNL-V3 application configured with an external actuator of 390 seconds drive time shows an excessive setpoint deadband of almost 20% of control range. Environment MNL-V3 controller Cause Unknown - Issue has been reported to product management. Here is an application fragment showing the issue.  Note the 390 second drive time. Resolution Use the following application fragment in your application to eliminate the excessive >22%) deadband. Here is an application fragment showing a suggested workaround:

Issue Error indicates - Invalid or inaccessible view "pxEditor:pxEditor" when attempting to view px pages through I/A Series G3 embedded Workbench via browser. Environment I/A Series G3 ENC Cause Incorrect licensing or missing pxEditor module Resolution Look in the ENC's license file under the License Manager, and look for this line: <feature expiration="never" name="web" parts="ENC-520-WEB, ENC-WB" ui="true" ui.wb="true" ui.wb.admin="true"></feature> If any of the "ui" fields are "false", then you need to have the ENC licensed for Embedded Workbench. Purchase part number ENC-WB. In the Software Manager, look for a module called pxEditor. If pxEditor is not installed, install using the Commissioning Wizard.

Issue Instructions for finding the version of LonMaker and LNS Server on a machine. Environment Echelon LonMaker Cause Knowing the version of LonMaker and LNS are necessary for many troubleshooting techniques. Support representatives may ask you to have this information available in order to assist you better. Resolution Please follow these steps to find the version of LonMaker and LNS server on the machine: Open LonMaker, then pick and completely open a network. Choose the LonMaker menu in the menu bar, then about LonMaker: This is the about LonMaker window that should be shown. As you can see in this screen capture, LonMaker 3.1 is being run with the LNS server version 3.27.

Issue Basic setup tips for the I/A Series G3 (Niagara) GCM driver, tacGcm. Environment ENC-520-2 ENC-410 I/A Series G3 GCM driver, tacGcm Network 8000 GCM (GCM-84000 series, GCM-86000 series) Cause This article is a work in progress. The intent is to provide information proven to be helpful, and add to it as we learn more. Resolution G3 GCM (tacGcm) driver setup basics: Serial communications between the UNC/ENC and GCM-84000 series must use GCM Port 2. The GCM-84000 series Port 1 is not buffered and cannot be used for network communications. The GCM participates on a network that includes 27 other GCMs. The recommendation is one UNC/ENC per GCM and to share data between the UNC/ENC devices with peer to peer links. The baud rate on the serial port is limited to 9600 and all communications (UNC/ENC, ASD, LCM, GCM to GCM, MMI, etc.) all share the same internal GCM communications buffers. It is this buffer on the GCM-84000 series that can easily be overwhelmed. Use Poll On Demand (POD) containers (G3 uses proxy points without history or alarm extensions) where possible. To optimize the use of the communications bandwidth, route alarms to the GCM serial port used by the GCM driver only as needed. Exceptions and Trend reports (and other reports generated by the GCM hardware) should never be routed to this port, as this data is not used and will utilize precious bandwidth. Only one HMI should be connected and active on the network.  Issues may occur when using the UNC / ENC GCM driver to poll a GCM network while simultaneously polling the same system with another HMI (e.g. Host, InVue, UltiVist, Signal, etc.). GCM-84000 series and ENC communications (tuning) Communications can greatly affect GCM operation and stability. As  indicated previously, all communications is process by a common communications buffer further affecting the GCM system RAM. Log into the GCM and review the current SYSRAM. It is recommended the GCM-84000 System RAM is stable and operating above 18K bytes. Low RAM will cause the GCM to appear to lockup, stop processing messages, and even reset. Review delta times for the blocks. Check the DETIM (Delta Time) attribute of a random sampling of blocks, especially those that have low update times assigned or involve device communications. Update times for blocks such as SNET, RNET, SGCM, RGCM, SLCM, and RLCM should especially be reviewed and increased as needed. These blocks default to 5 seconds and should be increased to a reasonable timeframe (e.g. 30 seconds). For other blocks, if the DETIM value is greater than the UPTIM value by more than a couple of seconds, the system may potentially be experiencing system throughput problems. This should be monitored as changes are made to the system to determine if it improves. Adjustment of update times should also be done in the other GCMs that may be requesting data via global type blocks. If the RAM has not stabilized and is below 18K bytes, decrease the GCM driver maxMessages from 5 towards 3 or 2. This controls the number of messages requested simultaneously from the ENC Note: DETIM block output is normally hidden. In order to see it, login to the GCM as user = BCFLD, password changes every day. Contact PSS - Rockford for a current password. Verify  that the "Write on Start", "Write on Up", and "Write on Enabled" are all set = false in the default Tuning Policy of the GCM Network.   

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 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 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 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 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 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).