Building Automation Knowledge Base

Issue Where are example Plain English programs and functions stored for typical BMS applications? Product Line Andover Continuum Environment Plain English (PE) Functions and programs. ACSM, PID, Optimiser, ISM, First Aid. Standards Bacnet Optimiser Cause It is always easier to write your Plain English programs starting from documented examples rather than a blank page. What is available? Resolution The following link is to a .zip file containing various BMS standard modules originally developed by the UK Application engineers for Infinity SX8000 and were known as the Infinity Standard Modules (ISM's), they were then updated to Andover Controls Standard Modules (ACSM's) for Continuum. These modules are example functions or building blocks that can by used globally by application engineers to provide the control and monitoring appropriate for your own buildings. Link: Click here. In addition to these functions other examples are in the online help for the corresponding Plain English keywords, and other applications can be found on the Forums; see Sample PE functions and programs for further details. For Smart Sensor examples see Example programs for Smart Sensors TTS-SD-LCD-1 and TTS-SD-LED-1 for details. For example Security programs see the Download Center link, Click Here.

Issue No official internet download available unless you have user name and password access to Schneider Electric websites. Product Line Satchwell MicroNet Environment VisiSat Engineering Guide  Installation and User Guide 1.2 2.1  Cause Not available for download online Resolution Further information regarding this object can be found in the VisiSat help file and engineering guide. VisiSat V1.2 Engineering Guide This document provides details for IAC 400, IAC 420, IAC 600 and IAC Touchscreen configuration. VisiSat V2.1 (185) Engineering Guide (This document contains details for configuring the MicroNet range of controllers. MN300, MN440, MN500, MN 620, MN350, MN450, MN550, MN 650, MNLCD and MN Touchscreens). VisiSat V2.1 (196) Engineering Guide (This document contains details for configuring the MicroNet range of controllers. MN300, MN440, MN500, MN 620, MN350, MN450, MN550, MN 650, MNLCD and MN Touchscreens). VisiSat V2.1 Installation and User's Guide VisiSat V2.1 data sheet VisiSat V2.1 Release note Related Articles: MicroNet 100 series controller MLi's and Data sheets MicroNet 50 series controller MLi's and Data sheets Where can VisiSat software and license be purchased and what Version/Build is supplied?

Issue While attempting to activate a purchased license, the entitlement ID shows that it is valid, but there is no available licenses that can be activated, or less available than listed on the entitlement certificate. The entitlement ID or certificate is lost. Unable to return the license in order to activate it on another PC Getting "This Operation is not applicable for Trusted Fulfillments" Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Cause In order to activate a SmartStruxure license, it must be available and unused. If a license is already in use, it needs to be returned before it can be activated. Note that all handling of licenses are to be carried out using the License Administrator. Licenses are not returned or rehosted as it was done for TAC Vista. Resolution Refer to WebHelp article #6687 for instructions on how to return a license If you are unable activate a license because you don't have the entitlement ID or certificate, note the activation ID before you return the license, and send that to Product Support Services in order to get the associated entitlement ID Launch the License Administrator Go to the Diagnostics tab and click the refresh icon in the top left corner. The entry in the list that is labeled Entitlement ID is actually the Activation ID. In the case that the computer has crashed or you are unable to successfully return the license on your own, contact Product Support Services providing the following details: A copy of the entitlement certificate The site name An elaborate explanation of why you are not able to return the license yourself

Issue Definition of number of nodes and points allowed using Modbus TCP/IP or RTU xdriver. Product Line Andover Continuum Environment Modbus Protocol Cause Definition of number of nodes and points allowed using Modbus TCP/IP or RTU xdriver according to the modbus protocol. Resolution The maximum number of nodes is 254. The address range for points is 1 through to 65535. The number of addresses is limited by the controller memory. We have had ~6000 points but please note the Modbus is a polled protocol so the more points you have the longer the poll rate.   Specific Modbus RTU Details Our Modbus RTU XDriver supports the node range from 0-255. According to the Modbus specification, the node range is from 0 – 255, with 0 being the master, 1-247 being the slaves, and 248-255 being reserved addresses. After 32 nodes (1 master + 31 slaves), you may need RS-485 repeaters to ensure proper communications. This depends on a number of different items, including if the RS485 transceivers are full or quarter load. You can find the Modbus serial standard at the link below for further details. http://www.modbus.org/docs/Modbus_over_serial_line_V1.pdf

Issue Some BACnet devices advertise support for services such as RPM, COV, etc but malfunction when the service is used. An example of such a device is the Johnson Controls TEC2627VVT which advertises support for RPM but fails to upload its objects when SBO uses RPM to get the object list. Product Line EcoStruxure Building Operation Environment BACnet Automation Server Enterprise Server Cause Some BACnet devices with inconsistent protocol implementation cannot process BACnet services such as RPM, COV, etc. Resolution Feature Supported in Version <no-rpm/> 1.8.1 and higher <no-cov/> 1.8.1.23701 and higher <ignore-unhosted-devices/> 3.2.3.9005 and higher (*)   Users can create a rule under the BACnet interface to configure SBO not to use the service. Some rules are global, while others can be for specific BACnet devices. For particular BACnet devices, they are specified by 'Vendor Identifier' and 'Model Name,' which need to match exactly as shown in that device's Properties - Advanced Tab.   Ensure you have installed the version that supports the feature you want to change. Setup file using the no-rpm rule. Use a text editor like 'Notepad' to create a text file or download the same file below. Enter the device's vendor ID (5)  and model name (TEC2627VVT) followed by the rule (no-rpm) using the format seen in the screenshot below. Save the file to the desired location on the PC with a name aiding later identification. Under the BACnet interface, create a new 'Document' object in the 'Application' folder. NOTE: The object MUST be named 'service_blacklist' in all lowercase. Click 'Next,' import the text file created in step 1, and save the 'Document' object. Restart the Server  Once the device is on the block list, SBO will not send 'readPropertyMultiple' requests to the device using only individual 'readProperty' requests. Add the service_blacklist to the EBO Server. Add the no-cov tag if you would like to block that service for this device:  Extended for multiple devices from different vendors simultaneously using this example for reference.   One can add a global rule using this syntax to ignore unhosted devices. * NOTE: It is recommended to remove <ignore-unhosted-devices/> after upgrading to EBO 4.0/2022 and higher because this feature is supported in the BACnet Interface Properties and BACnet Device Discovery view. Device Discovery for BACnet Controllers and IO Modules (se.com)  Once the Server has restarted, check the trace.log file and search for service_blacklist, there should be entries similar to this. 

Issue Getting modbus devices to communicate to Continuum may require some trial and error. Product Line Andover Continuum Environment Continuum Modbus RTU, ModbusRTU Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Manufacturers of modbus devices may have an offset for their register values and addressing these values requires trial an error. Resolution This article was created as a starting point. There are a lot of tools and methods to get values from modbus devices communicating. This resolution discusses some important concepts as well methods for trying to bring values in. The Modbus RTU protocol is a Master/Slave style of protocol. The Andover Controls CX will be the master on the Modbus RTU network. There can be only one (1) master at a time on the Network. The Slave number is always set in the third party device. This could be either a hardware setting such as dip switches or a software setting. Modbus-IDA (also known as Modbus.org) has set the limit that the slave address can be between 1 and 247. Address 0 is allocated as a broadcast message. The Andover Controls x-driver can support addresses in the range of 0-255. The third party manufacturer should be able to tell you what the expected function codes are for the points that you are interested in. Modbus.org has defined the function codes in a very loose manner and leaves it up to individual interpretation. Andover controls supports the following standard function codes: 1-8 15,16. Since when you request information from a Modbus RTU device you receive the exact value that is in the register Andover Controls has provided some special function codes that will help to convert some of the common engineering values into usable values. The listing in the x-driver documentation shows the special function code, what is expected from the third party and the equivalent function code that is truly sent to the device. For instance if a point is a Intel float and resides in the 40,000 range then function code 245 would be used in the Andover Controls x-driver. This will still send out a function code 3 in the Modbus message but the x-driver will take the value sent in from the third party device and convert it into a usable float. Most confusion occurs when talking about the data registers, (also known as addresses or channels). Modbus.org has the following statements about the addresses in the protocol document. All data addresses in Modbus messages are referenced to zero. The first occurrence of a data item is addressed as item number zero. For example: The coil known as ‘coil 1’ in a programmable controller is addressed as coil 0000 in the data address field of a Modbus message. Coil 127 decimal is addressed as coil 007E hex (126 decimal). Holding register 40001 is addressed as register 0000 in the data address field of the message. The function code field already specifies a ‘holding register’ operation. Therefore the ‘4XXXX’ reference is implicit. Holding register 40108 is addressed as register 006B hex (107 decimal). Register number also known as address. When setting the start channel number parameter on the x-driver tab the x-driver is expecting the exact decimal address that you are looking to obtain. For instance: if a device shows a listing for the first point to occur at 40,001 then the start channel number is typically 0. This can be confusing since some manufacturers have decided to have 40,001 as being 1 and not zero while others manufacturer have decided that 40,001 is 0. There are two ways of determining how the manufacturer has started the numbering system for the device if it is not documented: Method 1 is a trial and error method. Where you set the value to minus 1 of the register address, the actual register address and plus 1 of the register address and see which one you a response from. Method 2 uses a third party software to poll all the points to see what addresses are populated. There are many shareware Modbus RTU software packages on the Web. One such program is called ModScan32 by Win-Tech. www.win-tech.com Number of channels. The least amount of channels that will be requested is 1 so number of channels should always be 1 or greater. If the data is stored in multiple channels then you will need to set the number of channels equal to the number of registers. If you are not using a special function code you will need to set up a separate numeric with a manual log with the number of entries equal to the number of channels. When you poll for the value of the channels the data will then be stored in the manual log of this second numeric. The first element of the log will be the first channel that is requested. For instance if a value is stored in registers 40,000 through 40,003 then the start channel number will be set to 0 and the number of channels would be 4. Another numeric with a manual log of 4 would be created and linked in the x-driver numeric by placing the name of the new numeric in the annex point parameter. Once the x-driver point is polled the returning information will be stored in the annex point. The manual log of the annex point will contain the data for the 40,000 register in location 1. The data for each subsequent register location will be in the next manual log location. I.E. annexpoint[4] will contain the data for register 40,003 The Modbus RTU x-driver is a poll on demand x-driver. What this means to the user is that either a Plain English (PE) program, graphic or editing the x-driver numeric will cause a poll to occur. It is best to mirror the x-driver point and use PE to poll the x-driver points. A simple program would loop through and perform a simple line of mirroredpoint = x-driverpoint. This will avoid multiple polls to the same point tying up more CX resources then necessary. Then you can use the mirrored point in programs and graphics. If you try to get values from a slave device that is offline (not responding) the x-driver will poll each point three times before it moves on to the next point. This will cause the CX scan time to rise to seconds instead of tenths of a second. It is helpful to have a single x-driver point in the third party slave device that will return a known value, (Product ID or serial number for example). This can be used to avoid running the scan time of the CX up if the slave device can not communicate. Inside of the polling program try to poll for the value of this point. If the value does not come back then skip the polling for the rest of the points for this slave device. This point can also be used as an alarm for the offline device as well. For example: 1: If ProductID1 = 15 then Mirroredpoint1 = x-driverpoint1 Goto 2 else Goto 2 endif 2: If ProductID2 = 15 then Mirroredpoint2 = x-driverpoint2 Goto 1 else Goto 1 endif Some data may come back as a value when you need only a bit of information. In this case you will need to use the Bitand operator in PE to extract the exact bit that you are looking for. As seen below the PE code will take an alarm point from a Liebert AC unit and break out the individual bits of information. AC9_Alarm1 = x_ac9alarm1 'setting the mirrored point AC9_CommFail = AC9_Alarm1 bitand 1 'extracting bit 1 AC9_LocalOff = AC9_Alarm1 bitand 2 'extracting bit 2 AC9_RemoteOff = AC9_Alarm1 bitand 4 'extracting bit 3 AC9_HiHeadPrs1 = AC9_Alarm1 bitand 8 'extracting bit 4 AC9_HiHeadPrs2 = AC9_Alarm1 bitand 16 'extracting bit 5 AC9_LossAirFlow = AC9_Alarm1 bitand 32 'extracting bit 6 AC9_StbyGlycolOn = AC9_Alarm1 bitand 64 'extracting bit 7 AC9_LiquidDet = AC9_Alarm1 bitand 128 'extracting bit 8 AC9_ChangeFltr = AC9_Alarm1 bitand 256 'extracting bit 9 AC9_HighTemp = AC9_Alarm1 bitand 512 'extracting bit 10 AC9_LowTemp = AC9_Alarm1 bitand 1024 'extracting bit 11

Issue Remote Factory Reset of SmartX IP controller MPX RPC IPIO Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller (RPC) Building Operation EasyLogic RP-C Building Operation EasyLogic RP-V Building Operation EasyLogic RP IO Expansion Module Building Operation EasyLogic MP-C Cause From v3.1 there is a facility to remotely Factory Reset a SpaceLogic BACnet/IP devices (formerly known as SmartX) and EasyLogic BACnet MS/TP devices. A quick look at the process and what versions of SmartX controller firmware are required Resolution Remote Factory Reset fails if the Controller is at v2.00. Remote Factory Reset operates correctly if the Controller is at v3.00 or higher. A Remote Factory Reset on a Controller with Static IP is best avoided. Although a Factory Reset is now possible, it should not be considered standard work process, but it shows that using DHCP serving of IP addresses does have advantage if a factory reset is required.

Issue A more in-depth description of each of the Direct Digital Control (DDC) modules in I/NET Product Line TAC INET Environment I/NET DDC DCUs, PCUs, MRs Two Position Module (2POS) PID Controller (PID) Float Module (FLT) Reset Module DDC Hi/Lo Module (HI/LO) Relay Module (Single Pole Double Throw Relay) Calc Module Cause DDC is a system that measures a variable, compares the variable with a known value to determine the error, processes the error using a specific software algorithm, and then produces an output to modify the controlled variable. Resolution Most of these modules are discussed in both TCON 083 or  TCON 299 System Operator Guide for more details. (The System Operator Guide is installed by default on your I/NET Host Workstation) DDC Two Position Module (2POS) This module is used where the final control element is in either one state or another opposite state (ON/OFF, OPEN/SHUT). This type of control will commonly be used for simple heating or cooling systems, starting and stopping motors, controlling water sprays for humidification, etc. This module is available in our PCUs and DCUs; and you can customize it for your needs.  DDC PID Controller (PID) In Proportional (P), Proportional + Integral (PI), and Proportional + Integral + Derivative (PID) control, the control element moves linearly to a position that is proportional to the deviation and the rate of deviation of the controlled process variable from a prescribed setpoint. This type of control, in any of its three modes, or combinations thereof, is commonly used for the control of modulating valves, vanes or modulating motors where a proportional output control point is used. The proportional output control point may be either an analog output (voltage, current, resistance) or a pulse width output where the duration of the pulse is proportional to the error variation. This module is available in our PCUs and DCUs; and you can customize it for your needs.  DDC Float Module (FLT) Traditionally, floating control actuates a control device when the error, i.e. the difference between the controlled process variable and the setpoint, exceeds a deadband and maintains the control until the error is within the deadband. The floating controller is based on the same principle however it has been enhanced to include PID control without the requirement for analog output or pulse width position feedback. The output of this controller may be directed toward either a pair of variable pulse width discrete outputs to control a bi-directional drive motor or dual EP value arrangement which is generally described as a "pressure-vent" controller. This type of control is commonly used for the same applications as the PID controller where positive feedback is either unnecessary or economically unsound. This module is available in our PCUs and DCUs; and you can customize it for your needs.  DDC Reset Module (RESET) Reset is used to develop a setpoint output in an inversely or directly proportional relationship to one or two analog inputs and one or two operator-specific reset schedules. This module is available in our PCUs and DCUs; and you can customize it for your needs.  DDC Hi/Lo Module (HI/LO) This module is used to provide the highest and/or lowest value from two or more measured variables, most commonly temperatures. HI/LO can be cascaded to accommodate virtually any number of inputs of similar nature. Typically the lowest space temperature would be the most logical to use to directly reset the heating water setpoint. The HI/LO modules provide the control engineer with a convenient alternative method for making the selection. The HI/LO modules may also be used as an OR/NOR selector by using the state(s) of various monitored discrete points. This module is available in our PCUs and DCUs; and you can customize it for your needs.  DDC Relay Module (Single Pole Double Throw Relay) This module provides a mechanism for selecting one of two values or states based on conditions within the controlled environment. The actions of the relay are controlled by one discrete input and control which of two input states or values is directed to the output. The inputs and output may be either discrete or analog. The actions of this relay are analogous to its electric/electronic counterpart in its simplest form. This module is available in our PCUs and DCUs; and you can customize it for your needs.  DDC Calc Module This module functions similarly to calculations added to a point through the calculation extension editor. This module is only available in Micro Regulators (MR). It is not available in Application Specific Controllers (ASC). 

Issue One of the following error messages are displayed. Internal server error Server already part of a system Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation Server Cause Version Mismatch: The Automation Server is either not the same version as the Enterprise Server or it is still connected to a different Enterprise Server. If the Automation Server is still connected to another Enterprise Server then it must be detached before it can be added underneath a new Enterprise Server. User Permissions: In some instances, the User Permissions "System Address" is not added to the user account that is attempting to add the server.    Resolution If you are given an error that states "Domain: Internal Server Error" then you need to download the same version of firmware to the AS that is installed on the ES. Resolution #1: Detach the Automation Server Log in to the Automation Server.   In the system tree pane, right-click on the automation server and go to Advanced > Detach server.   The Disconnect Automation Server window will open; click yes.   The Automation Server is now detached and can be added to an Enterprise Server. Resolution #2: Verify User Permissions Check a current backup using the SBO xbk Analyzer and verify the number of servers listed under Reports>Servers Log on using the default admin account and see if these servers exist. Detach the server(s), as described above. If the secondary user still requires permission to add and see ALL servers: Go to the user and select the Permissions tab Ensure the ES path is selected Click on the Add System button (identified with the arrow) Enable all options to allow read/write, create etc.  Save these changes and log off and back on with this user to see the changes. This user should now be able to add/see ALL servers.

Issue BACnet proxy points and BACnet devices are configured to use COV subscriptions however points are listed as Polled when added to database. Product Line TAC IA Series Environment Niagara G3 all version, ENC-520, ENC-410 Cause The "Use Cov" property is set to false in the BACnetNetwork Default Tuning Policy. The "Use Cov" property default is "False." If set to "True," and the assigned proxy points are under a BacnetDevice that supports the Subscribe COV service, any necessary updates (Niagara proxy subscriptions) are attempted using BACnet COV subscriptions to the device. If the subscription attempt succeeds, the "Read Status" property of the point's BacnetProxyExt displays "COV." If the subscription attempt for a proxy point fails, normal polling is used and the "Read Status" property shows "Polled." Resolution The "Use Cov" property must be set to true for COV subscription to function. It’s a good idea to create a separate tuning policy for BACnet COV subscriptions. Creating a new Tuning Policy Expand Tuning Policies under the BACnetNetwork Right-clicking an existing policy, then choosing "Duplicate" in the shortcut menu. "Name" it as desired. Open the tuning policy you just created Set "Use Cov" to true and save. Assigning the new tuning policy to the proxy points under the BACnetDevice that is configured for COV subscriptions. Expand the Points folder of the BACnet Device Double-click on the proxy point you wish to configure to use Cov Click on the drop down menu next to Tuning Policy Name and select the tuning policy you created. Save. Configuring the BACnetDevice to use COV Open the BACnetDevice under the BACnetNetwork Set the "Use Cov" property to True. Note: Typically, you create multiple tuning policies in the BACnetNetwork—especially if you have multiple BACnet network ports enabled. This allows you to reference different tuning policies from BACnet proxy points under different networks (often with vastly different performance capabilities). For example, points under a BACnet MSTP network would likely use different tuning policies than those under a BACnet IP network. Reference the "About BACnet Tuning Policies" section of the Niagara AX-3.x BACnet Guide document for additional information.  

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 Both the STAT LED and the BEAT LED is off on the Jace controller and cannot successfully ping the JACE 8000 IP address Product Line TAC IA Series Environment I/A Series JACE 8000 Cause The STAT and BEAT LED remaining in an off state is an indication that no SD card is installed in the JACE card carrier.  When the Micro SD card is installed the STAT LED is solid Green, and BEAT LED is blinking Amber. Resolution Make sure to insert the SD card prior to startup commissioning of the JACE 8000. See JACE-8000 Install and Startup Guide

Issue How can EcoStruxure BMS server serve data to external devices or software? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Third party devices or software Cause The EcoStruxure Building Operation software supports the major communication protocols in building automation and security management. In many projects, it is required that an EcoStruxure BMS server serve data to external devices or software, E.X. HMI, SCADA or power monitoring. Resolution The following is a summary of the available options to serve EcoStruxure BMS server data to the external world: BACnet:  When you create a BACnet Interface, the system automatically creates the Application and IP network folders within the BACnet Interface folder on the System Tree. If you create a BACnet Interface for a SmartX server, you can optionally create an MS/TP network. You can create BACnet objects in BACnet application folder of EcoStruxure BMS servers and these object will be visible for external BACnet clients. More information about EBO BACnet interface: BACnet Interface   Modbus Slave network:  If you configure the Modbus Slave Network (and associate it with a serial port), you can set up any external Modbus master device to communicate with the internal Modbus Interface. In this example, a Modbus Slave Network is set up on an EcoStruxure BMS Server and the external master device is configured with the same Modbus properties as the Modbus Slave Network object. The Modbus master device can also be an HMI device. More information about Modbus serial interface: Modbus Serial Networks Modbus server network: You can create a Modbus TCP Network on an Ethernet network (TCP/IP).  You can create an internal interface which acts as the server to an external client/clients. More information about Modbus TCP interface: Client and Server Networks   MQTT: MQTT is a lightweight and flexible data transfer protocol for IoT resources. EcoStruxure Building Operation, V3.2 or higher, can be configured to send data to an MQTT broker on interval or event-driven. The below are the tested brokers: Microsoft Azure IoT Hub Amazon IoT Core IBM Watson IoT Mosquitto More information about MQTT interface: MQTT Overview LonWorks Interface: EcoStruxure BMS servers can have a local node on their networks that can act as a LonWorks node. In the local node, you can create your own NVs that can be bound to external LonWorks devices using LonWorks bindings. The NVs in your local node can then be used in EcoStruxure Building Operation bindings for applications and graphics. More information about LonWorks interface: LonWorks Engineering   SNMP: Simple Network Management Protocol (SNMP) is an Internet-standard protocol for managing devices on IP networks. The EcoStruxure BMS servers support SNMP version 3. The SmartX servers support several SNMP traps. SNMP traps enable an agent to notify the management station of significant events by way of an unsolicited SNMP message. More information about SNMP: SNMP EcoStruxure Web Service (EWS) server: EcoStruxure Web Services allows seamless sharing of operational data, including alarms and historical information, between software from different Schneider Electric Business Units. When the EcoStruxure BMS server is an EcoStruxure Web Service server, it exposes objects, such as values, to another EcoStruxure system that is an EcoStruxure Web Service client. The EcoStruxure Web Service client can read and change values on the EcoStruxure BMS depending on the configuration of the EcoStruxure BMS server. More information about EBO EWS Server: EcoStruxure Web Service Server Smart Connector: A development framework that simplifies and accelerates integrations with third-party systems or other data sources. It is an open, extensible and configurable application framework that allows developers to create innovative new capabilities, applications, and solutions which extend and enhance EcoStruxure Building solutions. Ex. SmartConnector can be used to serve EBO data in a RESTful manner, refer to: Configure SmartConnector RESTful EWS Gateway to serve EBO data   For further information watch the Smart Connector explainer video or visit the Smart Connector Developer Community on the Exchange: For developers wanting to get started using the Smart Connector framework visit: https://www.smartconnectorserver.com Smart Connector at Exchange:  EcoStruxure Building Operations SmartConnector 

Issue The Exchange Download Center contains all of the assets you once accessed through the Buildings Extranet are now available on a brand new platform. It's easy to search and fast to download. Stay tuned for more great features as we roll this into the all-new extranet solution for Buildings. We ask that you register for a new account on The Exchange.   Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Other, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Exchange Download Center Cause You can utilize the new Buildings web experience from The Exchange. Resolution Navigate to https://ecoxpert.se.com/ * Use a modern browser for the best experience: Google Chrome, Mozilla Firefox, Microsoft Edge, and Microsoft Internet Explorer version 8 or later. If you receive the following error in Internet Explorer despite using version 8 or later, the browser displays the page in Compatibility View. Click here for more information on Compatibility View and how to disable it. The Download Center will not function properly in Compatibility View.   On the header bar, you will see the option in the top right corner for “Login / Register.” Click it.   If you are already registered, enter your email address and password. If this is your first time registering, click the link for “New to the Download Center? Register here!”   Answer whether or not you are a Schneider Electric employee using the radio buttons. If you are a Schneider Electric employee, enter your SESA ID and your desired password for The Exchange. Click to accept Schneider Electric’s Terms and Conditions and hit “Create Account.” * The first time you register, you must be connected to the Schneider Electric network or connected via VPN. This is only required at registration. All future logins can be done externally. If you are not a Schneider Electric employee, enter your first name, last name, company name, location, business email address, and desired password for The Exchange. * It is important to use your business email address if you are a licensed partner. Your email address is used to automatically validate your Partner status and assign the correct permissions to your user profile.   An email is sent to your designated inbox with a link to click through and validate your email address. Once this is done, your login is created, and you are ready to start using the Download Center. * If an error is displayed when trying to validate your authentication code, please try to log in. This happens when an email address has already been verified and oftentimes does not indicate an error with the registration.   Once logged in, you can search and download assets available to your user profile. If you attempt to download a file that you do not have access to, you will be given a chance to report if this is in error. Your username, email, and the asset you are trying to access are recorded. Please enter a message if any further description is required and hit “Submit.” A member of our team will get back to you promptly with a resolution. Web Site Support For any issue regarding The Exchange Download Center, please contact us at exchangesupport@schneider-electric.com.

Issue PCT error 'Hardware virtualization is not enabled. Please enable in BIOS before continuing' Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool Windows 10 Cause Windows Hyper-V is enabled Resolution Firstly, in BIOS check and confirm the computer’s Hardware Virtualization is enabled.  See the following article which may provide assistance with this.  PCT Intel Processor Virtualization.   Once confirmed that this feature is enabled within the bios then, within Windows, open Control Panel\All Control Panel Items\Programs and Features, in the left pane select “Turn Windows features on or off” Check to see if Hyper-V is enabled: If it is, uncheck the checkbox next to Hyper-V. This change will require the computer to be restarted for the change to take effect.   If Hyper-V does not deactivate properly and gets launched automatically at startup, you can instead disable Hyper-V through an elevated command prompt with the following command: bcdedit /set hypervisorlaunchtype off  

Issue Is the I2/B3 865/866/885 UL 916 Listed Environment  I2/B3 865/866/885 Cause  I2/B3 865/866/885 UL 916 Listed Resolution Yes the  I2/B3 865/866/885 are UL 916 Listed Download the complete list of UL916 listed products.

Issue SVT Controller will not operate plant under Auto control following Clock replacement. Environment SVT 4201 Optimiser Controller. SVT 4251 Optimiser Controller. Cause Replacement Clock installed in SVT Controller is incompatible due to incorrect Clock specification selection.   Resolution 1. Check SVT Optimiser Controller Specification Number.      Specification Number 588-4-201 = SVT 4201     Specification Number 588-4-251 = SVT 4251   2. Check SVT Clock type.     Analogue or Digital ?   SVT 4201 is Analogue Clock version of SVT Replacement Clock installed should be of Analogue type. Replacement Analogue Clock Specification Number = 561-9-260   SVT 4251 is Digital Clock version of SVT Replacement Clock installed should be of Digital type. Replacement Digital Clock Specification Number = 561-9-261   3.  Replace Clock of incorrect type / specification with Clock of correct type / specification.   Please check the catalog for current equipment

Issue Enterprise Server does not start when computer is started/rebooted or shuts down right after starting it StruxureWare Building Operation Software Administrator log shows the following error: nsp.NspServer The server has made too many unsuccessful attempts to start... Product Line EcoStruxure Building Operation Environment Software Administrator Enterprise Server Cause StruxureWare Building Operation is prohibiting the Enterprise Server from starting up because the ES has exceeded the number of startup retries defined in server_startup.properties. When the server_startup.properties file is opened in a text editor, the first line indicates a startup failure. NspServer.Startup.Service.Status: fail Resolution Windows XP: This is caused by a dependency, set in the registry, on the service netprofm (Network List Service), which exists on Windows Vista and later, but not on Windows XP. The error has been verified on a new installation of Windows XP. Steps 1 and 2 below help to resolve this on the XP operating system. Windows 7 and Windows Server 2008 R2 including Virtual: Start ES manually from the Software Administrator. If this fails, the log in the Software Administrator explains why. Start the ES manually from the Services listed in Services (Start, My Computer, right-click, Manage, Services click the + to find Services) find StruxureWare Enterprise Server Go to the Software Administrator and modify the HTTP, HTTPS, and TCP ports to available ports. (suggested: 81, 444, & 4444). The number of startup retries is defined in the following file: 1.2.0 and below : C:\Program Files\Schneider Electric\StruxureWare X.X\Enterprise Server\etc\server_startup.properties 1.3.0                  : C:\Program Files\Schneider Electric StruxureWare\Building Operation X.X\Enterprise Server\etc\server_startup.properties 1.4.1 and above : C:\ProgramData\Schneider Electric StruxureWare\Building Operation X.X\Enterprise Server\db\etc\server_startup.properties Increasing this threshold in server_startup.properties will allow the Enterprise Server to have a better chance of achieving a successful startup. server_startup.properties -- Original settings NspServer.Startup.Service.Status: fail NspServer.Startup.Service.Status.NbrOfConsecutiveFails: 2 NspServer.Startup.Service.Status.QuitRetryAfterNbrOfConsecutiveFails: 2 server_startup.properties -- Threshold increase to 10 retries. NspServer.Startup.Service.Status: success NspServer.Startup.Service.Status.NbrOfConsecutiveFails: 0 NspServer.Startup.Service.Status.QuitRetryAfterNbrOfConsecutiveFails: 10   Last option, and please go through all the previous steps mentioned before attempting: Open regedit and go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Building Operation X.X Enterprise Server. Open the DependOnService and remove the first line (netprofm) and then reboot. The ES will now start automatically.     Alternative Workarounds Go to Computer Management by right clicking on Computer and going to Manage. In Computer Management, go to Services and Application > Services > Building Operation X.X Enterprise Server. Right click on Building Operation X.X Enterprise Server and go to properties. The two different settings that can be changed so that the Enterprise Server starts automatically as a service after a reboot are as follows. Under the General tab, change the Startup type from Automatic to Automatic (Delayed Start). Or under the Recovery tab, change the Restart service after to a value of 3 or more minutes.

Issue Differences between EcoStruxure Energy Expert and EcoStruxure Power Monitoring Expert There are some best practices and tips that can be used to save engineering time when setting up a EcoStruxure Energy Expert (Formerly Power Manager) system. To find out the differences between Energy Expert and Power Monitoring Expert (PME) see Differences between EcoStruxure Energy Expert and EcoStruxure Power Monitoring Expert. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation EcoStruxure Energy Expert EcoStruxure Power Monitoring Expert ETL Integration Tool Cause The following topics should be considered before and during the implementation of the EcoStruxure Energy Expert offering to achieve the cleanest and most effective database.    For more information on design considerations including IT considerations, software compatibility, server specification, hard drive space, etc; see Design Guide - EcoStruxure Energy Expert - formerly Power Manager. For more information on integration see Energy Expert with EcoStruxure Building Operation.  For more information regarding Power Monitoring Expert (PME) please visit the Solutions Expert Community. Here you can find documentation, content, and additional help.  Resolution You may get some benefit working thorough some older existing support material under Energy Expert's former name of Power Manager such as the Deploy Power Manager for SmartStruxure Solution in a Day document.  Also check out the Power Manager EWS Alarm Web Configuration Quick-Help video on the Exchange. General Always install the EcoStruxure Energy Expert software with full Windows administrative rights. Just logging in with a user that has admin rights may not be enough. If you are unable to save an ETL job or run as a service; close ETL, right click on ETL and select run as administrator.  Create one folder on the root level of the server that holds all of the extended trend logs you wish to transfer to EE. This folder can even be set up to be visible to only a designated admin account to prevent any changes to be made to the trends. If any other items like trend charts are in this folder, it will only slow down the process.  See StruxureWare ETL tool locks up or takes a long time while loading sources for information on how to improve the scan time of the ETL load sources function.    SQL Server It is not recommended to install EcoStruxure Energy Expert on a machine that has another instance of SQL already installed on it unless you have advanced SQL configuration skills. The default SQL instance name is ION and the system administrator password is ION!Everywhere. This should not be changed.   Selecting Between Architecture 1 and 2 The three items to consider when selecting an Architecture are device type, numbers of registers to be requested, and device location. The device type is the most important item to consider though. In order to get the most out of the high feature, more robust meters, Architecture 2 should be used. Architecture 2 should be used if the following features are present; ION meter, multi-address device, power quality functions, onboard logging, and/or onboard alarming. When low-end power meters, energy meters, or pulse meters are used, there is no difference between the two architectures in fulfilling the energy management requirement. Most of the Schneider Electric meters and circuit breakers are fully supported by EE. This means that EE has built-in drivers to utilize the full function of the device and the required commission time is minimized.   Architecture 1: Logging data in EcoStruxureWare Building Operation (EBO) It is recommended to use interval trend logs to log the raw data coming in from the meters.  The only durations that need to be set up in trend logs for ETL is the standard trend log duration. This is generally going to be 15 minutes as a industry standard. EE Dashboards and Reports have an aggregation mechanism to make use of the data. Thus durations such as day, week, or month do not need to be brought over into EcoStruxure Energy Expert (EE) as it can be calculated later based off of the 15 minute trend log value.  If both Trendlogs and Extended Trendlogs are used, it is recommended to send the data in the Trendlog to EE to avoid the lagging between Extended Trendlogs and Trendlogs.    ETL StruxureWare Building Operation version 1.6 RC EcoStruxure Web Services (EWS) do not support Secure Sockets Layer (SSL) URLs. For the ETL Extract task make sure to fill out the web service name (default is admin), web service password (default is admin), and web service URL (replace localhost:8080 with your web server address and port as needed) in the settings. For the ETL Load task make sure that the ION data database connection string and ION network database connection string are correct. Also change the field enable recorder and channel creation to True. The recommended naming convention for the Target Device field is [Group].[DeviceName] with no special characters such as \ * + = | : ; < > _. An example could be BuildingA.SubMeter1 where the building name is used as the group and the meter name is used as the device name. With this naming convention, all values brought in under this particular meter will have the same Target Device name.    The Target Measurement field is very important to set correctly as it will not bring the data over to EE correctly if the right unit has not been chosen. This is a process that will become easier with more experience but you can reference Section 6.9 Measurement mapping for ETL in the Power Manager for SmartStruxure Solution - Integration Manual. This chart can be used to search for the unit type you are dealing with and which corresponding Mapping should be use. 

Issue How do you set up the VisiSat server for MicroNet or IAC controllers? Environment VisiSat server settings Cause Assistance for correct configuration. Resolution LIB-4-485 is a RS-232 to RS-485 converter to be used with VisiSat for communicating to MicroNet NCP Controllers or Satchnet controllers without the need for a MNMI or MIU respectively. The LIB-4-485 is powered from the communications port of your PC and no external power is required, providing the PC port adheres to the RS-232 specification (we have used successfully with Dell PC’s). The connection to the LAN are:-  TD (A) – To negative (-) communications terminal of controller. TD (B) – To positive (+) communications terminal of controller. GND – Screen connected at LIB card only and not at controller.   VisiSat requires the following settings to be configured in the VisiSat Server. The Server is found minimized next to the clock in the system tray. At the bottom right corner of your desktop, double click the server icon to show the VisiSat Server client. Select settings from the Network Menu Option. The Configure Network Settings window will be displayed as below. Select ‘Serial Port’ as the Transport type, and click the Configure button. 1. The configuration for use with MicroNet controllers needs to be as detailed below. 2. The configuration for use with IAC controllers needs to be as detailed below. Once the correct selection has been made click OK. VisiSat is then ready to use with selected controllers.   The VisiSat Engineering guide contains additional information regarding the VisiSat server Click here to download or view the VisiSat Engineering manual.  

Issue Problems installing Continuum Continuum will not install correctly SQL Express will not install correctly Product Line Andover Continuum Environment Continuum Cause Cyberstation fails to install or run correctly Resolution Continuum Cyberstation can normally be installed very quickly (usually less than half an hour) on a normal windows installation that fits within the Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation, this would include SQL for a stand alone (Single User) installation. The Continuum Cyberstation uses many Windows components and services, and runs many executable files and batch files within its normal operation. We do not have a published list of services that Continuum requires to run since requirements vary depending on the site configuration. We obviously use Active Directory and .NET, RPC, MSMQ, SMNP, and all DCE services. SQL Server Management Studio Express is a free down from Microsoft and is an excellent tool for checking the SQL install Up to v1.94sp1 SQL2005 https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-2017 v2.0 and beyond SQL2012 https://www.microsoft.com/en-us/download/details.aspx?id=35579 There are a few items that can interfere with the smooth installation or running of a Continuum Cyberstation Ensure the workstation PC is within the Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation for the version being installed, especially Windows service packs and .NET framework versions. Ensure the minimum requirement for the workstation PC, is observed, as stated in the Cyberstation installation guide. Ensure the recommended requirement is observed, if the Cyberstation will be used for video or other more intense operations.  Local administrator accounts are required for some version of installation with passwords set. See How to create a local administrator log on in Windows. Automatic updates. See the individual installation guides, however, it is normally wise or even mandatory (depending on Continuum version) to leave them off, as updates include service packs and .NET framework updates that would take the installation off the Compatibility Matrix and could compromise the installation. There have also been other updates that have caused issues. See 5 below. MSXML6 Update SQL Express install fails on MSXML 6 Firewall & Anti virus issues. These should be disabled during installation. Issues with starting Continuum after new installation (Anti-Virus and Firewalls) Error when starting Continuum 1.9: Cannot find acc video recording service Access denied errors when installing Continuum or Webclient Crash of ACCDataServices on start up or running Continuum Another example of antivirus interfering with Continuum install is getting Microsoft Visual V++ error when opening a pin point graphic, when the install is completed with AV "webRoot" enabled.  SQL2005 Express (1.82SA onwards) When creating the sa password ensure the password is tested in notepad before typing in Database Initialisation, as if the keyboard is not set up correctly, you may be using an illegal character (eg " rather than @, in this case you will need to uninstall SQL, before re-installing via Database Initialisation) Custom Windows Images - Some Windows Images installed on new PCs include modifications that interfere with the Cyberstation installation, always use a clean MS Windows if possible, as this avoid such issues. HP Protect Tools - MFC error on Continuum startup or Continuum won't start on HP PC IT tampered Windows & domains. It is important to install Continuum with local Administrator rights as item 3, above, beware of PCs locked down by IT departments, the installation can be slow and difficult Error 1001, windows event log full. Error 1001 when installing Cyberstation or Webclient Problems with MSMQ (MicroSoft Message Queue) can cause install problems MSMQ errors and Continuum fails to start MSMQ error starting Continuum. "There appears to be a problem with the configuration of this system. Please check to make sure that you have correctly installed MSMQ." MSMQ error message: "Appears to be a problem with configuration of system please check to make sure you have MSMQ correctly installed" Trying to install CyberStation 1.9x.  It completes but then pops up 6 errors saying "Access denied" "Access Denied" messages during a CyberStation 1.9x installation Microsoft Update issues see Windows updates and Continuum Continuum Version 1.93 Fails to install. IssueReceive AccDataservice errors on startup. Continuum Version 1.93 Fails to install For Windows 7 installs see Disabling administrator rights messages in Windows 7 OS and above (Also known as UAC / User Account Control) If you see a Continuum install Error -  "Error, unable to open documentation list \misc\doclist.txt" then you are running the incorrect "setup.exe", you should install using the one in the Cyberstation root directory, not the one in the Continuum sub-directory. It has be found that Microsoft "Strong" passwords are required not only for the SQL sa password but also for Andover97 password, see Password requirements for Andover97 SQL Login for details For a v1.82 Stand Alone and beyond, if the install admin user has no password, it has been seen that the tasks (CS_Minute, CS_Distn and CS_hrly) are not always created, see Getting AccDataServices error with AlmUtil.dll error when closing Continuum If a Continuum re-install, on a LAN CyberStation is required (were some part or program has broken) then uninstall Continuum, then re-install. A workstation initialization may be required. Deleting the Continuum directory and clearing out Continuum from the registry may also be required (check for any local held graphics, .mnu files, etc. before deleting the Continuum directory) Seeing "Can not change directory to Continuum" see Cannot change directory to Continuum error during installation of Cyberstation Re-Installing Continuum is sometimes required, for example, an automatic update to the Antivirus software has been seen to stop listviews from working. The only way around this was to uninstall Continuum then re-install it. There are different levels to uninstalling possible, 1.Simple uninstall. 2. Uninstalled followed by removing the Continuum Directory and other .ini files. 3. Uninstalled followed by removing the Continuum Directory and other .ini files, followed by cleaning of the registry.  In a few more recent cases where Controllers will not come online (after testing for other errors) or where persistent MSMQ errors cannot be resolved, a complete re-install of the OS may be required to ensure a "clean" Windows OS is available. Uninstalling some Continuum required programs can cause issues, especially SQL. see Problem uninstalling software. The following method has been seen to work: Stop service, uninstall, delete folders, run CCleaner (or Revo) and clean registry, reboot, run CCleaner (or Revo) and clean registry, reboot, re-install SQL Shared Memory errors seen with 32b systems and v2.0SP1, see "Shared Memory" error on startup of Continuum