Building Automation Knowledge Base

Issue Workstation Device Node ID and BACnet Device ID settings Product Line Andover Continuum Environment Workstation BACnet devices Cause Require information on configuring the workstation Device Node ID and Bacnet Device ID Resolution When setting up a workstation two of the parameters to set are the Network ID and the Device Node ID.  The Device Node ID corresponds to the BACnet Device ID or BACnet Instance ID in the BACnet protocol. Essentially the workstation is a BACnet device and when setting the Device Node ID during setup in a BACnet installation, consideration should be taken into account when setting this number. By default Schneider BACnet controllers use their serial number as the BACnet Device ID but when using 3rd party BACnet controllers, some vendors use different means when setting their BACnet Device ID. In the past instances have been observed where the workstations Device Node ID is set to 1.   If the 3rd parties BACnet Device ID is set to 1 as well, that device will not be found when using find new BACnet devices. A method of avoiding this is to reserve 191 to 254 for creation of the workstations and set the Device Node ID to the same as the Network ID in the Database Initialization workstation configuration. Or set the workstations with the Device Node ID's starting with 1, but be aware of this setting when configuring any 3rd party BACnet devices.  The Device Node ID/BACnet Device ID must be unique within the BACnet network.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Need to setup SAML SSO with Azure EntraID Product Line EcoStruxure Building Operation Environment Building Operation Workstation Azure Cause The SAML configuration requires details setup Resolution Part 1: EBO configuration Creating and Configuring the SAML Configuration Object To create and configure a SAML configuration object. In WorkStation, in the System Tree pane, expand the System folder. Expand the Federated Authentication folder. Select the SAML Authenticator object. On the File menu, click New object. Select SAML Configuration. Enter a name, path, and description on the object you want to create. Click Create. Configure the settings. Enabling Federated Authentication To enable federated authentication In WorkStation, in the System Tree pane, select the EcoStruxure BMS server you want to configure. Click the Control Panel tab. Click Security Settings. Select Enable federated authentication. Click the Save button. Configure SAML Configuration object Service Provider To configure the service provider. In WorkStation, in the System Tree pane, click the SAML Configuration object. Click the Service Provider Settings tab. Configure the settings. Identity Provider To configure the identity provider. In WorkStation, in the System Tree panel, click the SAML Configuration object. Click the Identity Provider Settings tab. Configure the settings. Configuring the Security To configure the security. In WorkStation, in the System Tree pane, click the SAML Configuration object. Click the Security Settings tab. Configure the settings. Create and configure domains Create and configure a domain to be used for Federated Authentication. Create a Domains Create a group Configure the permission for the group Part 2: Azure Configuration Login to https://azure.microsoft.com/ Create SAML application under Entra ID Click Microsoft Entra ID Click Enterprise Application Select Create your down application Enter the name of the App Select “Integrate any other application you don’t find in the gallery (Non-gallery)” An Enterprise Application is created with the name Create a group Select Groups Click New Group Select “Microsoft 365” for the Group type Enter the name of the group, the “Group name” must match the Domains Groups name in EBO. Add Owners and Members to the group Configure Entra ID Select Assign users and groups in the Enterprise Application Overview Select Add user/group then click Assign The selected group is under the application Select Set up single sign on in the Enterprise Application Overview Under Basic SAML configuration Enter the information from EBO SAML Authenticator Basic Tab The Sign on URL is Base URL The Identifier is Entity ID The Reply URL is AAssertion Consumer Service URL Click on Edit from Attributes & Claims Click on “Add a group claim” Select Groups assigned to the application Select Cloud-only group display names under Source attribute update the “Unique User Identifier” Value to user.displayname Download the “Federation Metadata XML” certificate Open the XML file and find the line with certificate, it will start with <XXXXCertificate> Copy the string between the two brackets and paste it in Public key certificate under Identity Provider Settings Copy the Entity id and Single Sign On Service URL from Azure to EBO. The Entity Id is Microsoft Entra Identifier. The Single Sign On Service URL is Login URL. Part 3: Testing Test Single Sign On Go to Webstation by entering the SmartX Server network address. Click on Log on with SSO Select the account within the Azure Group Successful login screen

Issue What is Alarm decoration in EBO (EcoStruxure Building Operation) and how is it set up? Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Cause Alarm decoration is used when you wish to change the alarm configuration or appearance in the alarm list for a specific alarm or a group of alarms if it meets certain conditions specified when setting up the alarm decoration. If any alarm in the system meets the conditions specified when setting up the alarm decoration the alarm will be displayed in the alarm list as specified in the alarm decoration rule. Examples of alarm specifications that can be changed by an alarm decoration rule are: Alarm text message Alarm priority Auto hide Background color Resolution See the video below: The video will show how to: Create an Alarm decoration Set up an Alarm decoration filter with the conditions: -Alarm text: *offline* -Priority: 20 Set up Alarm decoration presentation with the specifications: -Priority: 300 -Auto hide: Yes After the Alarm decoration is set up any alarm in the system where "offline" is part of the alarm text and having priority 20 will be auto hidden and given the priority 300.  

  Issue No more equation characters can be entered into a Function Block application Product Line EcoStruxure Buildings Operation Environment Buildings Operation WorkStation Buildings Operations Function Block Editor Cause You have exceeded the maximum number of characters allowed in a Function Block expression editor.   Resolution Expression text must have less than 500 characters. Split larger equations into two Function Blocks if needed. How to add an Expression Block  Expression Blocks 

Issue Satchwell VZF 2-Port Flanged Valve Body requires replacement. Environment Satchwell 2-Port Plug and Seat Flanged Valve Body VZF1727                                VZF 1727 VZF1777                                VZF 1777 VZF1852                                VZF 1852 VZF1902                                VZF 1902 VZF1954                                VZF 1954 Cause Obsolescence of Satchwell VZF 2-Port Flanged Valve Body Resolution A number of alternative S-E 2-Port Flanged Valve Bodies are available to replace existing Satchwell VZF 2-Port Flanged Valve Bodies. Suggestion 1 Replace Satchwell VZF 2-Port Flanged Valve Body with S-E VG221F 2-Port Flanged Valve Body of appropriate size N.B. Existing Satchwell Actuator installed on VZF 2-Port Flanged Valve Body may be retained for installation on replacement S-E 2-Port Flanged Valve Body.  In such instances a S-E L9TVG Linkage Kit will additionally be required.  Alternatively an Actuator from the S-E range of Actuators may be installed on the VG221F 2-Port Flanged Valve Body, in which case no additional Linkage Kit will be required. Suggestion 2 Replace Satchwell VZF 2-Port Flanged Valve Body with S-E V222 2-Port Flanged Valve Body of appropriate size N.B. Existing Satchwell Actuator installed on VZF 2-Port Flanged Valve Body may be retained for installation on replacement S-E 2-Port Flanged Valve Body.  In such instances a S-E L8TV Linkage Kit will additionally be required.  Alternatively an Actuator from the S-E range of Actuators may be installed on the V222 2-Port Flanged Valve Body, in which case no additional Linkage Kit will be required. IMPORTANT NOTE It should also be noted that the face to face dimensions both of the S-E VG221F and V222 2-Port Flanged Valve Bodies differ to that of the Satchwell VZF 2-port Flanged Valve Body  Similarly, the centre line to bottom of third port dimensions both of the S-E VG221F and V222 2-Port Flanged Valve Bodies differ to that of the Satchwell VZF 2port Flanged Valve Body  As a result alterations to the pipework connected to the VZF 2-port Flanged Valve Body will be required. Details of the Satchwell VZF 2-port Flanged Valve Body may be viewed here. Details of the S-E VG221F 2 port Flanged Valve Body may be viewed here. Details of the S-E V222 2-port Flanged Valve Body may be viewed here. Details of the S-E L9TVG Linkage Kit may be viewed here. Details of the S-E L8TV Linkage Kit may be viewed here.

Issue How to get data from Rayleigh Instruments RI-78-80-C kWh power meters Product Line EcoStruxure Building Operation Environment Modbus RTU Interface Automation Server Continuum X-driver Cause The Rayleigh Instruments RI-78-80-C has a single 48bit Modbus RTU word available to be read (kWh) It does not respond with an exception when an incorrect register is requested (or a single 16bit part of the 48bit word requested) Only half of each 16bit registers within the 48bit word is used Thus Register address 0, 1 and 2 can have a value 0-255 (00 00 to 00 FF) only The value are actually in 1/100 kWh Reg2 0 to 255 (255 = 255/100 kWh)Reg1 0 to 255 (255 = 255 x 256/100 kWh)Reg0 0 to 255 (255 = 255 x 256 x 256/100 kWh) So if Reg0 = 3, Reg1 =167 and Reg2 = 59Then the reading would be(3 x 256 x 256 / 100) + (167 x 256 / 100) + (59/100)= 2394.19 kWh The value is in 1/100 kWh Reg2 0 to 255 (255 = 255/100 kWh) Reg1 0 to 255 (255 = 255 x 256/100 kWh) Reg0 0 to 255 (255 = 255 x 256 x 256/100 kWh) Example So if Reg0 = 3, Reg1 =167 and Reg2 = 59 Then the reading would be(3 x 256 x 256 / 100) + (167 x 256 / 100) + (59/100) = 2394.19 kWh   Resolution To read the three registers, Modbus Register Groups must be used within SmartStruxure, this ensure a single read is done for the 3 registers comprising the 48bit value. Then a program can be used to calculate the actual meter value. This device will not appear as online in SmartStruxure as the Device Online mechanism requires a response from a 16bit register read (this device does not respond with an exception when an incorrect register is requested and has no 16bit registers to read)   Download an example of Modbus Objects and Script. The below example script could also be atapted for Continuum Plain English Program Numeric Input ModReg0, ModReg1, ModReg2 Numeric Output kWReading Line Calc1 kWReading = ((256*256*ModReg0) + (256*ModReg1) + ModReg2)/100 Note This device may not operate correctly in v2.0 and v3.0 due to a change in the method of offline detection, but this is fixed in v3.1 Numeric Output kWReading   Line Calc1 kWReading = ((256*256*ModReg0) + (256*ModReg1) + ModReg2)/100

Issue How to connect and configure current inputs to a UI module? Product Line EcoStruxure Building Operation Environment Building Operation I/O Module 16 Ch UI (UI-16) Building Operation I/O Module 8 Ch UI/4 Ch DO (Form C) (UI8-DO-FC-4) Building Operation I/O Module 8 Ch UI/4 Ch AO (UI8-AO-4, UI-8/AO-V-4) Building Operation MP-C, MP-V, RP-C, IP-IO Cause How are Current inputs connected and configured? Resolution To connect and configure a current input to a SmartX device no additional external resistors are required, the internal resistor in the SmartX device is automatically put into the circuit by selecting "Current Input" when creating the input object, there are no DIP switches to change as in some other products. An external Power supply will be required to provide the current in the circuit through the sensor and into the UI input. 24V DC supplies are usually used to power the sensor & provide the current drive. Further information regarding the SmartX device's internal resistor can be found in the Hardware Reference Guide. Example Circuit: The input point configuration allows you to define the top and bottom or the current scale (usually 4-20mA or 0-20mA) and the engineering units this corresponds to i.e. 0-100% or 0 - 400 DegC. The following screen shot example shows the configuration for a 4-20mA input signal represented as 0-100%

Issue There is an error message on the LCD display of the old style Infinet controllers. What do these errors mean? Product Line Andover Continuum Environment Infinet Controller Cause Information on the error code received on the LCD display. Resolution Infinet controller is displaying error 1 on its LCD display. This message indicates that the controller received a bad packet of data on the Infinet. If the problem persists follow troubleshooting instructions. Verify Infinet cable connections, approved twisted shielded pair cable, less than 4000 feet of network cable between Infilink repeaters, no more than 31 controllers between Infilink repeaters. Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller. Check the baud rate switch on the Infilink repeater module, although the Infinet controllers auto baud, the Infilink baud rate must be manually switched. Break down the network in segments to identify the bad controller or network segment. A binary search is recommended. (i.e. break the network in half, if this resolves the problem add half of the deleted back on, if it does not resolve the problem cut the remaining network in half, etc.). Once the offending segment has been identified, troubleshoot to the cable segment or controller level Infinet controller is displaying error 2 on its LCD display. This message means that it could not pass a token to another controller on the Infinet. If the problem persists follow troubleshooting instructions. (No response to the Infinet token pass) Verify Infinet cable connections, approved twisted shielded pair cable, less than 4000 feet of network cable between Infilink repeaters, no more than 31 controllers between Infilink repeaters. Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller. Check the baud rate switch on the Infilink repeater module, although the Infinet controllers auto baud, the Infilink baud rate must be manually switched. Break down the network in segments to identify the bad controller or network segment. A binary search is recommended. (i.e. break the network in half, if this resolves the problem add half of the deleted back on, if it does not resolve the problem cut the remaining network in half, etc.). Once the offending segment has been identified, troubleshoot to the cable segment or controller level Infinet controller is displaying an error 3 on its LCD display. This means that the input reference voltage is out of range on the analog inputs. Verify that inputs coming from external transducers are not exceeding the voltage input range, either 5 or 10 volts depending on model, if so use a voltage divider on the input. Verify that any input wiring is not run in the same conduit as high voltage cable, or is properly shielded and grounded. If there is voltage getting coupled into the input wiring, separate the input wiring from the interference, or shield the cables. If the interference is being caused by the end device such as an auxiliary contact form an high voltage device, a cap between .01 and 1 microfarads across the input terminal to earth ground may alleviate the problem. Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it. Power down the Infinet controller and restart while connected to network. This will eliminate this unit having a duplicate ID on the network and it will also run the power up diags. Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller. Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it. Infinet controller is displaying an error 4 on its LCD display. This means that the analog output reference voltage is out of range. Verify that inputs coming from external transducers are not exceeding the voltage input range, either 5 or 10 volts depending on model, if so use a voltage divider on the input. Verify that any input wiring is not run in the same conduit as high voltage cable, or is properly shielded and grounded. If there is voltage getting coupled into the input wiring, separate the input wiring from the interference, or shield the cables. If the interference is being caused by the end device such as an auxiliary contact form an high voltage device, a cap between .01 and 1 microfarads across the input terminal to earth ground may alleviate the problem. Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it. Power down the Infinet controller and restart while connected to network. This will eliminate this unit having a duplicate ID on the network and it will also run the power up diags. Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller. Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it. Infinet controller is displaying an error 5 on its LCD display. This indicates the controller underwent a reset of power down and retained memory ( warm start). If there is not reason for this to occur power outages etc., then troubleshoot the problem. Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller. Measure the AC power at the controller, Verify it is within specification (nominal +/- 20%). Typically 24 VAC power that is daisy chained will drop the voltage along the connections leaving the power below the acceptable level even if the transformer is sized correctly. Verify that any outputs that are driving inductive loads such as relays, actuators, or valves, have a varistor across the coil n the field device. Verify that any input wiring is not run in the same conduit as high voltage cable, or is properly shielded and grounded. If there is voltage getting coupled into the input wiring, separate the input wiring from the interference, or shield the cables. If the interference is being caused by the end device such as an auxiliary contact form an high voltage device, a cap between .01 and 1 microfarads across the input terminal to earth ground may alleviate the problem. Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it.

Issue Details on how Modbus IP Multiple Queries and Multiple Query Packets work Product Line EcoStruxure Building Operation Environment Building Operation SmartX Servers Modbus IP Cause Understanding of how the Modbus synchronous and asynchronous transport layers differ. Resolution By default, the Multiple queries is Disabled, this is the synchronous transport layer. To enable the asynchronous transport layer the Multiple queries must be Enabled within the Modbus TCP Network properties as shown below. Setting to "Enabled" allows multiple queries (packets) to be sent to multiple Modbus devices, thus reducing wait times.  It also enables further settings in the Modbus Device properties "Maximum concurrent queries" and "Multi-query packets".   The maximum concurrent queries and multiple-query packets as shown below are configurations for the Modbus asynchronous transport layer. The Maximum concurrent queries setting is only enabled if the "Multiple queries" is enabled in the Network Properties. When enabled, this allows the "concurrent queries" to be sent as a single packet.     Modbus Synchronous Transport Layer Each Modbus query is sent out one after the other. Before sending out the next query the transport layer waits for a specified period for the previous query. Example Poll Sequence Device No. Objects 1 2 2 1 D=Device, Q=Query, R=Reply D1 Q1 Send D1 R1 Receive  D2 Q1 Send D2 R1 Receive  D1 Q2 Send D1 R2 Receive  If it takes 1 second for the device to reply, then this sequence would take 3 seconds. Modbus Asynchronous Transport Layer With the asynchronous transport layer enabled, the queries are transmitted to multiple devices at the same time. The maximum number of queries that are transmitted to that one device is controlled by the “Maximum concurrent queries” setting. The “Multiple-query packet” specifies whether the queries are transmitted in one TCP frame or not. Simple Example Poll Sequence Device No. Objects Multiple-query packet Maximum concurrent queries 1 2 False 1 2 1 False 1 D=Device, Q=Query, R=Reply D1 Q1 Send D2 Q1 Send D1 Q2 Send D1 R1 Receive  D2 R1 Receive  D1 R2 Receive  If it takes 1 second for the device to reply, then this sequence would take 1 second Complex Example Poll Sequence Device No. Objects Multiple-query packet Maximum concurrent queries 1 10 True 5 2 4 False 2 D=Device, Q=Query, R=Reply D1 Q1, Q2, Q3, Q4, Q5 Send D2 Q1 Send D2 Q2 Send D1 R1, R2, R3, R4, R5 Receive  D2 R1 Receive  D2 R2 Receive  D1 Q6, Q7, Q8, Q9, Q10 Send D2 Q3 Send D2 Q4 Send D1 R6, R7, R8, R9, R10 Receive  D2 R1 Receive  D2 R2 Receive  If it takes 1 second for the device to reply, then this sequence would take 2 seconds   NOTES The use of this feature should be avoided before EBO v3.1, there is also a defect in EBO v3.2 that means v3.2.3.5000 should be used (minimum) Some Modbus devices do not support multiple queries or multiple query packets, so the feature should be tested on an individual basis. (Some devices may even go offline until manually reset) This feature will increase the CPU usage on the EBO server. It should be avoided on EBO Servers that are already heavily loaded This feature also has the ability to reduce the system stability, it is usually better to optimize the use of Modbus Register Groups to increase performance

Issue Continuum 1.9x and above will not install correctly on a PC / Laptop that is on a domain, One example: When trying to run the Continuum Database Initialization program the following error message may pop up: You must have local NT administrative privileges to run this application. Environment Windows OS 7 8 10 Continuum 1.9x 2.x Inet SQL 2005 SQL 2008 SQL 2012 Cause Microsoft has introduced the use of a higher level of security in the install of their SQL database software SQL 2005 / SQL 2008 / SQL 2012. When you install Continuum you need to make sure you are logged onto the PC / Laptop as a local administrator, in the case of a lot of a corporate networks, you are most likely logged on as ether a restricted user or a domain administrator, these logons do not have the privileges you need to install an SQL database. Resolution Step by step guide to creating a local administrator user on your PC / Laptop Go to "Start" then "Control Panel" in Windows (Windows 7 and above, top right corner change "view by" to "small icons" this will show all icons) Go to "Administrative Tools" Go to "Computer Management" / "Local Users and Groups" In users, right click on the right panel and add new user Fill in the user name and password, un-tick user must change password Tick password never expires then ok it Now go back into control panel and click on "User Accounts" Click on the name you just created, this will open the properties screen (Windows 7 and above click on "Manage user accounts") Click on "Group Membership" then select others, and highlight administrators (Windows 7 and above double click on name you created, click "group membership" click "other" then in the drop down select "Administrator") Apply this and then ok it. Log off your normal account and log back on as the new user you have just created

Issue When creating an ETL task the "Run Once" option works, but when configured to run as a service, it doesn't work and an error occurs in the error log: 2015-05-22 17:13:59,069 ERROR ETLEngine (TaskName) - Thread ID (119) - Power Monitoring Expert Load Task: Task Power Monitoring Expert Load Task failed System.ApplicationException: Failed to populate the MetaDataSet. ---> System.Data.SqlClient.SqlException: Cannot open database "ION_Data" requested by the login. The login failed. Login failed for user 'NT AUTHORITY\SYSTEM'. Product Line EcoStruxure Building Operation, Other Environment Power Monitoring Expert Energy Expert (formerly Power Manager) ETL Tool Cause When testing the ETL task using "Run Once", the Windows account currently logged in, will be used to access the SQL database. However, when the same Task is then configured to run as a service, the account configured on that Service will be used to access the SQL database instead.  By default that account is the built-in account 'NT AUTHORITY\SYSTEM'.   The Position values for all of the mapped trend logs are set to an unreasonable timestamp. The timestamp is either very old or a date the preceeds the oldest values in the database.  Resolution Changing the Windows system account for the ETL service Either give the system account access to the database, or change the account used to run the service. Correct/Adjust the timestamp values in Positions tab of ETL The timestamps can be changed all at once by setting the Initial value field at the top of the "Positions" window in the ETL tool. 

Issue When being discovered by a 3rd party system what names will be seen? Product Line EcoStruxure Building Operation Environment Enterprise Server (ES) Automation Server (AS-P, AS-B, AS) Cause How is an Enterprise Server or Automation seen by a 3rd party system? Resolution The Enterprise Server (ES) and Automation Server (AS) conform to a specific BACnet Protocol Revision depending on version and firmware and the capabilities of a particular BACnet implementation are described in the Protocol Implementation Conformance Statement (PICS).  The PICS contains, amongst other details, a list of all standard and proprietary object types that are supported.  Please see BACnet Testing Laboratories (BTL) for a Listing of Tested Products.    For each object type supported the PICS describes: any optional properties that are supported which properties can be written-to using BACnet services if the objects can be dynamically created or deleted using BACnet services any restrictions on the range of data values for properties For a third party to discover an ES or AS it needs to be a BACnet Operator Workstation (BOWS).  Please see BACnet Testing Laboratories (BTL) for a list of tested BACnet Operator Workstation (B-OWS) and BACnet Advanced Operator Workstation (B-AWS)   Of the objects types detailed in the PICS the specific BOWS will determine what properties are shown.  An application such as YABE can provide an indication of these properties.  For example with a device the Vendor Name (1), Protocol Revision (2), Object Name (3),  Model Name (4) and Firmware Revision (5) are amongst the properties available. For an object such as an analog point the Object Name (6), Present Value (7) and Object Identifier (8) are examples of what will be seen.    Every BACnet device contains a device object that defines certain device information, including the device object identifier or instance number.  For additional information please see Introduction to BACnet.  

Issue Controller lost power or is new and needs to be reloaded Product Line Andover Continuum  Environment Continuum Cyberstation Cause How to reload a Continuum controller Resolution Steps to reload a Continuum controller Open Continuum Explorer Right-click and select Send to> Controller Open up the distribution window from the system icon tray(lower right-hand side) The distribution window will show controller reload progress and state when the reload is finished The attached documen provides additional information on the controller reload options that are available in the Continuum Explorer Options menu.  

Issue Controller fails to backup to flash. See error message "Unable to backup objects to flash ..." ACCStatusFlash variable should be ACCFlashValid not ACCFlashFailure Product Line Andover Continuum Environment Continuum Controllers NetController 2, bCX9640, bCX4040 Cause A Program or Function in the Controller is corrupt and cannot be compiled or is blank and does not have any Plain English code in it. Resolution Go to the config page (Controller Configuration) Clear database backup Fix up or delete the offending programs Re-attempt to save the database to flash

Issue When the BACnet Interface is created in Container Servers, the automatically generated Device Object ID aka Instance ID can be the same as another Container Server on the same container host. Product Line EcoStruxure Building Operation Environment Building Operation Edge Server Building Operation Enterprise Server for Linux Cause The algorithm used to pick BACnet Interface Device IDs in individual Automation Servers does not work for Container Servers since they share the same ethernet connection,. Resolution Perform tasks to ensure Instance IDs are unique. One can prevent the issue by ensuring uniqueness when adding the BACnet Interface  When adding Interface -> BACnet Interface, do NOT click Create or Create and Edit, but click Edit in Wizard.  Enter the following data BACnet Name Instance ID (ensuring unique ID to the entire BACnet system) Leave Network Type = IP network Network ID (this should be the same network ID as the IP network is attaching)  One can repair the issue and ensure uniqueness after creating the BACnet Interface. Changing the BACnet Device ID in an Automation Server to configure unique ID Repair Hosting a BACnet controller and IO Module  Fixing References in BACnet/IP Controllers 

Issue With the BCX Controller you can use either the Comm 1 or Comm2 port for the Modbus RTU X-Driver or you could use both simultaneously. Product Line Andover Continuum Environment BCX Controller Modbus RTU X-Driver Cause Enable Comm port for X-Driver Resolution Use either Comm port for the Modbus RTU X-Driver as per page 16 of the Modbus RTU user guide. If you use Comm2 you forfeit the Infinet or MSTP port, you must also create the Communications Configuration Point (Function 99) to tell the X-Driver if it should use RS232 or RS485 on Comm2. This point is required because on the BCX Comm 2 the X-Driver needs to tell the BCX to use the RS485 port (if that is what you want to use) not the RS232 port it defaults to in its Operating System. If you did not create the point the driver would default to the RS232 port. RS485 is half duplex so when transmitting data out the RS485 port, the driver needs to turn off the receiver so that it does not receive its own transmission. Also normally RS232 is full duplex and does not have to do this. However be aware that on BCX's Comm2 both the RS232 and RS485 ports are Half duplex, which although does not normally cause issues with Modbus because it is a Master / Slave network where we never get unsolicited data, it could cause an issue on other protocols. You can have X-Driver enabled on either or both ports, and there is nothing to stop you from having 2 Modbus networks, one on Comm1 the other on Comm2. You could even use a RS232 to RS485 converter on Comm1 if necessary (An Infilink200 would work fine). NOTE: The ability to enable 2 comm ports using Xdrivers can be done, but is not recommended by the Xdriver developers nor supported by PSS. The RTU Xdriver is poll on demand. This type of driver can request a lot of data and starve the CPU on the controller which then makes the polling irregular. If 2 ports are being used then there are typically more devices being added and therefore more points increasing the requests and demand on the controller's CPU. Use one program to control the polling on both ports. Two programs attempting to control the polling asynchronously will cause communication issues. The BCX is able to run 2 X-Drivers but will be a little slower than having 2 BCX's. It is really down to the individual project. If it has big networks connected or update speed is critical then split across 2 controllers. If you just have a few devices on each port and the update time is not critical then you would be fine with 1 controller.

Issue MD5B, MD10B, MD20B and MD40B Increase / Decrease Actuator is required to be controlled by means of ON/OFF CONTACT ( S.P.S.T.) Control Device instead of CHANGEOVER CONTACT ( S.P.D.T.) Control Device. Environment MD5B Increase / Decrease Actuator installed on a Damper and wired to a ON/OFF CONTACT ( S.P.S.T.) Control Device. MD10B Increase / Decrease Actuator installed on a Damper or Valve Body and wired to a ON/OFF CONTACT ( S.P.S.T.) Control Device. MD20B Increase / Decrease Actuator installed on a Damper or Valve Body and wired to a ON/OFF CONTACT ( S.P.S.T.) Control Device. MD40B Increase / Decrease Actuator in stalled on a Damper and wired to a ON/OFF CONTACT ( S.P.S.T.) Control Device. Cause MD5B, MD10B, MD20B and MD40B Increase / Decrease Actuator is required to be controlled by means of ON/OFF CONTACT ( S.P.S.T.)Control Device instead of CHANGEOVER CONTACT ( S.P.D.T.) Control Device. Resolution Wire MD5B, as indicated in On/Off control wiring diagrams on Data Sheet shown here. Wire MD10B as indicated in On/Off control wiring diagrams on Data Sheet shown here. Wire MD20B as indicated in On/Off control wiring diagrams on Data Sheet shown here. Wire MD40B as indicated in On/Off control wiring diagram on Data Sheet shown here.

Issue Is the I/A Series R2 software compatible with a specific version of Windows? Product Line TAC IA Series Environment I/A Series (Niagara) R2 software Windows 32-bit operating system Cause Only specific releases of the I/A Series R2 software have been certified compliant with specific versions of the Microsoft Windows software.  Resolution The following chart details the version compatibility between the releases of the I/A Series R2 software and the various 32-bit versions of the Microsoft Windows Operating System software.  NOTE: I/A Series R2 software cannot be installed directly in any 64-bit version of the Microsoft Windows Operating System. Virtual platforms such as VMware Server 2 or Microsoft Virtual Server 2008 are not supported in R2.   R2 522 R2 527 R2 529 R2 532 R2 535 R2Tunnel Clients TunnelAX Clients  VAS 2.50 VAS 3.92                     Windows XP Professional (SP3) (32-bit) Y Y Y Y Y Y Y Y Y Windows XP Professional (SP3) (64-bit) N N N N N N N N N                     Windows Vista Business / Enterprise / Ultimate  (SP2) (32-bit) N Y Y Y Y Y N N N Windows Vista Business / Enterprise / Ultimate  (64-bit) N N N N N N N N N                     Windows Server 2003 Standard  / Enterprise (SP2) (32-bit) Y Y Y Y Y Y N N N Windows Server 2003 Standard  / Enterprise (SP2) (64-bit) N N N N N N N N N Windows Server 2003 R2 Standard  / Enterprise (SP2) (32-bit) Y Y Y Y Y Y N N N Windows Server 2003 R2 Standard  / Enterprise (SP2) (64-bit) N N N N N N N N N                     Windows Server 2008 Standard  / Enterprise (SP2) (32-bit) N N N N N N N N N Windows Server 2008 Standard  / Enterprise (SP2) (64-bit) N N N N N N N N N Windows Server 2008 R2 Standard  / Enterprise (SP2) (32-bit) N N N N N N N N N Windows Server 2008 R2 Standard  / Enterprise (SP2) (64-bit) N N N N N N N N N                      Windows Server 2012 (All Versions 32-bit & 64-bit) N N N N N N N N N  Windows Server 2012 R2 (All Versions 32-bit & 64-bit) N N N N N N N N N                     Windows 7 Professional / Enterprise / Ultimate (32-bit) N N Y* Y* Y* Y* Y* N N Windows 7 Professional / Enterprise / Ultimate (32-bit) (XP-Mode) N N Y* Y* Y* Y* Y N N Windows 7 Professional / Enterprise / Ultimate (64-bit) N N N N N N N N N Windows 7 Professional / Enterprise / Ultimate (64-bit) (XP-Mode) N N Y* Y* Y* Y* N N N                     VMWare Server (all versions) N N N N N N N N N Microsoft Virtual Server (all versions) N N N N N N N N N                     Microsoft SQL Server 2000 Y Y Y Y Y         Microsoft SQL Server 2005 N Y Y Y Y         Microsoft SQL Server 2008 N N N N N         Microsoft SQL Server 2008 R2 N N N N N         * Refer to PA-00163 for Windows 7 Support Info. NOTE: When selecting a computer on which to install the I/A Series R2 software, select one that meets or exceeds the recommended hardware for the selected operating system. For the larger Schneider Electric BMS offering please refer to Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation

Issue  Evaluating Signal Levels on RS-485 Field Bus with an Oscilloscope. Environment Infinet Field Bus MSTP Field Bus Cause Documentation Resolution See  Evaluating Signal Levels on RS-485 Field Bus with an Oscilloscope.pdf

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue How does one get a clean database for the Enterprise Server or Enterprise Central? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Cause Need for clean database either for testing or start from scratch.  Resolution Stop Enterprise Server or Enterprise Central using Software Administrator Go to the location of your database using Windows Explorer. In EBO V3.2 or higher, software administrator has a shortcut button for the databse folder. For this example it is C:/ProgramData/Schneider Electric EcoStruxure/Building Operation 2.0/Enterprise Server/db Delete the following folders if (some might not exist): Configuration, Historical, Persistent, System, UDT Start Enteprise Server or Enterprise Central using Software Administrator, the system will create a new folders and files as needed. Note: Restoring a different database over the current database does not require the clean database state. Using the backup and restore procedure allows you to switch databases.