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 Unable to upload the same Lua script to multiple Room Controllers at the same time Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Automation Server Premium SSL SE8000 (all) Cause The alternative method of uploading the script to each of the room controllers using a USB cable Resolution To upload a script to multiple Room Controllers, follow the below steps: (This procedure assumes the BACnet MSTP network is already setup) 1 - Log in to Building Operation Workstation 2 - Right-click on MSTP network and click "Search" 3 - Search for "Lua program 1" or any other Lua program object 4 - Highlight all the Room Controllers that the script will be transferred to then click on the "show/hide property grid" button. 5 - Expand the "Basic" tab and copy the Lua script in the "Description" field then click Save. 6 - The script will be uploaded to each of the Room Controllers one at a time and will be played automatically. Recommendations & Limitations: - Each Lua Program can take up to 460 bytes of text (per script). (Total of 10 Lua programs) - Script must be placed on a single line. Use semicolons ( ; ) as carriage return - Use multiple Lua programs if the 460 bytes limit is exceeded - Encapsulate logic inside the following if statement if the logic is intended to run once: if not init then ---Script logic here init = true end For general information about Lua programming for SE8000 Room Controllers, refer to the following guide: Custom Programming Guide for SE8000 Series Room Controllers - Application Guide

Issue There is only 1 input available, but the end-user wants more than 1 sensor to be connected, where the reading will be averaged. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE8000 Cause The wrong sensor type or incorrect wiring might have been used. Resolution 4 resistive sensors of the same type are required. Depending on scenario, 2 sensors may have to be fitted adjacent to each other, or fit 2 sensors into 1 sensor housing to achieve the correct number of zones to be monitored. For wiring follow the drawing below:

Issue The user is inquiring about wireless communication Protocols that are available for the SE7000 series controllers Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server Cause Unable to find the correct communication Protocols Resolution There are 2 communication options for wireless: BACnet IP or BACnet MSTP. At this time there is no option for LON wireless.

Issue Unable to access SE7000 parameters as shown in the user interface guide. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE7000 Cause Parameters to configure SE7000 are inaccessible Resolution To access SE7600 and SE7300, press and hold the middle key until the thermostat display Pswd set? Y/N. To access SE7200, press and hold the override key until the thermostat display Pswd set 0. For SE7200, use override keys to select parameters and use up or down arrows for configuration. For SE7200, use the middle key to select parameters and use up or down arrows for configuration. For SE7600, use YES and NO keys to select parameters and use up or down arrows for configuration.

Issue Selecting the correct SE7000 Controller Model compatible with the user application Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment • Building Operation Workstation • Building Operation Automation Server • SSL SE7000 Cause There are several different SE7000 series controllers to choose from and it is important to select the correct one for the application Resolution The online selection tool is available SE7000 Room Controller Selection

Issue When converting b3/i2 Tristate outputs to EBO Multistate, care must be taken to convert to the appropriate Multistate OR Multistate Pulsed output type Product Line EcoStruxure Building Operation Environment Continuum b3850 Controller Continuum i2850 Controller Cause Continuum Tristate outputs controlling dampers need to be converted to EBO Multistate pulsed Resolution The tool will convert to Multistate or Multistate Pulsed based on the "Format" property of the Continuum Tristate output. To have the tool convert to Multistate Pulsed, change the 'Format" property of the Continuum output From $### to #.# or another applicable format that does NOT include the "$" This can be done in the dump file that is to be used for the conversion.

Issue Windows System Information may be requested by Technical Support to assist with a reported issue. Product Line All Product Lines Environment Microsoft Windows Operating System Cause Unspecified cause. Resolution Press WINDOWS + R on the keyboard of the Windows system that you wish to obtain the report from. The Windows key is usually located between the CTRL and ALT keys and has a picture of a flag on it. Type Msinfo32.exe and click OK The System Information tool will start. Click on File > Sav When prompted, save the *.nfo file to an accessible location. Email the *.nfo file to your support representative. Note: This application can also be accessed from Start, All Programs, Accessories, System Tools, and System Information. Using this method will open the System Information for XP and Windows 7, 32 and 64-bit computers. Refer to: Description of Microsoft System Information (Msinfo32.exe) Tool

Issue I/A Series R2 station installed on a JACE-645 retrofit board (TRD-RB-645) fails to run with the following errors Product Line TAC IA Series Environment JACE-645 Retrofit Board (TRD-RB-645) I/A Series R2 version 2.301.535.v1 I/A Series G3 version 3.6.406 Cause The R2 station has not been upgraded to R2 version 2.301.535 using the dbadmin command in the Niagara console. There are errors when converting the upgraded XML version of the station to SNS. Resolution Ensure that the R2 station is upgraded as per step 3 on page 4 of the Retrofit Board Niagara R2 Install & Startup Guide before copying the station into the JACE-645 retrofit board.

Issue I/A Series G3 Workbench License Manager build 3.8.37 will not automatically import from the License Server even when the connection to the Internet is active. The result is the display of the Request License dialog box that provides the host ID and email information for Schneider Electric. Product Line TAC IA Series Environment I/A Series G3 Workbench 3.8.37 Cause The issue is related to a setting within the brand.properties file included with the 3.8.37 install. This setting enables or disables the online license server request function within Workbench. The setting was inadvertently set to disabled (false). Resolution The issue can be easily resolved by changing the setting by one of the two methods shown below. Method 1 - Replace existing brand.properties file with an updated version Close Workbench Download the following zip file with the updated brand.properties file > brand.properties Use the Windows Explorer and navigate to the lib directory under the niagara-3.8.37 directory Extract the updated file from the zip and replace the existing brand.properties file Method 2 - Manually edit the brand.properties file Close Workbench Use the Windows Explorer and navigate to the lib directory under the niagara-3.8.37 directory. Open brand.properties using a text editor such as Notepad Carefully edit the following line changing the false to true: license.onlineRequest=false ... update to license.onlineRequest=true Save the file Workbench will now import licenses from the license server.

Issue Unable to add an Automation Server into the Device Administrator via IP. Error seen - Could not logon to server x.x.x.x This can be caused by providing the wrong password or the password has expired on the server. If the password has expired, log on to the server using WorkStation and change the password. Product Line EcoStruxure Building Operation Environment Building Operation Device Administrator Building Operation Workstation Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Automation Server Cause Failed attempts of connecting to an AS-P, AS-B, or any IP controller with device admin will trigger the EBO security feature of SSH console lockout. This security feature defaults to 15 minutes and since the device admin uses SSH for communication, it will not allow the connection to an automation server while in this lockout state. Resolution If a site is experiencing communication issues, then the SSH console lockout could be going into effect before a good connection is established. Reducing the SSH console lockout time period will allow for a connection to be made sooner without waiting out the default setting of 15 minutes. Use Workstation to log in to the server experiencing the issue. Go to Control Panel. Click on "Security settings" under the Security and Communication title. Locate the "SSH Console Lockout" configuration setting and adjust the lockout time to a shorter duration such as 1 second. Click Save. Open Device Administrator and add the Automation Server using IP.

Issue The OrOr object in MNB controllers always reports that it is "ON". Product Line TAC IA Series Environment I/A Series WorkPlace Tech I/A Series MNB Controllers Cause Input to the OrOr object is inverted and has nothing attached to it. When an "OR" input property of a logic object is inverted with nothing attached to it, the input will be seen as an "Off," resulting in an output of 100. Resolution If the input of an OrOr object is not connected to I/A Series BACnet controller, an "OR" input should not be inverted. If another object outputting a "NA" is attached, the "OR" input will function correctly.

Issue What hardware is required to connect directly to a BACnet/MSTP trunk containing just MNB controllers? Product Line TAC IA Series Environment I/A Series WorkPlace Tech I/A Series WorkPlace Tech Commissioning Tool I/A Series WorkPlace Tech Balance Tool Cause Replacement for the previously recommended adaptor, the B&B Electronics model USOPTL4. Resolution Purchase the following part: MNB-ROAM-IA. This is used in conjunction with WorkPlace Tech.

Issue As of EBO 4.0.1.86 it is not possible to bind to the "Restart" property of a b3/Infinet Script program Product Line EcoStruxure Building Operation Environment Building Operation - Continuum Interface Cause Unable to bind directly to the "Restart" property of b3 or Infinet Script program. Resolution While the issue may be resolved in a future version of EBO there is a simple workaround. The workaround consists of binding via an intermediate value object. EXAMPLE: A b3/i2 program (MasterProg) needs to run a second b3/i2 program (SlaveProg). Create a digital value in the device (ProgReStart), Instead of binding in MasterProg directly to the Restart property of SlaveProg, bind to the value of digital value ProgReStart, then bind the value of ProgReStart to the Restart property of SlaveProg. Here are the resulting bindings for the intermediate value object (ProgReStart) The sequence will then be as follows: 1. When MasterProg needs to run SlaveProg, it sets its output binding (bound to the value of ProgReStart) to 1. 2. Upon a change in its value from 0 to 1, ProgReStart will then set the Restart property of SlaveProg to 1 causing it to run. NOTES 1. Do not use Active/Inactive, it won't work, must use 1/0 instead. 2. MasterProg will need to reset ProgReStart to 0 before running SlaveProg a second time

Issue What actions should be taken if the alarm "Missing response from server" appears in the Enterprise Server? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 2.0 and later versions Cause ES/EC is waiting for a response from another server(most likely AS/AS-P/AS-B) for more than 120 minutes. Might lead to deadlock and starvation of resources. Can potentially replicate through the system and affect other servers. Examples of problems that could occur are: Values in graphics that reside in a sub server (most likely AS/AS-P or AS-B) are not updating. Not possible to login to ES/EC Resolution Acknowledge the alarm "Missing response from Server" If not triggered again after 15 minutes then it is not a problem anymore (or at least less likely) If triggered, then continue below In the Alarm view, locate which server the alarm "Missing response from Server" comes from and log in directly to that server. Is the server responding? If not, restart the server. If it is responding, unplug the network cable to the server for a few minutes. Plugin the cable again and acknowledge the alarm. If it triggers again after 15 minutes, then Take 2 core dumps on the server (for investigation of why this problem occurred). Contact your local Product Support contact for instructions on how to do that. Restart the server (should fix the problem)

Warning Potential for Damage/Loss: The steps detailed in the resolution of this article may result in a loss or damage of data/hardware 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 your local support for assistance. The self manufacture of this product precludes any warranty or liability to Schneider Electric. Issue HHC-USB-IF replacement cable for I/NET Hardware is no longer available, can we make or get details of how to manufacture this cable. Product Line TAC INET Environment I/NET Hardware Hand-Held Console Cause The product is no longer available. Resolution Details of how to manufacture this cable including components are shown in the HHC-USB-IF-331180rA.pdf.

To The Top!

Building Automation Knowledge Base

Related Forums

Intelligent Devices Forum

Bulk Lua4RC upload via BACnet (Mass upload)

SE7000/SE8000 Series Room Controllers COV and Effective Occupancy

SE7000 series room controllers local displays language settings

More than 1 temperature sensor is required to be wired on Single input - series parallel

SE7000 wireless protocol options

Unable to access SE7000 series parameters

Selecting the correct SE7000 controller

Converting Continuum b3/i2 Tristate outputs to EBO Multistate outputs

How to create a Windows System Information report (Msinfo32.exe)

AutoCAD wiring symbols for I/A Series MicroNet LON controllers (MNL)

I/A Series R2 station installed on a JACE-645 retrofit board (TRD-RB-645) fails to run

I/A Series G3 Workbench License Manager build 3.8.37 will not automatically import from the License Server

I/A Series Micronet LON controllers (MNL) SNVTs list

I/A Series R2 oBIX User Guide

Device Administrator fails to connect over IP

The OrOr object in MNB controllers always reports that it is "ON".

Connecting directly to a BACnet/MSTP trunk containing just MNB controllers

How to start b3/Infinet program from another b3/Infinet program

Actions to take when the alarm "Missing response from server" appears in ES

HHC-USB-IF

Building Automation Knowledge Base

Related Forums

This is a heading