Building Automation Knowledge Base

Issue Steps to backup within StruxureWare/EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment StruxureWare/EcoStruxure Building Operation site with AS and/or ES Backup, Automation Server, Enterprise Server, Workstation, .xbk, xbk, backup set, db backup, db_backup Cause Must an AS or ES be stopped in order to do a full backup? Is a raw copy of the database folder from within Windows Explorer sufficient for backing up an ES?  For instructions on how to restore a backup in StruxureWare/EcoStruxure Building Operation, see How to restore a StruxureWare Building Operation server backup set. Resolution Concerning the backup and comparing SQL to the proprietary database that StruxureWare/EcoStruxure creates begs the question, are these backup complete? StruxureWare freezes the database while a backup is in progress in different ways. For configuration changes, StruxureWare Building Operation queues up the changes until the backup completes. For historical data, StruxureWare Building Operation buffers the data based on the limits of the buffer size. A stop of the ES is not necessary, nor is a stop of an AS. Because of this freeze and buffering, the data is put into that backup folder referenced in the pdf you sent. Three rules to remember: Restores of backups must be same software revision Do not rename the backup set A StruxureWare/EcoStruxure Building Operation backup should not be renamed after it has been created. When creating a backup, give the appropriate prefix to the standard name format.     The backup file will be shown as below. Should the backup name need to changed, then either create a new backup, or, zip up the backup using the new name.   Backups default to every Sunday morning 1:00am Here is the procedure for backing up an AS or ES: In Workstation, in the System Tree pane, select an Automation Server (AS) or Enterprise Server (ES) On the Actions menu, click Backup. This opens the Backup Options window In the Include column, select the servers that you want to include in the backup In the Backup content column, select the type of data you want to backup for each server: Select All Data to back up both the historical and configuration databases. This combined option protects the configuration, historical data, and custom object type data for a specified date and time Select Configuration only to back up the configuration database and custom object type data. This data option protects the configuration data for a specified date and time In the Backup set description column, type a brief description up to 255 characters to help identify the content of the backup Click Backup Verify that each backup succeeded and click Close Backup Files of ES: The backup data files are stored in the C:\ProgramData\Schneider Electric StruxureWare\Building Operation 1.X\Enterprise Server\db_backup\LocalBackup or  C:\ProgramData\Schneider Electric EcoStruxure\Building Operation 2.X\Enterprise Server\db_backup\LocalBackup   Backup Files of AS: Login to AS from WorkStation and navigate to System > Backup and Restore > Backup sets> Local. Then Right-click on the backup file and Save To... (then select a folder on your HDD) Note: Let this not be confused with the 'Starting a Project Tutorial [101248].pdf' in section 5.1 page 44, where it describes the user simply doing a raw copy of the database folder from within Windows Explorer. This can be mistaken with the orderly backup that uses the inbuilt StruxureWare backup facility. This copy procedure described has no chance to freeze the database. The user can just do it at any random time and StruxureWare has no idea that the copy has been made. A sample database should be created using the Backup/Restore functions of the system, not by just doing a raw folder copy as the server may be in the middle of transactions to various files in that folder. A copy of this folder could be used, but only while the SE.EnterpriseServer.exe process has been stopped. However, it is recommend using the system’s backup facility to accomplish this (Not all items are backed up such as Alarm data. The Backup/Restore help section of StruxureWare Building Operation Guide discusses what is and isn’t backed up).

Issue Moving from SBO 1.9 to EBO 2.0 and above does not allow the Tech Tool to be used on SmartX Displays. Product Line EcoStruxure Building Operation Environment EBO 2.0 Cause The SmartX Display Tech Tool is being discontinued in EBO 2.0 in favour of a completely overhauled Webstation which is now designed for use on Tablets and Smart Phones as well as PCs. Resolution Tablet used here is the T580 First of all, the tablet itself will need to be brought up to Android OS 7 minimum (OS 8 works as well). Depending on how long it has been since the tablet was last connected online, the Android OS may require a number of updates before it reaches Android OS 7. Most importantly, when finished the tablet must have a firmware number ending with T580XXU2BQL1 or above.  (E.g. T580XXU2BQI9 is lower than T580XXU2BQL1). If for some reason this is not the case then please manually update the software instead. Next contact the Schneider Electric Global Expert Support Team, to obtain the latest versions of SmartX Kiosk and AD-Link application. One visible change in the Kiosk is that it now includes a Chrome shortcut as standard. The AD-Link is still required to establish the connection between the Tablet and the SmartX Server over USB using IP address 192.168.42.116. It is only the Tech Tool itself, that is discontinued. Once the AD-Link has been opened and connected, Chrome can then be used to connect to the SmartX Server using the same 192.168.42.116 Address. Successful logon can then be achieved using the same Username and Password as the Tech Tool. The new and improved Webstation interface can be accessed that is optimised for Tablet and Smart Phone screens In some cases, the customer may not want Chrome's open browser interface and may instead wish to lock down the appearance of the browser to be closer to that of the older Tech Tool. If this is the case, please refer to 'Locking Down' Chrome and Webstation in EBO 2.0 for SmartX Displays.

Issue Using Chrome and Webstation in EBO 2.0 for SmartX Advanced Displays generates an interface which is more open and less restrictive than the original Buildings Operation Technician's Tool it replaces. While this is a benefit, some users may require to have a 'Locked Down' interface Product Line EcoStruxure Building Operation Environment Building Operation Advanced Display 2.0 and above Cause The Technician's Tool app on the SmartX Advanced Display was a separate purpose-built tool which was just designed for accessing SmartX Servers only, While Webstation, in this case is using Chrome has been recently updated for use on PCs Tablets and Smart Phones in general as well as the SmartX Displays.  It is therefore a much more open interface with the opportunity of accessing the EBO System Tree as well as other Chrome tabs for Google, news and weather etc. Resolution By default, Webstation 2.0 includes a System Tree for easier navigation and the latest version of SmartX Kiosk now includes a Chrome shortcut, designed to be used instead of the old Technician's Tool (which can now be uninstalled in EBO 2.0 installations).  The shortcut can open Webstation as one of multiple Chrome tabs as designed.  While the System Tree and extra tabs should be seen as helpful features, some users may still wish to simplify the SmartX display as much as possible, removing as many menus and tabs as possible to maximise screen size and continue the look of the older Technician's Tool.  To achieve this a couple of minor changes will need to be made. Firstly, the System Tree within Webstation can be hidden altogether, this will reduce system navigation but will also free up a portion of the screen. Secondly, creating a specific shortcut to Webstation 2.0, rather than using the standard Chrome shortcut removes the additional tabs. The new shortcut is added to the tablet's Home Screen but it also appears in Kiosk Mode. 1) Ensure the AD-Link is connected. 2) Open up the Chrome shortcut. 3) Connect to the pseudo IP address to connect via USB. 4) Log in using the same Username and Password as usual. 5) Select the Webstation menu icon. 6) De-select System Tree and then close via menu icon. This will then ensure the System Tree is no longer shown when logging into Webstation. 7) Access the Chrome Settings Menu 😎 Select the option to 'Add to Page to the Home Screen. This will then add a shortcut for Webstation to the tablet's Home Screen and will also appear in the SmartX Kiosk Home Screen. Using this shortcut instead of the standard Chrome shortcut will then open the Webstation in future without additional Chrome tabs or menu bars. Whenever you connect, menu pages and System Trees are now removed allowing the object selected to take up the maximum screen space.

Issue Partners and branches need to understand the terminology used with Security Expert and what those terms mean from a Continuum perspective Product Line Security Expert Environment Security Expert Continuum Cause A table key to map object terminology between Security Expert and Continuum Resolution   Continuum Security Expert Objects Records User Operator Personnel User Area Door Group (Area) = Intrusion/Antipassback/Counting Area Rights Access Levels AC1/IOUs Reader Expanders/RDM2 Numerics Virtual Inputs/Outputs Plain Enlgish Programmable Functions/Function Code/services Event Viewer Status Pages Alarm Viewer Status Pages Listview Status Pages Power Supply Analog Expander Network Sites NC/ACX Controller SPC Doors Doors Security levels Security levels Schedule Schedule Scedule Exception Calendar Action Holiday Holiday Reset Manual - Factory default – short Reader, L2D0, download Array Data Values Permisssions/Security Levels Record Groups +V V+ Ground V- Data 1 1 1 Clock 0 0 0 LED L1    

Issue Is it possible to directly replace a TCX867 with an i2867? Environment TCX867, i2867 Triac Output negative, positive, load switching Cause The two products have different output circuitry and the i2867 will not always be a direct replacement. Resolution Both the i2867 and the i2867 have triac outputs that only switch AC loads.  The i2867 outputs internally have one side connected to ground, hence the terminals are labeled Outx (Out1, Out2 ..) and Gnd, this means that when switching electrical loads they must switch the return path from the load, not the power feed to the load. The older TCX867 has isolated outputs and could switch either the Power or ground side of the switched load. It has 2 terminals on each output both labeled with the channel name i.e. Out1 on both terminal 1 & 2. So you can replace a faulty TCX867 in the field with a i2867, but it may require changes to the plant wiring to ensure the -Ve side of the load is switched, failure to do this can result in damage to the i2867. See i2867 installation guide for full details on installing an i2867

Issue Is there a setting that will retransmit a BACnet point in case a BACnet device goes offline? Environment Niagara G3 ENS, ENC-410, ENC-520 Cause Points go offline and come back online with controller default values. Resolution The Max Write Time applies to writable proxy points. Specifies the maximum “wait time” before rewriting the value, in case nothing else has triggered a write. Any write action resets this timer. If property value is 0 (default), this rule is disabled (no timed rewrites). The Max Write Time of the Tuning Policy can be set to periodically write to proxy points at a set time interval. 1. Open the station and expand its BACnetNetwork 2. Expand Tuning Polices 3. Double-click on the policy you want to update 4. Enter a maximum time to be used in the Max Write Time property. (example 10 minutes) 5. Save change Note: In some cases setting this to some value, for example 10 minutes, may be useful. Often, a network may have devices that upon a power cycle (or even a power “bump”), have writable points that reset to some preset “default” value or state.

Issue Can the AS, work independently or together without an ES? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site, any version Cause Are bindings or other communication between two AS possible if there is no ES?  Resolution The AS, is designed to work independently or in conjunction with others, or in conjunction with an ES.  Points, Bindings, Schedules, etc. can be setup on the AS using the Workstation. With the ES service stopped, the Points, Bindings, etc. on the AS continue to reflect the values on themselves or if the Bindings interlink between multiple AS.  For multiple AS configuration check the AS are listed in the Communication tab of each other. From your workstation highlight the AS and the tabs shown are List View, Device Discovery, Date & Time, Communication, and Properties. Under Communication the other AS devices should be listed as well as the ES. For information on a Automation Server alone at a site and licensing requirements, see License requirements for AS alone at a site

Issue While editing a graphic, the editors components categories and menu options are too small to be used. This happens when Windows display scaling is not set to 100%. Product Line EcoStruxure Building Operation Environment Graphics Editor High Resolution monitor (4K) Scaling Cause An issue has been identified with how the default scaling used by Windows affects the Graphics Editor in EcoStruxure Building Operation 2.0 and later. Resolution Follow the steps below to work around the problem Update Windows with the latest available updates Update .NET Framework to latest version Change the compatibility settings of the Graphics Editor as outlined below   Open the Graphics Editor application file location   Open the properties for the Graphics Editor application   Override the DPI scaling 

Issue What is the best method for calibrating a thermistor? Product Line Andover Continuum Environment All CX controller All i2 devices All b3 devices Input Temperature sensors Thermistors Cause There is no documentation that details how to calibrate a Continuum sensor. Resolution There is no requirement to calibrate a Continuum Thermistor sensor, Thermistors are factory trimmed to provide an accurate temperature / resistance curve to within the tolerances defined in the datasheet. One exception to this could be if the connecting cable was of excessive length to add additional impedance to the circuit, in this situation the input point conversion line could be used to subtract an offset: Enter "ElecValue - x" where x is a factor to compensate for the cable impedance. See How to add an offset to a sensor reading for further information

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 Automation Server CPU usage goes between 80-100% even with few programs, trends or alarms. Product Line EcoStruxure Building Operation Environment AS Automation Server Cause Cause 1: BACnet into AS uses a lot of resources Cause 2: The AS has bindings from a point to a variety of places Also check out the AS CPU and Memory Loading Quick-Help video on the Exchange. Resolution Example Resolutions in order: The issue described is Functions as Design in StruxureWare Building Operation. The AS results with high CPU percentage with just one point from BACnet interface loaded; however, it had no effect on AS performance. Check the propagation of values. An example would be a Space Temperature which is required by the field bus, the BACnet interface, LON interface, etc. Make sure to properly disseminate this value so to avoid overloading the CPU.

Issue When troubleshooting server issues, it can be helpful to look at the logs that are recorded within the Enterprise Server or Enterprise Central Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Cause Within the Enterprise Server and Enterprise Central logs are many records that are logged as a part of normal operations and unexpected events. Resolution Collect ES and EC Logs via EBO Workstation: Refer to the Workstation section of KB article: Collect logs from an Automation Server Collect ES and EC Logs via Windows Explorer, especially if ES or EC will not run as a service or keep crashing: The ES or EC database path is listed in Software Administrator.   For Windows 7, Server 2008, or higher, the default paths for the logs folder are: Enterprise Server: C:\ProgramData\Schneider Electric [EcoStruxure|StruxureWare]\Building Operation [n.n]\Enterprise Server\db\logs Enterprise Central: C:\ProgramData\Schneider Electric EcoStruxure\Building Operation [n.n]\Enterprise Central\db\logs In EBO V3.2 or higher, shortcut buttons can be found in Software Administrator to go to the folder for logs and database directly.    By default, the "Program Data" folder is hidden, so Windows needs to be configured to view hidden files and folders. For Windows 10 or 11, open Windows Explorer and select View > Show > Hidden items. For other Windows versions, please refer to this Microsoft help article: Show hidden files (microsoft.com). Using Windows Explorer, Navigate to the ES or EC logs folder to find System and Trace logs. Copy the Logs folder contents and send them to Product Support as a compressed file if required. To open a log file, Right-click on one of the logs and select Open with... Expand the window and select WordPad. For Windows XP:   Other ways to review site-specific issues: Is the issue site-specific regarding workstation being used or applications/programs running on these machines? Always try to keep the programs on a workstation to a minimum. Review the Windows Event Logs. What specifically happens when an error occurs? Follow this KB article to view and save the Windows Events: Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes - Communities Make sure that PCs and Windows OS used for WorkStation, ES or EC meet the requirements mentioned in Information Technology System Planning Guide (se.com) Make sure that the firewall and antivirus are correctly configured, and required ports are open for EBO, as explained in Information Technology System Planning Guide (se.com) Make sure that the current installed EBO version is supported, as per the Software Support Policy for EcoStruxure Building Operation - PA-00300. Check if Microsoft currently supports the installed Windows OS: Lifecycle FAQ - Windows | Microsoft Docs

Issue Essex Pin Pad Reader Programming in I/Net Seven. Product Line TAC INET Environment Any Windows OS Version and I/Net Seven Version Cause Need to program an Essex Pin Pad reader in I/Net Seven. Resolution Here is the link to programming the Essex Pin Pad Reader Essex Pin Pad requires the site is not using Large Numbers The Essex Pin Pad is for site which wish to use Pin only for entry. Not Pox Card + Pin or Prox only. For information on a Prox card access which includes Pin Pad see HID PIN Pad reader for I/NET Part Number. For a higher security Pin Only option comparable to the Essex see Code-Guard Scramble Pin Pad Reader Programming.

Issue TAC EM 5 Actuator requires replacement. Product Line Field Devices Environment EM 5 EM5C EM5 Actuator Cause TAC EM 5 Actuator requires replacement Resolution The TAC EM5 Actuator is totally obsolete and no direct replacement is currently available. Details of the TAC EM5 Actuator can be found in EM5 OBSOLETE.tmp.pdf. The TAC EM5 Actuator was capable of use in control systems having alternative electrical wiring connections.   Alternative 1 Actuator electrical connections comprising 24 Vac power supply and 2-10 Vdc / 4-20 mA DC positioning signal. In instances where the positioning signal is 2-10 Vdc, the TAC EM5 Actuator may be replaced by the S-E MD10A-24. Details of the S-E MD10A-24 Actuator may be viewed in MD10A S-E.pdf. N.B. The S-E MD10A-24 should be checked for electrical compatibility with other control system devices that it is to be integrated with. It is unlikely that it will be mechanically compatible with the other control system devices such as the Control Valve Body. Arrangements may therefore need to be made for the design and manufacture of a suitable Linkage Kit.   Alternative 2 Actuator electrical connections comprising 24 Vac power supply and 2-10 Vdc / 4-20 mA positioning signal with 16 Vdc output. In instances where the positioning signal is 2-10 Vdc, the TAC EM5 Actuator may be replaced by the S-E MD10A-24. It should be noted however that no 16 Vdc output is available from the S-E MD10A-24 and none can be connected. A 16 Vdc power supply should therefore be installed to provide power to any external Controllers or Auxiliary Units.

Issue Can Microsoft Object Linking and Embedding (OLE) be used with Cyberstation? Environment Cyberstation linking to Excel using the OLE Toolkit. OLE, replacing the old DDE connections. Cause Live data is often required outside Cyberstation. Resolution The Continuum OLE Toolkit can be downloaded from The Exchange Download Center - download Continuum OLE Toolkit

Issue COVNotification messages in BACnet captures. Product Line EcoStruxure Building Operation Environment BACnet IP network BACnet MSTP network BACnet networks with controllers that support COV (Change of Value) Cause COV increment is an attribute that is available in several BACnet points that is settable and when this attribute COV Increment is left at a setting of zero can cause COVNotification messages appearing as broadcast storms creating un-necessary network traffic. Resolution It is suggested to set the value of the COV increment attribute to something other than the default zero or to a value that is pertinent to the point in question. The COVNotification services are uni-cast messages and can have a many to one relationship depending on how may clients are subscribing to the point. Example: Jobsite has a BACnet OAT (outside air temp) input point with the COV increment of zero. The OAT point is added to the watch window or a binding to a graphic or program. The OAT is changing ridiculously fast due to wind and intermittent clouds. The value is changing by 1/1000 of a degree and each COV (change of value) message is delivered out to any object that is referencing the point. But does the value need to display or do we care if the point changes by 1/1000 of a degree. Let's say that the sites requirement only needs value changes of 2 degrees or more. The COV increment can be set to 2.0 and now the UnconfirmedCOVnotification message would only be sent if the OAT changed by 2 degrees or greater. This alone would reduce 100's if not 1000's of network packets. Imagine a jobsite with the above scenario and 100 different points all with the COV increment of zero. Setting the COV increment to something other than the default of zero is one of many ways to improve BACnet communications and reduce what may appear as broadcast storms on the network.

Issue Attempting to modify the station program in a ENC on a jobsite and cannot connect to the ENC because of the License Brand Mismatch error. Environment Niagara AX WorkBench software and TAC branded ENC or I/A Series G3 Workbench and customer's third party branded AX Jace Cause I/A Series ENCs and Tridium JACEs are usually closed branded unless ordered with an open license. The branding on  the G3 / AX workbench software is always closed.  This procedure was defined by Tridium to protect the customer investment by allowing only authorized partner channel members to access the installed system at a customer site. Resolution I/A Series ENCs and  Tridium AX JACEs are normally supplied with a brand specific license that allows access only by the specific branded copy of the WorkBench software. A customer ordering a JACE or ENC can request that it be licensed as open branded.  This will allow the customer to access the JACE or ENC with their brand specific version of the Workbench software and will allow the Schneider Electric Buildings partner office to access the JACE or ENC with their TAC branded copy of Workbench.

Issue What is the process to replace a CX9400 with a CX9680 NC2? Product Line Andover Continuum Environment Upgrading a CX9200, CX9400 Eclipse, CX9900, CX9940 to a NCII Netcontroller. CMX9924. Model Number, Type change. Cause Where can I get the process to upgrade my obsolete CX controller. Resolution Cyberstation V1.74 SP2 or above is required to support the upgrading process of a CX9200, CX9900 and CX9940 up to a Netcontroller 2. The upgrade process for this is detailed in Appendix B or the NetController II Operating and Technical Reference Guide. For the CX9400 Eclipse controller they require a minimum of V1.91 to support the upgrade. For the older versions of Cyberstation that do not support direct upgrading of a model number, you will need to bring the Netcontroller II on line as a new controller, then in offline editing copy /paste (or Drag /Drop) all objects over to the Netcontroller II. Then go online and fully reload the Netcontroller II and any connected Infinet controllers. The old controller can then be deleted from the system. The objects could also be copied over using edited ASCII dump files if you prefer that method, but either way you may still have to re-animate your Pinpoint graphics unless you upgrade to a version that supports the Netcontroller II replacement. NOTE ACC-LON RS-485 and ACC-LON FTT-10A protocol options A CX9900 may be labeled CPU-8M and a CX9940 labeled CPU-4M. Later CX99 models may have FT added, eg. CPU-8M-FT When replacing a CX9900 or CX9940 it is vital to know if it requires an RS485 or FTT10 IOU module port (if this port is being used) as this CANNOT be modified on site. See article titled No response from I/O module when learning in an IOU This process cannot be used to upgrade the CMX9924 controllers.  The available range of Netcontroller II controllers available has recently been reduced, see PA-00535 "Andover Continuum Offer Optimization"

Issue Need to upgrade V3 Access Expert On Premise software to the most current version in order to gain additional functionality. Product Line Access Expert Environment Access Expert Premise Software V3  Cause It is unclear how to upgrade the Premise V3 software to the most current version of V3. Resolution Access Expert Premise Upgrades now require an SLA to obtain the actual software. Please contact your Sales and/or Security Contact for more details. Both the Access Expert (AX) Premise Server and Client Software need to be upgraded in order for additional features to work. Please note that you will experience issues if your AX clients do not match the AX server version. Take a backup of Mongo database (See MongoDB Backup section located here: https://community.se.com/t5/Building-Automation-Knowledge/Backup-and-Restore-MongoDB-for-Windows-for-Access-Expert-On/ta-p/583) Ensure ALL Windows Updates are completed. Capture screenshots of software installed on server. This can be done by navigating to Control Panel > Add/Remove Programs. It is imperative that you capture the following software and their versions: Access Expert Keep MongoDB SEQ At the writing of this, AX 20.3.1 is the latest. Please check this link to see if there is a new release. Once you have the software downloaded, there will be seven (7) files in the folder: Right-click on “Feenics.Keep.Installer.exe” From there, follow the steps from the Keep by Feenics On Premise Deployment Walkthrough starting from page 8 through page 18.  Note: You must be logged into the Feenics website to access the link in this step.  Navigate to https://www.feenics.com/training/ to login and then click the link above in this step. After a successful installation, click on the “Setup_AX.msi” or “Setup_AX.exe” file to install the latest On Premise client for customer machines. If you run into any issues, please contact Product Support and Services by submitting a case here: https://www.nampss.com/ If you require assistance or would like Schneider Electric to perform this upgrade for you, you can submit a request for that here: https://www.nampss.com/apps_request.php

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.