Building Automation Knowledge Base

Issue Support for UI16A CIO with FW 2.016 and HW C How is CIO FW 2.016 distributed? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation I/O Module 16 Ch UI Cause Due to component changes in the UI16A CIO module, a new HW version C has been created. Consequently, a new firmware (FW) file has been created specifically for that new HW version, 2.016. Resolution This FW version will be installed already at delivery from the factory for the new version of UI16A modules. For this new UI16A model, one cannot install older 2.015 firmware as it is not compatible. All the older modules can remain at the latest published CIO release 2.015. The HW version which is printed on the product label is changed from B to C on the new UI16A version. The Hardware version can also be viewed in the module object through EBO. For all other modules, the HW version will stay at B.

Issue Need to place the ADv3 Display remote from any AS-P.  Requires USB connection, as WIFI is not allowed. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Advanced Display Cause The standard for USB 2.0 provides a maximum cable length of 5 meters (16 ft 5 in). The standard for USB 3.0 provides a practical maximum cable length of 3 meters (9 ft 10 in). Resolution Schneider Electric has only tested with standard cables. It may be possible to find third-party solutions like Active USB cables or bridges. These solutions are not tested, nor supported by Schneider Electric.

  Issue PIBCV valves, stem up or stem down for valve open. Product Line Field Devices Environment PIBCV Valves VP220, VP221, VP222, VP228 Cause Further information required as to whether stem up or stem down for valve open position. Resolution When the stem is up (retracted into the actuator) the valve is open.   Example:

Issue When saving or importing a MTA (Menta) file in SmartStruxure Workstation, and error is shown indicating that there are more than one occurrence of one or more file types in the MTA file. Product Line EcoStruxure Building Operation Environment Workstation Menta Function Block Cause A MTA file contains various files that together forms the complete program. In some cases (e.g. when using a . in the MTA file name) various occurrences of the same file types will be placed in the MTA file. Resolution Open the MTA file in with the Menta editor Mark everything and export as an AUT file Create a new MTA file Insert the AUT file created in step 2 Save the MTA file only using standard characters Import the the MTA file Generate the MTA file to ensure you have no errors and all the public constants have been updated.

Issue Point values are not displayed in Vista Workstation.  Instead, all of them say [??787]. Product Line TAC Vista Environment Vista Workstation Cause The most common cause of the ??787 error message is a mismatch in the XIF between the device and the Vista database.  It may also be duplicate SNVT names in the XIF. Resolution There are a few common troubleshooting techniques that have been applied successfully to the ??787 error and resolved the issue.  The first is to upload parameters from the device.  The second is to browse the correct XIF to the device to eliminate any mismatch. Upload parameters Right-click on the device in Vista Workstation. Select Upload Parameters. Shut down Vista and restart. Make certain you are using the correct XIF The only way to be absolutely certain that the XIF in the device matches the one in the database is to upload the XIF from the device.  You may need to create a dummy LNS database to do so.  Add a generic device and commission with the option to upload the XIF from the device. Update the Vista database.  Again, this may need to be a dummy Vista database. To obtain that XIF, right-click on the device in Workstation and select Properties.  The XIF File tab lists the database copy of the XIF file (hexadecimal file name) that can be found in the Vista database directory in the $thisfil folder. Browse the correct XIF into the Vista Workstation If you are certain you have the correct XIF, right-click on the device in Vista Workstation.  Select the XIF File tab. At the bottom under Source File, click the "..." button and browse to the XIF file. Click okay.  Log out of Workstation and log back in to see the changes take effect. It may then be necessary to right-click on the controller and select Commission and Download. Remove duplicate SNVTs Open the XIF in a word editor (Notepad, Wordpad) Find the duplicate SNVT name using the Find feature Rename one of the SNVTs to a unique name. Use the above steps to browse this new XIF into Vista Workstation. XIF file contains internal variables Open the XIF in a word editor (Notepad, Wordpad) Search for the variable whose value displayed as [??787] If the variable is not listed in the XIF file, it is possible that this is an internal variable which Vista cannot read a value from Contact the manufacture of this device and ask if they can expose the value with a network variable in order for Vista to read it.

Issue When a Modbus device comes back online after being offline a message is sent from the Building Operation Server to the Modbus device which looks similar to: WriteData TX on /dev/tac_comporta: 01 2B 0E 01 00 70 77 ReadData RX on /dev/tac_comporta: 01 AB 01 9E F0 This message can cause the Modbus device to restart or stop responding, is it possible to disable it? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 1.5.xand above Modbus Device Socomec Power Meters Crompton Integra 1221 Power Meter Cause A feature was added in release 1.5 that is intended to read the device's identification (0x2B). It works by polling this function code (FC). If the Building Operation server does not get a valid reply to this message, it assumes it is not supported by the device and will not request this again. This is usually not a problem but some Modbus devices, such as those listed in the Environment above, are unable to handle this message and will stop communicating with the AS or ES. Resolution In Building Operation 2.0.4 and above the option to enable or disable the device identification request (Function code 2B) has been introduced, allowing the poll interval (and online detection) to be set. Some devices will stop responding to poll requests if the device identification is enabled. Once disabled the AS or ES and the device may need to be restarted to enable normal polling without any device identification request being sent and stopping the normal responses from the device.   In previous versions this message cannot be disabled, however, if device polling is disabled the device identification request won't be requested, which can be used as a work-around. To turn off the device polling: Open Properties Set "Poll interval" to "Inhibit" The trade-off with this workaround is that the online detection for the device is turned off, so the device will never go offline in Building Operation. In some instances, the third-party Modbus device will need to be restarted to allow communication to resume.

Issue Enterprise Server IP address does not match the IP address of the Local PC. SmartX Server is showing online but there is a "Communication failed" alarm showing for this server(s). Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Cause The IP address of the Windows system has been changed. This can be from a DHCP renewal or a manual change of IP address. This also may be an issue if an Enterprise Server backup is restored and the backup was from another PC with a different IP address. Resolution Update the Enterprise Server IP address from the Enterprise Server communications Tab and then the properties windows.  Refer to the video below for details on how to do this.     It is also possible to specify the Network Interface used by the Enterprise Central/Server.  Refer to the following WebHelp topic Configuring Network Interface Card for an Enterprise Server or for an Enterprise Central   

Issue The following error can occur when logging into Security Expert using a Remote Client:   Could not log on to Server. Please check your remote connection setup. The server has rejected the client credentials. Product Line EcoStruxure Security Expert Environment Security Expert Server / Client Cause The security policy settings are different between the Server and Client.   When installing the Security Expert Server and Clients, the default security policy is used. This requires that the Windows username and password that the operator has used to log in on a client machine is also a valid user on the computer that is running the Security Expert Server. These security requirements are very favourable for corporate networks and setups where the users and policies are easy to manipulate. For that purpose alone, the Security Expert Server and Client are installed with these settings by default.   All installations are not created equal however and sometimes the Security Expert Server is not located within a domain. In another scenario, the server may be in a domain but the operators need to connect to it from a machine that is not in the domain. In these cases, it has been requested that the security policy in place on a domain or the physical machine is disabled and although this is not recommended practice the security of the system can be maintained using a suitable VPN structure.   This solution should be used with full knowledge that the security of the system will rely on the operator user login name and password as well as the security measures put in place for a client to be able to hit the server with a login request. Protection of the infrastructure to the connection is beyond the scope of this document. Resolution The easiest solution would be to put the Client machine(s) in the same Domain as the Server.  However if this is not possible or if no Domain is used then you can still manually update the security policy instead. The following process is a manual edit of the XML configuration files  SecurityExpert.exe.config  SecurityExpertSV.exe.config  Both of these files are located in the .\Program Files\Schneider Electric\Security Expert directory on the Client and Server. It is recommended then to backup these two files prior to performing this task. Close all Security Expert clients and stop the Security Expert Data Service. We are first going to update the Security Expert Client configuration file SecurityExpert.exe.config on the client machine.  If using more than one Client, the change must be done for ALL clients Open Notepad as the administrator, browse to the specified location making sure the 'all files option' is selected.  Then open SecurityExpert.exe.config (Be aware that it may not have the file extension showing and will be called an XML Configuration file by default) Locate the netTcpBinding tag . Nested within this tag is the binding tag Ensure that you insert the below text after the opening binding tag and before the closing \binding tag . If you insert the text outside this tag, the application will fail to run.   "<security mode ="None"></security>" IMPORTANT You must ensure you enter "None" with a capital "N" (not lower case). Ensure you copy input text exactly as shown. Now save the file. If you get a write error then you need to open notepad as the administrator. Repeat the process for the Security Expert Server configuration file SecurityExpertSV.exe.config which is located in the same directory on the server machine.      Again, make sure the line is inserted after the opening tag and before the closing tag or the application will fail to run when you save the changes. Restart the Security Expert Data Service and test the connection settings.

Issue How to configure Custom 37-Bit as well as Infinity 37-Bit Card Format Product Line Access Expert Environment Access Expert Server 2012 and Above Version 2 Version 3 Hosted  Premise Cause When configuring Custom 37-Bit as well as Infinity 37-Bit Card Formats, the settings are different based on the Facility Code, Card Length and Card Formats. The HEX code generated in Live Monitoring can be deciphered to get the correct set of values required to make this work for your application. If you are unable to do so, please contact PSS and open a ticket so that they can help. Resolution The following settings on the screen shots show how to configure Custom, HID Formats and Infinity 37-Bit Formats, please pay attention to the one that will work for your specific application: Open and log on to the respective Access Expert Instance Select the tab Access Configuration to create a new Card Format Name the format accordingly in the description field, this can be used for Infinity 37-Bit if so desired Add the card range by clicking on the page Icon on the Number Range There is a Standard, HID Managed 37-Bit (not Infinity 37) in the drop down in the Card Format Presets This can be used by default but if you have a Custom 37-Bit Format and the Facility Code is known, however the Start Bit and Length will be different. An Infinity 3 Bit Format will use the Parity Bits Create the new format per the screen shots and configure accordingly. Once complete, click on Save or Save and Close, reboot the controller.

Issue WebStation connection is unreliable when using a 4G (cellular) connection Auto logoff times are not obeyed  Product Line EcoStruxure Building Operation Environment Building Operation WebStation 3.x Broadband Cellular Networks Cause WebStation creates a subscription with the Building Operation server, so it will attempt to connect every 10 seconds.  If this connection is removed/interrupted/ or no longer required for a period of 60 seconds, WebStation will force itself to log out.  This setting is currently fixed and cannot be adjusted.    Currently, there have been instances where this connectivity issue is seen when using, as shown below, a device with a broadband cellular connection attempting to connect to a Building Operation server that also connected to the same/similar cellular network this is the most common scenario where this issue is seen. Resolution It is recommended not to use these cellular network connections to permanently display Building Operation Server information, especially from mobile devices connecting to the cellular network.  This type of connection should be used sparingly and for quick access to view/check information as necessary.  Connection loss can be expected if you move away from the webpage for more than 60 seconds.  Any lengthy connections to the Building Operation Server are recommended to use a more permanent network connection.     Issues have not been seen when using broadband Internet or a similar connection as shown below to a remote cellular Building Operation Server.  This meaning that the EcoStruxure Building Operation system has remote Internet access via a broadband cellular connection. To troubleshoot this further, capture a HAR file using the details provided here How to collect a network trace | Microsoft Docs and reproduce the issue while this debugging window is open within your browser.  Note: This capture must be done at the source; that is where WebStation is running.  This may not be easy to do using a mobile device.   Send this saved HAR file and the Internet browser version and EBO version used along with connection types to your local support channel. 

Issue The file structure is incorrect for MNL-FLOW-BAL 3.0 software for use with Windows 7 64 bit OS.  The FlowBalance.exe needs to be run in Windows XP (Service Pack 3) compatibility mode. Product Line TAC IA Series Environment Windows 7 64 bit MNL-FLOW-BAL Balance Software Cause The paths for certain files being used by the software cannot be modified. When loaded on a 64 bit PC, the default paths are incorrect for the rest of the processes to find. Resolution Manually create and insert the folder structure required. Set the FlowBalance.exe compatibility Copy the TAC folder in the Program Files (x86) folder from Windows Explorer. Paste into the Program Files folder Open the pasted TAC folder and delete all the files except for the XIF folder and the FlowBalance.cfg file in the LON FlowBalance folder. Right-click the FlowBalance.exe icon created on the desktop Open properties/compatibility tab. Set as Windows XP (Service Pack 3)

Issue In BAS and Sigma, what batteries and PSU cards can be used in a x96 controller.? Product Line Satchwell Sigma Environment S-x96-STD S-x96-BAT Sigma BAS Cause What batteries and PSU cards can be used in a x96 Controller or BAS controller? Resolution See TPA-LOND-08-0017.02 S-ARM7-BAT is the Sigma UNC PCB Battery Spare for the ARM7 CPU Board. The battery itself is a Ni-MH 2-Button Cell, 2.4v, 80mAh. S-V53-BAT is the Sigma UNC PCB Battery Spare for the V53/V25 CPU Board. The battery itself is a Ni-MH 3-Button Cell, 3.6v, 150mAh. S-X96-BAT is the Sigma UNCx96 Hi-Capacity Battery for the x96 products. The battery itself is a Ni-MH D-Cell pack, 10.8v, 5Ah (12-Hour). S-X96-STD is the Sigma UNCx96 Standard Capacity Battery for the x96 products. The battery itself is Ni-MH AA-Cell pack, 10.8v, 1500mAh (1.2-Hour) Due to UK legislation in 2006 NiCad batteries could not be used and changes were made where NiMh batteries are used instead 2016-01-22: - Confirmed both the S-X96-STD and the S-X96-BAT battery packs are currently available. Note: Schneider sales do not understand dashes, so when asking for price and availability you need to remove the dashes or they will not find the parts. Specification Sales need Price provided by sales S-X96-STD SX96STD £ 198.05 S-X96-BAT SX96BAT £ 541.19 General Rules for battery replacement and PSU card replacement/modification are: 11/2008 to present - The controller was originally shipped with the NIMH battery and PSU card suitable for charging the NiMH battery. These PSU cards are suitable for charging both NiMH and NiCad batteries. 04/2004 to 10/2008 x96 BAS/V53 PSU cards - The PSU card have to be replaced to fully charge NiMH batteries. 1999 to 03/2004 x96 BAS/V53 PSU cards - The PSU card have to be replaced to fully charge NiMH batteries. Pre 1999 BAS PSU cards - 2 resistors are required, the TPA explains how. The resistors are shipped with the NiMh battery. Note: If upgrading to Sigma then the Upgrade kit S-x96-UPKIT should be used which includes a new PSU card.

Issue Existing SIM-MTECH communicates with a McQuay OPM (Open Protocol Master) and McQuay controllers under it. Can an AS-P replace the SIM-MTECH? Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series NW8000 GCM/SIM-MTECH (McQuay OPM) Building Operation Automation Server Premium Cause Replacing obsolete NW8000 GCM/SIM-MTECH with currently supported EBO AS-P Resolution The GCM/SIM-MTECH data base can be converted as a normal GCM through the Transition Tool on the Schenider Electric Exchange TAC I/A Series Transition Portal.  The blocks specifically associated with the OPM integration will not be converted. A third-party hardware device can be used that will allow the AS-P to communicate through the OPM to the McQuay controllers. This will be accomplished by BACNet or Modbus protocol to the AS-P depending on the third parties device selected.  Refer to these 2 documents and websites.  NOTE: These are third party devices and have not been tested or approved by Schneider Electric Product Support. FS-8700-80 McQuay MicroTech Open Protocol Mcquay Gateways

Issue What will happen with the EBO license when used with cloned Virtual Machines in a fail-over scenario to another host? Product Line EcoStruxure Building Operation. Environment Building Operation Enterprise Server Cause Even if the Virtual Machines are "cloned" the licensing will show as "Damaged" Since Virtual Machines don't have unique hardware and the software images can be identical, another identifier called UMN3 (Unique Machine Number 3) is provided by the Virtual Machine. This is, as the name indicates, unique for each Virtual Machine. Without this feature, it could be possible to cheat the licensing system and run many instances of software without a license being purchased for each instance.   See the following technical description of the virtual machine image identifier (VMID) that provides the UMN3   A hash of the universally unique ID (UUID or SMBIOS3) that the hypervisor issues whenever a virtual machine is created or cloned. SMBIOS is commonly virtualized by hypervisor providers such as VMware and Microsoft. In addition, virtualization management systems such as VMware’s VMotion ensure that all virtual machines being managed have a unique SMBIOS value. Resolution If Virtual machines are being utilized to provide a fail-over or "hot swap" of the EBO Server then licenses need to be purchased for each Virtual Machine, just as if two physical computers were used. Each Virtual Machine will require its own License Server installation and have the required licenses activated.

Issue The SmartX server has a "?" under the server name field and shows the error "SSL certificate validation failed!" as the server state in Device Administrator. In some instances, this may cause a failure to upgrade of the SmartX Server displaying these symptoms.  Product Line EcoStruxure Building Operation Environment Building Operation Device Administrator Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Automation Server Cause The SmartX Server is added into Device Administrator over HTTPS 443 but does not have a valid SSL certificate installed. Resolution Change the connection from HTTPS 443 to HTTP 80 This can be done by clicking into the server settings (click on the "?") Select "Edit Connection"   Change the EBO Server Protocol from HTTPS to HTTP  Create a trusted chain between Device Administrator and the problem SmartX Server using a self-signed certificate by following this workflow

Issue Would like to monitor and control points and alarms from an ESMI Fire Detection Panel in EBO. Product Line EcoStruxure Buildning Operation Environment Building Operation Automation Server Premium (AS-P) ESMI Fire Detection Panel Cause The integration between ESMI Fire Detection Panel and EBO enables the user to visualize and operate ESMI Fire detection systems effectively from graphics in EBO. Resolution The interface between the ESMI Fire panels and EcoStruxure Building Operation (EBO) is handled by the AS EN54 FIRE SmartDriver. The event and command information is sent/received by the Fire panel using RS-485 communication to/from the AS-P using the SmartDriver.   This resolution is in three steps: Enable communication via RS485 (INFO protocol in Fire panel) Use the AS EN 54 Fire Configurator to create the layout for EBO Install/configure the SmartDriver and create the Fire graphics in the AS-P   Step 1 - Enable communication via RS485 (INFO protocol in Fire panel) This video shows how to enable communication from an ESMI Fire panel and an AS-P over RS485. This is a prerequisite for using the Fire SmartDriver in the AS-P.     Step 2 - Use the AS EN 54 Fire Configurator to create the layout for EBO This video will give you a quick introduction to the AS EN54 Fire Configurator. The AS EN54 Fire Configurator is a Windows application that imports floor plans and configuration files to create the EBO interface, devices, points, alarms and graphics.     Step 3 - Install/configure the SmartDriver and create the Fire graphics in the AS-P This video shows how to connect an EBO SmartX Server to an Esmi Sense Fire detection panel (FDP). And how to create and edit the Fire graphics in the EBO SmartX Server, The fire graphics provide the user interface to visualize and operate Esmi Fire detection systems.  

Issue Could not start the TAC Xenta 102-AX LonWorks PlugIn, due to an Error message. Product Line EcoStruxure Building Operation. Environment EcoStruxure Building Operation Workstation. TAC Xenta 102 AX Cause EcoStruxure Building Operation does not support online PlugIns, as LNS is running in the background, without any communication port.. If selecting to Synchronize (Upload or Download) you will get an error message. Resolution Select "Skip" synchronize.

Issue The Sigma Client reports a "HTTP connection failed" error" when an attempt is made to start it. Product Line Satchwell Sigma Environment Satchwell Sigma release 4.05 and later Cause When the Sigma Client is started, attempts are made to make a connection to the Sigma Server, this connection fails and the Client cannot be started. Resolution There are a number of reasons why this error might occur, suggestions are listed below. 1.  Windows XP operating system - ensure that service pack 3 has been installed, and that all the Windows updates have been applied. 2. Windows 7 operating system - only Ultimate and Professional are supported. 3. Sigma Client/Server software must be installed by a Windows user with "Admin" privileges. 4. Windows Firewall must either have been switched off, or has "Exceptions" configured as explained in the Sigma 4.05 SP1 release note. 5. Check that the "SigmaSVR" service has been started. If this service cannot be seen, then this is an indication that the Sigma software has not been install by an "Admin" user, and the software must be reinstalled. 6. Corruption of the Windows "User" files has taken place. Create a new Windows user with "Admin" privileges. Log on to Windows as the new user and test the Sigma Client again. 7. If using a VMware image try rebooting the image. 8. SMART is being used and has a modem connected to the PC for uploading data. Ensure that the modem is fully functional. If not, the HTTP error can be caused. This was seen at Sigma: R4   Release 3.44.14. and Smart Task Manager  3.0.2.20. Added 26-07-2012 9. This may be because a proxy server is being used, eg on school networks. Log on to your PC computer with an administrator account. Open the "Start" menu and click on "Control Panel." Double-click on the icon labeled "Internet Options." Go to the "Connections" tab at the top of the window and then click on "LAN Settings." Make sure the box next to "Bypass proxy server for local addresses" is checked. Hit "OK" twice to confirm the new proxy port settings. Make sure the box next to "Bypass proxy server for local addresses" is checked. Hit "OK" twice to confirm the new proxy port settings. Added 25-09-2012. 10. This issue was reported from a School where Sigma 4.05 SP1 had been operating correctly for several weeks. The issue was traced to the Anti-virus software Sophos, which had received an update prior to the failure. Sophos had quarantined two Sigma dll files. To correct this issue both Sophos and Sigma were uninstalled. A later version of Sophos was installed, and then Sigma was reinstalled, this corrected the problem. Added 01-08-2013 11 - Sigma software installed when connected to a wireless network. The Sigma client will only connect to the server when the wireless connection is made. Uninstall Sigma, disable the wireless, enable the network card, and then reinstall the Sigma software. Added 03-10-2013 12. DELL PC, with firewalls and antivirus disabled and no wireless card fitted. There may be a service or an application running in the background as part of the vendors Windows platform makeup.Restore the same version of Windows, but without (where possible) any of the Vendors applications. Re-install Sigma. Added 16-05-2014 13. Check the port number in c:\sigma\bin\setupsvr.exe, the default is 8080. Added 19-05-2014 14. Flexera license software has been reported as a cause for receiving this error. Flexera license software uses port 8080, (IMADMIN.EXE). Stop Flexera and retry Sigma. Changing Sigma from port 8080 to 8081 could also provide a solution. Added 27-08-2014 15. The SBO PCS (StruxureWare Building Operation Project Configuration Server) also uses port 8080.This needs to be stopped or will conflict with Sigma and produce the HTTP error. Added 02-09-2014 16. Make sure any data is backed up from the installed Sigma system. Uninstall Sigma using Add/remove programs (Win XP) or Programs and features (Win 7). Wait for the Sigma un-install process has completely finish. Delete or rename the C:\Sigma folder to.......for example Sigma1. Re-install Sigma by using a right mouse click on the "SigmaSetup.exe" file and select  A new clean Sigma folder will be created during the install. Once completed reboot the computer. Check the SIgma server is running and run up SIgma. Added 01-10-22014 17. The HTTP error can also caused if the computer name contains extended ASCII or Unicode. For example a computer named "Pást" may fail, if the computer name is changed to "Past" this may correct the HTTP problem. Added 23-11-2021 18. On SE laptops, the McAfee firewall has been updated: Go to McAfee (under hidden icons) > right click 'Quick Settings' > 'Enable Firewall Timed Groups'. This will provide a 1 hour window to run Sigma, in the McAfee pop up window. add a reason e.g. Sigma.

Issue Checking operation of CSC. Product Line Field Devices Environment CSC5252 CSC5352 Cause The operation of the CSC compensator explanation. Resolution The operation of a compensator is to adjust the system flow temperature, in relation to changes in the outside air temperature. The system flow temperature can be further adjusted by the addition of a room temperature sensor, which will provide room influence. The CSC 5252/5352 controller is programmed with a complete set of "Default" settings, these settings will allow the controller to operate as soon as its powered up. Although the controller has a complete range of adjustable settings, accessed through the "Fine Tune Mode", for a basic installation the "Quick Set Mode" can be used. The screen shot below explains how to enter the Quick Set Mode and the settings available. Controller data sheet Controller User guide   Compensated Flow Temperature Set-point: The compensated flow temperature set-point is automatically adjusted based on a ratio for set-point adjustments against the outside temperature changes. A consistent ratio across the entire outside temperature range, may not provide suitable control. For example: with radiator type systems, radiators are less efficient at lower water flow temperatures and need to be provided with a higher temperature to compensate for this initially. The “Set compensator ratio 1”and the “Set Ratio 2” settings provide the ratio of the change to the flow temperature set-point for changes in the outside air temperature, the ratio used is based on the “Set Change-over Value”, with the compensated slope starting from the “Set Flow Origin”. The “Set Flow Temperature Set-up Value” and “Set Night Set Back Value” provide a constant adjustment of the flow temperature set-point to a given building control requirement. The default settings would give a resultant flow temperature as shown follows:     The CSC5352 Calculator presents these settings in a graphical and listed format, making it easier to visually confirm the effects any changes to these settings would make.    

Issue In EBO there is no build in way to view b3 array element value. In Continuum there is a command line that allows printing array elements by specifying the array index. Product Line EcoStruxure Building Operation Environment Building Operation ASP, ASB, AS b3 BACnet devices Infinet i2 device Cause The Infinet i2 device object array values can be viewed as WebHelp. This option is not available with b3 BACnet controllers. Resolution A workaround is to use a Script program to expose the array element value. See Sample Script Program to expose b3 array element value.