Building Automation Knowledge Base

Issue Temperature Sensor Resistance Charts Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Temperature Sensors Cause Temperature (°C) to Resistance Charts (ohms). Upgrading the site BMS, but retaining the existing sensors and the sensor resistance values are not known. Resolution The resistance of a sensor at a specific temperature can be downloaded below, there are a number of tables collated from different sources for a number of Schneider Electric sensors and other BMS suppliers.   In EBO, the thermistor selection in the IO module or controller does not represent the thermistor bead type, an example is the Continuum Type I in EBO, but the bead is a Type 3,. For further information regarding this see the KB article  Thermistor type selection in EBO.   The document All Sensors covers the following:   Satchwell DxT sensors are replaced by STR600, STP660, STD600, STO600 type T with shunt, and use the Satchwell T range chart Drayton DC1000, DC1100 30K6A1 is now known as STR600D, STP600D, STO600D Andover 10K4A1 TAC Inc. Vista 1.8KA1 I/A series 10K3A1 with 11K shunt INET 10K2A1 (10k Dale) BALCO 1000 ohm RTD   Older Satchwell ranges: Satchwell DW1204, DW1305, DWS1202 Satchwell DO Satchwell DD/DR Other manufacturers included: Allerton 3K3A1 Ambiflex 2012, Honeywell Aquatrol, Jel/Thorn, Trend, York 10K3A1 Schlumberger (air) 5K3A1 Schlumberger (immersion) 100K6A1 Automatrix, York, Sibe 10K4A1 Honeywell 20K6A Landis & Gyr PT100A, PT1000A   Further information regarding INET, IA, the document Thermistor Types Tables (Veris Industries) is available.  The 1k Balco resistance chart is also available.   Further information for the Continuum ACC Temp 10K Type 3 also known as 10K4A1, the document Thermistor Temp Resist Chart (Precon Thermistors) is available.   TC900 series TC900 RS-03 sensor chart   For I/A Series Controllers (MNL/MNB) Compatible sensors that have a built-in 11k shunt resistor include the TS-5711-850 TS-57011-850 TS-57031-850 TSMN-90110-850 Series Any sensor that matches resistance to temperature curve for a 10K Thermistor Type G (U.S. Sensor), Type 9 (Dale/Vishay) or Type III (ACI Series AH) can be used with the I/A Series MNL and I/A Series MNB series controllers, provided that a 11k ± 0.1% 1/8 watt resistor is wired in parallel with the sensor. The input has a range of -10 to 135 °F (-23.3 to 57.2 °C) with an accuracy of ±1% of span. Temperature / Resistance Reference Values Temperature Deg F (Deg C) Resistance Resistance Incl. 11k Shunt 32 (0) 25490 8,012 68 (20) 12,260 5,798 75 (25) 10,000 5,238 104 (40) 5,592 3,707 140 (60) 2,760 2,206 The full temperature/resistance table for the US Sensor 10K Thermistor R-T Curve Type G sensor. Please note that the controller may not be able to use the full temperature range shown in the table.  

Issue Due to a variety of reasons it is sometimes necessary to add an offset to the value obtained from a sensor to achieve the required accuracy. For example, a temperature sensor may be reading off by 0.5 degree as compared to a calibrated high accuracy temperature measuring device used as a standard. Product Line Andover Continuum, EcoStruxure Building Operation Environment All CX controller All i2 devices All b3 devices Cause Sensor tolerance. Resolution Add an algorithm in the conversion field of the input objects to adjust the value by the necessary offset. In the example here the conversion entered could be: Elecvalue + 0.5 or Elecvalue + TempSensorOffset where TempSensorOffset is an InfinityNumeric point that has been set to the amount of offset to apply.  While this example uses a very simple conversion algorithm, the input’s conversion can be thought of as a one line PE program that can use PE system functions. Elecvalue + Maximum(TempSensorOffset, 1.5)   Note: For inputs that use automatic conversion e.g. voltage inputs and InfinityFunction is required, see How to add a calibration factor or offset value to an input using automatic scaling for details.

Issue License Administrator fails install with an "Uninstall failed, installer cannot continue" error Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Cause Building Operation uses Flexera (Revenera) Software Technology for licensing. Other Schneider-Electric products may also use this technology for their licensing. Resolution Check to see if the site has other software programs/products using the Flexera (Revenera) Software Technology. Other Schneider Electric offers such as Unity Pro - IEC Programming Software for Modicon PAC, Power Monitoring Expert & TAC Vista as well as third party programs also use Flexera (Revenera) for their licensing. During installation of the Building Operation License Administrator the dialog below is shown: The default behavior of the Building Operation License Administrator installation program is to install both Building Operation License Administrator and a new local license server instance. If the default behavior is accepted, the installation program will attempt to uninstall any previously installed local license servers. If the Building Operation License Administrator installation program  does not have sufficient access rights to uninstall the license server previously installed by another product a "Failed to install Building Operation License Administrator" error will occur.   Multiple products can share a single Flexnet License server instance. If there is an existing Flexnet install then the License Server checkbox should be unchecked during installation of the Building Operation License Administrator This leaves the existing local license server installed by the other product intact, while still allowing Building Operation License Administrator to run. The license server used by Building Operation License Administrator can easily be changed by the user on the License Server Address tab in Building Operation License Administrator, if necessary.  

Issue Rehosting is defined as the process of moving a license from one machine to another. Is there a limit to the number of rehosts allowed per year? Product Line EcoStruxure Building Operation,TAC Vista Environment Building Operation Licensing Cause Re-hosting means that the license bindings to the physical hardware or its substitutes on a Virtual Machine are moved i.e. the host ID is changed. This can be required if the license is moved to a new computer or Virtual Machine.  A maximum of 4 license re-hosts are allowed in 12 months. Resolution If the re-hosting limit is exceeded and further re-hosting is justified and necessary, the policy can be overridden by Product Support. When contacting support please provide the entitlement details so that the license policy can be overridden.

Issue Why is "B" shown in the Concurrent license feature list in the License Server Interface (http://localhost:8888) Dashboard?   Product Line EcoStruxure Building Operation Environment Building Operation License Server Cause The Flexera framework requires at least 1 licensed feature to be present when installing a license server for it to start correctly. In this phase there aren't any licensed features so a dummy feature is created. Resolution It can be ignored as it is just a dummy license used for the installation.

Issue Trend Chart shows dotted line across the screen instead of expected chart data. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause Chart is waiting for a new record possibly caused by incorrect time in the Enterprise/Automation Server Resolution When waiting for a new record, the trend chart draws a dotted line (1) from the last recorded value and forward.  When a new value is recorded, the dotted line between the last and the new record is replaced by a solid series of lines.  Please see Trend Charts. Check the start time (2) and end time (3) period being observed in the chart includes data readings.  Additionally, ensure the Network Time is set appropriately .    

Issue When installing Building Operation software i.e. License Administrator, Workstation, etc. the following error may show: "This software requires .NET Framework version 4.7.2" Product Line EcoStruxure Building Operation Environment Building Operation installers Microsoft .NET Framework Cause Building Operation requires .NET Framework 4.7.2 or greater to install and function Resolution Most Windows machines have the latest version of Windows installed and updated for security reasons. If for some reason an older version of Windows hasn't been updated then it may show the error until .NET has been updated.   Here is a Microsoft article that shows how to determine what version of the .NET Framework is installed on the Windows PC. How to: Determine which .NET Framework versions are installed There are several methods, this is the registry method:   Windows 10 version 20H2 includes 4.8 as part of its default components. It is recommended to upgrade Windows to this version or greater.   Once the version of .NET Framework is upgraded, the error dialog will no longer appear

Issue Values from a third party BACnet device display the question mark character (?) instead of the correct engineering unit. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise/Automation Server Building Operation Workstation Third party BACnet device Cause The BACnet Standard revisions support a list of engineering units as enumerations, as shown in the extract below: - Enumeration Unit Unit type 0 square-meters Area 1 square-feet Area 2 milliamperes Electrical 3 amperes Electrical …. …. …. The question mark (?) placeholder is used when Building Operation reads an unknown BACnet unit enumeration identifier.  It is either a unit from a later revision of the standard, that has not been implemented by Building Operation yet, or it is a unit that is proprietary to the devices vendor. Resolution Based on different BACnet revisions, Building Operation can interpret the enumeration of units but proprietary units may not be handled correctly since these can vary by vendor, model and even the software version.   Any lookup is specific to the vendor, model and software version. The vendor of the third party equipment should be approached to modify their implementation according to the BACnet standard.  Additionally please see Points from an MPM display ? 

Issue DHCP server is required to assign addressing to IP devices Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series Jace 8000 I/A Series ScheniderMPx Modules Building Operation Multi-purpose VAV  Building Operation Multi-purpose Controller Building Operation Room Controller (RPC) 24 V Building Operation IP-IO Cause When working with the SchneiderMPx modules for engineering Spacelogic devices, the Jace can be used as a DHCP server for the field devices. Resolution This video discusses how to; - Configure the second IP network port for DHCP server use - Add an additional IP Port to the Jace station  

Issue Is EBO External Log Storage with PostgreSQL and TimescaleDB tested on Linux? Product Line EcoStruxure Building Operation Environment Building Operation Timescale Database Cause Need to install External log storage with PostgreSQL on Linux. Resolution Quality assurance testing has been performed by Schneider Electric with TimescaleDB and PostgreSQL installed natively in Windows enviroment. Other deployment scenarios have not been tested by Schneider Electric. For tested Windows versions, check: Information Technology System Planning Guide

Issue When attempting to edit a graphic on an SBO/EBO ES or AS the Graphics Editor, Function Block Editor or Script Editor reports it has lost connection. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Premium Cause A second instance of the workstation is running on the same computer The firewall is blocking the connection. The password was recently changed during the same session Workstation is connected via HTTPS but there is no valid certificate Resolution Solution 1 If using Remote Desktop (RDP) to access the SBO/EBO ES remotely, a second instance of the workstation could be initiated. Close the workstation on both the remote connection and at the SBO/EBO ES. Then open the workstation either at the SBO/EBO ES or via remote connection, not both.   Solution 2 Check if the firewall has been enabled while logged in to the SBO/EBO ES or AS, and disable the firewall Here is an example for McAfee   Solution 3 Make sure the network information (such as gateway) for the PC is entered correctly.   Solution 4 If you just changed the password of the logged in user, log out and in again   Solution 5 Workstation is connected via HTTPS but there is no valid certificate. Ensure that certificates are installed and trusted on the workstation/server so that no certificate warnings are received or use HTTP to connect to the server.   Solution 6 Update the Certificate Revocation List as described in First time a TGML graphic is opened after logging in it takes a long time for the graphic to load.

Issue What are the basic steps when doing a conversion from TAC Vista to EcoStruxure Building Operation (EBO)? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Vista Server Cause When doing a conversion from TAC Vista to EcoStruxure Building Operation (EBO), a tool called TAC Vista Conversion tool is used to build the EBO database using an export file from TAC Vista. Resolution This video shows a basic conversion of a TAC Vista database to EBO, and the steps that needs to be taken for a successful conversion.

Issue During certain situations, it may be required to switch from a hardwired to a wireless connection or wireless to a hardwired. In addition, you may be required to replace a failed NIC card with a new variant that may or may not be the same in terms of connection type. Other more rare situations where a technician travels with a laptop that has PCT "SERVER" mode installed would also be affected. Example: PCT Version - 1.1.2.57 Server mode was set up on a physical server that has two NIC cards. The initial setup was performed on NIC1 and now we are required to utilize NIC 2 which is wireless as a temporary solution. NIC card 1 is disabled and NIC card 2 is set up with the same IP details as NIC card1. In addition, the wireless network is an extension of the original network that was configured in NIC card 1. The server then gets rebooted. Once the server is up you start PCT and attempt to open a project. You receive the following errors: "VBoxManager.exe: error: Nonexistent host networking interface" "Failed to open project."    Product Line EcoStruxure Building Operation Environment Windows Client versions (64 Bit Only) Windows Server versions (64 Bit Only) PCT SERVER versions (64 Bit OS Only ) SBO Project Configuration Tool All versions Cause During the initial setup of Project Configuration Server mode, you are prompted to select a network interface card from a list of available NICs. PCT requires that you continue to use the same interface and if you change your connection type at the windows level PCT has no method of knowing this and will not be able to connect to previously created projects. PCT will produce the following complaint as seen in the log below: "Nonexistent host networking interface"   You can find the log path as follows: C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\loggermodule "ProjectsModule.log"   Resolution There are two solutions to address this: Revert your connection type back to the original Network Interface Card. Reboot the machine. Open PCT and attempt to get back into the project. If the idea is to stick with a different NIC, you would simply need to reinstall PCT and select the new NIC during "SERVER" mode setup. Reboot the machine. Open PCT and attempt to get back into the project.

Issue After setting up a REST gateway in SmartConnector, how can it be tested to see that it is working using the built in test client called Swagger? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central SmartConnector   Cause Swagger is a built in test REST client which can be used to read and set values in EBO. So it can be used instead of a "real" REST client to test the REST gateway in the SmartConnector and test that the connection between SmartConnector and EBO is working. Resolution The objective in this video is to set up a REST gateway in SC and show how we can test that the gateway is working using the built in test REST client called Swagger. Please see video.

Issue Receive alarm messages as "Server does not exist or access denied", "08001: [FreeTDS][SQL Server]Unable to connect to data source" or "08S01: [FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist" when using SQL Server Express for External Log Storage even though login credentials are correct. 08001: [FreeTDS][SQL Server]Unable to connect to data source 08S01: [FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist" Product Line EcoStruxure Building Operation Environment Enterprise Server Workstation External Log Storage SQL Server Cause SQL Server Express is using Windows Authentication and/or the TCP/IP network protocol is disabled. Resolution To use external log storage with SQL Server Express the User must be able to login with SQL Server Authentication (e.g. a username and password) and the TCP/IP Network protocol must be enabled.  Consult Setup External Log Storage using MSSQL for additional details.   Check SQL external log storage host address: In the host address type the IP address or DNS name of your external log storage, without the SQL instance name. Having the SQL instance name in the host address can cause communication failure if EBO server is connecting to remote SQL server, refer to: Microsoft SQL Server - Basic Tab. To check the User login credentials: Open SQL Server Management Studio and enter the details from EcoStruxure Building Operation into the SQL Server connection window.  Choose SQL Server Authentication (A), enter the server details (1), user name and password (2) and attempt to login. If an error message appears indicating cannot connect and the credentials are correct it is possibly SQL Server Authentication is not enabled. Login to the SQL Server using Windows Authentication and follow the Microsoft article Change server authentication mode to set to 'SQL Server and Windows Authentication mode'. Attempt to login to SQL Server and the specific database should be visible. To enable the TCP/IP Network protocol:  Open SQL Server Configuration Manager (1) In the SQL Server Network Configuration menu, select Protocols for SQLExpress (2) Right-click TCP/IP (3) and select Properties (4) In the window that opens, click the IP Addresses tab (5) Either set a different port number for each one of the IP addresses or simply set one for all (6).  The default is 1433 but will need to be a port that is free.   Click OK. Back in the SQL Server Management Studio ensure the SQLExpress service is restarted. For additional information please consult Default SQL Server Network Protocol Configuration and Enable or disable a server network protocol            

Issue When using EBO's registration page, the registration website that is opened allows the user to login and enter the new system ID, however, the user then cannot proceed any further. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Cause The link https://registration.smartstruxure.schneider-electric.com/, which redirects to the https://registration.smartstruxure.schneider-electric.com/WebConnectUI/RegisterUser/home This page may not allow the user to complete the site’s registration with the new system ID. Resolution Register the site’s EBO new system ID using the following website address. https://registration.smartstruxure.schneider-electric.com/ebo/Home

Issue When trying to change a BACnet value unit, the following error message pops up Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause Using a unit that is not supported by BACnet standard or using a prefix with a unit that doesn't support a prefix in BACnet. In the following example, we can see the "Airflow Input" has the kPa unit. Now, if the user wants to change the unit to N/M 2 , without removing the prefix k(10 3 ), an error pops up upon saving the settings.   Resolution Make sure to select a unit that is supported by the BACnet protocol. Supported engineering units in BACnet are listed in BACnet standard, ASHRAE 135 clause 21, refer to BACnet Engineering Units enumerations. To resolve the issue in the above example, the user needs to omit the prefix before selecting the unit OR  They need to make sure the selected unit supports that prefix.    

Issue When using an Echelon U10/U20 USB or other Lon network adaptor for communication with a laptop and standalone WorkPlace Tech, not WorkPlace Tech Editor, you must change the default configuration settings.  The default Lon Network Domain ID length (1 byte), Domain ID (18 decimal) and Subnet (254) in the AS-P conflicts with the defaults used by WorkPlace Tech. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech (Lon Network communication settings) Building Operation Automation Server Premium Building Operation Enterprise Server Cause Lon Network configuration Resolution Look at the LonWorks Network "Advanced" tab in the AS-P to determine the addressing information. Open the WorkPlace Tech WorkStation Communication Settings and select LonWorks.  Open the Change Address window Select the "Manual Setup" radio Button Modify to match the AS-P Lon Works Network configuration.  If a different Domain ID or subnet has been assigned in the AS-P, it will need to be assigned the same in WorkPlace Tech You can now browse the LonNetwork from the laptop.  If the MNL devices are assigned applications from the AS-P, do not modify the programs from the WorkPlace Tech Tool  

Issue When external internet access is not possible an alternative NTP Server is required to allow ES and AS to by time synchronized onsite. Product Line EcoStruxure Building Operation Environment Enterprise Server / Automation Server on closed network Eg Windows 7 Cause AS will not synchronize the time with a local NTP such as Windows 7 (32 or 64 bit) without it first being configured. Even then, increasing Cyber Security features within EBO means that the use of a 3rd Party NTP is becoming a much better option. Resolution Preferred Solution The very best option for the latest versions of EBO would be to investigate. Meinberg NTP which is a third party NTP server that runs on the Win7 or Win10 OS and provides NTP by synchronizing with four or more Internet clocks and is a trusted time source in NTP.  It is not an officially supported PSS tool, but it does fix the issue of the ES/AS not trusting the time.   Windows 7  Config If you still wish to attempt the Windows 7 NTP option first the procedure to setup is as follows:    In the 'Services' window (part of Administrative Tools) Stop the 'Windows Time' service if already running. The 'Startup Type' could be set as Manual or Automatic depending on the user needs. In the Registry Editor following changes to be made under the Key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time: ** Config -> AnnounceFlags = 5. ** HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time\TimeProviders\NtpServer -> Enabled = 1. Start the 'Windows Time' service in the 'Services' window(part of Administrative Tools). Note: NTP uses UDP Port 123 Below is a Wireshark capture using filter udp.port == 123 indicating the “Leap indicator” bits are 11, meaning “clock unsynchronized”. NOTE: The NTP client in the AS may ignore the time sent by the NTP server if the root dispersion is greater than 'X' seconds (unknown at this time). See Automation Servers ignore time sync message sent from Windows NTP server that uses local internal clock for information on how to determine whether this is a problem at the site and how to resolve it. Note: Test Lab results show that once validated and synchronized, the AS asks the time from the NTP about every 17 minutes. Two enhancements have been requested for a future release: Workstation gets an alarm if the NTP is not a valid reply A tick box setting in Workstation so the ES/AS can accept an invalidated reply(time)

Issue Some attributes used within Continuum PE programs on b3/i2 controllers are no longer appropriate with EBO Script programming Product Line EcoStruxure Building Operation Environment b3 Infinet Building Operation Server Script Programming Cause Some attributes used within Continuum PE programs on b3/i2 controllers are no longer appropriate or cannot be used with EBO Resolution An example of this would be the ElecValue attribute for an input or output. This can be used within the Conversion field of an input but cannot be used within a Script Program or Script Function. The Continuum example PE program for an STR502 or STR504 includes the line "If STR5xx ElecValue <= 0 then Return Upper" The correct result can be obtained within SmartStruxure by dropping the "ElecValue", so "If STR5xx <= 0 then Return Upper" Then ensure the STR5xx analog input is a Voltage type with no conversion configured. Note: The ElecValue keyword can still be used in the Conversion line of an Analog Inputs (e.g. for Counter input scaling). Some other Attributes not supported in Script Programming are: Size LogType