Building Automation Knowledge Base

Issue When importing an XIF into SmartStruxure, errors can be generated that vary in nature. Product Line EcoStruxure Building Operation Environment SmartStruxure Enterprise Server SmartStruxure Automation Server Building Operation Workstation Cause The XIF does not import successfully for a variety of possible reasons: There exists a device template in the server already that contains the same device ID as the XIF that is being imported.  The XIF does not comply with the LonMark Device Interface File Reference Guide published by LonMark. Resolution Before performing any of the steps below: Import the XIF file provided by the manufacturer of the Lon controller - if the manufacturer did not provide a XIF, try searching the LonMark product catalog If the provided XIF does not work, upload the XIF from the device to ensure that it is the correct file by following How to extract an XIF out of a Lon controller. Use the SBO SNVT Support tool found on The Exchange to identify unsupported SNVT's. Work through the troubleshooting steps below.   Device Template Fails without an Error This issue has been seen in some of the older versions of SmartStruxure (1.5 and older) and upgrading to the latest version will resolve the issue in many cases. If the issue occurs at the latest version of SmartStruxure: Use the SBO SNVT Support tool located on The Exchange to identify unsupported SNVTs. If the SBO SNVT Support tool does not identify any unsupported SNVTs, then send the XIF in to Product Support for further investigation.    Device Template Already Exists In order to complete the import of the XIF, follow these steps. Delete all controllers in that database that are using the device template that has the same device ID as the XIF file you are trying to import.  Now import the XIF again. Select the server in the system tree on the left and go to File > LonWorks import > Device Template. Click the Browse button and select the XIF you want to import. Click Import. Note: When the import is complete it will have overridden the old device template with that device ID. Two device templates with the same device ID will not be able to reside in the same database. For more information about device templates see Delete Device Templates.   Detailed Error Prompt with Specific Fields Listed Some examples of the detailed errors include but are not limited too: "Field X has error(s). The string must between X and X characters. nvoActualCapacity has X characters" on row X. "Field X has error(s). The number must between X and X. Field X has value X." on row X. "Field X has error(s). The value must be X but was X." on row X. Space or tab are not allowed in field 0Node Object on row X.   To Address these issues: Download Notepad++ to be able to better navigate the XIF by row number. Using Notepad++, open the XIF. NOTE: Backup the original XIF just in case there is a mistake when modifying. Find the row and field number prompted by the error messages and modify them accordingly. All the rules can be found in LonMark Device Interface File Reference Guide published by LonMark. Import the XIF again to verify whether it works. If not, contact Product Support for further investigation.

Issue Programming an application that requires a setpoint and deadband that operates in the same manner as the WorkPlace Tech Tool Thermostat object. Environment SmartStruxure AS or ES Cause No object exists in the Function Block library that is functionally equivalent to the I/A Series WorkPlace Tech LON/BACnet "Thermostat" object.   Resolution This is only one of several methods by which a differential type thermostat object can implemented in Function Block programming. The following Binary Expression (XPB) function block object can be used to simulate the differential type thermostat. Analog Input A is the "Input" Analog Input B is the "Setpoint" Analog Input C is the "Input Differential" Binary Input d is the "State Feedback"  This feedback link insures that the output state does not change when the input is within the range specified by the input differential The output of this object turns on when the Input value exceeds the Setpoint + 1/2 of the Input differential. The output of this object turns off when the Input value falls below the Setpoint - 1/2 of the Input differential. The xml file can be downloaded from here.

Issue Where can additional information on the SPW100 series differential pressure switches be found. Environment SPW100, SPW102, SPW104,SPW106, SPW108, SPW110, SPW114 Cause Only the Schneider Electric datasheet and CE declaration are posted on the Extranet, no installation documents are available. Resolution Attached are the OEM suppliers datasheet and installation guide along with the Schneider Electric documents. Download here.

Issue Procedures to purchase and unlock a permanent copy of WorkPlace Tech Tool (Asia Pacific customers) Product Line TAC IA Series Environment I/A Series WorkPlace Tech Tool software version 5.x. Cause WorkPlace Tech unlock code request should not be sent directly to Customer Care since orders in Asia Pacific are placed through Hub Asia.  Resolution 1. Install WorkPlace Tech. 2. After installation, generate the codes required to request an unlock code. 3. Complete the Unlock Code Request Form or output it to the file (InVueOrder.txt). Submit the form or the file together with the purchase order to your local orders processing team.  The procedure to generate the order codes can be found in the WorkPlace Tech Tool Installation Instructions. 

Issue There's a need to know what characters the XP Display will show Environment XP Display Cause Many languages use different character sets and not all are supported in the XP Display Resolution The standard ascii character set is supported by the XP Display. This is indicated on Pg. 17 of the XP Display User Guide. Click here to download the XP Display User Guide

Issue There's a need for information on the Personnel Import Utility Product Line Andover Continuum Environment Continuum Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause Finding the information on the Personnel Import Utility may be difficult to locate. Resolution The information for the Personnel Import Utility can be found in the latter part of Chapter 19 on Personnel. There is additional information in Appendix C related to the tables and XSLT file. Click here to download a copy of just the PIU Manual.

Issue This is a short guide to show the correct use of output blocks with forced values in Function Block programs Environment SmartStruxure AS using Function Block programs Cause There is a design difference between the Vista Menta function block programming and the new version for SmartStruxure. In the old Menta programs it is possible to connect the output from an output block and connect it to an expression block. The forced value from the output block was passed to an expression block connected downstream of the output block. This is NOT supported in SmartStruxure at the current release Ver 1.3 (April 2013) If this is done in SmartStruxure then should the output block be forced in any way the forced signal is ignored by the downstream block Resolution Follow the guidelines as detailed in the attached document.

Issue LNS plug-ins are needed in order to configure certain application specific controllers. Product Line EcoStruxure Building Operation Environment Workstation Open LNS Server Cause Many application specific controllers can be configured through Workstation but this can be very time consuming. Starting with Version 1.4.0, SmartStruxure is now able to support LNS plug-ins. Key points and features Click SBO v1.4 Activation Key for OpenLNS Server - SmartStruxure solution - PA-00285 to download the StruxureWare Building Operation v1.4 - Activation key for OpenLNS Server product announcement. Echelon OpenLNS Server must be installed on the computer that plug-ins will be used. LNS Server plug-ins can be used at the workstation to configure TAC Xenta devices using TAC STR 350 plug-in 5.1.9 or later. (earlier versions won't work) LNS Server plug-ins can be used at the workstation to configure TAC Xenta devices using TAC 100 plug-in 5.1.9 or later. (earlier versions won't work) LNS Server plug-ins can be used at the workstation to configure third party LON devices. The LNS plug-in capability will only work if the device does not require to be online to configure. If the manufacturer's plug-in requires active communication with the device then the plug-in implementation will not work. StruxureWare Building Operation database is automatically updated to any changes created with the plug-in. Resolution For LNS plug-ins to work in SmartStruxure, Echelon OpenLNS Server must be purchased and installed on the computer where plug-ins will be used. Purchasing Echelon OpenLNS Server An activation key must be purchased in order to install Echelon OpenLNS Server. The activation key is available to purchase through Schneider Electric using the part number SXWSWLNSX00001. The activation key can be purchased through standard product ordering procedures. After ordering, the activation key will be sent to you via email within a few days. Installing Echelon OpenLNS Server WARNING: You can not install OpenLNS Server on the same computer as TurboLNS without upgrading Turbo to Open. You will now be converting any TurboLNS databases to OpenLNS if they are opened on this computer. Once you have purchased the OpenLNS activation key and received it via email from Schneider Electric then you can now install Echelon OpenLNS. Double click on the executable to start the OpenLNS install wizard. Click Next. Select 'I accept the terms in the license agreement' and click Next. Fill out the information and enter you activation key. Click Next. Click Install. Click Next. Click Finish. NOTE - At step 7 above, if the PC is not connected to the internet, the registration may require an email to be send manually to Echelon to register the licence code.  Uninstalling Echelon OpenLNS Server Make sure you reference the OpenLNS Server License Guide here for information on how to return the OpenLNS license in order to use it again.   Registering LNS Plug-ins Note: Before registering LNS plug-ins, they must be installed on the computer first. If working with TAC Vista Xenta 100 and TAC STR 350 controllers, the plug-ins must be version 5.1.9 or greater. ZBuilder is included in the TAC Vista 100 download. These can be downloaded off of the Extranet in the same place as the SmartStruxure software. See LNS plugins for SmartStruxure 1.4 are not included in the release, but downloaded separately for more information. In SmartStruxure Workstation, go to the Control Panel. Click on 'LNS Plug-in Registration'. In the 'Available LNS Plug-ins' field, select the plug-ins you want to register and then click the right arrow to move to the 'Registered LNS Plug-ins" field. Click the save icon on the System tab. Note: If registering the TAC Xenta 100 plug-in, you will be prompted to select the devices you want to register. Then click OK.   Using the LNS Plug-ins Note: All changes made in the LNS plug-ins are offline configuration changes. The LNS plug-in support in SmartStruxure will not support devices that are required to be online for plug-in use.  Right click on the controller, click Configure... The LNS server is checked for a matching device template and the current device configuration is saved to the LNS server. Click Next. Double click on the plug-in listed in the window. This will launch the LNS plug-in. Make configuration changes to the controller and then save or exit the plug-in. Click Next. Click Next. The configuration changes that have been made will be listed in the window while they are being saved to the LNS server. Click Finish. Now the configuration changes that were made in the LNS server need to be downloaded to the controller. Right click on the controller in Workstation and select 'Download device configuration'.

Issue Documentation for KLR-E AC Room Controllers / Thermostats Environment AC Room Controllers Thermostats Cause Documentation for KLR-E type thermostats. Resolution KLR-E Thermostats are manufactured by EBERLE (Invensys) and available from Schneider Electric in Europe. Click here to download KLR-E documentation in French Click here to download KLR-E documentation in English/German

Issue Poor or unreliable ground connection of IO modules can cause controller failure, inputs to stop updating and communications to be poor. Environment Netcontroller IO modules Cause Strings of IO modules were installed on each DIN rail in a panel. One IO module per row had directly landed ground wires, but each of the other modules on the row relied on contact between a metal clip on the back of the module and the DIN rail.  Observed an average of two I/O modules per panel with inadequate earth ground (where this clip was not making an electrically sound connection). In some cases, resting a hand on one of the modules caused a wide variance in the grounding quality. Resolution After installing a panel (not just in the panel fabrication shop), measure each IO module's ground terminal to ground. Do not just assume that each IO module is properly grounded  to the DIN rail via the clip on the back. And do not just assume that the DIN rail is properly grounded - some DIN rail is plated to reduce corrosion and this can increase resistance. If there is (or will be) any vibration or moisture, or there are any other concerns that site conditions may negatively effect grounding of the IO modules in the future, consider grounding each IO module's ground terminal via a conductor to ground.   There is a Technical Product Advisory here that will provide further detail on this.

Issue Program to calculate the Sunrise time / Sunset time Environment Programmable Object Sunrise Sunset Cause Customer needs a program to calculate the Sunrise / Sunset times in Sheffield. Resolution To review the Sunrise / Sunset times for the required area, please click HERE. When connected to the site, proceed as follows; "Find a Location" enter the required location and select GO. Choose "Almanac" Choose "Sunrise / Sunset" Select the month you require. The required programmable Objects are shown below, or to upload the objects and lookup table details, please click HERE. Day of the Year. Object 1 10 XInt = DAY 20 IF MONTH >= 2 THEN XInt = XInt + 31 30 XFlo = FLOAT ( YEAR ) 40 XFlo = XFlo / 4.00000 50 XFlo = FRAC ( XFlo ) 60 IF XFlo = 0.000000 THEN YInt = 1 ELSE YInt = 0 70 IF YInt = 0 AND MONTH >= 3 THEN XInt = XInt + 28 80 IF YInt = 1 AND MONTH >= 3 THEN XInt = XInt + 29 90 IF MONTH >= 4 THEN XInt = XInt + 31 100 IF MONTH >= 5 THEN XInt = XInt + 30 110 IF MONTH >= 6 THEN XInt = XInt + 31 120 IF MONTH >= 7 THEN XInt = XInt + 30 130 IF MONTH >= 8 THEN XInt = XInt + 31 140 IF MONTH >= 9 THEN XInt = XInt + 31 150 IF MONTH >= 10 THEN XInt = XInt + 30 160 IF MONTH >= 11 THEN XInt = XInt + 31 170 IF MONTH >= 12 THEN XInt = XInt + 30 180 RETURN VIA TEXT 200 VALUE XInt  Sunrise Time Calc.  Object 2 10 XFlo = POINT 0|1 20 YFlo = FLOAT ( YEAR ) 30 YFlo = YFlo / 4.00000 40 YFlo = FRAC ( YFlo ) 50 IF YFlo = 0.000000 THEN YInt = 1 ELSE YInt = 0 60 IF YInt = 1 AND MONTH >= 3 THEN XFlo = XFlo - 1.00000 70 ZFlo = LOOKUP ( 1001 , XFlo ) 80 ZFlo = ZFlo / 60.0000 90 YFlo = FRAC ( ZFlo ) 100 ZFlo = ZFlo - YFlo 110 YFlo = YFlo * 60.0000 120 YFlo = YFlo / 100.000 130 ZFlo = ZFlo + YFlo 140 RETURN VIA TEXT 203 VALUE ZFlo  Sunset Time Calc.  Object 3 10 XFlo = POINT 0|1 20 YFlo = FLOAT ( YEAR ) 30 YFlo = YFlo / 4.00000 40 YFlo = FRAC ( YFlo ) 50 IF YFlo = 0.000000 THEN YInt = 1 ELSE YInt = 0 60 IF YInt = 1 AND MONTH >= 3 THEN XFlo = XFlo - 1.00000 70 ZFlo = LOOKUP ( 1001 , XFlo ) 80 ZFlo = ZFlo / 60.0000 90 YFlo = FRAC ( ZFlo ) 100 ZFlo = ZFlo - YFlo 110 YFlo = YFlo * 60.0000 120 YFlo = YFlo / 100.000 130 ZFlo = ZFlo + YFlo 140 RETURN VIA TEXT 203 VALUE ZFlo  Sunrise/Sunset Interlock.  Object 4 10 XFlo = POINT 0|2 20 YFlo = FRAC ( XFlo ) 30 XFlo = XFlo - YFlo 40 YFlo = YFlo * 100.000 50 IF HOUR >= INT ( XFlo + 1.00000 ) THEN GOTO 90 60 IF HOUR = INT ( XFlo ) THEN GOTO 100 70 XInt = 0 80 RETURN FALSE "Plant Off" 90 XInt = 1 100 IF MINUTE >= INT ( YFlo ) THEN XInt = 1 110 XFlo = POINT 0|3 120 YFlo = FRAC ( XFlo ) 130 XFlo = XFlo - YFlo 140 YFlo = YFlo * 100.000 150 IF HOUR >= INT ( XFlo ) THEN GOTO 170 160 GOTO 180 170 IF HOUR >= INT ( XFlo + 1.00000 ) OR MINUTE >= INT ( YFlo ) THEN XInt = 0 180 IF XInt = 1 THEN RETURN TRUE "Plant On" 190 RETURN FALSE "Plant Off"

Issue SCD100 is obsolete and needs to be replaced. Product Line Field Devices Environment SCD100: 004630100 004630110 SCD110: 5152300000 5152302000 (SCD110-D) 5152304000 (SCD110-D-H) 5152306000 (SCD110-H) Cause Replacing obsolete sensor SCD100 with new range of sensors SCD110. Resolution The range of SCD110 sensors are replacing the old and obsolete SCD100 sensors. For a complete overview and for more technical details, please see the SCD data sheet.

Issue What 10k Thermistor sensors are compatible with the I/A Series MNL and MNB families of controllers? Product Line TAC IA Series, Andover Continuum Environment I/A Series LON Controllers (MNL-xxxxx) I/A Series BACnet Controllers (MNB-xxxxx) Continuum 10K T3 Sensors Cause Specification information Job spec requires a specific family of sensors.  Need to know how to compare the TC curves. Resolution Compatible sensors that have a built-in 11k shunt resistor include the TS-5711-850, TS-57011-850, TS-57031-850, and TSMN-90110-850 Series.  NOTE: These sensors are no longer available for purchase. The TW2XAXK is the replacement Any sensor that matches resistance to temperature curve for a 10K Thermistor Type G (U.S.Sensor), Type 9 (Dale/Vishay) or Type III (ACI Series AH) can be used with the I/A Series MNL and I/A Series MNB series controllers, provided that a 11k ± 0.1% 1/8 watt resistor is wired in parallel with the sensor. The input has a range of -10 to 135 °F (-23.3 to 57.2 °C) with an accuracy of ±1% of span.   This includes the Continuum 10K T3 sensors.  The table below shows that the resistance in its normal operating range is within a few ohms of the TSMN non 11K shunted sensors.  The Continuum sensor can be used with a parallel 11K ohm resistor. The full temperature / resistance table for the US Sensor 10K Thermistor R-T Curve Type G sensor can be found here.  Please note that the controller may not be able to use the full temperature range shown in the table.    

Issue Some SNVT's are not updating correctly. Environment Sigma IC IC3 LON SNVT's Cause LON Bindings are not correctly configured as a "Sigma" connection type. Resolution The IC-LON configuration process is explained fully in the "IC-Lon Configuration document attached HERE. Part of the above document deals with the use of the IC-Lon Plug-in. This Plug-in will create the "Sigma" connection type which is used by the IC-Lon. Below is a screen shot of this connection type. This connection type is selected "Unackd", the advanced settings are shown below. If the correct connection type is not used, then the bindings will not operate correctly.

Issue Cannot order the VZ*9 valves, its no longer available.  Environment VZ*9 VZ*19E VZ*19* VZ*19C MZ20 Cause A new line of VZ valves is now available. Resolution The old VZ series valves have been replaced with a new. The old (VZ*9) is replaced by the VZ*19* (Either to VZ*19E (Flat face) or VZ*19C (Compression). The MZ20 actuator range can still be used with the new valve range. For more information and details, please see  the related data sheets. VZ*9 Valves, MZ20A Actuators and MZ20B Actuators.

Issue How many Modbus TCP Clients can be connected to Vista via an Xenta 913? Product Information TAC Vista Environment Vista 5.1.X Xenta 913 5.1.X or later Xenta 511 5.1.5 or later Xenta 701 5.1.5 or later Xenta 711 5.1.5 or later Xenta 721 5.1.5 or later Xenta 731 5.1.5 or later Cause When planning a system it's important to know how many devices are required. Resolution A maximum of 40 Modbus TCP clients are supported when communicating via a Xenta 913, Xenta 511 or Xenta 700. Each TCP Client may have up to 100 Modbus devices (see page 4 in the datasheet).  

Issue Error when trying to add exceptions to a schedule is seen when trying to "apply" the changes. Example: Personnel Manager Error saving data Communication Error Exception has been thrown by the target of an invocation. The personnel object was created Product Line Andover Continuum Environment Continuum Cause Too many old exceptions in the schedule. Sometimes RPC (Remote Procedure Call) errors happen on Cyberstation following the above error. Resolution Delete the old exceptions. This must be done manually for infinet schedules. 1.94 NOTE: If this issue is happening for 1.94, there is Hotfix for TPA CONT 12 0002.00 Schedule Exception Errors.zip that has been released for this issue. The V1.94 issue is also detailed in Technical bulletin: TPA-BOST-12-0002.00  

Issue Replacement for a V295 steam valve and an M750 actuator. Environment V295 Steam Valve M750 Actuator Cause Unable to purchase a V295 steam valve and an M750 actuator. Resolution The V295 steam valve and an M750 actuator are obsolete. M750 - 24v - 880-0010-000 -  Not available - To operate on steam you will require a spring return actuator, the M700-SRSU (880-0430-000). V295 - DN 40, PN25, KVS25 - Not available. A replacement could be the VGS211F-40CS please note this valve has a rating of PN16, where as the V295 was PN25. To review the VGS211F data sheet, please click HERE. To review the M700 data sheet, please click HERE.  

Issue Key/card numbers Largenumber Hexadecimal Decimal   Environment I/NET keycards Cause Converting Hexadecimal to Decimal and vice versa Resolution See the attached document for a clearer understanding of the formats conversion: Hexadecimal/decimal

Issue Working with a 3rd-party lon controller with no existing shadow object available.  Niagara G3 provides the ability to create a shadow object on the jobsite using the Lon Xml Tool. Environment Niagara G3 Cause A shadow object is not available for a specific 3rd-party controller and a dynamic device fails to interface properly.  Resolution The Lon Xml Tool provides the ability to create a Lon Xml file (.lnml) file for a device, using the source .xif file and (if necessary) other resource files, as made available from the device's manufacturer.  Review Appendix A of the Lonworks Integration Guide for Niagara G3.  The Lon Xml Tool is described starting on page A-1.  This section describes the need for custom Lon Xml files as well as an overview of the process and the steps to create one. docLonworks.pdf