Notifications

Ask Me About Webinar: Data Center Assets - Modeling, Cooling, and CFD Simulation
Join our 30-minute expert session on July 10, 2025 (9:00 AM & 5:00 PM CET), to explore Digital Twins, cooling simulations, and IT infrastructure modeling. Learn how to boost resiliency and plan power capacity effectively. Register now to secure your spot!

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

Invite a Co-worker

Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Building Automation Knowledge Base

Issue In a TAC Xenta group, there must be one TAC Xenta which is the master, which TAC Xenta device in the group is most suitable to be the master in the group? Product Line TAC Vista Environment TAC Xenta 401 TAC Xenta 301/302 TAC Xenta 281/282 Cause TAC Xenta group master devices have additional communication responsibilities to the Vista Server -- reporting online/offline status of their group members. Resolution During network planning, choose the master device to be the group member with the: least amount of SNVTs least TACNV least amount of I/O modules least memory used least communication least processing load If adding controllers in an ad-hoc manner, the first controller commissioned must be the group Master to enable communication with any other controllers. If the group master is offline, the whole group will be offline. Remember that when a controller is added to a group all controllers in that group need to have the application and parameters downloaded. If the Master Device is changed after the group is set up you will also need to download every controller, Download the new Master first so that as you download the rest of the controllers they will come online after the download.

Issue Is SP-MNR2 compatible with SP-C-WEB and SP-ACX? The documentation only refers to "controller" and not SP-C/SP-C-WEB/SP-ACX specifically. Product Line Security Expert Environment Security Expert Security Purpose COMMS Expander (SP-MNR2) Security Expert WEB Controller (SP-C-WEB) Security Expert ACX PCB Controller (SP-ACX) Security Expert Controller (SP-C) Cause Compatibility information needed to make a correct solution design. Resolution The SP-MNR2 is compatible and will work with both the SP-C-WEB and the SP-ACX, as well as the SP-C, with no issues.

Issue Empty Legacy Code and Error converting PE code seen in Continuum Conversion Tool Many objects shown as "Partially converted" Product Line EcoStruxure Building Operation Environment Continuum Conversion Tool Infinet i2 BACnet B3 PE programs and functions Cause The Continuum dump file converts, but numerous errors are seen as below PE programs and functions are empty in line with the error Empty Legacy Code and Error converting PE code Resolution Create a new Continuum text dump by highlighting the b3 or Infinet controllers only (rather than the Network Controller (bCX, NC2 etc)) and create a text dump. This is achieved by right clicking on the highlighted devices, choosing "Send To" then "Text File...". Use this new text file in the Continuum Conversion Tool. If this converts correctly then there is an issue in the Net Controller configuration. Alternatively check the Net Controller configuration, specifically the "CommPort", in this example; the first 'CommPort' line should not exist and is the problem, once removed, the conversion then proceeds correctly. 'TYPE : DEVICE : NAME : TEMPLATE : DEFAULTMODE : BAUD : ALIAS CommPort : SiteName\ControllerName : 6780 : False : Printer : Baud9600 : CommPort : SiteName\ControllerName : comm1 : False : Infinet : Baud19200 : comm1 CommPort : SiteName\ControllerName : comm16 : False : LON : Baud19200 : comm16 CommPort : SiteName\ControllerName : comm2 : False : NotConfigured : Baud9600 : comm2 CommPort : SiteName\ControllerName : comm3 : False : AutoSet : Baud9600 : comm3 CommPort : SiteName\ControllerName : comm4 : False : NotConfigured : Baud9600 : comm4

Issue Direct Connect to Xenta 527-NPR Product Line TAC INET Environment I/NET Xenta 527 Xenta 527-NPR Cause Newer versions of Xenta 527-NPR with 5.1.0 and 5.1.1 revisions are unable to be directly connected to the system. Resolution Using the FTP connection through IE (Internet Explorer) to connect to the device. Log on using the root username and password Now go to sys/system/hwconfig.cfg Copy out the hwconfig.cfg file and open it with Notepad Modify the part that says serial_A_function="7" and change it to "5" Save this and now copy it back in again. Restart the device Start I/NET and the direct connect through the NPR to the system should be working now. Warning: Reloading the system program (such as performing upgrades) will remove this change.

Issue When attempting to open WorkPlace Tech Editor or Monitor an error is displayed stating: A supported version of Visio must be installed for WorkPlace Tech Editor or Monitor to function properly. Product Line EcoStruxure Building Operation Environment Building Operation Workstation WorkPlace Tech Editor and Monitor Cause This message is displayed if WPTE requests Visio be started and Windows is unable to comply. Resolution Confirm the version of Visio loaded is a supported version. If it is then set Visio.exe and SE.WorkStation.IA.wptEd.exe to "run as administrator" and retry. To set a program to always run as Administrator, locate the executable file then right click it and select properties. From the Compatibility tab check "Run this program as an administrator" and then click OK Find the SE.WorkStation.IA.WptEd.exe for the EBO version being used and perform the same process as in step 2+3. See the path below

Issue Users are finding it difficult to locate the settings for Password Expiry on EBO Accounts Product Line EcoStruxure Building Operation Environment EcoStruxure 1.7.1 and later Cause When the standard Administrators User Group is examined (of which the admin account is a member), the Password Expiry, Change Password and Auto Logoff settings cannot be altered. Everything is greyed out. Even if a new User Group is created, while Passwords Change permissions and Automatic Logoff settings can now be adjusted, the Password Expiry is still not available. Resolution For Password Expiry settings select: Control Panel / Security Settings / Password Policy. All Password options including Password Expiry can be adjusted here and will apply to all users rather than a single User or Group

Issue Care must be taken about the precedence of operators in Plain English programming to achieve expected results. The following PE program was created with the intent of monitoring how long a point has been in alarm and unacknowledged The user intent was to have the program increment ‘TimeInALM’ for every minute the point has been in alarm without an ACK WaitOneMin: IfTS > 59 then Goto CheckALM CheckALM: TimeInALM = TimeInALM + PSS\ACX2.48\Num1 Alarm1 = On and PSS\ACX2.48\Num1 AckTransToOffNorm <> 255 IfTimeInALM > 4 thenGotoAlertGuard ElseGotoWaitOneMin AlertGuard: TimeInALM = 0 GotoWaitOneMin Instead of incrementing as was the intent, ‘TimeInALM’ kept toggling between 0 and 1. Product Line Andover Continuum Environment Continuum Cyberstation Continuum (All CXs) Continuum Plain English Cause The rules of precedence dictate that the + is done first then the AND. So this is what happens: TimeInALM = TimeInALM + PSS\ACX2.48\Num1 Alarm1 = On and PSS\ACX2.48\Num1 AckTransToOffNorm <> 255 We start with TimeInALM = 0 PSS\ACX2.48\Num1 Alarm1 evaluates to 1 and so does PSS\ACX2.48\Num1 AckTransToOffNorm So we have 0+1 = 1 ANDed with 1 = 1 Now TimeInALM = 1, so second pass is 1+1=2 ANDed with 1 = 0 So TimeInALM is now zero and the cycle repeats Resolution Use parentheses to enforce the order of operations. This resolves potential ambiguities. TimeInALM = TimeInALM + (PSS\ACX2.48\Num1 Alarm1 = On and PSS\ACX2.48\Num1 AckTransToOffNorm <> 255) Here is the complete PE Operator Order of Precedence for reference.

Issue How to determine if a controller is capable of Full Duplex and the Link Speed used. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause How to determine if a controller is capable of Full Duplex. Link Speed can also be determined. Resolution Windows Powershell can be used to determine if a controller is capable of Full Duplex. The Link Speed and MAC address can also be identified. Identify the testing PC's network adapter name that will be used to connect to the controller. Using an Ethernet cable, connect directly to the controller's Ethernet port. Set the PC's IP address to one that is on the same subnet (but not to the exact same IP address of the controller). Using Windows Powershell, enter the following command line: Get-NetAdapter | Select-Object -Property Name, FullDuplex, LinkSpeed | where name -eq 'card name' where 'card name' is the name of the adapter as identified in 1. If the controller is capable of Full Duplex, it will be shown along with its LinkSpeed. Note, Full Duplex and Link Speed can only be achieved by the IT equipment the controller is connected to.

Issue Need to re-add firmware package to EBO for SmartX controllers and receive the error "firmware already exists" Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Multi-purpose Controller (MP-C) Building Operation Multi-purpose VAV (MP-V) Building Operation Room Controller (RP-C) - all Building Operation IP-IO Cause Cannot add a firmware package of the same revision if one is already in the firmware list. Resolution Open the Control Panel within WorkStation and select Firmware Management Select the firmware package you want to delete and click the delete button

Issue When doing an "import Trend Logs" in TAC Vista Conversion Tool only HTTPs works and not HTTP. When using HTTP the error message below is shown: "Log on to Building Operation server failed because Failed to access the server, a network error occurred" Product Line EcoStruxure Building Operation Environment TAC Vista Conversion Tool version 3.1.1 Cause This is an issue fixed in TAC Vista Conversion Tool version 3.2. The issue is that the "Import Trend Logs" tab looks at the HTTP/HTTPS settings of the "Convert Database" tab instead of its own. Resolution Use TAC Vista Conversion Tool version 3.2 when available. Workaround: Set the HTTP/HTTPS settings on the first tab(Convert Database) even if "Import of trend logs" is done.

Issue License Administrator shows failed when adding a new license file. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.1.x License Administrator Windows XP Chinese Version Cause The License Administrator can not load the license file correctly that path contains non-English characters. Resolution Move the license file to a new location where the path does not contain non-English characters. (eg. "C:\")

Issue If a user is created in an ES domain, will that user be visible under the AS if the AS is in the same domain? Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause When a user is logging in for the first time to the AS, the AS will ask the ES for the user and password and then save it in the AS, but this will not visible for the user. The next time the user can log in to the AS even if the connection to the ES is broken as the user is now saved in the AS. Resolution Users will not be visible in the AS, only in the ES.

Issue Cannot connect to, and send reports to a monitoring station through a reporting service Product Line Security Expert Environment Security Expert Server Cause Trouble connecting to a central station Resolution All the necessary information for a reporting service should be provided by the monitoring station. These can include the following: Client Code Reporting Protocol Any necessary encryption information IP Address Port Number Phone Number Steps: Ensure all of the information provided by the monitoring station has been entered correctly. Ensure the Service is running. Has the controller downloaded the change? Ensure the Service has been assigned to the appropriate area. This is done in the Programming > Areas > Configuration menu. Ensure the Area's main portion / 24hr portion is armed. Ensure the Inputs that are being monitored have an input type assigned and are in the area. Ensure the Input Type has the correct options selected (e.g. generate alarms) Under Programming > Services > Options, ensure you have selected the checkboxes are selected for what you'd like to report to the monitoring station. Has the IP Port been opened on the controller's network to allow outbound and inbound traffic? Report IP services have some checkboxes in the Options tab that can help diagnose where the issue is. If the message is failing to reach the station, enable these options for troubleshooting. Log Acknowledge Response Log Polling Message Log Message Retries Log Reporting Failure ContactID also has a checkbox that will produce events for each step in the communication process and will indicate where the problem is. If the message is failing to reach the station, enable this option for troubleshooting. Log Modem Events to Event Buffer Important Note Always disable these troubleshooting options when the site is running without service issues as they will fill up the event database very quickly.

Issue When trying to lock the path of a binding point, the path doesn't change. Right clicking on a binding path to lock the path The locked symbol appears (1), but nothing happens to the path (2). 1. The path is unchanged. 2. The lock symbol is displayed When trying to save the changes the locked symbol (1) disappears. Product Line EcoStruxure Building Operation Environment Building Operation Workstation v. 3.0 Cause Lock Path is not converting the relative path to an absolute path hence the save is not working as expected. This works fine in version 2.0 and is fixed in version 3.1. Resolution Upgrade to version 3.1 where this problem is fixed. In version 3.0 the path can be manually updated to the correct locked path before saving. Manually updated binding path to a correct locked path In the example above the path to the Analog Value in the binding point is /Server 1/test/Analog Value Therefore the correct locked path should be ~/test/Analog Value/Value Make sure you have locked the path before saving.

Issue Only one Xenta Server can be installed in Vista on a single Lonworks network. Product Line TAC Vista Environment TAC Vista Lonworks Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause When a Xenta 500/700/913 is installed in Vista as a Xenta Server, it is intended to act as the Lonworks network interface for Vista. By default, the Xenta 500/700 also handles the alarms generated in devices on the Lonworks network. Only one Xenta Server can, therefore, exist on a single Lonworks network. To enforce this, Vista does not allow you to add a Xenta Server to an existing Lonworks network. Resolution Install the first Xenta 500/700/913 device as a Xenta Server. Install any additional Xenta 500/700/913 as Lonworks Devices on the network. As the Xenta Server handles the alarms generated in devices on the Lonworks network, the additional Xenta 500/700s must be prevented from handling alarms. This is done by changing the Alarm Server setting in XBuilder to 'Disabled'. The XBuilder projects for the Xenta 500/700/913 configured as Lonworks Devices cannot be accessed from Vista. In A LNS environment, SNVTS will be able to be seen through Vista workstation but no XBuilder parameters. These XBuilder projects must be treated as standalone and an XBuilder project backup is managed from outside the Vista database. For details on configuring multiple Xenta 500/700/913s in Classic and LNS networks see these manuals: TAC Vista - Classic Networks - Technical Manual TAC Vista - LNS Networks - Technical Manual TAC Xenta Server - TAC Networks - Technical Manual TAC Xenta Server - Gateway - Technical Manual

Issue TC300 Series Networking Digital Fan Coil Thermostat - Modbus Protocol Documentation Product Line Field Devices Environment TC300 Series Digital Fan Coil Thermostats Cause Modbus protocol information is needed in order to perform Modbus integration to the TC300 Series Digital Fan Coil Thermostats. Resolution The TC303 thermostats come with the option of Modbus communication for both 2- and 4-pipe configurations. Modbus is an open, widespread and well established serial communication protocol used within building automation. The support of Modbus communication allows simple integration of the TC303 thermostats to a building management system, using standard Modbus serial communications. The following models provide support for Modbus connectivity: TC303-3A2LM TC303-3A4LM TC303-3A2DLMS TC303-3A4DLMS TC303-3A2DPMS TC303-3A4DPMS The TC303 thermostats communicate as a Modbus RTU slave device over a serial RS-485 connection, allowing for the transfer of real time data. Thermostats manufactured from November 2018 (2018-W44-4)* onward can be configured to communicate at 9600 (default) or 4800 bps. The communication parameters for TC-300 thermostats manufactured prior to this date cannot be adjusted and are fixed as follows: 4800bps Baud Rate 8 Data Bits Odd Parity 1 Stop Bit The actual Modbus address of the thermostat can be set for each individual device on the RS-485 network. The address is defined via the parameter menu on the thermostat itself. The address range available is from 01 to 32 and is defined under menu item 04 of the parameter settings. For full details on this, other parameter setting options available and Modbus communications parameters/registers, please refer to the Installation Instructions. Connection to the RS-485 network is made via dedicated terminals on the back of the thermostat and marked A (+) and B (-). TC300 Series Digital Fan Coil Thermostat Installation Instructions TC300 Series Modulating Fan Coil Thermostat Installation Instructions * Note - The Installation Instructions have not been updated to include the information that thermostats manufactured from November 2018 (2018-W44-4) onward can be configured to communicate at 9600 (default) or 4800 bps.

Issue Preparing LonWorks Configurations for Upgrade You use this procedure when you want to prepare LonWorks configurations for a version 1.5.x upgrade, a version 1.6.x upgrade, or a version 1.8.x upgrade to a final 1.9.X or Higher version. WorkStation ONLY hotfixes are needed to Prepare the LonWorks configuration in order to upgrade to an SBO system 1.9.X or higher. Links to locating hotfixes on Exchange are needed. Product Line EcoStruxure Building Operation Environment SBO Workstation Hotfix Only v1.5.0.17121 SBO Workstation Hotfix Only v1.6.2.1220 SBO Workstation Hotfix Only v1.7.2.11111 Note: AS-P HW.62 required for a LON system with a minimum SBO Software revision at 1.7.2.X Note: For Systems that are running SBO Software Revision 1.8.X please follow TPA-SBO-17-0002.00 -Server with LonWorks devices - Important software update - TPA-SBO-17-0002.00 Cause Difficulties experienced in locating these files on the Exchange. Resolution Prepare LonWorks Systems Running Version 1.5, 1.6, or 1.7. For Systems that are running SBO Software Revision 1.8.X please follow TPA-SBO-17-0002.00 - Server with LonWorks devices - Important software update - TPA-SBO-17-0002.00 SBO Workstation Hotfix v1.5.0.17121 - Contact Country Level PSS SBO Workstation Hotfix v1.6.2.1220 - Contact Country Level PSS SBO Workstation Hotfix v1.7.2.11111- Link To prepare LonWorks configurations for upgrade via the WorkStation Only Hotfix: Bring the system up to the base version within your respective site to SBO V1.5, 1.6.2, or 1.7.2. Then apply the WorkStation Only Hotfix from the list above to your respective version. 1. In WorkStation, in the System Tree pane, select the EcoStruxure BMS server you want to prepare for the upgrade. 2. On the File menu, point to LonWorks and click Pre-upgrade LonWorks configuration. 3. Click Next. 4. Click Finish. NOTE: Any EcoStruxure BMS that is currently at 1.8 or higher can be upgraded directly to 3.1 with one added note, if the system has LON it will need to go through the LonWorks Pre upgrade before you can upgrade to 1.9.X or HIGHER. If you are upgrading from a version that is older than 1.8, read the documentation that describes the upgrading process for the relevant version.

Issue Users login to EBO using Windows Authentication via the Workstation client encounters the error "User account not associated with a group. Contact your administrator". Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server - SXWSWESXX00001 Building Operation Enterprise Central - SXWSWECXX00005 Building Operation Workstation - SXWSWWORK00002 Cause The "Local System account" used to run the "Building Operation Enterprise Server" service does not have sufficient permissions for EBO/Active Directory integration. One function call from EBO to the Active Directory fails when EBO tries to fetch the groups for the user logging in. Resolution The service account used to run the "Building Operation Enterprise Server" service must be able to read the token-groups-global-and-universal (TGGAU) attribute. The IT department or the Active Directory administrator needs to grant this explicit access to the service account by adding the service account to the built-in group in Active Directory called "Windows Authorization Access Group". For more details regarding the TGGAU attribute, see this article from Microsoft Support, Some Applications and APIs Require Access to Authorization Information.

Issue Digital SAT outputs are not available when using the EBO MN-HPFC object Product Line TAC IA Series. Environment I/A Series Network 8000 MN-HPFC Building Operation Automation Server Premium Building Operation Automation Server Cause The standard MN-HPFC device object in EBO cannot be used when the device was previously configured for Satellite Mode used in a Network 8000 system or R2 integration. Resolution Use the MN:MicroNet 2000 Generic object to interface to an MN-HPFC when configured for satellite mode. This object provides a set of generic inputs and outputs that map over to the satellite controller points. See the attached MN-HPFC Reference Manual that details the inputs and outputs starting on page 6-11. DIN6 ( Digital Input 6 ) controls DO1 Sat Cmd DIN7 ( Digital Input 7 ) controls DO2 Sat Cmd DIN8 ( Digital Input 8 ) controls DO3 Sat Cmd

Issue What is spacing for the screw terminal blocks of the SP-MRDM2 2 Door Mini Expander, and what do the terminal blocks look like? Product Line Security Expert Environment Security Expert 2 Door Mini Expander Cause Screw terminal block details needed for ordering spare parts. Resolution The 2 Door Mini Expander uses two different screw terminal blocks. The lower is the normal terminal with 5.08 mm pitch labelled 2EDGK, and the upper is upside down, also 5.08 mm pitch and labelled 2EDGKF. See also data on the manufacturer's website.

To The Top!

Building Automation Knowledge Base

Related Forums

Intelligent Devices Forum

Determining which device should be the Master Device in TAC Xenta Group

SP-MNR2 Compatibility

Empty Legacy Code seen in Continuum Conversion Tool

Direct Connect to Xenta 527-NPR

Attempting to open WorkPlace Tech Editor or Monitor displays a Visio version Error

Adjust Password Expiry on EBO User Accounts

Operator precedence in PE programming

How to find out if a controller is capable of Full Duplex

Removing firmware from SmartX upgrade list

HTTP doesn't work for "Import Trend Logs" in TAC Vista Conversion Tool

Fail to add license file on Non-English Windows system

Possibility to see an ES domain user in an AS

Security Expert Reporting Service not Communicating with the Monitoring Station

Lock path of binding point does not work

Installing multiple Xenta Servers on a Lonworks network.

TC300 Series Networking Digital Fan Coil Thermostat - Modbus Protocol Documentation

Preparing LonWorks Configurations for Upgrade - LonWorks Pre-Upgrade - Links to Workstation Only hotfixes.

Windows Authentication (Active Directory Integration) Login In EBO Failed With Error

Network 8000 MN-HPFC Issues When Used in EBO

SP-MRDM2 2 Door Mini Expander terminal block spacing

Building Automation Knowledge Base

Related Forums

Welcome!