Building Automation Knowledge Base

Issue When tunnel through a UNC using an HTTP port other than 80 the Ax Serial Tunnel will not connect and locks up. Environment R2, G3 I/A Series tunneling Cause Including the port number after the IP address when entering the Host address in the Ax serial tunnel window will cause it to lock up trying to connect with the port entered. Resolution Do not include the port number after the IP address when entering the Host address in the Ax serial tunnel window.

Issue Encountered the following error when running the SNMP service: Start service: SnmpService [1272] SnmpService SnmpReceive: unable to create socketjava.net.BindException: Address already in use: Cannot bind Environment I/A Series R2 SNMP driver Windows Server 2008 Cause The SNMP ports are being used by another application / process. In this particular case, the SNMP Service (which is available in Windows Server 2008) has been enabled. Resolution The I/A Series R2 default ports for SNMP are 161 (receive SNMP requests) and 162 (receive SNMP trap messages). Check if the SNMP Service in Windows Server 2008 is enabled. If it is enabled and not in use: Disable it by stopping the service and setting it to 'Manual' so that it does not start whenever the computer reboot and starts. Uninstall it using Windows 'Add or Remove Programs'   Alternatively, you can change the SNMP ports in I/A Series R2. To do this,  in your station, go to the SnmpService properties, 'General' > 'Config' tab.

Issue An object’s override and set pop-up boxes do not fully open in Niagara G3. You have to grab and pull the corner of the pop-up to open it completely. Niagara version 3.5.x is installed on a Windows 7 PC. Environment Niagara G3 Version 3.5.x and older Cause Versions of WorkBench prior to 3.6.31 have not been officially certified with Windows 7. Resolution The issue is more of a nuisance, but does not affect functionality in any way. There are a couple of options you can try to try and correct the issue. The first option is to try to reduce the font size in Windows 7. - Click on the Start button and open the Control Panel - Open the Fonts folder and select Change font size. - Select smaller fro the font size and click apply The other option is to change the screen resolution slightly. Note: Since Niagara versions prior to 3.6.31 have not been certified for the Windows 7 operating environment, the above my not correct the issue.  

Issue LinePrinterRecipient 'Load Printer List' does not bring up a list of the available printers Environment I/A Series G3 Enterprise Network Server (ENS) or Enterprise Network Controller (ENC). Cause At this stage the reason that this occurs is unknown but the following resolution is the current workaround. Resolution Since you are not able to find the printer using the 'Load Printer List' button, you should just type in the name of the printer in the LinePrinter Recipient's properties 'Printer' field. To make sure you get the name correct, go to Windows Control Panel and go to 'Printers and Faxes'. Find the line printer and right-click on it to the properties. Copy the name of the printer. Go to Workbench and paste the name of the printer in the LinePrinter Recipient as per described above.  

Issue The MN-S3, MN-S4, and MN-S5 sensors allow for local setpoint adjustment.  This ability is provided by configuring the sensors in WorkPlace Tech with a MNL or a MNB controller.  When a custom setpoint is entered via the sensor, is there a scenario when it could be replaced by the default setpoint? Environment MN-S sensors MNL controllers MNB controllers Cause End user described a situation where main power was lost in the building and all custom setpoints were replaced by the default setpoints. Resolution The only scenario when custom setpoints are lost is if the associated controller's database is re-installed and the MN-Sx sensor is disconnected at the time of the download.  Once the download is completed, and the MN-Sx is re-connected, the default values are used by the controller.  The custom setpoints have to be re-entered at the sensor. A power loss to the controller does not remove the custom setpoints.

Issue Xenta Server Error: Ethernet autonegotiation error (Error#: 59) Environment Xenta Server System Error log Xenta 527 Cause The Ethernet negotiation error comes from bad connection with the Ethernet switch. The negotiation is the low level negotiation between the PHY (physical layer) interface on the Xenta and the PHY on the switch. It negotiates speed (10/100 Mbps ) and duplex. This error can indicate a bad cable or other problems with the switch. Resolution Replace any patch cables Replace connectors on any suspected bad cables Use a different port on the ethernet switch. *Note that the Xenta Server Ethernet port is only capable of 10 Mbps. Speed negotiation is unnecessary if the port on the switch can be manually configured.

Issue Schedule Import will not update. Environment G3 Niagara Cause Schedule import defaults to Manual update this will prevent the schedule from automatically.. Resolution Schedule execution time can be set to daily, days of week, interval and manual.  Please consult Doc Drivers document.  

Issue Enterprise Server station upgrade failure from I/A Series R2 version 529 to 532. The station in version 529 was successfully converted from DB to XML format. The following error was seen when converting the station from XML to DB in version 532. ERROR: c:\niagara\r2.301.532\stations\ \config.xml (7270,149) : Unknown class "tridiumx.commercialCooking.CommercialCookingService". Parse of XML failed.   Environment I/A Series r2.301.529 and earlier I/A Series r2.301.532 Cause When you create a new station as a server station in I/A Series R2, you will normally select the option 'Is this station going to be a server?' checkbox in the New Station Wizard. When you make this selection, the Backup Service and the Database Service which are needed by a server station will be automatically selected. In versions r2.301.529 WorkPlace Pro and earlier, the Commercial Cooking Service is also automatically selected, so this should be unchecked since this is not being used. However, if you did not uncheck the Commercial Cooking Service, the Enterprise Server station will still run and work normally. In I/A Series version r2.301.532, the Commercial Cooking module is no longer available and is not installed during the installation of the I/A Series software. The error will occur if you try to convert the station database from XML to DB in version 532 because the database contains the Commercial Cooking Service which does not have a corresponding module. Resolution In I/A Series version 529, you should remove the Commercial Cooking Service from the station before you perform a conversion from DB to XML format.

Issue How do we specify the amount of memory (base or extended) when ordering a UNC-520-2 or ENC-520-2? Environment UNC-520-2 or ENC-520-2 Cause Customer request Resolution All UNC-520-2 and ENC-520-2 controllers shipped since April, 2010 have been shipped with extended memory.  

Issue Where can I find documentation on the JACE-600 or JACE-700 controllers?  Product announcement did not include the documentation or any location references. Environment JACE-600 JACE-700 Cause Product documentation was being finalized at time of announcement. Resolution The documentation for the JAC-600, JACE-700 and all accessories for them are available in the documentation set included with the latest release of the I/A Series G3 software.  This software and included documentation is available by downloading "Release 3.6.31 Files" on The Exchange Download Center. As of the date of writing, both the "TAC_IA_Series_ENC_SW-3.6.31.7.zip" and "TAC_IA_Series_ENS-3.6.31.7.zip" include the documentation in Mounting and Wiring section of index tree.

Issue Where can I find the SE7000 Room Controller LonMaker Plug-Ins and device resource files? Environment SE7000 Series Room Controller Cause Plug-ins and device resource files required for interface into LON network management tools (e.g. Echelon LonMaker, etc.). Resolution The files are available for download from the Exchange Extranet.

Issue Can more than one MS41-7153 actuator be paralleled when being driven by a MNB series controller? Environment MNB series controller Several MS41-7153 actuators controlled by a common signal. Cause Series of parallel dampers are to be controlled by the same control signal. Resolution Yes several MS41-7153 actuators can be driven by the analog output from a MNB series controller. There are two acceptable methods of providing parallel control. 1. Control the first actuator using either the voltage output or current output from the controller and cascade control from the feedback AO of one actuator into the AI of the next actuator.  The AO of the last actuator should be routed back to the controller to provide feedback confirmation of the damper operation.  In this way should any damper fail, the feedback will indicate that one (or more) of the actuators did not drive to the desired position.  Using this method there is theoretically no limit to the number of actuators that could be driven from one controller AO output.  When controlling a series of actuators in this manner, you must make sure that the power to the actuators are phased correctly, especially if using more than one transformer.   2. Alternate method for use with four or less actuators.  Up to four actuators may be driven using the 4-20 ma drive from the controller.  The 500 ohm resistor should be connected across the actuator wired closest to the controller.  When using this method, and more than two actuators are being parallel controlled, the resistance of the parallel resistor may need to be increased slightly or the drive signal may need to be increased by as much as 2.5% to make up for the parallel resistance effect of the 80 k-ohm input impedance of the actuators.

Issue Are the Niagara G3 ENC-520-2 or the ENC-410-1 certified under UL-864? Environment Niagara G3 Cause Product is being considered as a replacement for the Network 8000 GCM-86000 (which is UL-864 rated). Resolution Both the ENC-520-2 and ENC-410-1 are NOT fire-rated (or UL-864 approved).

Issue Unable to expand "Files" from the Category Service - Category Browser Environment G3 niagara Cause When there are many large backup files in the Files folder Java can run out of memory when attempting to open it. Resolution Move all backup files to a different directory and the Category Browser will open the Files folder.

Issue Trying to access and display I/A Series R2 graphic pages from an Enterprise Server using my Blackberry that has Java ME installed on it but after logging in, nothing is displayed. Environment I/A Series R2 Enterprise Server or UNC graphics pages Cause The I/A Series R2 graphics are not compatible with the JavaME (Java Micro Edition or Java Mobile Edition) that comes pre-installed on the mobile device (smartphone). Resolution The full Java Runtime Environment (JRE) Version 6 is not available on any smartphones or tablet devices at this time.  The I/A Series R2 graphics requires the use of the full JRE Version 6 and is not compatible with JavaME.

Issue Customer is using UI1 of a MNB-300 and is missing an occasional pulse (approximately 1 %) when counting pulses from a water meter. Environment MNB-1000 (DI Inputs only) MNB-300 MNB-70 MNB-V1 MNB-V2 Cause High contact resistance / low open resistance or too short a pulse width. Resolution To detect a closed contact, the contact resistance must be less than 300 ohms.  If the contact resistance is greater than 300 ohms, the contact closure may not be detected. To detect an open contact, the contact resistance must be greater than 2500 ohms.  If the open contact resistance (open circuit resistance) is less than 2500 ohms, the controller may not detect that the contact is open. MNB-1000 DI1 - DI4  require a minimum contact closure duration of 50ms and a minimum contact open duration of 50ms. MNB-300 UI1 require a minimum contact closure duration of 50ms and a minimum contact open duration of 50ms. MNB-300 UI2 - UI6 require a minimum contact closure duration of 500ms and a minimum contact open duration of 500ms. MNB-70 UI1 - UI3 require a minimum contact closure duration of 500ms and a minimum contact open duration of 500ms. MNB-V1/V2 UI1 - UI3 require a minimum contact closure duration of 500ms and a minimum contact open duration of 500ms.

Issue When starting an I/A Series G3 station on an ENC, the error message "Fox tunneling not licensed" is displayed in the Application Director console output log. Environment I/A Series G3 ENC Cause FOX Tunneling license option not present in station license. Resolution Fox Tunneling is not intended for use through an ENC and therefore cannot be licensed on the ENC. Fox tunneling is configured as part of the Niagara Fox Service on the properties page of the "NiagaraNetwork" driver. 

Issue R2 UNC station fails to start and displays the following error messages in the Standard output window: Tridium Niagara Station, r2.301.529.v1 [UNC9] tridium.foundation.TRuntimeException E_INVALID_DSTABLE_CODE {165.16} at tridium.foundation.DsTable.codeToSpec (bytecode 58) at tridium.foundation.DsTable.codeToClass (bytecode 1) at tridium.foundation.node.NodeProperty.readExternal (bytecode 70) at tridium.foundation.node.Node.readExternalSchema (bytecode 27) at tridium.foundation.node.Node.readExternal (bytecode 50) at tridium.foundation.node.NodeSet.readExternal (bytecode 132) at tridium.foundation.node.NodeSet.read (bytecode 43) at tridium.foundation.prism.LoaderModule.loadFromSns (bytecode 48) at tridium.foundation.prism.Prism.loadFromSns (bytecode 4) at tridium.foundation.Sys.bootLocalSns (bytecode 11) 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) *************************************************************** FATAL: Cannot boot station from sns java.lang.IllegalStateException: NodeProperty.readExternal: tridium.foundation.T RuntimeException E_INVALID_DSTABLE_CODE {165.16} at tridium.foundation.node.NodeProperty.readExternal (bytecode 143) at tridium.foundation.node.Node.readExternalSchema (bytecode 27) at tridium.foundation.node.Node.readExternal (bytecode 50) at tridium.foundation.node.NodeSet.readExternal (bytecode 132) at tridium.foundation.node.NodeSet.read (bytecode 43) at tridium.foundation.prism.LoaderModule.loadFromSns (bytecode 48) at tridium.foundation.prism.Prism.loadFromSns (bytecode 4) at tridium.foundation.Sys.bootLocalSns (bytecode 11) at tridium.tools.StationMain.bootSns (bytecode 0) at tridium.tools.StationMain.doIt (bytecode 352) at tridium.tools.StationMain.main (bytecode 10)   Environment Niagara R2, UNC-410, UNC-520 Cause A needed Lon module is not installed in the UNC. Resolution Typical the Standard Output Window error messages usually provide some reference to the missing jar file. In this case, the lonTrane module was not installed in the UNC. Check to see what lon devices are installed in the station, and install all of the needed modules (jars) to the UNC.  

Issue Supported Oracle database version for I/A Series R2 Environment I/A Series R2 Oracle database driver (IA-ORCL-DBS) Cause A customer wants to use an Oracle database for I/A Series R2 instead of the default Cloudscape database. They need to know the Oracle database versions that has been tested with the driver. Resolution The I/A Series R2 Oracle database driver is compatible with Oracle database version 9i and has also been tested with Oracle version 11g.  

Issue What was the last version of Windows supported by Wonderware for Intelligent Buildings (WIBS) version 1.1 service pack 3? Environment WIBS 1.1 InVue 1.1 Cause A customer must replace his computer hardware and will make efforts to obtain the operating system supported by WIBS / InVue. Resolution The last operating system supported was Windows 2000 service pack 3.  There have been several instances of it working on Windows 2000 service pack 4 and Windows XP service pack 3. In all three instances, virtual machines were not tested. Windows XP and Windows 7 have not been tested and will not be tested.