Building Automation Knowledge Base

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

Issue Official Product Announcement on the Discontinuation of Micronet 2000 and Network 8000 (PA_00152). Environment Micronet 2000 Network 8000 Cause Components for manufacturer no longer available. Resolution The following products will no longer be available after December 31, 2011:  

Issue How are two 4-20 mA loop-powered sensors wired into a MNL-200? Environment MNL controllers with at least two UI inputs (MNL-100, MNL-150, MNL-200, MNL-800) Cause n/a Resolution The image below provides a basic (but accurate) diagram of two loop-powered sensors and how they are wired with a power supply and a MNL controller.

Issue When trying to connect XPSI version 4.1 to a MicroZone II, using a B&B Electronics converter, model USOPTL4, an error is received: "No communications adapter found. Comm error = -5". Online XPSI functions may be grayed-out and not available: Environment XPSI version 4.1 USB / RS-485 adapter, B&B Electronics model USOPTL4 Network 8000 MicroZone II controller Cause One cause of the error appears to be closing the XPSI Site Group window: Resolution Leave the Site Group window open. Edit the Site setup. In the following example, the site is named "B&B converter to MZ2". To communicate to a stand-alone MicroZone II, the Network Number and GCM Number do not matter, they can be left at their default values. The "Connection Type" should be set to PSI HOST   The "Port" should be set to match the hardware port assigned to the B&B converter when installing its drivers. It will be named " RS-485 Isolated Port (COMx)". COM3 in the following example. Note the Universal Serial Bus Controllers, Model USOPTL4. Once the site is configured, access the controller: Enter the user name and password for the MicroZone II on the MicroZone II PSI Main Window:   In the "Functions" menu, use the arrow keys to move the cursor to "Device Number", and press "Enter". Type in the address of the controller, which is set by its DIP switch. The MZ2 is set to address = 1 in the example: While XPSI is connecting to the MZ2, the TD and RD LEDs on the model USOPTL4 should blink.  The  yellow (RX) and green (TX) LEDs on the MicroZone II should also blink. When XPSI is connected to the controller, the Main Window will display the device number. In the example, MZ II # 001 is connected: When finished accessing the MicroZone II, logoff and select "Disconnect" from the Access menu. This will properly shut down XPSI and the drivers for the B&B converter.

Issue I/A Series (Niagara) R2 station, needs a LON shadow object for a Square D Altivar 21 with Program ID 80:00:13:3C:0A:0A:04:50.  The closest match is Atv21, with Program ID 80:00:13:3C:0A:0A:30. Environment I/A Series (Niagara) R2 station in a UNC with a LON trunk, build 532, 529, or 522 Square D drive, Altivar 212, with LON card, Program ID 80:00:13:3C:0A:0A:04:50. Cause Square D Altivar 212 with a new LON profile and XIF file, program ID 80:00:13:3C:0A:0A:04:50 Resolution Download a new jar file: lonSquareD-2.303.532a.zip, which includes a shadow object named Atv212, manufacturer Id = TA_Control, and Program ID  = 80:00:13:3C:0A:0A:04:50. LonUtilities Manager after the jar file has been installed:

Issue How do I expose the temperature setpoint SNVT, nciSetPts, in a GxPage for Niagara R2? Environment Niagara R2 all versions Cause N/A Resolution The nciSetpt temperature values can be displayed and changed via graphic with the use of the SnvtTempSetptCmd conversion object. The SnvtTempSetptCmd object is located in the local library: /tridiumx/lonworks/conversion folder. The vt7600R shadow object was used in this example. Use the shadow object which matches the program ID of the device being used. Open the Local library and go to the /tridiumx/lonworks/conversion folder Copy and paste the snvtTempSetptCmd object to your Workspace. Link the nciSetPts property of the shadow object to the snvtTempSetpt property of the SnvtTempSetptCmd object and click ok. (see Figure 1) Figure 1. Add two GxText objects for each setpoint you want accessed and label them accordingly. (see Figure 2) Select the temp setpoint property under SnvtTempSetptCmd object and binding for the GxText property. (see Figure 2) Figure 2. Repeat step 5 for each setpoint to be exposed. Return to the Workspace view once all the desired setpoints have been exposed. You can now Right-click on the desired setpoint and change its value. Figure 3. Figure 4.

Issue In an R2 (Niagara) station with BACnet, getting errors in Standard Output Window, "Transport lockup detected!" and multiple "TException E_QUEUE_FULL {BClient}". Environment I/A Series R2 (Niagara) UNC station with BACnet service. Cause Queue sizes in BACnet Service are too small. See the BACnet Integration Reference, Chapter 6, "Configuring BACnetService Properties", "Engineering", Figure 6.4, and section titled "Message Queue Properties" for further details. Resolution Increase all three of the queue sizes(transportQueue, serverQueueSize, clientQueueSize) , from the default values of 16, up to 90.   Monitor the Standard Output Window for errors, and increase the queue sizes in increments of 50, up to 500. It may be necessary to reboot the station in order for the changes to take effect, because the changes are being made to a service.

Issue A Niagara R2 UNC has been installed in place of a DMS-3500 and two Microsmart trunks has been merged into one.  The trunks have been checked out physically and all controllers are powered, online, and ready to communicate to the UNC. A Device Discovery displays only a partial list of the installed controllers.  Why are the rest of the Microsmart controllers not being found? Environment Niagara R2 (all versions) Microsmart controllers (all versions) Cause A DMS-3500 has been removed and replaced with a UNC with the Microsmart driver.  The two Microsmart controller trunks have been merged into one trunk. Resolution In the Properties of the ibsMs service, ensure that the firstControllerAddress is set to 1 and that the maxControllers number is set to the same value of the licensedControllerCount. In the image below, the ibsMs service is licensed to communicate to 124 controllers but the maxControllers is only set for 60.  A Device Discovery from the ControllerListManager will only look for controllers addressed from 1 to 60.  Any controller addressed 61 and higher will not be searched for and, as a result, not discovered.