Issue How is Continuum configured to validate FIPS 201 PIV card credentials? Environment CyberStation CX9680 ACX5740 ACX5720 Cause Questions on how to configure a Continuum physical access control system to validate FIPS 201 PIV credentials at the door. Resolution Configuring Continuum for FIPS PIV card credentials Click here for instructions on creating a custom FIPS-PIV card format Versions needed for FIPS-201

Issue Some jobsites require the use of conduit for all wiring between controllers. Is there a specific enclosure made for this purpose?  A general purpose enclosure such as the ENCL-100 can be used but must be punched or drilled to fit the damper shaft. Product Line TAC IA Series Environment MN-FLO / MN-FLO3T MNL-V1RVx / MNL-V2RVx MNB-Vx Cause Installation manual with reference to part number was misplaced. Resolution MNA-FLO-1 This enclosure is listed as an optional item in the installation manuals for all VAV controllers listed above. Click here to see F-26282-5, Installation Instructions for the MNL-V1RVx and MNL-V2RVx. Click here to see F-27346-4, Installation Instructions for the MNB-V1 and MNB-V2 Click here to see F-25718-6, Installation Instructions for the MN-FLO and MN-FLO3T

Issue What is the SubLAN and what is the C-LAN in regards to Ethernet and termination resistor information? Explanation of termination resistor, RS-485, baud rate, token passing, and polling method. Is the Host LAN above or below the Ethernet LAN? Product Line TAC INET Environment I/NET Seven Network Cause A better understanding of the I/NET network architecture and communication components can help to avoid the need to troubleshoot issues later. Resolution When defining the network in I/NET, the chart below helps to explain which components communicate to others including resistor termination. This is a simple explanation on where the various I/NET components are located in an I/NET Seven Network. C-LAN & Sub-LAN Wiring Specifications are available here as a PDF document. Selecting the link Network Definition CLAN SubLAN downloads and opens the pdf document shown below.

Issue After rebooting the PC, TAC Vista Server (TACOS) doesn't get a license. You need to restart TACOS after each reboot to get a license. Product Line TAC Vista Environment TAC Vista License Server TAC Vista Server Cause TAC Vista Server (TACOS) starts up before the license system is ready to serve licenses, and therefore everything is offline until you restart TACOS. Resolution Download these tools TAC Vista Run Mode TACLicenseServer Settings (only for TAC Vista 5.1.8 and later) First of all, make sure that you have a system that is working normally and has the appropriate default settings. For more information, watch this video on YouTube Make the following setting in TACLicenseServer Settings [1] Set the startup type to "Automatic" and the taclic port to 2170 [2] Click the "License Setup" button, and write the name or IP address of the local PC. Don't use "localhost" or 127.0.0.1 but the actual name or IP.   [3] Click the "License Files" button, and check that only valid license file(s) is present in the license files folder - no other files can be in this folder. [4] Start the license server Make the following setting in TAC Vista Run Mode [1] Enter the username and password of a user with local administrator rights that have at some point been logged in on the PC. LocalSystem can be used, but it is not recommended. [2] Set TACOS to run as a service [3] In "Service Tools" set the service to start type "Automatic Delayed" [4] Start the service Now reboot the PC If TACOS still doesn't get a license after a reboot, try making this additional setting in TAC Vista Run Mode [1] Stop the service [2] Make the service depend on the license server, and also the Loytec driver if it is used in the system. Now reboot the PC If TACOS still doesn't get a license after a reboot, try adding this environment variable to Windows [1] Open the properties for the computer (Click the Windows start button, right-click "Computer", click "Properties") [2] Click on "Advanced system settings" [3] Add a new system variable called "TCP_NODELAY" and give it the value 1 Now reboot the PC If TACOS still doesn't get a license after a reboot, contact Product Support Services and reference this article Now reboot the PC If TACOS still doesn't get a license try making this additional setting in TAC Vista Run Mode Now reboot the PC If TACOS still doesn't get a license try making this additional setting in TAC Vista Run Mode

Issue Unable to determine whether the Enocean device in hand is compatible with MPM controllers Unable to add more devices to a MPM controller Product Line EcoStruxure Building Expert Environment Multi-Purpose Manager Cause Some pre-configured icons in the "Add Devices" list have a name but do not have a specified Enocean profile or vice versa. Resolution The Following devices are embedded in the MPM firmware and require no scripts to integrate with an MPM. All Devices in the below list (except for Enocean relay) are outbound devices (i.e. devices that are only able to send telegrams to other devices) MPM Sub-device list Description Compatible Schneider-Electric Products CO2 Sensor A5-09-04 CO2 Sensor SR04 CO2 (LSS442510) (868MHz) Door/Window Sensor D5-00-01 Single Input Contact SED-WDS-U-5045 (902MHz) 10020032 (LSS10020032) 10020042 (LSS10020042) 10020047 (LSS10020047) Double Rocker Switch F6-02-01 Light and Blind Control – Application Style 1 EDRPU-W-EO (902MHz) 10020048 (LSS10020048) (868MHz) Enocean Relay Inbound profile   Enocean Switch Light and Blind Control – Application Style 2 ESRPU-W-EO (902MHz) 10020049 (LSS10020049) (868MHz) Enocean Thermostat Obsolete   KeyCard Switch F6-04-01 Key Card Activated Switch SED-KCS-U-5045 (902MHz) Light Sensor A5-06-01 Light Sensor Range 300lx to 60.000lx 10020047 (LSS10020052) Light Sensor A5-06-02 Light Sensor Range 0lx to 1.020lx SED-LLS-U-5045 (902MHz) LSS10020053 (868MHz) Motion Sensor A5-07-01 Occupancy Sensor with Supply Voltage monitor SR-MDS Bat SED_CMS_U_5045 (902MHz) Thermostat A5-02-05 Temperature sensor Range 0°C to +40°C SED-T00-U-5045 (902MHz) 10020046 (LSS10020046) 10020033 (LSS10020033) Thermostat A5-04-01 Temperature & Humidity sensor Range 0°C to +40°C and 0% to 100% SED-TH0-U-5045 (902MHz) 10020041 (LSS10020041) SR04 rH Thermostat A5-08-01 Light, Temperature and Occupancy sensor Range 0lx to 510lx, 0°C to +51°C and Occupancy Button SR-MDS Thermostat A5-10-03 Room Operating Panel: Temperature Sensor and Set Point Control SR04 P (LSS226172) Thermostat A5-10-05 Room Operating Panel: Temperature Sensor, Set Point and Occupancy Control SED-TS0-U-5045 (902MHz) Thermostat A5-10-10 Room Operating Panel: Temperature and Humidity Sensor, Set Point and Occupancy Control SED-THS-U-5045 (902MHz) Thermostat A5-10-12 Room Operating Panel: Temperature and Humidity Sensor and Set Point SR04P rH(LSS252331) Thermostat A5-10-19 Room Operating Panel: Humidity, Temperature Set Point, Temperature Sensor, Fan Speed and Occupancy Control   -The maximum number of devices added to each MPM is 49 -The maximum number of EnOcean devices added to each MPM is 49 -The maximum number of EnOcean devices with the same EEP added to each MPM is 49 .This only applies to firmware 2.13.1 and later, the limit for previous firmwares is 20. An Exception is the following limits for devices/widgets per MPM 20 EnOcean Switches 20 EnOcean Relays 4 EnOcean Thermostats The Devices in the next table do not have a pre-configured icon in the devices list, however, scripts can be used instead and can be found below (Please read PDF first) Enocean Scanner Enocean device driver Valve driver Enocean profiles supported in script EnOcean Equipment Profile (EEP) Description Example of Compatible Devices (EEP A5-38-08) Central Command Gateway Plug-in 15 Amp 120V 902Mhz 5-Wire 6A Relay 24V 902Mhz 3-Wire 6A Relay 120/240/277V 902Mhz (EEP A5-11-01) Lighting Controller 15A-20A 120/277/347V 902Mhz (inbound profile: A5-11-01) 15A 120-277V 902Mhz (inbound profile: A5-11-01) (EEP A5-10-04) Temperature Sensor, Set Point and Fan Speed Control Thermokon SR04PS (EEP A5-02-14) Temperature Sensor Range -20°C to +60°C Thermokon SR65TF (EEP F6-03-01) 2 to 4 Rocker Switch (Light and Blind Control) Push-button, 2-gang (EEP A5-20-1) Battery Powered Actuator Thermokon SAB02/SAB05     Din Relay 1 channel (inbound profile: F6-02-02)     PWM 230V valve driver (inbound profile: A5-02-05) PWM 24V valve driver (inbound profile: A5-02-05)

Issue Program IDs do not match. There is an incorrect or out-of-date program version. (Subsystem: NS, #38) Product Line TAC Vista Environment LonMaker 3.X NS Error codes are not specific to any one LON environment, the display of the error may vary, but the steps to resolve should be the same. Cause A Program ID is a unique identifier assigned to each XIF (or device template) in an LNS database. Controllers with different XIFs cannot share the same Program ID. When a device is created in an LNS database, its Program ID is extracted from the XIF and stored in the database. When a controller is downloaded, the Program ID is transferred and stored in the controller. If the Program ID that resides in the controller differs from the one stored in the LNS management tool, the commission command will fail due to the Program ID mismatch. Resolution The appropriate resolution to the NS, #38 error depends on which controller is failing to commission. Select from the categories below which best describes the offending controller.  Xenta Programmables (follow steps below) Xenta 28X, 30X, 401(:B) Download the controller through the Vista System Plug-in before attempting to commission. If the error remains after a download, then the download did not go through, despite all indications that it did. Connect to the RS-232 serial port of the controller and attempt to download the Menta file directly. This will often bring to light parsing errors that are not detected by the System Plug-in. Find and correct the errors to allow the file to download properly. See Menta Parser Errors for more information on parser errors. The controller should then commission successfully. --- If the error persists, continue ---   Open the Menta file of the controller that will not commission. Under Options > Device Specification, uncheck the box for "XIF-Header generated according to LonMaker standard." (You may have to temporarily assign a System Version to activate this checkbox.) LonMark standard headings only use 255 combinations of IDs. It may be that two controllers just happened to be assigned the same Program ID. After unchecking this box, go to Options > Simulate, Commands > Generate to regenerate a new Program ID without using the LonMark standard header which opens up many more Program ID combinations and lessens the already low probability of two being the same. Download the new Menta file with the new XIF and new Program ID into the controller. It should now commission successfully.   Xenta 5/7/9XX Xenta 511, 527, 701, 711, 721, 731, 913 The XIF in the LNS database must be updated. See How to update a modified Xenta 5/7/9xx XIF file in LonMaker for detailed instructions.   ASCs/LON Devices (choose an option below) Xenta 100 series, third-party devices Replace the device using the correct XIF obtained from the manufacturers website. Replace the device using the correct XIF obtained from https://www.lonmark.org/. Replace the device with a generic device. Commission with the option of getting the XIF from the device.   Xenta 400 Series I/O Module (choose an option below) Xenta 42X(A), 45X(A), 47X, 49X Be sure the correct module is defined in Menta if adding I/O modules automatically. If adding I/O modules manually, be sure to use the correct stencil on the LonMaker drawing. You will get this error if you try to commission a 451A module with a 451 stencil.

Issue BACnet AlignIntervals Error when downloading b3 controller after a Continuum conversion Product Line EcoStruxure Building Operation Environment Continuum conversion b3 Controllers Cause After a Continuum conversion the b3 controllers will not download correctly and AlignIntervals error is seen. Resolution This is most likely a result of have older firmware in the b3 controllers. No exact EBO supported version is stated for the b3 controller, but it is advised to always use the latest firmware version. Early versions of SBO (v1.0 to v1.9) would have been tested with v4.500064 (June2010) and v4.500076 (Mar2014). Most EBO testing being done at v4.500077 (Nov2017). It is likely a b3 with firmware v4.500049(Jul2009) could operate correctly.   It is advised to use the current version of firmware in a b3 controller.   Continuum Conversion Tool Notes See Known Issue v3.0 See Known Issue v3.1 So for Continuum conversions, EBO v3.0.x, v3.1.1 and v3.1.2 up to CP4 should avoided. The work around for these versions is to convert using v2.0 then upgrade to the required version. Or for v3.1, use v3.1.2.6000 CP5 or later. The issues are fixed in v3.2.

Issue How do I format a Comma Separated Variable file (CSV) to create personnel objects via import that will include area assignments and photos. Product Line Andover Continuum Environment CyberStation Cause Need way to mass create personnel objects. Resolution Typically personnel information is provided from Human Resources in a MS Excel file, the data can be saved as a CSV file and easily formatted for import into the Continuum system which will automatically create one personnel object per row using the information (LastName, FirstName etc) included in the file. Assigning areas during import is accomplished by specifying a personnel template (previously created using Continuum). Different areas can be assigned to different personnel objects as a template can be specified per row. When the personnel object is created via the CSV import, it will be assigned all the areas found in the specified template. Importing a photo for the personnel object is accomplished by specifying an image file in the PhotoFile column. Click Here for a sample CSV file.

Issue It is not clear which part of the license system handles the end-user license and which part handles the demo license. Having both TAC Vista and EcoStruxure Building Operation(EBO) installed on the same PC can cause conflicts in the license system. Product Line EcoStruxure Building Operation   Environment Building Operation Enterprise Server   Cause If an EcoStruxure installation is only used for engineering and therefore will only have demo licenses activated, you don't need to install the license server. The service "FLEXnet Licensing Service" is installed by any EcoStruxure software package, and that is the service that will handle the activation of demo licenses. Resolution If you will only use demo licenses on a PC and/or also have TAC Vista installed on the same PC, only install the license administrator and not the license server.   It is also possible to run TAC Vista and EBO using the same License server, please see Lesson Learned SmartStruxure license and TAC Vista license on the same PC

Issue General configuration for these controllers. Environment Drayton DC1100 Satchwell DC1400 Cause Access to the documentation unavailable and uncertain of the correct configuration. Resolution The available controller configurations are all shown in the controller data sheets, please select the required data sheet below. To review the Drayton DC1100 general data sheet, please click HERE. To review the Drayton DC1100 "A" data sheet, please click HERE. To review the Satchwell DC1400 general data sheet, please click HERE. To review the Satchwell DC1400 "A" data sheet, please click HERE. For a general overview of the DC1100/DC1400, please click HERE.

Issue Control Valve Sizing Environment Control valves Cause Selecting the wrong control valves can cause improper control operation  Resolution Refer the Application Note CA-28, Control Valve Sizing. This is a good reference document for sizing a control valve. 

Issue TRD-IO-16 and TRD-IO-34 Installation (Wiring) & Configuration Guides Environment Niagara G3 Cause Quick access Resolution These guides are also available at http://www.niagara-central.com. TRD-T-IO-16 TRD-T-IO-34

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