Building Automation Knowledge Base

Issue Trying to locate the BACnet PICS for a UNC and ENC.  Where are they located? Environment Niagara R2 revision 522 and higher Niagara G3 revision 3.2 and higher Cause Trying to locate a web-based resource for this information Resolution For Niagara R2, click here for the BACnet PICS.  For Niagara G3, click here for the BACnet PICS. 

Issue Ordering the proper software options for a Vykon Energy Suite installation on a Niagara G3 jobsite. Environment Niagara G3 Cause The Vykon Energy Suite is only available for purchase via Sourced Products from Tridium.  The part numbers and descriptions are difficult to locate. Resolution The feature that licenses TEA-BASE (eas) is included with the standard ENS-1. So, a separate purchase of TRD-TEABASE-G3 is no longer required (since it is not usable without licensing stations or points). TRD-TEASTA-G3 increments the station limit parameter and allows unlimited points from an ENC. TRD-TEAPNT-G3 increments the point limit parameter and allows individual points from an ENC as well as points within the ENS as required. Additional documentation: VES G3 Users Guide VES G3 Datasheet These two part numbers are now available on iPortal for ordering.  Contact Customer Care at ccc.orders@schneider-electric.com or 1-888-444-1311 (press 1) to place an order.

Issue Is a license required for the S4 BACnet to N2 Routers? Environment S4 BACnet to N2 Router-16 S4 BACnet to N2 Router-32 S4 BACnet to N2 Router-64 S4 BACnet to N2 Router-128 S4 BACnet to N2 Router-256 I/A Niagara R2 I/A Niagara G3 I/A BACnet Metasys N2 network Cause Additional information on 3rd party router Resolution No license is required. But you will need to fill out the S4_Group_Order_Form and send it to CCC at the time of ordering. Link to S4 BACnet to N2 Routers for additional information

Issue As of December 2010, Microsoft® Windows XP is no longer available, preinstalled on new computers. Is there a valid, legal and legitimate workaround for running our software products that will not run on Microsoft® Windows 7? Environment New computer that was purchased pre-loaded with Microsoft® Windows 7 Professional or Microsoft® Windows 7 Ultimate I/A Series software that runs only on Microsoft® Windows XP such as: I/A Series (Niagara) R2 - all releases I/A Series (Niagara) G3 - all releases prior to 3.6.x  Signal XP WorkPlace Tech Tool 3.2sp1 Cause Microsoft® Windows XP is no longer available on new computers. Resolution Downgrade the Microsoft® Windows 7 Professional / Ultimate installation to Microsoft® Windows XP. According to the Microsoft® Windows 7 Professional / Ultimate EULA (End User License Agreement) that the computer user must read when starting up a new computer, the following Operating System downgrade rights are available: Downgrade rights for Windows 7 are an end-user right, documented in the Software License Terms that customers accept upon first running Windows software. Windows 7 end user downgrade rights will be available through the sales lifecycle of Windows 7 which is up to two years after the launch date of a new version.  UPDATE:  As of November 2012, Microsoft has upgraded their Windows Lifecycle information, indicating that this upgrade right expires in February, 2014. More information is available from the Microsoft Windows web site and from the attached document.

Issue Shielded twisted pair cable may have been installed in an area of high EMI/RFI, and proper grounding of the shield wire is necessary to make the shield effective. Environment A segment of LON trunk with shielded, twisted-pair cable. Cause Proper grounding helps to avoid DC and 50/60 Hz ground paths from being formed through the shield. Resolution Follow the Guidelines as presented in the Echelon FT 3120/ FT 3150 Smart Transceiver Data Book, page 114, Figure 5.7 "Terminating and grounding Shielded Twisted Pair Cable." Grounding Shielded Twisted Pair Cable When using shielded twisted pair, terminate the twisted pair and ground the cable shield, as shown in Figure 5.7. Figure 5.7 Terminating and Grounding Shielded Twisted Pair Cable The twisted pair is terminated according to the guidelines listed in the previous sections. The cable shield should be grounded using a capacitor to tie the shield to earth ground, and a large-value resistor to bleed off any static charge on the shield. Tie the shield to earth ground through a capacitor, instead of a direct connection, in order to avoid DC and 50/60 Hz ground paths from being formed through the shield. Typical values for Rb and Cc are as follows: Cc = 0.1 µF, 10%, Metalized Polyester, ≥100V Rb = 470kΩ, 1/4W, ±5% The cable shield should be grounded at least once per segment, and preferably at each device.

Issue How many MicroSmart devices and Microsmart trunks does the Niagara G3 driver ENC-DRV-MS support? Environment ENC-520 Series ENC-DRV-MS Cause Incorrect product data sheet F-27425-3. Resolution ENC-DRV-MS driver supports 124 MicroSmart devices and a maximum of 4 Microsmart trunks. Note ENC-520 product data sheet [F-27425-3] options for ENC-DRV-MS31,MS62,MS93,MS124 are incorrectly shown.

Issue I/A Series R2 (Niagara) ibsAsd driver "FATAL: Cannot boot station from sns java.lang.NoClassDefFoundError: tridiumx/serialDriver/services/AsyncEventSource" Environment I/A Series R2 (Niagara) ibsAsd Driver Cause serialDriver Module is missing.  Resolution Use the Admin Tool (Configure Modules Only) and add the serialDriver jar.  Click Here to see document

Issue Review of Windows event log, product event logs, or error windows during operation provides an error code number that is unreadable. Environment Microsoft Windows Cause Microsoft uses a standard list of error codes which programs can access. The display of these errors is typically in a decimal or hexadecimal format. Resolution Use the Windows Error Codes spreadsheet which allows the user to enter the code as either Hexadecimal or Decimal format and provide the text description for the error code. Use the error code description to further diagnose the problems being experienced. Guidance on whether a code is Hexadecimal or Decimal: 0x00000001 - Hexadecimal -214000000 - Decimal

Issue Displayed temperature on the ETR is offset from the actual temperature reading of the controller. Environment ETR Thermostat Cause Factory calibration is offset from actual temperature. Resolution Click here to download the Installation and Operating Instructions Temperature Display Adjustments Temperature display may be adjusted by adjusting the ZERO or OFFSET Potentiometer (P2) as shown on the diagram.  Adjust P2 until the LCD Display reading, matches your controllers temperature reading if necessary. Note that all LCD Displays, are factory calibrated using an NIST Certified Glass Thermometer.

Issue When viewing a graphic (or other object requiring a Java plugin) in Google Chrome you get the message "This plug-in is not supported" where the graphic should have been shown Environment Webstation Xenta Server I/A Series G3 version 3.8.xx or earlier Cause Google Chrome has disabled Java in version 42 and above Resolution 1: Open Google Chrome 2: In the address field, enter the following: chrome://flags/#enable-npapi 3: Click on "Enable" to enable the feature so it looks like this 4: Click on relaunch to restart Chrome   More information from Java's web site

Issue When a graphic is dragged out of the kitPxGraphics module, the image location on the px page shows ‘file:^px/’ and the path.  Sometimes the image displays, sometimes is does not display.  It behaves like this on some laptops but on others, it’s fine.   Environment Niagara G3 / AX 3.8.37 server stations and soft jaces Cause There could be an issue with a recent Windows update. Resolution The work-around is to exclude a line from the system.properties file:   niagara.ui.px.maxImageModuleFileSize=2047 Place a '#' sign in front of this line and the module path is used instead of the px file space.

Issue Does the Valve & Actuator Selection Tool work on Windows 8? Environment Valve, Actuators Cause Current desktop, laptop, and tablets are installed with Windows 8 Resolution Until a newer version is released, the following work-around will allow the Tool to operate in a Windows 8 environment: To install, the program will need to detect .Net 2.0.  To do that, ensure some .Net features are on.  Internet access is required.   1.  Go to Control Panel - Programs - Programs and Features and in the upper left will be a link to "Turn Windows Features on or off"  -  click that. 2.  From the Windows Features Screen, make sure there are check boxes next to .Net Framework 3.5 and the two boxes below it as shown here: 3.  Restart Windows and then install the Valve & Actuator Selection Tool 4.  Turn off User Access Controls in Windows.  Go to User Accounts and Family Safety (Control Panel) - User Accounts  - click the link to "Change User Account Control Settings".  In the dialog that follows - move the slider to the bottom (Never Notify) 5.  Right-click on the Valve & Selection Tool icon on your desktop (from the installation in step 3) and choose "properties". 6.  On the Compatibility Tab - check the box to run the program in Windows 7 compatibility mode and the box to run the program as administrator. 7.  Run the Valve & Selection Tool program.

Issue Getting error message: “Login Failed - Could not connect to fox server. Check that fox and web SSL settings match or try connecting using https.” when trying to connect to G3 station via a web browser. Product Line TAC IA Series Environment In Niagara G3, Version 3.7.106 Cause Security setting for the Web browser and Fox Service do not match, or the FOX or FOXS port is being blocked. In Niagara G3, Version 3.7 and later, users can set up SSL for both HTTP and FOX connections. The intention is that, when using the applet, SSL settings for HTTP and FOX must match (i.e. HTTPS/FOX or HTTP/FOXS are not allowed). In Niagara G3 3.7 update1 and earlier, users can connect to the applet using the invalid HTTPS/FOX combination. In addition, when loading the applet while using HTTP/FOXS, users are redirected back to the login screen with no error message. In NiagaraAX 3.7 update2 and later, users attempting to use the applet with an invalid HTTPS/FOX or HTTP/FOXS connection will be redirected to the login screen. An error message will appear indicating what went wrong. The Web and Fox settings do not match. They must be set to either HTTP/FOX or HTTPS/FOXS. We’ve found that there is a condition where the error message still displays even though both Fox Service and HTTP match. Reason being is during login to a station via web browser, a check is performed to determine if the Fox Service match the HTTP setting be used. If accessing via HTTP, then port 1911 (FOX) is checked. If accessing via HTTPS, then port 4911 (FOXS) is checked. We found that the corresponding, FOX or FOXS, port were not opened.  Resolution Open the needed FOX or FOXs port: Depending on if HTTP or HTTPS is used, the correct port must be opened for the corresponding FOX or FOXS connection. Port 1911 needs to be open if using HTTP/FOX connections, and if using HTTPS/FOXS, port 4911 needs to be open. Port need to be open to bidirectional TCP traffic.

Issue MicroNet Heat Pump / Fan Coil Controller Diagnostic Table Environment MicroNet 2000 MN-HPFC Cause Quick reference table with corrective action Resolution This table is an excerpt from the MicroNet Heat Pump / Fan Coil Controller Reference Manual (F-26174):

Issue When adding MNL controller in Workstation for Projects, it will show up an error: Object type is not supported. Environment SmartStruxure 1.5 Workstation for Project PCS MNL controller Cause When using the Project Configuration Server, you cannot create MNL LonWorks devices and applications. Accordingly, the WorkPlace Tech Editor option does not display in the Control Panel. Resolution MNL LonWorks devices can be added in an Enterprise Server or Automation Server after deploying a project to one of these servers.

Issue The property list for an Analog Input / Output or Binary Input / Output object in the WorkPlaceTech application shows a "Process Time" parameter: OR instead of a "COV Increment" parameter" Note that for Binary I/O objects, the COV increment is implied as any change of binary value and is not displayed. Environment MNB series controller WPT application file MNB series controller with firmware release 1.4 or newer WorkPlace Tech Tool software, release 5.5 or newer Cause Prior to firmware version 1.4, the MNB family of controllers did not support COV Subscription functionality. Resolution The existing I/O object must be deleted and recreated, using the WorkPlace Tech Tool software release 5.5 or newer, to allow the use of the COV Increment parameter.

Issue Can additional mounting clips for the MNL-VxRVx or MNB-Vx controllers be purchased? Product Line TAC IA Series Environment MNL-VxRVx or MNB-Vx controllers Cause Each MNL-VxRVx and MNB-Vx controller includes one mounting clip that can be moved from the factory shipped location (bottom) to the side of the controller base.  The mounting clip is also known as the mounting foot or pivot bracket. Resolution Replacement or additional mounting clips can be purchased using part number DVAV-242.

Issue Application Director output window and LON proxy point indicates fault: java.lang.ClassCastException: javax.baja.sys.BDouble ERROR [14:56:22 20-Aug-14 EDT][lon1] Could not decode nv update data Misc9:nvoSpaceTemp java.lang.ClassCastException: javax.baja.sys.BDouble    at javax.baja.lonworks.londata.LonFacetsUtil.makeLonQualifiers(LonFacetsUtil.java)    at javax.baja.lonworks.londata.LonFacetsUtil.getQualifiers(LonFacetsUtil.java)    at javax.baja.lonworks.londata.BLonData.primitiveFromInputStream(BLonData.java)    at javax.baja.lonworks.londata.BLonData.fromInputStream(BLonData.java)    at javax.baja.lonworks.londata.BLonData.fromNetBytes(BLonData.java)    at javax.baja.lonworks.BNetworkVariable.receiveUpdate(BNetworkVariable.java)    at com.tridium.lonworks.NvManager.receiveLonMessage(NvManager.java)    at com.tridium.lonworks.loncomm.NLonComm.routeToNvListener(NLonComm.java)    at com.tridium.lonworks.loncomm.NLonComm.receiveLonMessage(NLonComm.java)    at com.tridium.lonworks.loncomm.NLonLinkLayer$AppBufferReceive.run(NLonLinkLayer.java)    at java.lang.Thread.run(Unknown Source) Environment I/A Series G3 (all versions) Cause This error is related to a mismatch between the lonworks module running on the ENC/JACE versus the version being used within the Workbench modules folder.  A different version of Workbench and/or lonworks module is being used to engineer the ENC/JACE. Resolution Review the versions between the Workbench and ENC/JACE and match the versions.

Issue After troubleshooting a communications issue, the DCM daughterboard (or piggyback board) was deemed defective.  Can it be removed and replaced with another in the field? Environment DMS MicroSmart controller (revision 9) -- Model numbers affected are DCM-UC, DCM-IOC, DCM-GPC Cause Internal board failure Resolution Yes, the DCM board can be swapped out.  Care must be taken not to damage the pins and clips (identified below in yellow).

Issue A GCM has been removed in the field and replaced with a newer product (i.e. a Niagara Jace or a SmartStruxure AS).  How can the GCM be disabled from communicating in TreeTech without actually deleting it?  Environment TreeTech (all revisions) Cause The GCM's programming logic will be used for a short period of time as a reference.  Then, the entire GCM will be deleted from TreeTech. Resolution Right-click on the GCM and go to Properties. Click the Offline Status tab. Select Offline from the drop-down menu. Close the window. Offline mode disconnects the GCM database in TreeTech from the field.