Building Automation Knowledge Base

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.

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Issue Need for a dual redundancy power supply for the Automation Server. Product Line EBO EcoStruxure Building Operation. Environment Building Operation Automation Server. Cause Understanding how to create a fail-safe power supply for an Automation Server.  Resolution To provide dual power redundancy to an Automation Server, a possible solution can be to use a Phaseo ABL4_ABL8RED24400. This will allow the connection of two 24V PSU's to be connected to the inputs. Then connect the output of the Phaseo ABL4_ABL8RED24400 to the AS's PS-24V See the attached document and diagram for more information.

Issue Troubleshoot Security Expert Controllers showing offline in the client. Product Line EcoStruxure Security Expert Environment Security Expert Cause Require some common troubleshooting steps to help determine why controllers may be offline to the client. Resolution The main items to check are: Refer to the Troubleshooting Security Expert Controller Connectivity - Application Note on Exchange. If a controller has failed and the Replacement controller unable to be brought online then check if controller encryption had been enabled on the replaced controller. Restart the client software. Power restart the controller. Remove power Wait for all LED's on the controller to go completely off Apply power to the controller. In the controller web interface, on the Settings page, check that Event Server 1 has the correct IP address. Check that the Firewall is disabled. Check any Anti-Virus Firewalls/settings as well. If the Firewall cannot be disabled, ensure that all required ports are open between devices. See SX-SRVR Security Expert - Network Administrators - Installation Guide for details. Restart the Security Expert services under the PC's Services option in Control Panel. These need to be restarted when any changes are made. Confirm that the User Interface, Data Server, Event Server and Download Server module versions are all the same. Go to About  > Version and check there. If the database has not been upgraded to the same version as the client software, then this can cause communications issues. On the Security Expert Server check that MSMQ is installed as this is now a requirement   Security Expert MSMQ is required (Not showing live point status / shows "Unknown Status" error)   If MSMQ was installed after Security Expert, you'd need to reinstall Security Expert to allow it to run correctly. If MSMQ is installed and controllers are still not coming online (or the controllers are "bouncing" offline/online) then anecdotal evidence suggests enabling Windows 8 Compatibility Mode may help especially for Windows Server 2016 and Server 2019. Set the Windows 8 Compatibility Mode checkbox in the Properties page for C:\Program Files (x86)\Schneider Electric\Security Expert\SecurityExpertEvtSvr.exe   Also, note that if a database backup has been imported, then there is a need to check/change some other settings as well to ensure everything is set up for the specific server and controller.   Under Global > Download Server confirm that your computer name is the name of the PC where the download server service is running. Under Global > Event Servers ensure that the computer name is the name of the PC where the event server service is running. Under Sites > Controllers confirm the Serial number, IP Address, Download Port, Download Server and Control and Status Request Port match what is set in the controller's configuration web page (browse to the controllers IP Address to view). On that same General tab go to Diagnostic Windows and open the download and event server windows. Review the information contained and if there are any errors shown. Right click the controller and select Get Health Status. Review the status messages displayed.

Issue Certificate for FDA regulations in the manufacturing of pharmaceuticals, 21 CFR Part 11 "Electronic Records / Electronic Signatures." Can Building Operation incorporate a comment section to capture a reason for change made by an operator/user? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause Building Operation site in need of the compliance certificate for 21 CFR Part 11 "Electronic Records / Electronic Signatures." Usually, these are pharmaceutical manufacturing sites, and the full FDA document PRT11Elect.pdf is attached to this article. Resolution EcoStruxure Building Operation 3.2 and higher Compliance Pack enables 21 CFR Part 11 compliance for regulated industries. The Compliance Pack is an add-on module to EcoStruxure Building to help regulated industries meet the compliance requirements for Electronic Signatures & Electronic Records that are in place in the region.   This feature in our EcoStruxure Building Operation software provides facility-wide accountability and traceability of the environmental conditions that can impact the quality and safety of products developed in controlled environments in line with the 21CFR Part 11 regulation.   Compliance Pack is a licensed feature and compatible with EcoStruxure Building Operation V3.2.1 and later. Part Number Description SXWSWCMPLPK001 Compliance Pack – includes TimescaleDB, Digital PDF Signing, Change Control, For one Enterprise Server or one Enterprise Central For technical documentation and sales enablement tools for the Compliance Pack, please visit The Exchange Building & Power Extranet and use the search keyword: 21cfr ebo   EcoStruxure Building Operation 3.1 and below EcoStruxure Building Operation V3.1 and below has not addressed the pharmaceutical market and there is no electronic signature feature set that meets the FDA regulations 21 CFR part 11.   For sales issues surrounding FDA regulations, please contact through your sales channel to the local Category Manager. Americas: Americas.EcoStruxureBuilding@schneider-electric.com EMEA: EMEA.EcoStruxureBuilding@schneider-electric.com Asia Pacific: AsiaPac.EcoStruxureBuilding@schneider-electric.com

Issue Confusion over the thermistor type selection for an EBO Temperature Input object Product Line EcoStruxure Building Operation Environment Building Operation I/O Module Building Operation Automation Server Bundled Building Operation Multi-purpose Controller (MPC) Building Operation Room Controller (RPC) Building Operation IP-IO Cause The Thermistor type selection lists sensor "Types" I through V     This is confusing since, for example, the Continuum sensor is listed as 10k Type I but in manufacturers literature and temperature vs resistance tables is often referred to as 10k Type 3 Resolution The reference to Thermistor 10k Type in the selection list is an internal reference and not intended to refer to the types listed in manufacturers literature and temperature vs resistance tables. For reference the selections refer to the following sensor types:   Thermistor 10k Type I (Continuum) – Thermistor 10K4A1 also referred to as 10K Type 3 - SpaceLogic Sensors (as SLASXXX, SLAWXXX and SLABXXX), STx5xx Sensors (see HVAC Sensor catalog for details) Thermistor 10k Type II (I/NET) – Thermistor 10K2A1 Dale/Vishay - STx20x Sensors (see HVAC Sensor catalog for details) Thermistor 10k Type III (Satchwell) – Thermistor 10K3A1 (No Longer Applicable for Satchwell sensors) Thermistor 10k Linearized (Satchwell DxT - Type T) - STx6xx Sensors (see HVAC Sensor catalog for details) Thermistor 10k Type IV (FD) – Thermistor 10K4A1 type ‘G’ (U.S. Sensor) Thermistor 10k Type V (FD w/ 11k shunt ) – Thermistor 10K type ‘G’ (U.S. Sensor) with external 11k ohm shunt resistor installed Thermistor 1.8k (Xenta) – Thermistor type 1.8KA1 - STx1xx Sensors (see HVAC Sensor catalog for details) Thermistor 1k (Balco) – (not a thermistor) RTD, 1000 ohm Balco Thermistor 20k (Honeywell) – Thermistor 20K6A1 type H Thermistor 2.2k (Johnson Controls) – 2.2K3A1   Refer to the Temperature Sensor Resistance Charts Knowledge Base article for temperature vs resistance charts for these sensor types and others.

Issue When logging in to an AS or ES, WorkStation freezes or it takes a very long time (>30 minutes) before the login process finishes. Building Operation WorkStation hangs on "Reading data..." when trying to login to an AS or ES Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation WorkStation Cause The problem is related to a delay when validating the license details. It only seems to happen when running a mixed EBO/SBO 1.9.3 system and after having EBO license administrator 2.0.1 previously installed. Resolution Run the SBO License Server Reset tool and perform Reset - Simple Log in to WorkStation, and if the hang or freezing is still present, then follow the next set of instructions. Run Diagnostics in the License Administrator and take note of all the ACT (Activation) and Entitlement IDs Return all the licenses Close all WorkStations and stop all SBO/EBO processes (whichever may be running) Uninstall all License Administrator and License Server Run the SBO License Server Reset tool and perform a Reset - Complete (you will get an output of the commands and result) Install the latest released version of License Administrator and License Server (the latest released version of License Administrator has fixes for virtual servers and some cyber security vulnerabilities, note that License Administrator is backward compatible with earlier SBO versions) Activate the licenses based on the info from step 3 Note: If running the demo license, steps 3 and 4 may be skipped. If problems continue to occur, then send the above details collated (in step 3) and email this/contact support.

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

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

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