Building Automation Knowledge Base

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 During installation of hotfix for EBO you get a "Hotfix file signature validation" error saying that Device Administrator cannot verify the issuer of the file signature's certificate.   In older versions of Device Administrator you might get an alternative error message "Invalid hotfix file" saying that the file does not have a valid Schneider signature. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Device Administrator Offline system Version 3.1 and later Cause EBO hotfixes for SmartX Server are signed with a certificate to ensure that only valid files can be used. This certificate must be validated before you can use a new PC to install a hotfix. If the PC has not had any internet connection while previously installing a hotfix or does not have an internet connection, the certificate cannot be validated and hotfix installation therefore fails. Resolution There are two solutions Solution 1 Connect your PC to the Internet and install the hotfix on a SmartX Server. The certificate is validated, and the PC can subsequently be used to install hotfixes on other SmartX Servers, even if you are offline. Solution 2 You can manually import certificates and CRL (Certificate Revocation List) Download and save the following files: http://s1.symcb.com/pca3-g5.crl http://sv.symcb.com/sv.crl If the above URL's are blocked by your browser please download them here or the attached ZIP file.  Start a command prompt (cmd.exe) as administrator. Browse to the folder where the files from step 1 are stored. Run the following commands: CertUtil -AddStore CA pca3-g5.crl CertUtil -AddStore CA sv.crl Export host, intermediate, and root certificates from the hotfix file. Install the 3 certificates with the default selection. Restart Device Administrator and install the hotfix. Video for step 5 and 6:

Issue The Drayton Theta YBL1A Valve Body / Actuator assembly is to be replaced. Product Line Field Devices Environment Replacement Drayton Actuator Valve YBL1A Cause The Drayton Theta YBL1A Valve Body / Actuator assembly is obsolete. Resolution OVERVIEW The Drayton Theta YBL1A Valve Body / Actuator assembly is obsolete, and there is no purpose built replacement. The Valve Body was available in 1.1/4", 1.1/2" and 2" B.S.P. sizes and was normally installed as a mixing valve in variable temperature, constant volume, compensated heating circuits. No Valve Body / Actuator assemblies are currently available in these sizes. Details of the YB Valve Body may be viewed here.   VALVE BODY REPLACEMENT To replace the YBL1A Valve Body the following is required:- S-E SatchwellMB Valve Body of appropriate size - MB1552 (1.1/4"), MB1602 (1.1/2"), MB1652 (2") Details of the MB Valve Body may be viewed here.   ACTUATOR REPLACEMENT (6-WIRE INSTALLATION) The YBL1A Actuator normally comprised a 6-wire electrical connection enabling it to be operated by a Theta Potentiometric Controller as follows :-  Terminal M1 – Open signal Terminal M2 – Close signal Terminal M3 – Common  Terminal M4 – 135 ohm Feedback Potentiometer – winding Terminal M5 – 135 ohm Feedback Potentiometer – wiper Terminal M6 – 135 ohm Feedback Potentiometer – winding Where 6 wires are connected to the YBL1A Actuator then the Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-24 MD20B-24 (if MD10B-24 not available) Details of the MD10B-24 Actuator may be viewed here Details of the MD20B-24 Actuator may be viewed here. N.B. The YBL1A Actuator also included an additional 3-wire electrical connection associated with an integral S.P.C.O. Auxiliary Switch wired as follows :-  Terminal S1 – Normally Closed Contact Terminal S2 – Common Terminal S3 – Normally Open Contact Where external wiring is connected to the YBL1A Actuator Auxiliary Switch then an Auxiliary Switch Kit containing a S.P.C.O. Auxiliary Switch should be installed on the MD Actuator. Auxiliary Switch Kit MD-S1 (914-1060-000) Details of the MD-S1 Auxiliary Switch Kit may be viewed here. The MD-S1 Auxiliary Switch Kit should be wired as follows :-. Terminal S1 – Common Terminal S2 – Normally Closed Contact Terminal S3 – Normally Open Contact   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here   IMPORTANT NOTE In such 6-wire installations not only will the YBL1A Valve / Actuator assembly need to be replaced but the associated Theta Potentiometric Controller and its Sensors will also need to be replaced.   CONTROLLER REPLACEMENT The Theta Potentiometric Controller may be replaced by the S-E Satchwell CSC5252 or the CSC5352 Compensator Controller. Details of the CSC Controllers may be viewed here.   SENSOR REPLACEMENT Theta 3-wire Temperature Sensors may be replaced by S-E Satchwell 2-wire Temperature Sensors compatible with the S-E Satchwell CSC 5252 or CSC5352 Compensator Controllers selected from the following as appropriate. Outside Air Temperature Sensor (STO 600) Contact Temperature Sensor (STC 600), or alternatively :- Immersion Temperature Sensor (STP 660) + Sensor Pocket Adaptor (DWA 0001) Room Temperature Sensor (STR 600) – OPTIONAL ONLY Details of the STO 600 Outside Air Temperature Sensor may be viewed here. Details of the STC 600 Contact Temperature Sensor may be viewed here. Details of the STP 660 Water Temperature Sensor may be viewed here. Details of the DWA 0001 Sensor Pocket Adaptor may be viewed here. Details of the STR 600 Room Temperature Sensor may be viewed here.   N.B. ACTUATOR REPLACEMENT (3-WIRE INSTALLATION) Should only 3 wires be connected to a YBL1A Actuator then the Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-24 MD20B-24 (if MD10B-24 not available) Details of the MD10B-24 Actuator may be viewed here. Details of the MD20B-24 Actuator may be viewed here. N.B. The YBL1A Actuator also included an additional 3-wire electrical connection associated with an integral S.P.C.O. Auxiliary Switch wired as follows :-  Terminal S1 – Normally Closed Contact Terminal S2 – Common Terminal S3 – Normally Open Contact Where external wiring is connected to the YBL1A Actuator Auxiliary Switch then an Auxiliary Switch Kit containing a S.P.C.O. Auxiliary Switch should be installed on the MD Actuator. Auxiliary Switch Kit MD-S1 (914-1060-000) Details of the MD-S1 Auxiliary Switch Kit may be viewed here. The MD-S1 Auxiliary Switch Kit should be wired as follows :-. Terminal S1 – Common Terminal S2 – Normally Closed Contact Terminal S3 – Normally Open Contact   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here In such 3-wire installations the YBL1A Valve / Actuator assembly only will need to be replaced, while any associated Controller and Sensors may be retained.

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 In the LON Flow Balance program the k-factor calculated by the balance process can be displayed at the end of the procedure.  I cannot determine how to read it in the BACnet Flow Balance program.  The value is needed so that the application file can be updated so that if the controller needs to be re-downloaded, it will not need to be balanced again. Environment BACnet  MNB-V1 or MNB-V2 controller WorkPlace Tech Tool software release 5.7.2 or newer  (Optional, for backup) Cause The BACnet Flow Balance process uses a procedure that results in a more accurate flow calibration process. As a result of this process the rate box flow value does not get re-calculated during the balance process. Resolution The BACnet MNB-V1 & MNB-V2 controllers do not rely on a calibration constant (k-factor) stored in the application.  The Flow Balance calibration data is stored separately from the application data so that a revised application file can be downloaded to a controller without losing any of the recorded air balance calibration data.  The Flow Balance data is also saved as part of the file produced by the controller backup function of the Workplace Commissioning Tool.  Refer to the WorkPlace Tech Tool 5.7.2 release notes for more information. The Flow Balance calibration data can be displayed after balancing the BACnet MNB-V1 or MNB-V2 controller by clicking on "Balance Data" in the menu on the left side of the Flow Balance screen.  The Flow Balance Data screen shows the data entered and produced as a result of the flow balance process.  Refer to the figure "Flow Balance Reporting -- Flow Balance Details" in the Air Balancing chapter (Chapter 5) of the "MicroNet BACnet Commissioning Tool / Flow Balance Users Guide", F-27358 for more details.  In addition to being able to manually display the balance data for a single controller, both the BACnet Flow Balance program and the WorkPlace Commissioning tool can generate a flow balance for any or all of the BACnet VAV controllers on the jobsite. Refer to the section "Flow Balance Reporting" in the Air Balancing chapter (Chapter 5) of the "MicroNet BACnet Commissioning Tool / Flow Balance Users Guide", F-27358 for more details.  The resulting report is automatically saved when it is generated and the HTML version can be displayed / printed without the need to reopen it in the BACnet Flow Balance program. In addition to being able to manually re-enter the balance data into a replaced controller, Release 5.7.2 of the WorkPlace Tech Tool software introduced a software function that allows the complete application including COV subscription data and flow balance calibration data to be backed up.  Should it be necessary to replace a controller, the WorkPlace Commissioning Tool can be used to restore the backup into the new controller.  Refer to the "WorkPlace Tech Commissioning Tool Backup and Restore feature" section on page 10 of the release notes (F-27526-3) for more information.  The release notes are available here.

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.  

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 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 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 The display on the smart sensor module (LCD1/LED1) is blank. Product Line Andover Continuum Environment CyberStation B3 devices/i2 devices with Smart Sensor port. Cause LCDDisplay/LEDDisplay element #2 has a value of 0 which turns off the display The host controller is not sending power to the SPWR port It could be a newer version of the smart sensor, see i28xx-V & i28xx-V-WL Controller v3.501037 - Release Notes Resolution Set LCDDisplay/LEDDisplay[2] to a valid display format value. (see Smart Sensor Installation and User Guide) Measure the voltage between return and SPWR and make sure it is 8.4 volts DC, if the voltage is not correct disconnect the Smart Sensor and measure again, if the second measurement is correct then the Smart Sensor may need to be replaced, otherwise the host controller may have to be replaced.

Issue For further information, refer to the FLEXnet Licensing End User Guide, available on the Flexera website. Product Line TAC Vista Environment Vista 5 Workstation FLEXnet Licensing Cause If you get this error and attempt to find the End User Guide, you will discover that the company that produces the FLEXnet software has gone through several name changes: Macrovision to Acresso to Flexera. Resolution If you would like a copy of this document, you can find the FLEXnet License Administration Guide (previously called the End User Guide) here.

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 VTRA Valve Body requires replacement due to obsolescence. Product Line Field Devices Environment VTRA 3-port Mixing Valve Body Cause Obsolescence of VTRA Valve Body Resolution VTRA Valve Bodies are obsolete and have been for many years. VTRA Valve Bodies were available with either Flanged or Screwed connections.  Details of the various size / connection combinations available appear VTRA Specification Sheet. REPLACEMENT OF VTRA FLANGED CONNECTION VALVE BODY A replacement for the VTRA Flanged Valve Body (32-80mm) may be selected from the VTRE range of Flanged Valve Bodies, see VTRE S-E Specification Sheet for more datails. N.B. It should be noted that the VTRE Valve Body is rated PN6 whereas the VTRA was rated PN10. The VTRE Flanged Valve Body may be operated by the EM9 Actuator, see Alternatively the VTRE Flanged Valve Body may be operated by the M9B Actuator, See EM 9 Specification Sheet for more details. No Linkage Kit is required to mount the EM9 or M9B Actuator on the VTRE Valve Body. Alternatively a replacement for the VTRA Flanged Valve Body (65-80mm only) may be selected from the the S-E VG311F and V321 3-Port Flanged Valve Bodies, more details can be found in the Venta VG311F 65-150C Specification Sheet and the Venta V321 Specification Sheet N.B. It should be noted that the S-EVG311F and V321 Valve Body are rated PN16 whereas the VTRA was rated PN10.   REPLACEMENT OF VTRA SCREWED CONNECTION VALVE BODY A replacement for the VTRA Screwed Valve Body (15-50mm) may be selected from the MB range of Screwed Valve Bodies, see the MB/MBF data sheet for more details. The MB Screwed Valve Body may be operated by the MD10B series Actuator, see the MD10B specification sheet for more details. Alternatively the MB Screwed Valve Body may be operated by the MD10A Actuator, see the MD10A specification sheet for more details.  

Issue SE7300 and SE8000 room controller fan speeds do not turn off when fan mode is set to auto. When cooling and / or heating is no longer needed, the fan speed remains at low speed. Product Line EcoStruxure Building Expert, Field Devices Environment SE7000 series room controller SE8000 series room controller Cause It is required that the fan be turned off when no demand for cooling or heating is needed. Resolution SE7300 controllers Enter the configuration mode of the room controller. Refer to page 19 of the SE7300 Series Installation Guide for the procedure to enter the configuration mode. In configuration mode, there is a parameter 'AutoFan'. The default mode for this parameter is 'AS'. In order for the fan to stop when there is no demand, the mode should be set to 'AS AD'. AS (Default) = Auto Speed during occupied periods. Fan is always on during occupied periods. Low, medium and high speeds operate on temperature offset from set point. AS AD = Auto Speed / Auto Demand during occupied periods. - Medium and high speeds operate on temperature offset from set point. Low speed operates on demand and will shut down when no demand is present. SE8000 controllers On the room controller, select the fan mode parameter from the home screen. The fan mode must be set to Smart in order for the fan output to function as expected. In Smart mode the fan will turn off when there is no demand for cooling or heating. For SmartStruxure applications of the SE8000 controller This issue can also be seen when binding to the "Value field of the Occupancy Command of the SE8000 controller. Make sure to bind to a priority, not to Value otherwise the fan command will not turn off.

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 Replacements for Satchwell sensors Product Line Satchwell MicroNet, Satchwell Sigma, Field Devices Environment DR DR3253 DRT DRT3451 DRT3453 DRT4453 DRT3651 DRT3652 DRT3801 DRT3851 DU DU4301 DUS DUS4302 DUSF DUSF4351 DUSF4352 DRTE DRTE2201 DRTE2801 DRTE2851 DRH DRH7702 DRH7703 DRTH DRTH7712 DRTH7713 DOT DOT0001 DOT0002 DOS DOS0002 DDT DDT1701 Cause Replacements for Satchwell Room sensors Resolution DOT0001/0002 Outside temperature sensor For CSC, KMC, MMC, IAC, MNN New part number: STO600/5126060000 DOS0002 Outside solar sensor For CSC, KMC, MMC, IAC, MNN New part number:  SSO600/5126050000 DR3253 Room sensor non-adjustable For SVT New part number: STR614/004604900 DRT3451 Room sensor exposed adjustment For CZU, CSC New part number: STR612/004604700 DRT3452 Room sensor concealed adjustment For CZU, CSC New part number: STR611/004604600 DRT3453 Room sensor non-adjustable CZU, CSC, CXR, CZT, KMC, MMC, IAC, MNN New part number: STR600/004604100 DRT4451 Room sensor non-adjustable As DRT 3453 in S-Link housing Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRT3651 Room temperature sensor exposed adjustment For CXR, CZT, KMC, MMC, IAC, MNN New part number: STR602/004604300 DRT3652 Room temperature sensor exposed + LED For MMC, IAC, MNN Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRT3801 Room temperature sensor fan switch On/off for CZU, MNN, IAC Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRT3851 Room temperature sensor fan speed switches As above plus medium and high Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DU4301 Room sensor temperature For MNN & URC New part number: STR601/004604200 DUS4302 Room sensor temperature setpoint advanced basic sensor New part number: STR613/004604800 DUSF4351 Room sensor temperature setpoint adjustable fan auto/on/off fan override New part number: STR609/004604400 DUSF4352 Room sensor temperature setpoint advanced fan Auto/1/2/3 fan override New part number: STR610/004604500 DRTE2201 Active room detector Basic sensor Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRTE2801 Active room detector On/off Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRTE2851 Active room detector Off/low/medium/high Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRH7702 2% 0-10V DC humidity only For KMC, MMC, IAC, MNN New part number: SHR100/006902340 DRH7703 3% 0-10V DC humidity only For KMC, MMC, IAC, MNN New part number: SHR100/006902340 DRTH7712 2% 0-10V DC humidity with Satchwell NTC TEMP OUTPUT For KMC, MMC, IAC, MNN New part number: SHR100-T6/006902420 DRTH7713 3% 0-10V DC humidity with Satchwell NTC temperature output For KMC, MMC, IAC, MNN New part number: SHR100-T6/006902420 DDT DDT1701, DDT1702 and DDT0001 Duct sensor non-adjustable New part number: STD660 5126030000 Contact Details: Titan Controls: http://www.titancontrols.net/ Sontay Controls https://www.sontay.com

Issue Unable to retrieve license file for Vista 5.x.x. You may receive an error from Vista stating "Unable to retrieve license file". You may also see the following error within read pain in LMTOOLS/Server Status. FLEXlm Error: The desired vendor daemon is down 1) Check the lmgrd log file, or 2) Try lmreread Feature: ARC/INFO Vendor:Host: ESRI : server License path: @server;@client; FLEXlm error: -97,380. System Error: 10061 "" For further information, refer to the FLEXlm End User Manual, available at "www.globetrotter.com". Program not run. Product Line TAC Vista Environment Vista 5.x.x LMTOOLS License Server Cause License Server cannot start until it is able to connect to and checkout a license from this license server. One known cause of this error is an incorrect license Host ID in your license file. Resolution Open LMTOOLS Select the Config Services Tab Click the "View Log" button to view the debug log text file. Review the contents to see the actions taken by your license server. The MAC address on the Vista Server machine may have changed if you see the below error within this log file -Wrong hostid on SERVER line for license file: -C:\Program Files\Schneider Electric\License Files\LicenseFilePro5.1.lic -SERVER line says 001c4213f460, hostid is 0050569d001a -Invalid hostid on SERVER line You must log on to the License Activation Portal to rehost this license to the new MAC address using the original entitlement ID. Please see Rehosting a Vista 5 License on the FlexNet License Server.

Issue Interfacing M-Bus meters to Modbus. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell Sigma Environment Sigma IC3-Modbus Mbus Modbus Kampstrup Heat Meter Multical 601 Cause Multical 601 M-Bus meters are required to be interfaced with the BMS. Resolution A M-Bus/Modbus converter (RS-485, RS-232 or TCP) and configuration software are required. The converter  and software are available from SyxthSense or similar suppliers. Using the converter and software setup the M-Bus/Modbus system without the BMS system connected. The M-Bus/Modbus converter will automatically assign the M-Bus registers as Modbus registers. From the software note the tables and registers used. Create the Modbus registers as required for the BMS system used. For Sigma - Create the gateway.txt, connect and configure the IC3-Modbus. A sample of the gateway.txt can be downloaded here: MultiCal Modbus Gateway.zip. For further M-Bus information see M-Bus Protocol Information. 

Issue EcoStruxure Building Operation different types of licenses and all features Version 1.9 and older: Difference between Workstation standard and Workstation professional Product Line EcoStruxure Building Operation Environment All versions Cause Due to different features of each license, customer may get confused which license to order. Resolution See the version of the latest EcoStruxure Building Operation Part Number Summary document on the Exchange for all license part numbers.   Versions 2.0 and Newer Note: The licensing part numbers and structure has vastly changed starting in version 2.0 and newer.  See the search query below on the Exchange for more detail regarding the Scalable Pricing Policy that started in version 2.0. EcoStruxure Building Operation Scalable Pricing Information   Versions 1.9 and Older Note: There is no part number for WebStation; it is a default feature of the Automation Server and Enterprise Server (with no need for additional licensing)  

Issue The License Server is not working and may show Vendor Daemon Down errors. The LMadmin log shows the error. LicenseEngine (taclic) exited with status 28 Product Line TAC Vista EcoStruxure Building Operation Environment Vista Building Operation Enterprise Server License server Cause Data Execution Prevention (DEP) is activated. Antivirus or other software can scan/use the port used by the vendor daemon. If the time drifts over two minutes and a time synch occurred, the vendor daemon can stop. https://support.citrix.com/article/CTX137111 Resolution First, check that DEP is not activated. Make sure that there is no antivirus program that has portscan activated Make sure there is no other software that uses the same port as the vendor daemon Make sure that the time does not drift too much, if the time drifts two or more minutes and then a resynch occurs the vendor daemon can stop This is more likely on VMware where time synch can occur from either the domain or VMware tool. Check Windows event log (Security) for time synch messages. NOTE: It can also appear just by stopping the server manually.