Building Automation Knowledge Base

Issue When should end-of-line (EoL) terminating resistors be installed on a BACnet/MSTP network? Product Line TAC IA Series Environment BACnet/MSTP network Cause Knowing where to implement the termination helps reduce signal reflections, which might cause issues in the system. Resolution Resistors of 120 ohm value must be installed at each end of a MSTP (or RS-485) trunk segment. They help reduce signal reflections and RF interference. Failure to install end-of-line resistors may result in intermittent communications.

Issue (2019-06) The current version supplied is 2.1 build 196 Also available for VisiSat 2.1 Build 196: Service pack 1 (Build 200) Service pack 2 (Build 201) Product Line Satchwell MicroNet Environment MicroNet controller programming IAC controller programming MMC controller programming.  VisiSat MN-VSCORE Cause Different versions of VisiSat must be used with specific Windows operating system and Microsoft Visio versions. The latest version/build of VisiSat may not be compatible with the users current system.. Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- VisiSat 2.1 Build 196 (MN-VSCORE) is available to download from the Exchange Extranet , since January 2018, VisiSat can be freely used without the need for a license. Refer to PA-00597 - MN-VSCORE End of Commercialization - Satchwell MicroNet for further details on the availability of the VisiSat Configuration Tool . The VisiSat data sheet provides information on operating system and Microsoft Visio compatibility for different builds of VisiSat 2.1. SOFTWARE VisiSat 2.1 Build Number Windows Operating System Visio Release 185/196 Windows 7 2003/2007/2010 XP Professional 2003/2007 148 Vista Ultimate 2003/2007 XP Professional 2003 137 XP 2002/2003 17 XP 2002 14 Two service packs are available for VisiSat version 2.1 Build 196. Service pack 1 provides the following corrections: In the ARCnet debug Excel spreadsheet, the property editor can now be run. Exporting points to MicroNet View or Xenta Xbuilder, now allow up to 32 characters for the name and up to 50 characters for the description. In SBO (StruxureWare Building Operation) or EBO (EcoStruxure Building Operation) WorkStation, MicroNet Interfaces can no longer be exported/imported. All MicroNet engineering should be done in VisiSat first and then imported into SBO/EBO. Newly created blank pointslists can now be saved, without production an error message. Exports to SBO/EBO no longer produce Memory leaks. Adding service pack 1 takes the VisiSat 2.1 build number of 196 to 200 Service Pack 1 is available to download from the Exchange Extranet and VisiSat version 2.1 Build 196 service pack 1 Service pack 2 provides the following correction: Import file replaces all non-ASCII chars with replacement character. Once added the characters are converted correctly and points with alarms and trends results in the import file is generated. Adding service pack 1 takes the VisiSat 2.1 build number of 196/200 to 201. Service Pack 2 is available to download from the Exchange Extranet and VisiSat version 2.1 Build 196 service pack 2 Further information on VisiSat installation and operation can be found in Download latest VisiSat Data Sheets, Engineering Guides, Installation and User Guides, and Release Notes.

Issue Files required to install EcoStruxure Building Operation Web Reports Server Product Line EcoStruxure Building Operation Environment Building Operation WebReports up to version 3.2.  Note: WebReports is no longer included in Building Operation 2022 and above. Cause Tutorial for configuring Web Reports Resolution EcoStruxure Building Operation WEB Reports Server Release To start installation, download WebReports Operating Guide and WebReports Reference Guide Installation Outline: The WebReports Reference Guide provides detail information about hardware, software requirements, and steps required to configure the applications. The following steps are an overview of the complete installation. Points 1-4 are easily and/or automatically done using "SBO Reports Preparation" available from the Buildings Community. This tool is not officially supported, but has proven to be helpful in many cases. Install and Configured required Windows applications, roles, and features. Outlined in Sections 3.4 of the WebReports Reference Guide Download and install SQL Server 2008 R2 Standard with Advanced Services it requires version 10.5 or later. Follow configuration steps found in Section 3.5-3.6 of the WebReports Reference Guide SQL 2008 R2 Standard with Advanced Services file name SQLEXPRADV_x64_ENU.exe Install .NET framework 4 per WebReports Reference Guide section 3.7 Ensure that the Enterprise server is running on another machine, or at this point install and configure it on the local machine Install WebReports Server using the processes defined in WebReports Reference Guide section 3.9 and 3.10 The online help guide for EcoStruxure has a tutorial which will walk you through configuring the report Server, and running reports: WebReports Overview  If you wish to create custom reports. Please follow the instructions as outlined in How to create custom reports in Building Operation WebReports APPENDIX A: Verifying system is ready for reports installation Before installing WebReports, but after configuring Windows Roles and Features, SQL and install .NET 4.0,(SBO 1.5 uses .NET 4.5) the user should always: Check to see that SQL Server is up and running Check that the user you are planning on installing WebReports with can connect to SQL and Microsoft Reporting Services. Log into SQL using SQL Server Management Studio User should be able to connect and view databases. Connect to the MS Reporting Services URL You can obtain the URL by: Start->All Programs-> Microsoft SQL Server 2008 R2->Configuration Tools->Reporting Services Configuration Manager. Once logged into Reporting Services Configuration Manager click on “Report Manager URL” and click the URL Verify that Reporting Services Manager page loads without error. If you run into issues with the above, a possible solution is to turn of User Account Control Settings. This can be disabled by going to the Windows Control Panel, selecting User Accounts, selecting "Change User Account Control Settings" and moving the slider all the way down. You must restart the PC for this change to take affect. Repeat the above steps and contact PSS if you are still unable to validate the system. APPENDIX B: Upgrading a report server installation As described in appendix A, the logged in Windows user is used to install the report server, and this user must have access to the SQL database. That is also true when upgrading the report server installation, so make sure you are logged into Windows with the correct user. Another option is to SHIFT + right click the installer, and select "Run as other user".

Issue General use of the Wireshark program. Product Line Access Expert, Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Ethernet Networks Cause General Information on using WireShark. Resolution Wireshark is an Ethernet packet analysis programme, Which can be downloaded from: Latest version available from Wireshark Locally stored version 1.0.9 Installing Wireshark If necessary, unzip the WireShark executable file to a suitable location on the PC/Laptop you wish the programme to be installed on. Run the executable file and follow the on-screen instructions. Rules for capturing LAN traffic using Wireshark: Do not use a switch or router to connect the LAN capture PC to the network as these will filter important network activity that you will need to see. You will want to capture everything that is passing over the network at the point of concern. Usually, this means tapping into the ethernet at the Controller or controllers, that is having an issue. midBit-Technologies-LLC-10-100 is an example of a device that can be used to easily tap into the network to take the capture. The monitoring PC must see all traffic from the controller's point of view. The monitoring PC can be connected in either two ways: Connected to the network at the controller The customers IT department can mirror all the network traffic from the controllers port to another port the PC can be connected to. If connected to the network at the controllers, the connection must be made through a true ethernet hub. A hub will not selectively filter important network traffic as a switch or a router will do. More information on what a "true ethernet hub" can be found at http://wiki.wireshark.org/HubReference There are however some switches that feature port mirroring, please see How to Configure a NETGEAR Prosafe Plus Switch for Mirroring. If connected to a mirrored port, the port must mirror 100% of the network traffic to and from the controller. No filtering should be done. Once a complete capture file has been obtained it can be filtered after the fact using WireShark or EtherReal. Using Wireshark Run WireShark Start a trace by choosing the "Capture" menu and then select "Interfaces" Choose the appropriate interface. Generally, this can be identified by its IP Address, but if not, then the packets increasing are an indication. Press the "Start" button. The trace will start and will be similar to the following screenshot. After an appropriate time, the trace can be stopped by selecting "Capture" menu and "Stop" To save the capture file, choose "File" menu and "Save As".

Issue What resources are available to get more information on the Modbus protocol? Product Line Andover Continuum,EcoStruxure Building Operation,Field Devices,Satchwell BAS & Sigma,Satchwell MicroNet,TAC IA Series,TAC INET,TAC Vista Environment Modbus ASCII/RTU Modbus TCP/IP Cause The Modbus protocol information is available on www.modbus.org Use the menu on the left and select Technical Resources. Select the Modbus Specifications. Resolution Found on www.modbus.org are the protocol specifications: Modbus ASCII/RTU Modbus TCP

Issue Sigma parallel port dongle or USB dongle upgrade to software license Product Line Satchwell Sigma Environment Sigma version 4.08 Cause It is difficult to purchase computers with parallel ports. With the use of virtual computer operating systems, USB ports may not be available either. ∴ A different type of Sigma licensing will be required. Resolution Please note: EBO 3.x has now entered into its limited support period with Sigma support coming to an end, this free of charge service, provided by PSS in good faith, will no longer be available from the 1st May 2024. Any remaining Sigma systems will need to continue to use their current licensing method or be upgraded to EBO.   Product Support can arrange for an upgrade from your existing parallel port or USB type Sigma dongle to a Building Operation software license entitlement for Sigma 4.0.8. Sites running Sigma software 4.07 or older where support for software licensing isn't available need to be upgraded to Sigma version 4.08.57 or later to use the software option. Sigma Software license type availability is documented on page 8 in the Sigma 4.08 release note.   For engineers using Sigma 4.08: The Building Operation Evaluation License, available from the Schneider Electric Download Center, will unlock the Sigma 4.08 for testing etc for the period of the Evaluation License (maximum 3 months or until the expiry of the downloaded license).   Unlock Sigma software using the Building Operation Evaluation License. To install the software licensing option for Evaluation License: - Stop the Sigma server service. Install Building Operation License Administrator. Add Evaluation License file to the Building Operation License Server. Start the Sigma server service. Sigma should now be licensed. For customer sites using Sigma 4.08: To reduce the Sigma system downtime, Install the Building Operation License Server version 1.6 or later. (it is recommended that the latest available version of the Building Operation License Server compatible with the computer's operating system is used). Dongle Upgrade Procedure: Download the Sigma Dongle Replacement - Required Data 2020 form. Complete the cells that are highlighted/filled in blue. Open a case with your local support team.. Supply the completed spreadsheet. The Product Support representative that is assisting you with your license upgrade, will contact you and provide the address and details where to send the site's Sigma dongle. Once the dongle has been received a software license will be ordered and then the software license entitlement for Sigma will be sent to you. If the site is a standalone Sigma site, Product Support will need to get approval from the regional category manager before escalating for the software license.   To install the software licensing option for Sigma 4.08: - Stop the Sigma server service. Install Building Operation License Administrator. Add the entitlement to the Building Operation License Server. Start the Sigma server service. Sigma should now be licensed.   Note: If your current Sigma dongle contains Remote Alarm Manager licensing, Remote Alarm Manager does not support the Building Operation license server option. The USB dongle can still be used or a TAC license server type license can be used instead of the dongle.

Issue Can the Continuum Software be downloaded from the web, or ordered on CD? Product Line Andover Continuum Environment Continuum Cyberstation software Cause Download of Continuum Cyberstation software Resolution The Continuum Cyberstation software is available for download from The Exchange Download Center. The link below will direct you to the Cyberstation software. CyberStation Software If specific older versions of software are required see Older CyberStation versions not found on the Extranet (Exchange Online). If a customer specifically requests the software on a CD, then these can be ordered through the regular Order Entry channel specifying the version required.

Issue When adding License Entitlements via Device Administrator using the online method. After clicking activate, a "Communication failed" message is displayed:   Could not establish contact with License Server using SmartX Server Followed by a "License Operation Failed" message:   Add entitlement failed. License Server is offline. Error code: 41 Error message: CURL error: Product Line EcoStruxure Building Operation Environment Device Administrator Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause When activating a SmartX Server license online, the SmartX server will try to connect to the license activation server to activate the license. If it cannot resolve the license activation server site name and connect, it will show up as offline. Resolution Make sure that the SmartX Server DNS is properly configured in the AS-P.  In Device Administrator select the Ethernet 1 Configuration tab. Check the Primary, Secondary, and Tertiary DNS settings If unsure of the correct DNS address, enter the Google DNS address of 8.8.8.8 or 8.8.4.4. The example below shows a local router address as the Primary DNS and Google DNS as the Secondary and Tertiary DNS.   To confirm that the SmartX Server can resolve the license activation server address Open a Console session on the SmartX Server in Device Administrator. Enter the command: ping schneider-electric.flexnetoperations.com If the DNS is correctly set in the SmartX Server, the result should look similar to that shown below: Note: Ensure that the ASP is fully connected to the Internet in order to perform Online Embedded License Activation. You need to be connected to the Automation Server using IP (Not via USB) to activate the embedded license.

Issue Download a Menta application file to a Xenta controller using the Menta software tool and a directly connected serial RS-232 cable. Product Line TAC Vista Environment Menta Programming Tool Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cableguide Kableguide Programming Serial Kit 0-073-0920-0 Note: The Online command is not available for the Xenta Server 700 devices so the following procedures do not apply to these devices. Cause Throughout the engineering, installation and commissioning phases of a project it may be necessary to download directly to a Xenta programmable controller. Also, performing a directly connected Menta download may be necessary in order to fix certain issues. See the following: The device is applicationless, or is not associated with a program record. (Subsystem: NS, #5) Resolution Use Menta Setup program (this is found in the TAC Tools menu) to select the Com port that is being used. Do not change any other setting before clicking Close. Connect the RS-232 cable and Programming Adapter between the PC and the RS232 port on the TAC Xenta. (these are part of the TAC Xenta: Programming Serial Kit, part no. 0-073-0920-0 For more information about the cable and adaptor see Xenta Cable Guide , Adaptor A1 and Cable L1 or Schematic for the RS-232 cable used to direct download Menta applications and system files.)  Open the Menta file to be downloaded. Change to simulation mode in Menta by clicking Options menu and selecting Simulate. In the simulation mode click Online. In the Connecting to Device dialog click Download. In the Tam32 dialog choose whether or not to generate files for an OP menu. For more information regarding Menta direct downloads see the TAC Menta Technical Manual  Section 16.4.1. Notes: Network information containing network addresses and other properties for the Xenta device and it's I/O modules is included in the download. For more info about this network info see the TAC Menta Technical Manual listed above or for problems with downloading the network information see No blueprint in TAC Xenta! Don't forget to download the network configuration if the TAC Xenta is to function in a network!. If Menta returns Parser Errors during download see Menta Parser Errors. If Menta returns Unsupported I/O Warning during download see Reference to unsupported I/O Error in COD file - Error:13. If a serial connection is not available on the PC a USB adapter can be used. The appropriate version of the TAC Menta Engineering Tool can be downloaded from the Exchange

Issue TC300 Series Networking Digital Fan Coil Thermostat - Modbus Protocol Documentation Product Line Field Devices Environment TC300 Series Digital Fan Coil Thermostats Cause Modbus protocol information is needed in order to perform Modbus integration to the TC300 Series Digital Fan Coil Thermostats. Resolution The TC303 thermostats come with the option of Modbus communication for both 2- and 4-pipe configurations. Modbus is an open, widespread and well established serial communication protocol used within building automation. The support of Modbus communication allows simple integration of the TC303 thermostats to a building management system, using standard Modbus serial communications. The following models provide support for Modbus connectivity: TC303-3A2LM TC303-3A4LM TC303-3A2DLMS TC303-3A4DLMS TC303-3A2DPMS TC303-3A4DPMS The TC303 thermostats communicate as a Modbus RTU slave device over a serial RS-485 connection, allowing for the transfer of real time data. Thermostats manufactured from November 2018 (2018-W44-4)* onward can be configured to communicate at 9600 (default) or 4800 bps. The communication parameters for TC-300 thermostats manufactured prior to this date cannot be adjusted and are fixed as follows: 4800bps Baud Rate 8 Data Bits Odd Parity 1 Stop Bit The actual Modbus address of the thermostat can be set for each individual device on the RS-485 network. The address is defined via the parameter menu on the thermostat itself. The address range available is from 01 to 32 and is defined under menu item 04 of the parameter settings. For full details on this, other parameter setting options available and Modbus communications parameters/registers, please refer to the Installation Instructions.  Connection to the RS-485 network is made via dedicated terminals on the back of the thermostat and marked A (+) and B (-).   TC300 Series Digital Fan Coil Thermostat Installation Instructions TC300 Series Modulating Fan Coil Thermostat Installation Instructions   * Note - The Installation Instructions have not been updated to include the information that thermostats manufactured from November 2018 (2018-W44-4) onward can be configured to communicate at 9600 (default) or 4800 bps. 

Issue Satchwell MEU 3-port Unit Control Valve is obsolete. Product Line Field Devices Environment Satchwell MEU 3-port Unit Control Valve installations Cause Satchwell MEU 3-port Unit Control Valve requires replacement due to failure. Resolution Satchwell MEU 3-port Unit Control Valve may be replaced by Schneider Electric VZ319 series Unit Control Valve, although dimensional differences may apply. It should be noted that VZ319 series Unit Control Valves are available in both Flat Face and Compression fitting specifications. The latest issue of the Schneider Electric Valves and Actuators Catalogue should therefore be consulted in order to determine the availability of the particular size / kv / fitting combination required. It should also be noted that any Actuator installed on the Satchwell MEU 3-port Unit Control Valve will not be compatible with the replacement Schneider Electric VZ319 3-port Unit Control Valve and that a Schneider Electric MZ20 series Actuator of the appropriate operating voltage / signal type will also be required.

Issue After configuring the system per Setting up a Local / Internal NTP Server, the Automation Server's time would not sync to the local NTP computer's time. Wireshark capture shows a 'Root Dispersion' greater than 10 seconds. In the screenshots below, 10.169.90.13 is an Automation Server (NTP client), and 10.169.90.6 is the NTP server. CLIENT REQUEST SERVER REPLY This behavior of adding 10 seconds to the root dispersion is only observable when using the internal clock otherwise it is 0. This appears to be the intended behavior by Microsoft so that this NTP server would rank lower if using multiple NTP servers that might have more reliable time. Product Line EcoStruxure Building Operation Environment Automation Server (AS) Network Time Protocol (NTP) Cause The NTP client in the AS ignores the time sent by the NTP server if the root dispersion is greater than 'X' seconds (not known at this time) Resolution In the Windows registry of the machine being used as the time server, make the following change:  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\LocalClockDispersion The default for this key is “A” in hex. Change this to “0” and then restart the Windows Time service.  Do this by running the following command net stop w32time && net start w32time. Here is what Wireshark shows after the time has been synchronized. SERVER REPLY

Issue Automation Server - Warm and Cold Start differences Product Line EcoStruxure Building Operation Environment Building Operation Automation server Cause The explanation on the differences between a warm start and a cold start in the documentation and web help may not be clear to some.  Resolution Warm Start: Restarts the controller's application Cold Start: Restarts the controller's operating system An Automation Server can be warm/cold started from Workstation or by using the reset button on the Automation Server. Refer to Reset Functions on Web Help for an explanation of the differences between warm and cold starting the AS.  Basically, you can set the Retain Levels for variables in Building Operation to 'No', 'warm start' or 'cold start'. To change the retain level of a variable and go to its properties.  - Click on the gear icon. - Set the retain level of the variable. 1. Retain level set to 'No' - The variable is reset to the value set when the object was created. When you create an Analog Value object, the value of the newly created object is '0'. A user can set this to another value. When retain level is set for this Analog Value object, after a warm or cold start, the value of this object will default back to '0'. 2. Retain level set to 'Warm start' - The value is set back to the last value set by the user. If a user change the value of an Analog Value object to another value and save, after a warm start, the object will return to the last value set by the user.  3. Retain level set to 'Cold start' - The value is set back to the last value set by either the user or the system (for instance by a program). The operation is similar to the warm start but in this case, the last value set by the system will also be retained. 

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Upgrading a JACE-8000 or Edge-10 from 4.10U7 to 4.11 or 4.12 will prevent Niagara Daemon from starting.  You will be unable to connect via Workbench or Browser. Product Line TAC IA Series Environment I/A Series N4 Jace 8000 Tridium Edge 10 Cause The software in builds 4.10u7 and later LTS builds (4.10u8, 4.10u9, 4.10u10) was released after 4.11 and 4.12 reached EOL.   4.10u7 contains a newer signing key that is not recognized by 4.11 and 4.12. Resolution When upgrading JACE-8000 and/or Edge 10 running 4.10 LTS builds 4.10u7 and later, please skip over 4.11 and 4.12 and instead upgrade to 4.13u3 or newer. Alternatively, you may apply the dist that reverts JACE-8000 to clean 4.9u1 state, or for Edge-10, the dist that reverts it to clean 4.7 state. You can then install 4.11u2 or 4.12u2, if that's the version you have to use.  If you've already attempted the commissioning operation and bricked a device, and have backups, you can connect to the debug port and use the factory reset process per the documentation.  For Edge 10, consult the section titled Factory Default Recovery  in the Niagara Edge 10 Install and Startup Guide.  For JACE-8000, consult the section titled Restoring factory defaults  in the JACE-8000 Backup and Restore Guide. If you are lacking any backups for the host, then before performing the factory reset, you should enable SSH/SFTP via the debug port, and then copy out the Station files using Filezilla or WinSCP or equivalent.  Reach out to your support channel if you have difficulty finding the location of station files. Typically, the files will be in a subfolder of /home/niagara/stations. The config.bog file will be keyring encrypted, and you'll have to reset it using the Bog File Protection Tool. See Editing the .bog file passphrase offline in the Niagara Platform Guide  for details on using the Bog File Protection Tool.  For details on using the debug port on JACE-8000, see Debug port  in the JACE-8000 Install and Startup Guide.  For details on using the debug port on Edge-10, see Connecting to the debug system shell  in the Niagara Edge 10 Install and Startup Guide.

Issue Unable to login to Workstation. Getting error "Requested license is not available on the license Server" even though the license for the StruxureWare Enterprise Server is valid. License server does not support this feature (Error code: -18) Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation v1.3/1.4 WorkStation Enterprise Server License Server Cause When using Network Licenses this possibly indicates there was no valid WorkStation license. The Enterprise Server license does not also provide a Workstation license to run Workstation. If using Local Licenses, such as the Evaluation / Demo license and you are attempting to connect to an Enterprise Server from a separate WorkStation, the License server and the demo license file must be installed on both the Enterprise Server and each Workstation since the local license can not be shared between computers. Check Online help for additional detail. Resolution Network License: A new WorkStation license is required to use WorkStation. This would need to be acquired and added to the license Server. The part numbers for these are below. WorkStation software (including editors) Part number Product name Description SXWSWWORK00001 SW-STATION-STD-0 WorkStation Standard, 1 concurrent user license, (no maintenance subscription included) SXWSWWORK00002 SW-STATION-PRO-0 WorkStation Professional, 1 concurrent user license, Professional WorkStation version includes Editor licensing, (includes TGML Graphics editor, Function Block & Script Programming, no maintenance subscription included) Depending on what your requirements are, it may be possible to use the WebStation instead of a dedicated WorkStation for light monitoring duties. There is no part number for WebStation; it is a default feature of the Automation Server and Enterprise Server (with no need for additional licensing) in v1.3. Details on the WebStation and WorkStation can be found at the below links. WorkStation WebStation Local License: If using Local Licenses, such the Evaluation/Demo license and you are attempting to connect to an Enterprise Server from a separate WorkStation, the License server and the demo license file must be installed on both the Enterprise Server and each Workstation since the local license can not be shared between computers. Check Online help for additional detail.

Issue Configuring Security Expert Readers Product Line EcoStruxure Security Expert Environment Security Expert Smart Card Readers Cause Security Expert Smart Card Readers have options such as Mifare Reading Mode, LED colors, etc. that can be configured. How the readers are configured will depend on the reader's firmware. Resolution The method used to configure a Security Expert Smart Card Reader depends on the firmware version it is using. There is no way to visually determine the firmware version. To identify what firmware the reader was shipped with from the factory refer to Knowledge Base article Identifying Security Expert Smart Card Readers Firmware. 1. Smart Card Readers with firmware below build 200 - (I.e. 1.04.64) These are older readers which were configured with a serial terminal program by connecting to the reader using a USB-RS485 converter. Please refer to the 'Installer Programming' section of the attached Smart Card Reader Installation Manual - Feb 2017. This has been replaced by a newer version of the manual on Exchange which no longer includes this information. 2. Smart Card Readers with firmware build 200 or above (I.e. 1.04.229) These newer readers do not have a serial interface and will require a configuration card to change reader options. The configuration card (SX-ISO-CONFIG) is ordered from Schneider Electric, see the Security Expert Credentials Order Form for details.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Some IO modules status showing as 'Blacklisted device detected" or "Address shift detected" or a system alarm is received indicating the condition. AS trace logs may show one of the following entries... 2015-08-18 17:41:02.675 [1256862784] nsp.pin.cio.IODevice Module at address 14 is reporting Internal Error Code 32 2015-08-18 17:41:02.757 [1256862784] nsp.pin.cio.IODevice Module at address 28 is reporting Internal Error Code 32 2015-08-18 17:41:02.825 [1256862784] nsp.pin.cio.IODevice Module at address 12 is reporting Internal Error Code 32 2015-08-18 17:41:02.869 [1256862784] nsp.pin.cio.IODevice Module at address 13 is reporting Internal Error Code 32 2015-08-18 17:41:02.951 [1256862784] nsp.pin.cio.IODevice Module at address 15 is reporting Internal Error Code 32   2015-06-18 10:05:13.912 [1255584832] nsp.pin.cio.CIOException Error: Bad_Address (0xb0000), module Automation_Server_Io_Bus(31), moduleCode 0, dispString "AS address is invalid", techString "nsp_servers/plugins/CentralIOPlugIn/CIO/source/IOManager.cpp line 460" 2015-06-18 10:05:20.789 [1255584832] nsp.pin.cio.IOBus IOBusServer::run: Caught CIO exception from slot 3   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause One or more terminal base may have to be replaced. Intermittent IO connection (typically in S-cable). Resolution Follow this document or Blacklisted Device Detected for steps to resolve the problem.

Issue Understanding and Troubleshooting Modbus Product Line EcoStruxure Building Operation, TAC IA Series, Other  Environment All Modbus environments. Cause Modicon first introduced Modbus in 1979. Modbus is an open standard,and it is the most widely used in the industrial environment. Modbus is publicly available and,due to its simplicity, many manufacturers use Modbus as a solution for integration in their own products. Many commercial products and systems support the Modbus RTU and Modbus TCP protocols. For further information, visit the Modbus website at http://www.modbus.org. Resolution For a brief understanding on Modbus and how to troubleshoot Modbus, refer to the Modbus Troubleshooting PDF

Issue Blank window while capturing a photo using "Logitech HD Pro Webcam C920". Product Line EcoStruxure Security Expert Environment Security Expert Cause While capturing a user photo using "Logitech HD Pro Webcam C920", it shows up as an image source (in the drop-down along with Topaz). When selected however, the screen is blank. Resolution With this webcam, you need LWS software by Logitech installed on your machine. G Hub has replaced LWS however it seems like G Hub is not currently functional with the integration. Find more information about the  "LWS280" driver HERE.  The driver can be downloaded from the attachment.

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