Building Automation Knowledge Base

Issue What type of Viconics sensor is a SE7600H5045E?  It maps to another model number of VT7600H1018E (which is on the label affixed to the packaging). Environment Viconics controllers Cause Documentation not readily available Resolution Below is a 'Product Matrix Selector' for the SE7600 Series Staging and Heat Pump Controllers.  It was obtained from the installation guide.

Issue In Niagara G3, the ProView wizard does not recognize folders that exist in the station under the Lon Network. Environment Niagara G3 Cause The wizard cannot identify 'regular' folders. The wizard also does not identify a folder with a space character in the folder's name. Resolution Use Device folders as created from the Lon Device Manager.   Use an underscore character instead of a space character for the folder name.

Issue A new Niagara R2 UNC is installed with a license. The license installs correctly. After a reboot, the station fails to start. The standard output window displayed a fatal error as illustrated below: Product Line TAC IA Series Environment Niagara R2 Cause Certain foreign characters are not recognized by Tridium's License Generator.  In this case, a French character (with a symbol above the letter) was used in the customerSite name.  When the license was generated, the French character converted to a question mark (?): customerSite=Rotondle des S?urs The ? symbol is not recognized by Niagara.  So, when an UNC is rebooted, it will read the license file and stop when it comes to the customerSite name. Resolution Contact the factory to have the license modified. After correction by the factory, the customerSite line in the license example above reads: customerSite=Rotondle des Seurs

Issue Just installed  WorkPlace Tech (WPT) 5.8.2 on a Windows 7, 32-bit laptop,  but cannot start it. Received an error,  "The program cannot start because WPTUtility.dll is missing from your computer. Try reinstalling the program to fix this problem."   Environment WorkPlace Tech Tool, Revision 5.8.2 Cause The software installer was not able to install the  WPTUtility.dll. Resolution 1. Uninstall WPT 5.8.2 2. Make sure user is logged in as administrator 3. Turn off UAC (User Account Control)  until WPT is installed, then turn it back on when finished.       a. Go to the Windows Control Panel and select User Accounts       b. Select Change User Account Control Settings                c. Slide the selector to "Never Notify".  You may want to change this back to your original setting after installing WPT. 4. Install WPT 5.82 as admin, there's a r-click option for it   5. If  steps 1-4 don't work, you might need to disable anti-virus on the laptop, then repeat  steps 1-4.  

Issue In a G3 station, BACnet Device Manager, not able to Discover any MSTP devices. Environment ENC with a BACnet MS\TP trunk under it, all revisions Cause There are multiple settings that must be made before BACnet communications will be enabled on the MS/TP trunk. Resolution 1. The Object Id of the BACnet Local device must be set to a value other than -1. 2. The BACnet Network must have the Enable flag set = true 3. The MSTP port itself must be enabled. Right-click on the MstpPort in the tree, select Actions / Enable. 4. Verify that the MSTP port Enabled flag is "true", and the port is enabled. 5. Verify that the Port Name (COM3 in this example) is an active RS-485 port on the ENC. 6. Verify that the Baud Rate (19,200 in this example) matches the baud rate of the MSTP controllers. In the case of MNB- series controllers, the network baud rate is established by the WorkPlace Tech Commissioning Tool. 7. Remember that the MSTP Network number must be unique on the BACnet internetwork.  In this case, the MSTP network number  = 7966, which is not a likely default value, so minimizes the possibility of being duplicated by another vendor.

Issue On a Niagara R2 UNC, a DNS server will be used. What is the 'node' name or 'computer' name for the UNC on the Microsoft network? Environment Niagara R2 Cause End customer requirements Resolution The Computer Name on the Network Settings tab in Admin Tool will appear as the node name on the Microsoft Network.  See image below. The Computer Name is modifiable.

Issue A specification for a power meter states that it provides KYZ pulse outputs. What is a KYZ pulse output? Product Line All Product Lines Environment Utility Meter with KYZ pulse outputs Cause Some meter specification sheets may state that the device outputs KYZ pulses. Resolution KYZ is a designation given to a relay used to create pulses for electrical metering applications. It is commonly a Form C relay (SPDT). The term KYZ refers to the contact designations: K for common, Y for Normally Open, and Z for Normally Closed.

Issue A Niagara G3 Microsmart driver is being used to integrate an existing system of Microsmart controllers. Mode control points are used to command heating stages at different setpoint values.  How can the stage setpoints be modified (identified as the PVALU element) from the Niagara G3 station?  They are learned into the Niagara G3 station as Numeric Points and do not have the option to be writable. Environment Niagara G3 Microsmart driver Microsmart controllers Cause Modification of stage setpoints to be provided to the customer on the system graphic. Resolution 1.  Add the PVALU element for the specific Mode Control point to the database:     2. Add text to the Command String and modify the Index value to match the specific PVALU element to be changed (ie: Index = 6 maps to PVALU,6 in the Mode Control point):   Now, a right-click on the numeric point provides an action item and the ability to change the PVALU element for the Mode Control point down in the Microsmart Driver.

Issue During initial setup, the incorrect ethernet IP address or subnet mask was entered. Now when rebooting the ENC/JACE, I cannot reconnect to it using the I/A Series G3 Workbench. How can the incorrect information be corrected? Environment ENC-520-x, ENC-410-x, JACE-600, JACE-600E, JACE-7 Cause Network connectivity cannot be established if the IP address or subnet mask was entered incorrectly. Likewise, if an invalid subnet mask is entered, the ENC/JACE may not boot completely (or at all). Resolution The following information is provided in more detail in the section "About JACE serial shell mode" subsection of the "JACE Niagara AX Install and Startup Guide", provided with the G3 software. This document is provided with and installed with the I/A Series (Niagara) G3 software. This document can be displayed by selecting "Doc - JACE Startup" from the documentation index. Required hardware: Serial Cable Terminal Emulator software on computer (such as "Hyperterminal" or "Putty") Procedure: Configure the Terminal Emulator.  ENC-410 and ENC-520 at 57600 baud, 8 bits, one stop bit, no parity, hardware flow control.  JACE-6xx and JACE-7xx at 115200 baud, 8 bits, one stop bit, no parity, no flow control.  Jumper the upper two pins of the Console "MODE" connector,  located in the upper right corner of the ENC410 and 520 circuit board (See photo at right).  JACE-6xx and JACE-7xx remove cover and configure serial mode select jumper as labeled. For ENC-410 and ENC-520, connect the terminal emulator via a UNCC-405 serial cable to port COM1 on the ENC and power-cycle the ENC.  For JACE-6xx and JACE-7xx, connect the terminal emulator via a standard DB-9 null modem cable to port COM1 on the JACE and power-cycle the JACE. Wait for the ENC/JACE to complete its bootup process (do not break out of the boot process). At the login prompt, enter the platform user name and at the password prompt, enter the platform password.  The JACE System Shell menu will then be displayed. Select option 2 to display and, if needed, update the ENC/JACE's network settings. The network parameters will be displayed, one at a time.  To change a value type in the corrected value and press the key.  To keep an existing value, just press the key. When all parameters have been displayed, a confirmation screen will be displayed.  Press to save the changes.  When the information has been saved to the ENC/JACE a prompt will be displayed. press the key to continue. Press 7 to reboot the ENC then press to confirm the reboot request.. Disconnect the serial cable and remove the jumper installed in step 2.

Issue Is it possible to recover the block programming database from a failed GCM-84000 series controller? Environment Network 8000 GCM-84000 series controller (1) failed CPU board, GCMA-112 (1) replacement CPU board, GCMA-112 Cause A GCM-84000 series CPU board has failed, and a backup of the GCM block database cannot be found to install in a replacement controller. Resolution It MIGHT be possible to extract the block database from a failed GCM-84000 series controller, as long as the PROM chips on the CPU board (GCMA-112) were not damaged by the "event" that damaged the rest of the CPU board. Assuming the PROM chips are not damaged, the procedure is as follows: Note: When changing the PROM chips, be sure to wear a well-grounded ground strap to help prevent static electricity from damaging the sensitive chips. 1. Remove the chips labeled PROM-22-300 and PROM-22-400 from the "old" CPU board.     2. Install them on the spare CPU board. Do not interchange the PROM chips, and maintain their original orientation. 3. Replace  the CPU card into a working GCM. If the original PROM chips were undamaged, the GCM will reboot successfully, and the block database from the original GCM will now be transferred to the replacement GCM.  4. Backup the GCM database immediately.

Issue java.io.EOFException    at javax.baja.xml.XParser.read(XParser.java:753)    at javax.baja.xml.XParser.parseString(XParser.java:555)    at javax.baja.xml.XParser.parseAttr(XParser.java:492)    at javax.baja.xml.XParser.parseElemStart(XParser.java:421)    at javax.baja.xml.XParser.next(XParser.java:262)    at javax.baja.xml.XParser.parseCurrent(XParser.java:146)    at javax.baja.xml.XParser.parse(XParser.java:119)    at javax.baja.xml.XParser.parse(XParser.java:102)    at javax.baja.ui.px.PxDecoder.decodeDocument(PxDecoder.java:77)    at javax.baja.ui.px.PxDecoder.decodeDocument(PxDecoder.java:64)    at javax.baja.workbench.px.BWbPxView.loadPx(BWbPxView.java:176)    at javax.baja.workbench.px.BWbPxView.doLoadValue(BWbPxView.java:90)    at javax.baja.workbench.BWbEditor.loadValue(BWbEditor.java:233)    at com.tridium.workbench.shell.NHyperlinkInfo.loadView(NHyperlinkInfo.java:563)    at com.tridium.workbench.shell.NHyperlinkInfo.hyperlink(NHyperlinkInfo.java:100)    at com.tridium.workbench.shell.BNiagaraWbShell.doHyperlink(BNiagaraWbShell.java:350)    at com.tridium.workbench.shell.BNiagaraWbShell.hyperlink(BNiagaraWbShell.java:316)    at com.tridium.workbench.shell.WbCommands$BackCommand.doInvoke(WbCommands.java:718)    at javax.baja.ui.Command.doInvoke(Command.java:303)   Environment G3 (Niagara) station with px files, any revision level. Cause The px file did not copy correctly. Resolution There are three possible approaches to recover from this situation, as follows: Try copying the file again.   Open the px file with a text editor. It might be possible to determine what was either not copied at all, or what might have been corrupted during the copying process. The example shown below is part of the BoilerRoom.px file from niagara-3.6.47 \ stations \ demo \ px \ plant. Lines 489 through 495 contain 'closing tags' for the Canvas Pane, Scroll Pane, Border Pane, content, and px statements that were opened at an earlier point in the px file. If one or more of these 'closing tags' were not copied, or were somehow corrupted during the copying process, the error would result .  If necessary, restore the px file from a backup.

Issue After configuring a Niagara R2 station with BACnet MSTP communications, the UNC displays an error in the standard output window: "Cannot load BACnet MSTP Driver". Error details below: *************************************************************** ERROR: Cannot load BACnet MSTP Driver tridium.nre.DriverException: Not found [mstp]    at tridium.nre.Platform.installDriver (bytecode 98)    at tridium.nre.Platform.getDriver (bytecode 42)    at tridium.nre.Nre.driver (bytecode 4)    at tridiumx.bacnet.services.link.mstp.MstpLinkService.init (bytecode 3)    at tridiumx.bacnet.services.network.NetworkPort.linkInit (bytecode 14)    at tridiumx.bacnet.services.network.NetworkPort.linkStart (bytecode 😎    at tridiumx.bacnet.services.network.MultipleNetworkService.start (bytecode 29)    at tridiumx.bacnet.services.network.RouterNetworkService.start (bytecode 1)    at tridiumx.bacnet.services.BACnetService.startService (bytecode 44)    at tridium.foundation.Sys.startServices (bytecode 49)    at tridium.foundation.Station.startStation (bytecode 63)    at tridium.foundation.Sys.boot (bytecode 27)    at tridium.foundation.Sys.bootLocalSns (bytecode 17)    at tridium.tools.StationMain.bootSns (bytecode 0)    at tridium.tools.StationMain.doIt (bytecode 352)    at tridium.tools.StationMain.main (bytecode 10)    at java.lang.reflect.Method.invoke (Native Method)    at tridium.nre.Nre.mainImpl (bytecode 271)    at tridium.nre.Nre.main (bytecode 1) *************************************************************** Product Line TAC IA Series Environment Niagara R2 Cause BACnet MSTP driver does not load on a UNC reboot. Resolution Add the line illustrated below to the drivers.properties file and reboot the UNC: driver.mstp=tridium.nre.vxworks.mstp.VxWorksMstpDriver

Issue How to configure an analog input on a DMS MicroSmart controller as a contact input. Environment MSC-MPC (revision 10) and MSC-MPC-001 (revision 11) MicroSmart controllers Cause No contact inputs available on the MSC-MPC Resolution Below are illustrations and explanations on how to configure an analog input as a contact input.  

Issue MN-Sx, MN-SxHT sensors calibration Environment I/A Series MicroNet Sensors (MN-Sxxx series) Cause Sensor readings inaccurate Resolution 1. Calibration in WorkPlace Tech application program Calibrate the temperature and / or humidity offset in the Hardware Wizard. Enter a positive or negative offset value. For examples, -0.5 or 0.5. The WorkPlace Tech application has to be compiled and downloaded to the controller for the offset to take effect.   2. Calibration via sensor's Diagnostic Mode (only available in MN-S3xx, MN-S4xx, MN-S4xx-FCS, and MN-S5xx) To enter the sensor's Diagnostic Mode, press the Up and Down buttons simultaneously until the sensor enters the Diagnostic Mode. Press the Override button (while still in Diagnostic Mode). This will lead you to a display where you can enter an offset for sensor calibration. Allow the sensor to return to the normal display (takes about 30 seconds).

Issue In Niagara G3, a Learn Nv command on a MNL controller generates the following error: Environment Niagara G3 LON Cause Attempting to learn the new snvt profile from a controller that is already assigned a lnml file. Resolution If a LearnNv command is required on a controller already assigned a lnml file, the only way to avoid the error is to remove the lnml file assignment such that the file assignment is null. Then the LearnNv command will successfully complete. Access the Property Sheet of the LON controller and clear the 'Xml File' and Save.  The file name will be replaced with 'null'. Note:  Performing a Learn Nv on any Lon device previously using a Lon Xml file, LonComponent data from any manufacturer-defined type info is removed (lost).

Issue TCP/IP ports used in Niagara G3 (AX), various drivers, features, and functions - Quick Reference Table Environment Niagara G3 all versions Cause quick online reference for the ports used in Niagara G3 Resolution

Issue What I/A Series G3 object can be used to retrigger a write a value to a Modbus controller? Environment I/A Series G3, Modbus Cause Various Modbus controllers require the rewrite of values to maintain use of remote values versus local values.  This fallback mechanism allows the local Modbus controller to maintain control in the event of a BMS controller failure or loss of communications. Resolution The I/A Series G3 Modbus driver utilizes Modbus preset components to perform the rewrite function.  Presets allow writing preset values to the target addressed data items upon right-click action (command). If required, the “Write” action of any preset container can be linked into other control logic. For example, the “Trigger” slot of a TriggerSchedule can be linked into a ModbusClientPresetRegisters container component for periodic writes of child registers defined under the parent.  The same is also true using a periodic trigger object found in kitControl.  Preset components can be found in the modbusAsync palette and modbusTcp palette in the “Presets” folder. Note: Modbus client preset components are not proxy points or proxy extensions.  Modbus client preset components are not polled and do not read data from the device.  Modbus client preset components are only used to write data to the device. Presets exist for both Modbus coils and holding registers. Reference the I/A Series G3 Modbus Guide (About Modbus preset components) included with G3 documentation for more details.

Issue A Niagara R2 UNC station fails to start, producing the following error in the standard output window: FATAL: Cannot boot station from sns java.lang.ClassNotFoundException: tridiumx.webuser.WebUserAdminService Full Error Message: Environment Niagara R2 Cause Missing a supporting jar file Resolution Install the webuser jar file and reboot the UNC.

Issue Unable to add a new user in a G3 (Niagara) ENC station accessed via web browser. There is no "New" tab displayed under the Services / UserService / right-click, User Manager page. Environment I/A Series ENC-520, ENC-410 Embedded Workbench feature, part number ENC-WB Cause The ability to add a user to the ENC via web browser requires the Embedded Workbench feature be enabled. Resolution To determine if the ENC has the Embedded Workbench feature enabled, open the Platform, License Manager, view the license, and the feature name = "web" ... ui.wb.admin = true indicates that the feature is enabled.  See the high-lighted lines in the screen capture below. If the feature is not enabled, it can be ordered and added to the ENC license.  

Issue A Niagara G3 DMS driver is being used to integrate an existing DMS system with Microsmart controllers.  Setpoint values are provided to LOOP points in the Microsmart with Application Type 7 points (AP7) which can also be referred to as Chain Calculation points.  The AP7 points are not linked to the DMS database.  They are learned into the Niagara G3 station as Numeric Points and do not have the option to be writable. How can this be achieved? Environment Niagara G3 DMS Microsmart Cause Microsmart AP7 points are learned into a Niagara G3 as Numeric points and are not writable. Resolution Learn the AP7 point's PVALU element into the database: Go to the Property Sheet of the object above and add a Command String: An action option will now appear on the Wire Sheet (transferable to a graphic):