Building Automation Knowledge Base

Issue At times the firmware and software on the Roam IO2 requires updating and instructions are needed Product Line Andover Continuum, EcoStruxure Building Operation Environment Roam IO2 Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Windows Mobile Cause Instructions for upgrading the software and firmware are provided in the User's guide, but this article places them in an easy to find location Resolution The full instructions for installing and using the RoamIO2 software and hardware are in the User Guides: BACnet Service Tool User Guide + Software Infinet Service Tool User Guide + Software NOTE: The RoamIO2Appl2.000002.upd firmware firmware can only be updated from the BACnet service tool, the Infinet service tool does not have the update OS option.     Please see instructions for installing firmware and hardware for the RoamIO2 for an overview.  

Issue Using addition in a JavaScript, but it is performing a string concatenation. Example: The value in the database is 3. value = value + 1; The resulting value is 31, not 4.  Comparisons are returning unexpected results NaN (Not a Number) resulting from a JavaScript function Product Line TAC Vista Environment TGML JavaScript Vista 5 Graphics Cause Values that are read into a JavaScript in a TGML graphic need to be cast to the correct data type. Some values may be read in as an ASCII string, and this can cause unexpected results. Resolution Cast the value being read to the desired data type. There are three options for casting values to numerical values that can then be used in mathematical operations. In the example below a variable named "value" reads a database value from a binding. No type casting is performed, so this value may be interpreted as an ASCII string. function OnSignalChange(evt){ value = evt.getValue(); } To ensure that the data are represented as numerical value, select one of the three options below. Replace the variable declaration (highlighted) with one that utilizes the appropriate type casting. Number() value = Number(evt.getValue()); The Number() function will treat the whole object as a number. Non-numerical characters will return NaN. parseInt() value = parseInt(evt.getValue()); The parseInt() function will convert the beginning of a string to an Integer value, ignoring any decimal points or any trailing non-numbers. parseFloat() value = parseFloat(evt.getValue()); The parseFloat() function will convert the beginning of a string to a floating point decimal value, ignoring any trailing non-numbers. Also check out the JavaScript Essentials - Episode 3 - Value Types Quick-Help video on the Exchange.

Issue Certain Xenta controllers and I/O modules can accept 10k thermistor temperature inputs. Product Line EcoStruxure Building Operation,TAC Vista Environment Xenta 102-AX Xenta 420A, Xenta 450A Cause The Xenta 102-AX has always used 10k thermistors. Now some of the I/O modules and programmable controllers also have an option for 10k thermistor inputs. A common question is -- what type of 10k thermistors? Type 2? Type 3? Resolution The reason there is no reference to 10k Type 2 or 10k Type 3 is because these are Continuum-specific terms. The 10k thermistor that is compatible with Xenta 42XA and 45XA I/O modules are the same that I/NET uses. They are Vishay Dale Curve #1. View this PDF for the Resistance vs. Temperature Conversion Tables for this thermistor.

Issue Where can I get example programs and programming information on the Smart sensors? Product Line Andover Continuum Environment Smart Sensors: TTS-SD-LCD-1 TTS-SD-LED-1 Cause Smart sensors require specific Plain English programming that is different from other controllers, where is the documentation to support this? Resolution The Smart Sensor Installation and User's Guide and Example programs for the Smart Sensors are available for download from The Exchange Extranet.   PSS Example programs

Issue Controller cold starts after power fail Product Line Andover Continuum Environment Continuum 1.x CX BCX Cause ACCRestartMode system variable is set to Cold Start Resolution Change the ACCRestartMode system variable. See the bCX1 Controller Technical Reference Guide Rev F  document page 55 onwards for an explanation of the changes that are required.

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 Faulty operation of BMS equipment due to electrical interference from other equipment can be difficult and costly to identify and fix.  Guidance is required for the best installation practices to minimize the source of the interference and to protect against it when it occurs. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment All electrical equipment Cause Poor installation can cause equipment to generate high and low-frequency electromagnetic interference that can disrupt the operation of other systems. Resolution Schneider Electric has produced a document Practical Installation Guidelines which discusses the theory and offers practical guidelines to protect against and minimize the generation of, electromagnetic interference.

Issue Satchwell “M 1201” Actuator forming part of combined Actuator / 2-port Valve Body assembly requires replacement. Environment Stand alone Satchwell “M 1201” Actuator forming part of combined Actuator / 2-port Valve Body assembly M 1201 Actuator 2-port Valve Body Cause Obsolescence of Satchwell “M 1201” forming part of combined Actuator / 2-port Valve Body assembly. Resolution There is no direct replacement for the "M 1201" Actuator and as a result both the "M 1201" Actuator and the 2-port Valve Body to which it is connected will also require replacement.  Replace Satchwell “M 1201” combined Actuator & 2-port Valve Body assembly with Schneider Electric MD10B-230 Actuator, LMD-MB Linkage Kit and Satchwell MB series 3-port Valve Body of appropriate size. Details of the original Satchwell “M 1201” combined Actuator & 2-port Valve Body assembly may be viewed here. Details of the replacement Schneider Electric MD10B-230 Actuator may be viewed here. Details of the replacement Schneider Electric LMD-MB Linkage Kit may be viewed here. Details of the replacement Satchwell MB 3-port Valve Body may be viewed here. N.B. Satchwell MB series 3-port Rotary Shoe Valve Body may be converted for use as a 2-port Zone Valve by means of the installation of a plumber’s plug in Port 3 Install plumber's plug in Port 3 of MB series 3-port Rotary Shoe Valve Body. Tighten plumber's plug sufficiently to ensure PN 10 rating of Valve Body is not compromised. It is possible that the "M 1201" Actuator may have been fitted with an Auxiliary Switch. If so then an MD-S1 Auxiliary Switch may be fitted to the MD10B-230 Actuator if required. Details of the MD-S1 Auxiliary Switch may be viewed here.

Issue Moving from Webreports going to Postgres/TimescaleDB instead, leaves us without a reporting engine. SSRS can supposedly utilise a PostgreSQL database, but SSRS is a licensed part of MSSQL. Product Line EcoStruxure Building Operation Environment Building Operation Timescale Database Cause From EcoStruxure Building Operation version 4.0 (2022) the Building Operation Report Server is no longer supported. Instead, we support PostgreSQL/TimescaleDB, using Dashboards and Excel from within EBO, to make reports, using Notification reports to start Excel and reports. Resolution EBO 3.2 introduced Enhanced Reporting, based on the current feature Notifications in combination with Notification Report Template, which also supports report data such as Alarms, Groups, Multi Log list, Relative events and Users. The Notification result can also be presented in XLSX format and converted to PDF with signing capabilities. If External Log Storage is configured and connected (PostgreSQL/TimescaleDB), then historical report data can be fetched from there.   EBO 2023 introduced External Log Storage support for Microsoft SQL Server in addition to PostgreSQL/TimescaleDB   Information  and examples of Enhanced Reporting and Dashboards can be found in EBO Webhelp, My LearningLink and the Automation Experts Community.   NOTIFICATION REPORTS : EBO Webhelp: Notification Reports  Community: Reporting in EcoStruxure Building Operation 3.2 Community: Reports showcase - share your reports! Community: Get more data out of the system with Notifications! EcoXpert Extranet Video: Community Video : Fusion Fridays - Session 20 Community: Change Control and Enhanced Reporting Lab Guides Community: Example Report Templates  Community: Forced Values Report Example My LearningLink: EcoStruxure Building: Enhanced Reporting and Dashboards 3.2 My Learning Link: EBO 2022: Enhanced Reporting and Dashboards   DASHBOARDS : EBO Webhelp: How Dashboards Work EcoXpert Extranet Video: Dashboards EcoStruxure Building Operation 3.0 - Informational Video Community: What Custom Types have to do with Dashboards Community: Public vs Personal Dashboards Community: Graphics in Dashboards [Advanced] Community: Dashboards: Share your screenshots! EcoXpert Extranet: PA-00701 EcoStruxure™ Building Operation 3.0 Captures the Spotlight

Issue On a new JACE-8000, or on one in which the clean-dist or factory restore procedure has been applied, the JACE can be pinged but, you cannot connect to the platform, and the system time's year shows as 2020 or greater.   The following symptomatic messages can be observed in the serial shell via the debug port:  ERROR [01:26:53 01-Jan-2037] [tid = 1] niagarad: policy file verification failed. Policy files may have been tampered with. Cause is: [/opt/niagara/security/policy/java.security failed signing verification]  ERROR [01:26:53 01-Jan-2037] [tid = 1] niagarad: throwable occurred while initializing daemon (java.lang.SecurityException), can not continue  sysmon: niagarad is no longer running  The following symptomatic messages appear in the system logs:  Jan 01 01:26:53 2 11111 0 niagarad: policy file verification failed. Policy files may have been tampered with. Cause is: [/opt/niagara/security/policy/java.security failed signing verification]  Jan 01 01:26:53 2 11111 0 niagarad: throwable occurred while initializing daemon (java.lang.SecurityException), can not continue  Jan 01 01:26:53 2 11111 4 sysmon: niagarad no longer running Product Line TAC IA Series. Environment I/A Series Jace-8000 Cause This issue is encountered when the RTC clock's date is Wednesday, December 30, 2020, or later.  Resolution Use the debug port to connect to the system shell with PuTTY. See the System Shell section of the JACE-8000 Install and Startup Guide Set the system clock to a date before the year 2020, and then commission the JACE with 4.2 or newer.  The issue is corrected within the fix for the following issue, addressed in Niagara 4.2.36.10:   NCCB-19628: Code signing timestamps checked improperly, verification will fail Jan 1, 2021    We will continue to see the issue on new JACE-8000 as they ship with a 4.1 daemon. This may also occur on a JACE-8000 on which the clean-dist or factory restore procedure has been applied.

Issue TAC Graphic Clipart library is a collection of clipart to use as a starting point for an image based graphic page. There are pieces for building air handler ductwork, controlled equipment, dampers and actuators, and water side equipment. Product Line TAC INET, TAC Vista Environment I/NET gpg graphic Vista ogc graphic Cause Without libraries to build a background image for HVAC equipment, it can be difficult to create user-friendly graphic pages to display dynamic data.  In a graphic editor that relies on bitmaps or jpgs to build the airflow diagrams, floor plans, water side diagrams, etc, this library can be used as a starting point. Resolution Download the attached .zip file. Unzip the contents to a location on the hard drive of the computer that will be used to edit the graphic pages. Browse the contents of the .zip file.  It will be separated into logical folders.

Issue How can the format of a custom card be determined/understood Product Line Andover Continuum Environment Access Control AC1 AC1Plus ACX Cause The format of access cards is unknown. Resolution The document Understanding custom card formats in Continuum describes how to determine the custom format of proximity cards.  

Issue Once the occupied cooling and heating setpoints are written from a BMS, the user is not able to change the setpoint from the room controller Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment Automation Server Enterprise Server SE8000 Series Room controller Viconics branding VT8000 Series Multi Purpose Manager (MPM) BACnet Cause By default, the occupied setpoint value is written to Room Controller with priority level 16 by the BACnet front end. Attempting to change the setpoint locally using the up and down arrows on the SE8000 Room controller will not be allowed since the Room controller uses the relinquish value internally (priority 17) which will be automatically overwritten by the BACnet front-end. Resolution The work around is to release the BACnet front-end control over the BACnet object using a LUA4RC script. The script can be uploaded using one of the following two methods: 1 - Uploader Tool A USB cable is required to upload the script. The uploader tool can be downloaded from the Exchange Download Script Download Uploader Tool   2 - BACnet The script can also be directly uploaded via BACnet using the "Description" field as shown in the image below if (ME.AV92 == 6 or ME.AV92 == 7) then ME.AV39_PV[16] =nil ME.AV39_PV[10] =nil ME.AV40_PV[16] =nil ME.AV40_PV[10] = nil ME.AV92_PV[17] =0 end Where, ME.AV92 is the Keyboard value ME.AV39 is the Occupied Heating Setpoint ME.AV40 is the Occupied Cooling Setpoint Using this method, the script can be uploaded to multiple SE8000 Room Controllers by following the steps in Bulk Lua4RC upload via BACnet (Mass upload) For more information about Lua4RC, refer to the Lua4RC Programming Guide

Issue Supplemental Documentation on the Menta OPT block for optimized start and stop. Product Line TAC Vista, EcoStruxure Building Operation Environment Menta Function Block Cause The document below is intended to clarify the inputs and configuration parameters of the Menta OPT block and when/how to use them. Resolution Click here to download the example Menta macro A Brief Overview of Optimized Control Optimal Start Optimal Start measures how long it takes a room temperature to reach setpoint each morning when the air-handling unit is enabled. These measurements are then used to predict how long it will take the next time. As time goes on, the predictive algorithm is refined until it becomes quite accurate. An optimally started unit saves energy by only starting as early as is needed, not just an arbitrary hour or two before occupancy. Optimal Stop Optimal Stop is less common. An optimally stopped unit stops running prior to the end of the day. It measures how long it takes before the measured room temperature drifts outside of an acceptable range around the setpoint. This saves energy on cooling a building until 5:00pm (for example) when the occupants are just about to walk out the door. The example in this document will not implement Optimal Stop. Inputs to the OPT Block RoT Room Temperature. If there is just one room temperature sensor being served by the optimally started unit, then this is where it would be used. However, if the unit has several room temperatures or serves many VAV terminal units, consider the following options: Average all temperatures Pick one interior zone Highest room temperature for cooling/lowest room temperature for heating Use return air temperature In all of these scenarios, some consideration should be made for if the input sensors fail: Averaging all temperatures is the most robust method. However, if SNVT inputs are used, it may be necessary to discard invalid values (621.8°F) from the averaging calculation. If one interior zone is used and the temperature sensor fails, the unit will eventually revert to starting as early as is allowed every day. The default value for this is 12 hours early; the example in this document uses 2 hours. If the primary sensor fails, use a secondary, or disable optimal start on a failed condition. Instead of the highest and lowest room temperatures, it may be wise to use the second highest and the second lowest room temperature. This allows for one failed sensor in each direction before the Optimal Start calculation is affected. Using return air theoretically is a lot like using the average of all room temperatures. Adjusting the setpoint to get the desired result might be required. A failed sensor input should disable the Optimal Start calculation. SP Setpoint. Using two OPT blocks – one for Optimal Start cooling, one for Optimal Start heating – allows each to be fine tuned. If there is a morning warm-up sequence, then the heating Optimal Start may be much quicker than the cooling. Using one block requires the internal calculation to adjust as the needs change from cooling to heating, and can be less agile when switching from cooling to heating requirements. OuT Outdoor Temperature. Resets to the curve occur based on the outside air temperature. If it is very cold or very hot outside, the unit will start sooner. This curve is reset automatically as time goes on to better predict the effect outside air temperature has on the controlled space (if AutoAdjust > 0). OpI Operation Indication. In the example of an air-handling unit, OpI would be the fan status. If the configuration parameter OperIndicF is set to 1, then this will be used for internal calculations. Otherwise, it will just use the command as status. This prevents a mechanically failed unit from affecting the calculation. A good rule to follow is if fan status is available, use it. TmL Time left. A time schedule (TSCH) input goes here. This tells the calculation how much time is left before the unit is scheduled to turn on (or off). The OPT block then starts the unit early based on this number. It also ensures that the unit always runs during the scheduled occupied time. Mode Mode is for heating/cooling or enabled/disabled. It is advantageous to always program in a method for disabling Optimal Start through a public variable (PVB). Many times the seeming complexity of Optimal Start is found to be undesirable by building operators and they will ask to have it disabled. Mode could be programmatically set for heating/cooling based on outside air temperature (or some other factor), but in the example in this document, two separate OPT blocks are used and are hard-coded for their respective modes. Configuration Parameters of the OPT Block AutoAdjust AutoAdjust refers to whether or not the OPT block gets smarter by adjusting the curves set initially on the first download. If AutoAdjust is set to 0, then the OPT block will still adjust the start time every day based on the room temperature and outside air temperature, but it will not adjust those early start times based on past experience. Set the AutoAdjust to 1, and the curves will adjust a little every day. Set AutoAdjust to 2 and the OPT block will also adjust the holiday compensation (the unit will start a little earlier after a 3-day weekend, but may need to learn exactly how much as time goes by). To maximize the potential of the OPT block, it is suggested to set this value to 2. RoomTempF Room Temperature Flag. Is a room temperature sensor present? Without a room temperature sensor, it is not possible for the OPT block to adjust its curves. It is guessing at that point based on pre-determined curves. It is not recommended to use OPT without a room temperature sensor. OperIndicF Operation Indication Flag. If OperIndicF is set to 1, then the OpI input will be used for internal calculations. Otherwise, the OpI input is ignored and the command is used as status. This prevents a mechanically failed unit from affecting the calculation. A good rule to follow is if fan status is available, use it. StartTimeLo Start Time at Low Outside Air Temperatures. When it is cold outside, how much earlier should the unit start? This will change between a cooling and a heating optimal start block. If AutoAdjust is set to 1 or 2 then this is just a default value. It will adjust as needed each day, but a good default value is important. StartTimeHi Start Time at High Outside Air Temperatures. When it is hot outside, how much earlier should the unit start? This will change between a cooling and a heating optimal start block. If AutoAdjust is set to 1 or 2 then this is just a default value. It will adjust it as needed each day, but a good default value is important. HolidayComp Holiday Compensation. This is the default compensation for a holiday (longer than 48 hours of continuous unoccupied time). The value is a percentage. If there is a 3-day weekend, how much earlier should the unit start on the following Tuesday? If AutoAdjust is set to 2 then this is just a default value. It will adjust it as needed each day, but a good default value is important. MaxStartTi Maximum Start Time. This is the maximum amount of hours the unit is permitted to start prior to the occupied time. The default value is 12 hours. The first time the unit is downloaded, it will start this early and measure how long it takes to achieve setpoint. 12 hours is very early. The example in this document uses 2 hours. Even if something goes wrong with the internal calculation (failed sensor input, for example) the earliest it could start would be 2 hours early. ETol Error Tolerance. How close to the desired setpoint does the temperature sensor need to be to be considered at setpoint? An error tolerance of 0.5°F is default and is usually acceptable. StopLoTemp, StopTimeLo, StopHiTemp, StopTimeHi, StopTimeErr All of these parameters refer to the Optimal Stop portion of the OPT block. Setting them to 0 disables the Optimal Stop functionality. Output of a OPT Block There are three possible output values of an OPT block: 0 = The unit is off, unoccupied 1 = The unit is on, occupied 2 = The unit is on, optimally started Putting It Into Practice The example below is a Menta Hierarchy Function Block (HFB) and shows HFB inputs to the blocks. The top OPT block is set to heat mode and looks to a heating setpoint. The bottom OPT block is set to cool mode and looks to a cooling setpoint.   OPT_START_HEAT OPT_START_COOL AutoAdjust 2 2 RoomTempF 1 1 OperIndicF 1 1 StartTimeLo 60 0 StartTimeHi 0 60 HolidayComp 0 0 MaxStartTi 2 2 Etol 0.5 0.5 StopLoTemp 0 0 StopTimeLo 0 0 StopHiTemp 0 0 StopTimeHi 0 0 StopTimeErr 0 0 Using the hints and tips suggested will allow not only for proper programming techniques, but also for creation of macro libraries that can be reused and shared to improve effectiveness across business units.

Issue SPP920 Datasheet, Technical Information and Installation Instructions Product Line Field Device Environment SPP920 Differential Pressure Switch Cause No information available for the SPP920. The Sensor catalogue says it is supported by Huba. Resolution Either click link www.hubacontrol.com and search for 630. or the Technical information can be downloaded here. Installation Instructions can be downloaded here. Mechanical connections are: P1 = High Pressure (discharge/flow), P2 = Low Pressure (suction/vacuum) All of the various pressure range options come with the following options: - EPDM diaphram material - Brass Case - Spec Cover PG9 - IP65 Rating - Bracket Type A

Issue Simple Modbus Lua Script Product Line EcoStruxure Building Expert Environment Lua Programming Cause Simple script to test Modbus function Resolution In each of the samples, the following needs to be observed: The Modbus port is closed and opened with the port settings. The samples can be combined but the port is only set once. The settings for the Modbus RS485 port requires an address, in this instance 99 is used. This must be different from the slaves. The nnn.MOD1 must be left unchecked so that it is not enabled. This will allow the Lua script ModbusB to work. For added functionality the "Print" command is used. The "print" command provides added functionality indicating a successful read / write in the output window. If the result = 0 then the read / write is successful. Anything else is an error code. Contact Product Support. The value = is the value that is either read in or written dependant on the function used. The following samples provide simple read / write functions.: Coil Registers Digital Input Registers Holding Registers Input Registers 32bit Floating Point

Issue Documentation for architectural design for illustration, explanation, sales presentations, or other medium Environment Schneider Electric office, partner office, or other site needing documentation Cause Inability to find literature and need to explain, illustrate, or define issues. Please find the links below for each of the product lines. Resolution Continuum: download architectural Flyer:  pdf   jpg  INET: download  architectural Flyer Vista:  download architectural flyer pdf   jpg  I/NET and Vista together pdf

Issue “Invalid certificate for https communication” alarm pops up after upgrading to EBO 4.0     Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause "Invalid certificate settings for Server to Server communication" is set to enabled (Generate Alarm) by default for new installations/upgrades. This function was deliberately designed to alert existing installations that their sites might be subject to security-related issues, and necessary action needs to be taken. Resolution If users want to get rid of this alarm, they need to: Suppress the alarm by unchecking the “Generate alarm” under Security Settings/ Invalid certificate settings for server to server communication   Or Replace the server certificates with one that can be validated against a CA certificate.   Note: Please refer to the following web pages for more information. CA Certificate Management Security Settings – Control Panel  SSL Certificates 

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.

Issue Controllers underneath a LonWorks Interface are going offline, or values are taking long periods of time to update. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause There could be a number of causes for Lon communication problems including running the communication wire near high voltage, the Lon is shorted out, or loose terminations. Resolution In EcoStruxure Building Operation (EBO) Workstation you can use the Diagnostics tab under each controller to help troubleshoot the communication issue. From here you can monitor the device state, packet errors, transaction timeouts, receive transaction full errors, lost messages, missed messages, last reset case, and the last error logged. To access the Diagnostics tab, select the controller in the System Tree, and click the Variables tab. Then click the Diagnostics tab on the right side of the screen. Here you will find the different device statuses and statistics. The Packet errors can be used to help identify controllers that are having severe problems and may need the communication wire to be physically checked. In order to test the Packet errors, first you will want to clear the current packet error count. You can do this by right clicking on the controller and selecting Advanced -> Clear Status. This will set the packet error count back to zero and now you can click refresh to monitor how fast the errors are building up. If this number is climbing quickly then there may be a physical layer communication problem. If a lot of packet errors is found, the next step in the investigation will be a deeper analysis of the Lon network, using, for example, a Lon Protocol Analyzer (LPA). Refer to the Knowledge Base Article Troubleshooting LON Network Communication.