Building Automation Knowledge Base

Issue Receive alarm messages as "Server does not exist or access denied", "08001: [FreeTDS][SQL Server]Unable to connect to data source" or "08S01: [FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist" when using SQL Server Express for External Log Storage even though login credentials are correct. 08001: [FreeTDS][SQL Server]Unable to connect to data source 08S01: [FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist" Product Line EcoStruxure Building Operation Environment Enterprise Server Workstation External Log Storage SQL Server Cause SQL Server Express is using Windows Authentication and/or the TCP/IP network protocol is disabled. Resolution To use external log storage with SQL Server Express the User must be able to login with SQL Server Authentication (e.g. a username and password) and the TCP/IP Network protocol must be enabled.  Consult Setup External Log Storage using MSSQL for additional details.   Check SQL external log storage host address: In the host address type the IP address or DNS name of your external log storage, without the SQL instance name. Having the SQL instance name in the host address can cause communication failure if EBO server is connecting to remote SQL server, refer to: Microsoft SQL Server - Basic Tab. To check the User login credentials: Open SQL Server Management Studio and enter the details from EcoStruxure Building Operation into the SQL Server connection window.  Choose SQL Server Authentication (A), enter the server details (1), user name and password (2) and attempt to login. If an error message appears indicating cannot connect and the credentials are correct it is possibly SQL Server Authentication is not enabled. Login to the SQL Server using Windows Authentication and follow the Microsoft article Change server authentication mode to set to 'SQL Server and Windows Authentication mode'. Attempt to login to SQL Server and the specific database should be visible. To enable the TCP/IP Network protocol:  Open SQL Server Configuration Manager (1) In the SQL Server Network Configuration menu, select Protocols for SQLExpress (2) Right-click TCP/IP (3) and select Properties (4) In the window that opens, click the IP Addresses tab (5) Either set a different port number for each one of the IP addresses or simply set one for all (6).  The default is 1433 but will need to be a port that is free.   Click OK. Back in the SQL Server Management Studio ensure the SQLExpress service is restarted. For additional information please consult Default SQL Server Network Protocol Configuration and Enable or disable a server network protocol            

Issue When using EBO's registration page, the registration website that is opened allows the user to login and enter the new system ID, however, the user then cannot proceed any further. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Cause The link https://registration.smartstruxure.schneider-electric.com/, which redirects to the https://registration.smartstruxure.schneider-electric.com/WebConnectUI/RegisterUser/home This page may not allow the user to complete the site’s registration with the new system ID. Resolution Register the site’s EBO new system ID using the following website address. https://registration.smartstruxure.schneider-electric.com/ebo/Home

Issue When trying to change a BACnet value unit, the following error message pops up Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause Using a unit that is not supported by BACnet standard or using a prefix with a unit that doesn't support a prefix in BACnet. In the following example, we can see the "Airflow Input" has the kPa unit. Now, if the user wants to change the unit to N/M 2 , without removing the prefix k(10 3 ), an error pops up upon saving the settings.   Resolution Make sure to select a unit that is supported by the BACnet protocol. Supported engineering units in BACnet are listed in BACnet standard, ASHRAE 135 clause 21, refer to BACnet Engineering Units enumerations. To resolve the issue in the above example, the user needs to omit the prefix before selecting the unit OR  They need to make sure the selected unit supports that prefix.    

Issue When using an Echelon U10/U20 USB or other Lon network adaptor for communication with a laptop and standalone WorkPlace Tech, not WorkPlace Tech Editor, you must change the default configuration settings.  The default Lon Network Domain ID length (1 byte), Domain ID (18 decimal) and Subnet (254) in the AS-P conflicts with the defaults used by WorkPlace Tech. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech (Lon Network communication settings) Building Operation Automation Server Premium Building Operation Enterprise Server Cause Lon Network configuration Resolution Look at the LonWorks Network "Advanced" tab in the AS-P to determine the addressing information. Open the WorkPlace Tech WorkStation Communication Settings and select LonWorks.  Open the Change Address window Select the "Manual Setup" radio Button Modify to match the AS-P Lon Works Network configuration.  If a different Domain ID or subnet has been assigned in the AS-P, it will need to be assigned the same in WorkPlace Tech You can now browse the LonNetwork from the laptop.  If the MNL devices are assigned applications from the AS-P, do not modify the programs from the WorkPlace Tech Tool  

Issue Downloading a license update, such as after adding features to a site license or extending the evaluation period on an evaluation license, and this fails with the below error being shown. The SSN is invalid for this installation. Product Line EcoStruxure Security Expert Environment Security Expert Cause Wrong SSN being used. The SSN being used is different to what was used when Security Expert was initially installed. Resolution Uninstall Security Expert and re-install using the correct SSN. Backup the SecurityExpert and SecurityExpertEvents databases and copy the resulting backup files somewhere safe. Manual backups can be initiated from the Global > Global Settings menu. Select the directory location and press backup now. Uninstall Security Expert from Windows Add or Remove Programs. Search for "Security Expert" to filter the results. Install Security Expert from available installation files. When asked for the license make sure to use the correct SSN.

Issue Access Expert On-Premise setup needs procedures and tools to backup and restore the database Product Line Access Expert Environment Access Expert Premise Software V3 MongoDB Cause The procedures for backing up and restoring the MongoDB is documented online at the link below. https://docs.mongodb.com/manual/tutorial/backup-and-restore-tools/ However, these instructions do not outline how to use the commands (mongodump and mongorestore) within the Windows OS environment using specific examples. Resolution The following procedures are designed to fill in the gap for Access Expert administrators who need to do manual MongoDB Backup and Restore. These procedures assume that Access Expert V3 has been installed and is functioning normally. You will need 2 separate Command Prompts, run as Administrator, open for these procedures. Mongo DOS Shell to attach to and run commands within MongoDB environment Standard DOS Shell to run the Mongo backup and restore commands MongoDB Backup Ensure MongoDB service is running (Start> Run> services.msc) Open a Command Prompt as Administrator (referred to as the Mongo DOS Shell) Type mongo(command) Type show dbs (command) - shown above, to give a list of the dbs available) If the MongoDB service is "Running," but the client cannot connect when typing mongo, it's probably because the path to the mongo bin folder hasn't been added to the PC's environment. To Add a local path locations variable to a PC environment https://docs.microsoft.com/en-us/previous-versions/office/developer/sharepoint-2010/ee537574(v%3Doffice.14) Ex. C:\Program Files\MongoDB\Server\3.6\bin (This will vary based on the version of Mongo) Open another Command Prompt as Administrator (Standard DOS Shell) Use the CD command to navigate to where you would like the backup files to be created Ex. C:\Data mongodump (command) The mongodump command creates the dump folder with admin, Keep, Signalr subfolders MongoDB Restore In the (Mongo DOS Shell) Prompt show dbs (command) use Keep (command) (Case sensitive) db.dropDatabase() (command) Use the Command Prompt as Administrator (Standard DOS Shell) mongorestore (command) The window should indicate "Finished Restoring Keep.Events," "done" and RESTORE COMPLETE If there are “E11000 duplicate key error collection” Keep.Events errors, it’s because the collection events are already in the folder and need to be deleted first.   Steps to correct the E11000 duplicate issue: (Stop the service, delete and recreate the DB folder, restart service) Right-click on the MongoDB service and Stop (you can’t delete files while the service is running) Delete C:\Data\db folder (not the Data, only DB) MANUALLY CREATE THE DB FOLDER - Right Click > New Folder and name it DB Restart the MongoDB service - this creates the necessary files in the DB folder Once these steps have been done, rerun the mongorestore command mongorestore (command) Verify that users can log into Access Expert with this database

Issue How much ethernet bandwidth do lonworks systems consume using Loytec L-IPs, iLons, etc.? Environment TCP/IP ethernet network LNS System Cause IT professionals will sometimes hesitate to allow the control system to use the same TCP/IP network as the internet, phones, etc. They may ask what the expected bandwidth usage will be before granting access. Resolution It is impossible to explicitly state how much bandwidth a LonWorks system will consume on the ethernet. It depends heavily on the amount of LON traffic being sent by the controllers. The routers themselves do not produce traffic, they only pass the traffic onto and off of the ethernet. The traffic is created by the LON devices, Xenta controllers, Vista and LonMaker or other HMIs. Vista can create a maximum of 15 LON telegrams/second. This is very little traffic with respect to IP bandwidth. Unless you have made bindings into the LNS NI (which we never do in a Vista-scenario, since Vista cannot read these) there is basically nothing at all going out from LonMaker/LNS unless you are commissioning devices. Starting the LonMaker Browser also generates traffic. But this is also normally just in the design phase of the network, not in "operating mode". SNVT bindings or TAC network variables from one LON network to another over the IP channel also generate traffic. A typical Xenta can produce 2 SNVTs propagation/second and/or maybe 10 TACNV. This is not much (as IP-traffic), but if there are hundreds of nodes communicating simultaneously all passing through L-IP gateways, the amount of IP traffic will grow. If you are using a Loytec L-IP, it uses a protocol feature called "packet bunching". Before it sends out a packet on the IP side, it waits for an adjustable time (Aggregation Time, default = 16ms) if some packets are following, which have to be sent to the same IP addresses. If some packets are following, it puts the packets in the same IP frame and sends it all together in a single IP packet. The receiving node unpacks it and makes multiple EIA-709 (Lonworks) packets again.

Issue Initialization errors when starting I/NET Seven 2.42 or higher Error: "You must install an instance of SQL 2008R2 (64bit) before completing the INET install" Product Line TAC INET Environment I/NET Seven 2.42 Windows Server 2008 64-bit Windows 7 64-bit SQL 2008 64-bit Windows 8 Cause I/NET 64-bit requires specific installation process in order to function on a 64-bit PC Resolution Installing SQL Download SQL2008 R2 Express 64 bit (SQLEXPR_x64_ENU.exe) from this location: http://www.microsoft.com/en-us/download/details.aspx?id=30438 Run SQLEXPR_x64_ENU.exe In the left hand section, select Installation In the Right and section, select New SQL Server stand-alone installation of add features to an existing installation. At the "Setup Support Rules" screen select OK At the "Product Key" screen, select Next At the "License Terms" screen, check accept and select "Next" At the "Setup Support Files" screen, select Install At the "Setup Support Rules" screen, select Next At the "Feature Selection" screen select: Database Engine Services, SQL Server Replication, Management Tools - Basic (If Present) and SQL Client Connectivity SDK. Leave the Shared feature directory as default. At the "Instance Configuration" screen, select the Default instance option, accept the default Instance ID, accept the Instance root directory default settings and select next. At the "Disk Space Requirements" screen, select Next At the "Server Configuration" screen, under SQL Server Database Engine set the Account name to NT AUTHORITY/SYSTEM, leave the password field blanks, and set the startup type to automatic. Under SQL Server Browser Service, set the Startup Type to Automatic At the Database Engine Configuration screen, set the Authentication Mode to "Mixed Mode", Define a strong password (example: @sql2008), in the Specify SQL Server administrators section click "Add Current User". Select Next. At the "Error and Usage Reporting" screen, select Next At the "Installation Rules" screen, select Next At the "Ready to Install" screen, select Install At the Installation Progress screen, when the setup process is complete, select Next At the "Complete" screen, select Close. SQL Configuration: In the Windows Start Menu, launch the SQL Server Configuration Manager In the Left hand section of the window, highlight SQL Server Services Verify that SQL Server Browser and SQL Server are Running In the left hand section of the window, expand SQL Server Network Configuration and highlight Protocols for MSSQLSERVER Enable Named pipes and TCP/IP Close the SQL Server Configuration Manager Restart the PC Installing SQL Server 2005 Backward Compatibility On the I/NET 2.42 or higher installation CD, look in Support\SQLBCM_64Bit and launch the SQLServer2005_BC_x64.msi file Follow all the prompts on each screen and accept all defaults. Install I/NET Seven 2.42 or higher Install I/NET Seven 2.42 or higher using the installation CD Follow prompts and use defaults When prompted for the SQL password, select "Windows Authentication" Restart the PC Open I/NET Configuration through the start menu. Modify the default Config profile or create a new profile. Close I/NET Configuration Start I/NET NOTE: If error occurs during SQL installation stating invoke or begin invoke failed, follow instructions at this link: http://support.microsoft.com/kb/975055 UPDATE: SQL2008 SP1 prevents the invoke failed error. It can be installed with the same instructions as above. Download it at this link: http://www.microsoft.com/en-us/download/details.aspx?id=25052

Issue The object identifier of a BACnet device (device id) must be unique internetwork-wide, different vendors use different methods for calculating the device id default value. When integrating devices from different vendors sometimes it become necessary to change a device's default object id. Product Line Andover Continuum Environment bCX4040 b3s Third party BACnet devices Cause BACnet integration Resolution If the BACnet device is a Continuum device (bCX4040 or b3), Continuum provides a mechanism for changing the default device id. For a third party BACnet device, VTS can be used to write to the Object Identifier of the device in order to change the device id. Note that this will only work if the device manufacturer has made the object identifier for the device object writable. Click here to download VTS Click here to see the procedure to follow to set a third party device id using VTS.

Issue Are username and passwords encrypted during transmission from the remote client or the web client to the Sigma server? Product Line Satchwell Sigma Environment Sigma Remote Client WebClient Cause Are username and passwords encrypted during transmission from remote client to the Sigma server? Are username and passwords encrypted during transmission from web client to the Sigma server? Resolution Usernames are not encrypted during HTTP transmission from the remote client and web client to the Sigma server. Passwords are encrypted during HTTP transmission from the remote client and web client to the Sigma server.

Issue When external internet access is not possible an alternative NTP Server is required to allow ES and AS to by time synchronized onsite. Product Line EcoStruxure Building Operation Environment Enterprise Server / Automation Server on closed network Eg Windows 7 Cause AS will not synchronize the time with a local NTP such as Windows 7 (32 or 64 bit) without it first being configured. Even then, increasing Cyber Security features within EBO means that the use of a 3rd Party NTP is becoming a much better option. Resolution Preferred Solution The very best option for the latest versions of EBO would be to investigate. Meinberg NTP which is a third party NTP server that runs on the Win7 or Win10 OS and provides NTP by synchronizing with four or more Internet clocks and is a trusted time source in NTP.  It is not an officially supported PSS tool, but it does fix the issue of the ES/AS not trusting the time.   Windows 7  Config If you still wish to attempt the Windows 7 NTP option first the procedure to setup is as follows:    In the 'Services' window (part of Administrative Tools) Stop the 'Windows Time' service if already running. The 'Startup Type' could be set as Manual or Automatic depending on the user needs. In the Registry Editor following changes to be made under the Key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time: ** Config -> AnnounceFlags = 5. ** HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time\TimeProviders\NtpServer -> Enabled = 1. Start the 'Windows Time' service in the 'Services' window(part of Administrative Tools). Note: NTP uses UDP Port 123 Below is a Wireshark capture using filter udp.port == 123 indicating the “Leap indicator” bits are 11, meaning “clock unsynchronized”. NOTE: The NTP client in the AS may ignore the time sent by the NTP server if the root dispersion is greater than 'X' seconds (unknown at this time). See Automation Servers ignore time sync message sent from Windows NTP server that uses local internal clock for information on how to determine whether this is a problem at the site and how to resolve it. Note: Test Lab results show that once validated and synchronized, the AS asks the time from the NTP about every 17 minutes. Two enhancements have been requested for a future release: Workstation gets an alarm if the NTP is not a valid reply A tick box setting in Workstation so the ES/AS can accept an invalidated reply(time)

Issue Some attributes used within Continuum PE programs on b3/i2 controllers are no longer appropriate with EBO Script programming Product Line EcoStruxure Building Operation Environment b3 Infinet Building Operation Server Script Programming Cause Some attributes used within Continuum PE programs on b3/i2 controllers are no longer appropriate or cannot be used with EBO Resolution An example of this would be the ElecValue attribute for an input or output. This can be used within the Conversion field of an input but cannot be used within a Script Program or Script Function. The Continuum example PE program for an STR502 or STR504 includes the line "If STR5xx ElecValue <= 0 then Return Upper" The correct result can be obtained within SmartStruxure by dropping the "ElecValue", so "If STR5xx <= 0 then Return Upper" Then ensure the STR5xx analog input is a Voltage type with no conversion configured. Note: The ElecValue keyword can still be used in the Conversion line of an Analog Inputs (e.g. for Counter input scaling). Some other Attributes not supported in Script Programming are: Size LogType

Issue When attempting to enable .NET Framework 3.5 on Windows using the DISM command mentioned in the WebReport installation guide, the attempt fails with error 1910 Command: dism /online /enable-feature /featurename:NetFX3 /all /Source:e:\sources\sxs /LimitAccess Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.14393.0 Error: 1910 The object exporter specified was not found. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log Product Line EcoStruxure Building Operation Environment WebReports Cause The Windows Modules Intaller service is not operating correctly, and has to be restarted. The service is however protected, so this can not be done through the services control panel. Resolution Kill "TrustedInstaller.exe" from the Windows task manager (CTRL+SHIFT+ESC) Start the "Windows Modules Installer" service from Windows services (Start->Run->services.msc) Try again, either using the command or the SBO Reports Preparation tool.

Issue When importing an XIF into SmartStruxure, errors can be generated that vary in nature. Product Line EcoStruxure Building Operation Environment SmartStruxure Enterprise Server SmartStruxure Automation Server Building Operation Workstation Cause The XIF does not import successfully for a variety of possible reasons: There exists a device template in the server already that contains the same device ID as the XIF that is being imported.  The XIF does not comply with the LonMark Device Interface File Reference Guide published by LonMark. Resolution Before performing any of the steps below: Import the XIF file provided by the manufacturer of the Lon controller - if the manufacturer did not provide a XIF, try searching the LonMark product catalog If the provided XIF does not work, upload the XIF from the device to ensure that it is the correct file by following How to extract an XIF out of a Lon controller. Use the SBO SNVT Support tool found on The Exchange to identify unsupported SNVT's. Work through the troubleshooting steps below.   Device Template Fails without an Error This issue has been seen in some of the older versions of SmartStruxure (1.5 and older) and upgrading to the latest version will resolve the issue in many cases. If the issue occurs at the latest version of SmartStruxure: Use the SBO SNVT Support tool located on The Exchange to identify unsupported SNVTs. If the SBO SNVT Support tool does not identify any unsupported SNVTs, then send the XIF in to Product Support for further investigation.    Device Template Already Exists In order to complete the import of the XIF, follow these steps. Delete all controllers in that database that are using the device template that has the same device ID as the XIF file you are trying to import.  Now import the XIF again. Select the server in the system tree on the left and go to File > LonWorks import > Device Template. Click the Browse button and select the XIF you want to import. Click Import. Note: When the import is complete it will have overridden the old device template with that device ID. Two device templates with the same device ID will not be able to reside in the same database. For more information about device templates see Delete Device Templates.   Detailed Error Prompt with Specific Fields Listed Some examples of the detailed errors include but are not limited too: "Field X has error(s). The string must between X and X characters. nvoActualCapacity has X characters" on row X. "Field X has error(s). The number must between X and X. Field X has value X." on row X. "Field X has error(s). The value must be X but was X." on row X. Space or tab are not allowed in field 0Node Object on row X.   To Address these issues: Download Notepad++ to be able to better navigate the XIF by row number. Using Notepad++, open the XIF. NOTE: Backup the original XIF just in case there is a mistake when modifying. Find the row and field number prompted by the error messages and modify them accordingly. All the rules can be found in LonMark Device Interface File Reference Guide published by LonMark. Import the XIF again to verify whether it works. If not, contact Product Support for further investigation.

Issue 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 When discovering the SLP Series Living Space Sensors they show up in the BACnet discovery summary as Non-conformant. Attempting to add this non-conformant sensor results in a WorkStation error similar to the following:  Validation Error Workstation Error in "~/BACnet Interface/MSTP Network/Living Space Room Unit 4E5932F5_«1»_07/ForeignAddress". Property value "<device, 10000>" already assigned to "~/BACnet Interface/MSTP Network/SLPSTC2/ForeignAddress". COML Validator0 Product Line EcoStruxure Building Operation Environment BACnet MSTP Living Space SLP Series Air Quality Sensors Living_Space_REV2.05.21 Cause Building Operation does not allow duplicate BACnet IDs and hence, during discovery, if a device is found with a BACnet ID (Object Identifier) the same as an existing device it shows as a non-conforming BACNet device. The default device ID for SLP devices should be equal to (Vendor ID * 1000) + MAC Address. Where vendor ID is our Schneider Electric BACnet vendor ID = 10 and the MAC address is unique to each devices MAC address DIP switch setting. This will be corrected in a future release of the Living Space firmware.  Until corrected, and since the Device ID is a read/write attribute the customer is able to change it to avoid duplicates on the bus. Unfortunately, Building Operation does not currently have a method to write a new device ID. Resolution The current workaround is to use a third-party BACnet Explorer such as Yet Another BACnet Explorer (YABE) to write a new device ID value. Once the new ID has been updated the SLP device can then be rediscovered within Building Operations'. 

Issue Unable to find details on all commands that have been added to Security Expert objects to implement new functionality. Having this information available would help determine feature set possibilities. Product Line Security Expert Environment Security Expert Client, SP-C Cause Commands used in objects such as Controllers, Doors, and Access Levels may not be documented in the online help, installation, or operation manuals as they are being used to implement new functionality that has not been added to the Security Expert yet. There is no stand-alone list of all available Commands. Resolution Commands are listed in the firmware Release Notes and defined further in Application Notes.

Issue Controller loses data following power failure or mains noise (from transients or spikes). Product Line Andover Continuum Environment All CX, ACX, i2, bCX, b3 controllers Cause Controllers are exposed to operating conditions outside their operating envelope and tested limits. This can cause them to reset, go offline or lose data. In extreme circumstances, poor installation can take controllers outside their operating envelope and cause damage requiring a repair. Resolution If a controller is setup on a bench with a clean power supply and the correct grounding, you will be able to turn off/ on the power and the controller will warm start every time. This test will confirm the controller is operating correctly, not faulty and that the software settings are correctly set for warm starting. Also that the RAM backup battery is connected and operating. If site resets, lockups, loss of memory or other corruption are seen on a site, then here are some of the installation issues to consider: Grounding - All controllers require a clean low impedance earth to sink all of the noise and emission energy a controller may be exposed to. The noise protection circuitry within a controller is designed to dissipate this energy down to earth, if this path is not low impedance the energy can cause a controller to reset or even be damaged permanently. Shared Ground - The earth cable to the Controller should not be shared with any other equipment that is a high inductive or capacitive load, these can generate noise spikes back into the controller. This includes motors (pumps/ fans etc) lighting circuits (capacitive loads), inverters (high frequency noise). Induced emissions - The controller should not be installed near any equipment that may induce excessive radiated emissions into the unit, the radiated emissions from Motors, inverters, radio & microwave equipment, lighting circuits, power wiring can all produce radiated emissions that could exceed the specified limits of the Controllers. By fitting the controllers into earthed metal enclosures you can minimize the external emissions by effectively creating a Faraday cage protecting the controllers circuitry. Power feed - The power requirements for every controller is defined in its datasheet with the defined tolerance, taking the power levels outside these limits can cause incorrect operation. Power spikes - Surges or spikes in power feeds or connection I/O cabling can cause controllers to reset, lose data or even become damaged. Fitting varistors to the power supplies and across any output loads can minimize the impact on the controller, See What Varistors should be used?. Shared Supply - The power feed to a controller should never be shared with other equipment that can generate electrical noise. Never use the same supply to power both controllers and field equipment like valve/ damper actuators in BMS systems or magnetic door locks in Access control, both actuators and the solenoids in Mag locks can generate large back EMF pulses into the controllers that can cause resets or even damage.. Fitting power filters or an external UPS on the controller can protect it from spikes on power up/ down, it is however always best to remove the noise spikes at source, so fit filters the generators, motors, contactors etc. It is also possible for the above issues to cause Infinet networks to Reconfig as well as other networking problems. Note: All controllers are approved and tested to the defined limits for FCC and CE induced and radiated emissions as detailed in the datasheets, for a controller to fail, restart or lose data it must be exposed to levels exceeding these specifications. They are not however power equipment and cannot be exposed to the noise levels power and industrial controls equipment is designed to withstand.

Issue Security Expert is denying user entry to a door and generating an event message stating waiting for Bio Mode Card Input Credentials.  Biometric credentials are not being used for the door. Product Line EcoStruxure Security Expert Environment Security Expert Client Cause Custom credential settings are not correctly configured for the door and reader.  The door is set to use a Door Type expecting a Custom Credential but the Reader is configured to use a standard card format.   Resolution To fix the issue the Reader must also be configured to use a Custom Credential.  Navigate to Reader Expanders and select the associated Reader Expander. For the Reader set the Reader(x) Format to Custom Credential as expected in the Door Type Right click the Reader Expander, select Update Module, and after a successful update test the operation.

Issue When using the 20k (Honeywell) thermistor type on an EcoStruxure IO Module, the temperature value does not change and reads an inaccurate value. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server IO Module Cause The 20k (Honeywell) thermistor type does not work properly in Automation Server IO module firmware versions 2.009 and older. Resolution Check and upgrade the Automation Server IO module firmware to the latest version. Follow the steps below: Select the module in the System Tree (1) and on the Properties tab (2) check the Firmware version (3) If the firmware requires upgrading the latest version can be downloaded from The Exchange Download Centre.  For instructions on how to upgrade the firmware see Upgrading Automation Server IO Module Firmware.