Building Automation Knowledge Base

Issue Cannot change the IP address or host a SpaceLogic IP device, MP or RP controllers, or IP-IO modules in a second EBO Server. Product Line EcoStruxure Building Operation Environment IP address BACnet Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller  Building Operation IP-IO Building Commission Application Cause 1. IP settings are saved (eg in Building Commission), but the IP address of the Controller does not change. (Option to change most settings is grayed out from Building Commission for hosted SpaceLogic IP devices) 2. The Controller is already hosted by an EBO server and cannot be hosted by a second EBO server, thus data objects cannot be read. 3. Rehosting an SpaceLogic IP device to a different EBO server Resolution 1. Changing the IP address "settings" can be done with Building Commission application, formely know as eCommission Tool, in some earlier versions but if the SpaceLogic IP device, formely known as SmartX IP device, is already fully hosted by an EBO Server, then a warm start from the Building Commission is inhibited. (Option to change most settings is grayed out from Building Commission for hosted SpaceLogic IP devices) Without the hosting Server initiated warm start the new IP setting will not be used. If the SpaceLogic IP device is not hosted then the IP address can be changed from the Building Commission, using the warm start option. Notes A local warm start initiated at the SpaceLogic IP device(manually with the reset button) will not force the SpaceLogic IP device to use these new settings. See BACnet/IP Controller Commissioning Scenarios The IP address of a Hosted SpaceLogic IP device cannot be modified from eCommission Tool A factory reset will force the SpaceLogic IP device to return to AutoIP and DHCP, the BACnet Id will generally be retained see Automatic Association after a Factory Reset in a BACnet Controller or IO Module 2. When a SpaceLogic IP device is fully hosted by an EBO Server, it can be BACnet hosted by a second EBO Server, but this will only contain the standard BACnet Applications folder. This hosted BACnet Device needs to be manually created using the SpaceLogic IP device instance Id.  Below, it can be seen that the fully hosted SpaceLogic IP device and the BACnet only hosting under ASP_22   3. When a SpaceLogic IP device is configured or programmed via the hosting EBO Serving using WorkStation, some of the objects (eg. Scripts or Function Block) data is not fully contained within the SpaceLogic IP device. Thus if the hosting EBO server is changed, some of the configuration data will be lost and a simple upload to the new hosting EBO Server will not upload all the data required to recreated these objects. In such a case, an export from the original hosting EBO Server should be imported into the new hosting EBO Server to ensure no data is lost.

Issue When logging in to SmartStruxure WorkStation you get a security certificate risk warning Security Certificate Risk There were errors validating the security certificate in use. This may pose a security risk to the system. The certificate presented by this server was issued for a different server's address. How do you wish to proceed? Trust certificate or Cancel You can also get a warning when logging in through WebStation if you use the https address Warning in Google Chrome - FireFox - Internet Explorer Product Line EcoStruxure Building Operation Environment SmartStruxure version 1.6 and newer WorkStation WebStation Cause Starting in version 1.6, a new security feature has been introduced validating the ES and AS server identity based on security certificates. In order to avoid seeing this warning each time you log in, you need to apply a certificate to each server (ES, AS, ASP or ASB) - either a self-signed or an existing. Resolution This article will describe how to import or generate a certificate, and how to install the certificate through WorkStation or a browser. If you generate the certificate for an Automation Server, make sure that the time and time zone is correctly set in the Automation Server before generating the certificate. Regarding external CA certificates In step 8 below, it's shown how to generate a self-signed certificate. It might be that it's required to use an external CA certificate issued by a trusted issuer e.g. Verisign. All X509 certificates are supported. The format of the certificate must be PEM (as opposed to DER, PKCS7 or PKCS12). More about certificate types here. SBO currently only supports certificates using the PEM format which is the most common. If the external CA certificate is delivered in a container format (such as .pfx) it must be extracted before it can be used in SmartStruxure. More about extracting certificates here. Importing or generating a certificate Log in to Workstation clicking "Trust certificate" Navigate to the control panel Click on "Security Settings" Click on "Certificates" If you see a message saying that a secure communication protocol is not in use, it means that one or more AS's are communicating with the ES using the TCP port (4444) rather than https. In order to manage certificates for all servers in one operation, you need to change the communication ports. Click on "Configure communication settings" to do that. - and change the protocol to HTTPS and the port to 443 Back in the certificates settings, select one or more servers (in this example just the ES) and click "Manage Certificate" Select a certificate type to add. Unless a certificate is bought from a third party provider, select "Generate certificate" which will make a self-signed certificate. Enter a name, tick "Use IP/DNS..." and select a date when the certificate will expire as a minimum, and fill out more info if needed. Click "OK".  NOTE: Do not exceed year 2060 in the "Valid to" field, doing so will result in a certificate expired error when trying to apply the certificate. Select the certificate just created and save   Installing a certificate through Workstation Close Workstation (just logging out is not enough) Open Workstation and log in using the IP address or DNS name - never "localhost" as that name will not match the certificate. Now you will be able to tick "Always trust this certificate" as the name (IP address or DNS name) in the certificate matches the server you are logging on to. Tick the box, and click "Trust Certificate". Click "Yes" to confirm the installation of the certificate Now you will not get the security warning when logging on Installing a certificate through a browser Access the server using Internet Explorer (important) entering the https address (e.g. https://localhost) Click on "Continue to this website" Click on the "Certificate error" field next to the address bar Click on "Install certificate" Select "Trusted Root Certification Authorities" Click next and ok Close the browser Now you can use both Internet Explorer, Google Chrome and FireFox to access the server from Webstation using https and not get the warning If the certificate fails to install and be trusted properly, it might be because you need to manually select which physical storage to add it to. Refer to the following discussion

Issue When attempting to downgrade an AS / ASP over IP or the direct connect USB cable, the new firmware fails to complete the install. Product Line EcoStruxure Building Operation Environment Automation Server (AS) Automation Server Premium (ASP),  Cause When installing a a "New Database" in to an AS or ASP, it first needs to clear out what is in the controller and then load the firmware with a blank database. This process may require DFU mode to achieve the install.  Resolution To downgrade an Automation Server or Automation Server Premium to an older version of software, put the controller in to DFU mode before beginning the direct USB download of a new database. To put controller in DFU mode, attach the Device Administrator to the AS via USB and press the reset button on the front of the controller 3 times in rapid succession. Note: The IP address of the controller will be reset to default. (192.168.1.99) Changing the version between v1.8 and the current version can often be achieved with a DFU reset, however the DFU reset clears out the history of the device which can be an advantage.

Issue How can I troubleshoot a communication issue with the Modbus protocol Is there a log available within the AS or ES that shows the Modbus communication between Modbus devices Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Building Operation Enterprise Server Cause When troubleshooting Modbus issues in an AS or ES it can be helpful to see the communication between devices to help identify this issue. The trace log within both server types is available and is configured as described below in the resolution. Resolution Open Workstation and navigate to [AS/ES name]/System/Modules/Trace/Loggers/nsp/nsp.pin. Right-click "nsp.pin.modbus" and choose Properties. Under Level, change from "Information" to "Debug", then click ok. In EBO 7.0 and higher, "Debug" will report 1 line per transaction, where "Trace" will report 8 lines for the same transaction. In EBO 7.0 and higher, instead of logging all Modbus with "nsp.pin.modbus," you can log separately Modbus TCP and Modbus Serial using either "nsp.pin.modbus.CommunicationLayer.ModbusCommsLogger.Serial" or "nsp.pin.modbus.CommunicationLayer.ModbusCommsLogger.TCP" Let it run a few minutes. If there are some user input needed to recreate the Modbus issue, then perform these steps now. Retrieve the log by right-clicking [AS/ES name]/System/Modules/Trace/TraceSettings and choose Trace settings->Get trace log.  Save the log file. A useful tool available on the Community, the Modbus decoder can be used to assist in viewing/debugging the Modbus trace log file information saved in the previous step. Once debugging is complete remember to change log level back to "Information" (reverse of step 3). Note: If the ES or AS is reset, i.e. cold started or warm started, the log level will return to 'Information', so if further increased logging is required, the procedure will need to be repeated. Note2: From v6 (2024), adding the trace below can be helpful for Modbus RTU /[ASName]/System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.sport/nsp.pin.sport.DeviceRS485   Here is a video showing the above process. 

Issue The SUM Alarm does not generate an alarm when an Automation Server goes offline 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 Cause The online status of the Automation Servers needs to be monitored so that an alarm can be generated if any of them go offline. Using the following configuration does not work. 1. Create a sum alarm 2. Add Source and set to AS path (e.g /SWXnetwork/servers/AS1). Replacing AS1 with a * makes no difference 3. Add System alarm ID and set to "Server Offline" 4. Add Alarm State and set to "Selection as required" Resolution Options that do work Option 1 System Alarm ID = Server offline Alarm Text = */Servers/* Alarm State = Alarm and Alarm Acknowledge - (Select as required). Option 2 System Alarm ID = Server offline Alarm State = Alarm and Alarm Acknowledge - (Select as required). Source Name = AS1 or AS*   Option 3 System Alarm ID = Server offline Alarm State = Alarm and Alarm Acknowledge - (Select as required). Source = /SWXnetwork/System/Server Communication/To/AS* - (As the alarm is in the ES, the path comes from the ES).

Issue How can the MNB-1000 be set back to factory defaults? Product Line TAC IA Series Environment I/A Series MNB-1000 Cause Reconfigure the MNB-1000 Resolution Do the following: Set all of the dip switches on the MNB-1000 to the ON position (all ones)  and cycle power.  Wait until the controller completely boots up (solid green status light), then change dip switches from all ones back to the desired address. Cycle power again. Note - Setting the MNB-1000 back to factory defaults will delete the installed application.

Issue Configuration of multiple BACnet BBMD's over several subnets Product Line Andover Continuum, EcoStruxure Building Operation Environment Bacnet BBMD Cause Bacnet Broadcast communication through IP router Resolution Configuration of multiple BBMD's over several subnets: INCORRECT METHOD For example if there are 4 subnets on the same B/IP (BACnet IP Network): Subnet 1: Workstation setup as a BBMD with an entry in the Broadcast Distribution Table for each BCX Subnet 2: BCX setup as a BBMD with an entry in the Broadcast Distribution Table for itself and the Workstations BBMD Only. Subnet 3: BCX setup as a BBMD with an entry in the Broadcast Distribution Table for itself and the Workstations BBMD Only. Subnet 4: BCX setup as a BBMD with an entry in the Broadcast Distribution Table for itself and the Workstations BBMD Only. The BCX's do not reference any points from each other. Since there is no data sharing between the BBMD's, one might think that in each BCX's Broadcast Distribution Table that there would only be a need to add one entry for the Workstations BBMD. Sounds like with this setup we'll reduce traffic by only adding the one entry in each BCX's BBMD Broadcast Distribution Table. The above scenario could in fact slow down a network and cause unnecessary traffic.   The supported method is that every BBMD on a B/IP network have the same routing tables(better known as the Broadcast Distribution Table) as in the below configuration. CORRECT METHOD For example there are 4 subnets on the same B/IP (BACnet IP Network). Subnet 1: WS BBMD with an entry in the Broadcast Distribution Table for itself and all BCX's setup as BBMD on the same B/IP. Subnet 2: BBMD with an entry for all BBMD's(including self) in the Broadcast Distribution Table on the same B/IP. Subnet 3: BBMD with an entry for all BBMD's(including self) in the Broadcast Distribution Table on the same B/IP. Subnet 4: BBMD with an entry for all BBMD's(including self) in the Broadcast Distribution Table on the same B/IP. The entry below can be found in the BACnet Standards 2004:   J.4.3 BBMD Concept Each IP subnet that is part of a B/IP network comprised of two or more subnets shall have one, and only one, BBMD. Each BBMD shall possess a table called a Broadcast Distribution Table (BDT) which shall be the same in every BBMD in a given B/IP network.

Issue Unable to compile a b3 Script program if there is a bind to the priority array of a commandable property. How to command an object at a particular priority in b3 Script program. Product Line EcoStruxure Building Operation Environment b3 WorkStation Automation Server Cause Because of historical reasons (that are outside the scope of this article) in the evolution of the b3 firmware, binding to the priority array of an object within a Script program in the b3 is NOT supported. Resolution To command an object from a Script program in the b3 at a specific priority the WriteProperty command MUST be used. NOTE If the b3 firmware is 4.500064 then priority 10 will always be set rather than the one specified in the WriteProperty command. This was fixed in v4.500076, it is best to use the the latest firmware

Issue It is not clear how to replace an existing AS with a new AS-P Product Line EcoStruxure Building Operation Environment Automation Server (AS) Automation Server Premium (AS-P) First detected in version 1.7 Cause Detailed instructions on how to replace an existing AS with a new AS-P are needed Resolution WebHelp references Automation Server Replacement Using Restore Automation Server Replacement Using Restore Workflow Overview Main differences between an AS and an AS-P: In the AS-P, the RS-485 ports have been re-located to the top. The AS-P has 2 Ethernet ports; port 2 can be used as a switch only as of SBO version 1.81. AS-P device USB port format changed to mini USB. Operator Panel port has been removed. Hardware factory reset has been removed. AS-P uses pluggable connectors for field buses. (not shown in picture above) Consider the power consumption. AS-P requires 10 watts, while the Automation Server only required 7 watts. Preparations In preparation for replacing an Automation Server with an AS-P the following considerations must be made: Power consumption Since the AS-P consumes three more watts than the classic Automation Server, the power budget needs to be reviewed to check whether an additional power supply and/or rearrangement of the current configuration is needed, if the configuration includes IO modules. Terminal base The terminal base for the classic Automation Server can be used with the new AS-P after removal of the upper terminal block. Note though that all field buses wiring has to be moved to the pluggable connectors used with the AS-P. RS-485 field bus re-wiring Since the RS-485 ports and connectors have been relocated, the termination at the server of any field bus located on those ports will need re-wiring. Also, the physical specification of the RS-485 port is changed in the AS-P, so review whether the termination resistors needs to be replaced. Refer to Configuration Selection for Generic RS-485 Network Devices AS-P firmware Unlike the classic Automation Server, the AS-P ships from the factory with no firmware installed. Make sure to procure the appropriate Device Administrator firmware to install in the unit. First version that supports the AS-P is 1.7. Note once again that the USB port format in the AS-P is mini USB, so procure the appropriate USB cable. Backup file Make a backup of the classic AS to be replaced, the AS-P will restore from a classic AS backup but this is a one way process, the classic AS will not restore from an AS-P backup file. If the classic AS is running an older version of firmware, it will have to be upgraded first to at least 1.7.2. Power budget review Since the AS-P consumes 10 watts of power versus 7 watts for the classic Automation Server, it is necessary to review the power budget to ensure there is enough power for the AS-P, if the Automation Server being replaced is hosting IO modules. One power supply (PS-24V) can supply 30W. The following table shows power consumption for the different device types Device Power AS-P 10 AS 7 DO-FA-12-H 1.8 DO-FA-12 1.8 DO-FC-8-H 2.2 DO-FC-8 2.2 DI-16 1.6 RTD-DI-16 1.6 AC-4 11.1 UI-16 1.8 AC-2 5.5 AO-8-H 4.9 AO-8 4.9 AO-V-8-H 0.7 AO-V-8 0.7 UI-8-AO-4 3.2 UI-8-AO-4-H 3.2 UI-8-DO-FC-4 1.9 UI-8-DO-FC-4-H 1.9 UI-8/AO-V-4 1.0 UI-8/AO-V-4-H 1.0 In case one or more additional power supplies are needed, refer to the example given in last part of this article.   Note: The following "replacement procedure" applies to SBO 1.7.x, 1.8x, 1.9x, EBO 2.0x and 3.0.x and 3.1.x. The AS-P must be running the same version as the original AS backup. The AS was no longer supported from EBO 3.2.x. If the site needs to take the AS-P to EBO 3.2 or later, the following should be followed at the AS supported version, then once the AS backup has been restored to the AS-P, the AS-P can be upgraded further, following the supported upgrade path, which can be found in the release notes for the specific EBO version.   Replacement procedure The following procedure assumes the classic Automation Server is being replaced with a brand new AS-P from the factory If the Automation Server is hosting IO modules then perform the steps in the 'Power Budget' section below before going to the next step. Perform pre-maintenance procedure per site requirements, i.e. put equipment in hand control mode etc. Pull out the classic Automation Server from the terminal base. The hardware is designed for hot swapping so there is no need to power down the system. Remove the terminal block from the terminal base as indicated above. Insert the AS-P in the terminal base. Connect Device Administrator to AS-P via USB and install a new database on it. You may want to check the 'Set time on device' check box to initialize the time in the AS-P since its current time is most likely at default if this is a brand new unit or a unit that has been powered down for a while. Using Device Administrator set the communication parameters of the AS-P (IP address etc) to match the settings of the classic Automation Server being replaced. Connect Ethernet cable from network switch to Ethernet 1 port on the AS-P. If a hotfix was installed on the Automation Server that is replaced, apply any hotfix needed to match the version of the firmware in the AS-P to the version of the backup from the Automation Server. Since the AS-P should now be able to communicate over IP the application of any HF can be done either over USB or IP. Using WorkStation, log in directly into the AS-P and restore the backup from the classic AS. Insert pluggable connectors for field buses. If there is an Enterprise Server, log into Enterprise Server from WorkStation and verify the newly swapped AS-P is online. Verify IO modules (if any) are online. Verify field devices (if any) are online. Return the system to software control per site requirements. Verify the system is operating correctly then perform a backup of the AS-P. Power supply addition example Consider the following system If we do the math, the power consumption of this system is 29.8 watts. To avoid exceeding the capacity of the existing PS we need to add an additional PS to the configuration before we replace the Automation Server with an AS-P. In order to maximize the use of the capacity of the first PS we will add a new PS at slot #7 and move the UI8AO4 IO module from slot #7 to slot #8.   Steps Disconnect the UI8AO4 IO module making sure it powers down. It is necessary that any IO modules being relocated on the IO bus are powered down so that they 'forget' their current module IDs. *** Logon to the Automation Server, make sure UI8A04 shows offline then edit the module and change its Module ID from 7 to 8. Insert power supply at slot #7 Attach the UI8A04 after the new PS (slot #8), when it powers up it will obtain its new Module ID (8) from the Automation Server. Last, if the module’s name contains the ID (Slot07:UI8AO4) it may be a good idea to rename it using the new ID to avoid confusion. (Slot08:UI8AO4) *** It is absolutely necessary that all the modules that will change IDs be powered down, if there are multiple power supplies in the chain make sure to power down all power supplies that are supplying power to any modules that will change slot #. When removing or inserting IO modules or handling S-Cables, care should be taken not to bend or otherwise damage the pins that connect the module to its IO terminal base, any damage to the pins may cause the module address to shift.   Tip There is a tool on the community (SBO xbk Analyzer) that can be used to automatically calculate the power budget from a backup of the AS/AS-P. Here is the power budget report generated from the tool after addition of second power supply at slot #7 before replacing the classic AS with an AS-P. The total power consumption is 29.8 watts but we have increased the power capacity of the system to 60 watts with the addition of the second power supply.   The instructions above are available as a PDF: Replacing a classic AS with AS-P

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 Unable to configure the schedule in SE8000 series thermostat. Product Line EcoStruxure Building Expert, Field Devices Environment SE8000 Cause The system is not following building occupancy and operation as needed Resolution Tap and hold the top middle of the screen and tap on lower right arrow of page 1/2 setup. There are seven different schedule setting screens, one for each day of the week. Each day can have different scheduled events. Options The options settings allow the Room Controller to function in Occupied or Unoccupied. Occupancy Command Local occupancy: occupancy is determined by local PIR or schedule, as configured under Occ. Source from the configuration menu. Schedule Type 7 days: Independent scheduling for each day 5+1+1 days: Weekdays scheduling and Independent Weekend scheduling for Saturday and Sunday 5+2 days: Weekdays scheduling and Weekend scheduling

Issue The following Popup window is displayed when attempting to open WorkPlace Tech. WPTech Unable to load WorkPlace Tech Ribbon for Visio. There was a problem loading the WorkPlace Tech Fluent Ribbon for Visio, therefore, it will be unavailable. Product Line TAC IA Series Environment Visio 2010, 2013, 2016, and 2019 WorkPlace Tech Tool release 5.8 or later Cause If Visio crashes when a third-party ribbon bar function is in use, Visio may lockout that ribbon bar, believing that something on that ribbon bar caused Visio to crash.  In this case, a menu function, selected from the WorkPlace Tech (WPT) ribbon bar was being processed at the time Visio crashed, therefore Visio locked out the WorkPlace Tech ribbon bar. This is a system protection mechanism built into the ribbon bar handler in all Microsoft Office applications including Visio.   Resolution To re-enable the WorkPlace Tech ribbon bar, perform the following steps: Open Visio.  NOTE: Open Visio, not WorkPlace Tech. Select Options from the File menu. From the menu in the Visio Options window, select Add-ins At the bottom of the window, you will see a field that says 'Manage:' with a selection box after it, select 'Disabled Items' and then click the [Go] button. In the 'Disabled Items' window, select 'WorkPlaceTech.VisioRibbon' then click the [Enable] button. Close the open Visio windows and sub-windows. After closing Visio, the WorkPlace Tech ribbon bar will be available in WorkPlace Tech.  

Issue Modbus devices such as power meters require the monitoring of values that are held in a 64-bit unsigned integer data format.  I/A Series G3 Modbus proxy points cannot be configured to directly support the 64 bit register format. Environment I/A Series G3, Modbus, Modicon, Schneider Electric PowerLogic PM800 Series Power Meters Cause Modbus devices such as power meters require the monitoring of values that are held in a 64-bit unsigned integer data format.  I/A Series G3 Modbus proxy points cannot be configured to directly support the 64 bit register format. Resolution As a workaround, the Modbus proxy points can be configured to poll the register as four integers and convert or combine the four integers to a single unsigned 64-bit value.  NOTE: that all four registers will need to be polled in a single message.  The following are two examples that can be used to read and convert unsigned 64-bit values.  The first example converts a Modicon power value with data type UINT64.  The second example converts a Schneider Electric PowerLogic P800 Series Power Meter with data type MOD10. Example 1 (Modicon UINT64):  The memory map below indicates the Total KWh+ value is presented in an unsigned 64-bit data format (four Modbus integers) starting at physical address 0500h. Create four Modbus Client Numeric Points under the Modbus Async Device Points container. This can be done by copying four objects or by using the Modbus Client Point Manager. Configure the points to read the integers that represent the value required. For example, the Modicon address 301280 (0500h) would be configured as follows. NumericPoint1 > Data Address (Address Format Hex, Address 500, Reg Type Holding, Data Type Integer) NumericPoint2 > Data Address (Address Format Hex, Address 501, Reg Type Holding, Data Type Integer) NumericPoint3 > Data Address (Address Format Hex, Address 502, Reg Type Holding, Data Type Integer) NumericPoint4 > Data Address (Address Format Hex, Address 503, Reg Type Holding, Data Type Integer) The values will attempt to poll and still will most likely be in fault as the value must be read in the same message request. This is where a Device Poll Config Entry will be required to configure the data to be read in a single message. The Device Poll Config Entry can be configured using the Learn Optimum Device Poll Config or by manually adding a Device Poll Config Entry to the Device Poll Config container. For this example, the Device Poll Config Entry would be setup with the start address of Hex 500, Data Type Holding Register, Consecutive Points To Poll 4 and Read Group Size 1. The consecutive points to poll may can be adjusted to read multiple UINT64 registers depending upon the maximum number of registers allowed by the Modbus device. Otherwise additional Device Poll Config Entry objects can be added and configured. Converting or combining the values can be performed in a couple of ways. The first is by using standard math logic (see image below). The inputs are multiplied by the correct binary multiplier and added together. The constants to use for each object are as follows. Multiply = 65536.0 Multiply1 = 4294967296.0 Multiply2 = 281474976710656.0   The second method is to use a program object and connect the four integers to the inputs. The same calculation as previous method is performed within the program.  The ModbusIntegersToUINT64 program object can be copied into a station database. Example 2 (PowerLogic P800 Series Power Meter MOD10):  The memory map below indicates the Energy (Real Out) value is presented in an unsigned 64-bit data format (four Modbus integers) starting at physical address 1708. Create four Modbus Client Numeric Points under the Modbus Async Device Points container. This can be done by copying four objects or by using the Modbus Client Point Manager. Configure the points to read the integers that represent the value required. For example, the address 1708 would be configured as follows. NumericPoint1 > Data Address (Address Format Decimal, Address 1708, Reg Type Holding, Data Type Integer) NumericPoint2 > Data Address (Address Format Decimal, Address 1709, Reg Type Holding, Data Type Integer) NumericPoint3 > Data Address (Address Format Decimal, Address 1710, Reg Type Holding, Data Type Integer) NumericPoint4 > Data Address (Address Format Decimal, Address 1711, Reg Type Holding, Data Type Integer) The values will attempt to poll and still will most likely be in fault as the value must be read in the same message request. This is where a Device Poll Config Entry will be required to configure the data to be read in a single message. The Device Poll Config Entry can be configured using the Learn Optimum Device Poll Config or by manually adding a Device Poll Config Entry to the Device Poll Config container. For this example, the Device Poll Config Entry would be setup with the start address of Decimal 1708, Data Type Holding Register, Consecutive Points To Poll 4 and Read Group Size 1. The consecutive points to poll may can be adjusted to read multiple MOD10 registers depending upon the maximum number of registers allowed by the Modbus device. Otherwise additional Device Poll Config Entry objects can be added and configured. Converting or combining the values can be performed in a couple of ways. The first is by using standard math logic (see image below). The inputs are multiplied by the correct binary multiplier and added together. The constants to use for each object are as follows. Multiply = 10000.0 Multiply1 = 100000000.0 Multiply2 = 1000000000000.0 The second method is to use a program object and connect the four integers to the inputs. The same calculation as previous method is performed within the program.  The ModbusIntegersToMOD10 program object can be copied into a station database.

Issue Documentation on the MSC-MPC Microsmart controller and its associated modules. Product Line TAC I/A Series Environment Microsmart controller MSC-MPC MPC-4AO MPC-8AI MPC-2PO MPC-SSR MPC-4CO Cause Obsolete controller Resolution Click here to view the installation instructions on the MSC-MPC. Click each associated module part number below to view its installation instructions: MPC-4AO MPC-8AI MPC-2PO MPC-SSR MPC-4CO

Issue Email notifications from 3rd party email account such as Gmail, Hotmail, Yahoo SMTP issues Event notification Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with any of the following: AS, ES, Reports Server Cause Sending notifications to Gmail, Yahoo mail, Hotmail, or other outside email account. Wanting to use other SMTP than Schneider Electric E-mail Server: if wanting to setup an ES or AS to send email notifications with third party SMTP, an Exchange server using port 25 supports the notifications. In release 1.7.1 and earlier though Gmail, for example, suggests port 465 and 587, the workstations alarms that the email can not be sent since it cannot connect to email server. The problem is with the Gmail-account and often other 3rd party email providers both public and private, Google requires that you connect with SSL, which have been missing in the requirements and therefore these releases do not have this functionality. In release 1.8.1 and later, you can send emails not encrypted or encrypted using either the TSL or the SSL protocol. You can select one method for the primary email server and another method for the secondary email server. The Schneider Electric Email Server does not support encrypted emails. When logging on to the email server, the user is authenticated using an authentication protocol. If no user name is specified, no authentication protocol is specified. If a user name is specified, the SmartStruxure server tries to authorize the user using the CRAM-MD5 protocol. If the first authentication fails, the SmartStruxure server tries to authorize the user using the LOGIN protocol using the CRAM-MD5 protocol. Resolution In Email Notification put the 3rd party email address such as yourname@mailprovider.com. AS and ES will use the Schneider Electric SMTP server or the POP server of your choice to send the email notification. For multiple emails, check Multiple Email Addresses for Email Notifications or Alarm Recipients. Sometimes the mail is put in the Spam folder for the recipient. Check there and change settings to Not Spam. Installing a valid SSL certificate for the Enterprise Server to allow SSL operation is not planned in a future version. Currently, the default certificate does not identify the system and is not trusted, but nevertheless enables SSL operation. ESMTP (Extended) is not supported through current release. Base64 SMTP authentication is not supported. Wanting to use SMTP other than Schneider Electric E-mail Server: An Exchange server or SMTP server which supports POP and uses port 25 supports AS and ES Notifications. Other servers which would require the setting of Primary/Secondary E-mail server fails to login to SMTP Server require an encrypted (SSL/TLS) connection which is not supported in Struxureware Building Operation versions up to and including 1.7.1. A solution is to use an SMTP proxy on the ES or another computer on the network that will handle the TLS/SSL authentication. Release 1.8.1 and later support TLS and SSL for email authentication natively. Using SmtpProxy on an Enterprise Server SmtpProxy is a small freeware application that listens on a port you choose; the default port is 25. When SmtpProxy detects a connection on this port, it does the following: Connects to the SMTP server you configure (GMail / Microsoft Live Mail / any other SMTP server) Starts an encrypted connection with the SMTP server Returns the connection information to the ES After the initial connection is established, SmtpProxy acts as a middleman. Any SMTP data received from the ES is forwarded to the SMTP server and any data returned from the SMTP server is sent the ES. SmptProxy runs as a Windows service so it can be installed on a LAN server and used by multiple devices such as AS. Note that SmtpProxy does NOT login to the SMTP server but rather credentials are passed through from the ES or AS. Note: SmtpProxy is a third party application and therefore no support is provided by Schneider Electric. Installing SmtpProxy SMTPProxy can be downloaded from http://smtpproxy.codeplex.com/ The download is a Windows Installer (MSI) file that can be used to install SmtpProxy on any machine that supports the .NET Framework v4 – Client Profile. Configuring SMTPProxy for Gmail SmtpProxy is configured using a config file. A sample config file is installed with SmtpProxy, this is a plain text file that can be edited with Notepad. Create a copy of the sample config file and rename it to: On 32 bit machines: C:\Program Files\SmtpProxy\SmtpProxy.exe.config On 64 bit machines: C:\Program Files (x86)\SmtpProxy\SmtpProxy.exe.config The following items can be configured with SmtpProxy’s config file: SmtpProxy can write a log of all its activities. The default file to write the log file to is SmtpProxy.trace.log. SmtpProxy can log several different types of activities. You can control what is written to the log file by setting the log switches. By default, they are set to Off so nothing is written to the log file. Valid switch values are Off, Error, Warning, Info, and Verbose with each one providing more information than the last. Once you have SmtpProxy working, you should turn logging Off. The Url to the SMTP server. Default is smtp.live.com. The SMTP server port. Default is 587. The port to listen on. Default is 25. Scroll to the end of the config file and locate the section SmtpProxy.Properties.Settings section and find the string mail.live.com Edit this to smtp.gmail.com After modification, you must restart the Smtp Proxy service from the services control panel for the new settings to take effect. Configuring ES to use SmtpProxy Right click on the Server in the tree and select Properties then click the Email tab Select Primary/Secondary E-Mail Server Enter Sender E-mail (e.g. Mysite@gmail.com) Under Primary E-Mail Server Settings enter Host: localhost (or 127.0.0.1) Enter the users account information. User name: e.g. gmailaccountname@gmail.com Password: MyPassword Confirm: MyP

Issue Not able access a new MNB-1000 via its default IP address. It will not respond to when pinged. Product Line TAC IA Series Environment WorkPlace Tech all versions, WPT Version 1.50E and later Cause The ability to ping the MNB-1000 controller was removed starting in Firmware version 1.50E. All MNB-1000s are shipped with IP port disabled. Resolution Starting with firmware revision 1.50E, the ability to ping a MNB-1000 controller was removed; so any MNB-1000 controller at or above firmware Revision 1.50E will not respond to a ping. Reference Unable to ping the MNB-1000 (Plant Controller) using firmware Revision 1.50E or higher for further details. All new MNB-1000 controllers are shipped from the factory with their IP and MS/TP ports disabled. The Ethernet port is the only port enabled. The MNB-1000 controller must first be accessed via its Ethernet port. Once gaining access, its BACnet/IP port can then be enabled.  Note: Both BACnet/Ethernet and BACnet/IP ports should not be enabled at the same time. So if BACnet/IP is being used and once the BACnet/IP port is configured and enabled, then disable the Ethernet port. NOTE:  Firmware 1.537 made the MNB-1000 visible via the ping command again.

Issue During some circumstances, an additional license may be needed for testing/evaluation/demo purposes. Product Line TAC Vista Environment TAC Vista 5 Cause During some circumstances, an additional license may be needed for testing/evaluation/demo purposes. PSS is creating demo license files with a monthly validity. Resolution Monthly demo license files are made by the Malmö PSS team, and may be requested from PSS. The "TS_OK" demo file is used for "Remote Desktop" applications, giving access equivalent to the demo file available for download from the The Exchange Download Center, usually valid until the end of the month. Additionally, a OPC Server license file with the same validity is also available by request. Evaluation license for TAC Vista 5.1 Demo TS License TAC Vista 5.1   More information can be found in Where to find Evaluation license for TAC Vista and Struxureware Building Operation.

Issue There have been questions about how the new EcoStruxure Building Operation 2.0 demo license works with the new scalable pricing structure. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 2.0 and up All previous builds of SBO 1.9 and below Cause Understanding what the EcoStruxure Building Operation evaluation license will allow to function in the newer versions of the product.  Resolution The EcoStruxure Building Operation Evaluation License is a temporary license used when a database is being brought online before the permanent license has been deployed or on engineering laptops. All authorized Schneider Electric employees and partners can download the file from the Exchange Extranet. The file is updated every quarter as each one has an expiration date. The functionality of the demo license has not changed in version 2.0 and newer. This license file will still allow functionality and engineering of a database to take place as long as the file is valid. The only difference is the new warning banner that will be present until permanent licenses are installed.  Note: With the new scalable pricing starting in version 2.0, once the evaluation license is removed from the site, a license is needed for each Automation Server attached to the Enterprise Server.  More information on the Scalable Pricing structure can be found in EcoStruxure Building Operation Licensing and Scalable Pricing Info. 

Issue Trouble synchronizing the time of the Automation Server or Enterprise Server to a NTP server or between each other Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Enterprise Server EcoStruxure Building Operation Automation Server Cause The Enterprise Server and the Automation Server (ASP/ASB) do not synchronize time to each other, they must use an NTP server for synchronization Resolution The information below is mainly concerned with synchronizing the time setting but not the actual time.   Overview To synchronize the server times an NTP Server will be required, they do not synchronize time with each other. A common misconception is that the Automation Servers sync time with the Enterprise Server via server-to-server communications. To find an external NTP server consult support.ntp.org . Alternatively, an existing internal NTP server can be used or consult Setting up a Local / Internal NTP Server to configure the Enterprise Server computer as a time server The time settings on the Enterprise Server are configured through the operating system settings on the computer where Enterprise Central is installed.  EcoStruxure Building Operation cannot be used to configure the NTP server for the Enterprise Server. Please refer to Network Time on WorkStation, Enterprise Server, and Enterprise Central To find the Network Time Protocol (NTP) configured on a WorkStation, Enterprise Server, or Enterprise Central computer open a command prompt and enter w32tm /query /peers. If configured the peer NTP server(s) will be listed If you need to ensure an NTP server is actually running on certain IP or DNS address, please reference Ensure IP or DNS address is valid NTP server The time settings on the Automation Servers can only be configured via the Workstation. As per the image they can be configured to look at an NTP server (1) or set manually (2). For synchronization, they must use an NTP Server. Please refer to  Network Time Server on an Automation Server on Webhelp Starting in version 1.5, the time adjustment depends on how much the Automation Server drifts from the NTP server. The faster the Automation Server drifts, the more frequently the time is updated.  Please refer to How often will an Automation Server ask the NTP server for the time?  If the time server is a URL, such as time.nist.gov, then it is critical that a Primary DNS is set for each Automation Server, and possibly a Secondary DNS via Device Administrator. Without a DNS, the Automation Server will be unable to resolve the URL to an IP address. Please refer to Configuring the Automation Server IP Address on Webhelp The time displayed for a server in Workstation (Properties -> Basic) will reflect the time zone of the local computer that Workstation is installed on. All events and alarms will be automatically modified to match the time of the workstation that was used to log into the server. The "Server time" will represent the date and time of the server adjusted to client local time zone, while the fields below "Server time" represent the settings of the Automation Server.   How to synchronize date and time settings on multiple Automation Servers   IMPORTANT: Only the time settings are synchronized via the Lead/Shadow configuration, the time itself IS NOT synchronized via the Lead/Shadow but rather by all servers synchronizing with the configured timer server.   The synchronizing of multiple Automation servers can be achieved with a lead/shadow relationship. The primary and secondary network time server settings for connected shadow Automation servers are defined on the Enterprise server. Setting up the Primary and secondary time servers in the Enterprise Server only passes those configuration settings to the AS controllers, it does not send the actual time and date value.   Select the Enterprise server (1), click the Date & Time tab (2), select Enable (3) and enter the Primary time server (4) and, if used, the Secondary time server (5) the Automations Servers will use. Ensutre the time zone for the Enterprise Server is set correctly (6).   Save the settings  From EBO version 2.0 all Automations Servers are automatically configured to shadow the date and time settings configured in the Enterprise Server. To verify this expand the System folder of an Automation Server and select Time Settings -> Date and Time (1). Observe the Date and Time are Shadow-Read only (2), replicating the Enterprise Server settings. Attempting to change any of the settings, other than the Lead object (3), will result in an error. All the Automation Servers will be 'looking' to the same Primary (4) and Secondary time servers, i.e. they will all receive the same time and be synchronized Similarly, select the Time Zone (1) of the Automation Server in the System Tree; this will also be shadow-read only (2). The lead object is set to the Time Zone on the Enterprise Server (3) Before EBO version 2.0 the Automation Servers were not automatically set to shadow the Enterprise Server settings but this could easily be achieved en masse using Search . In the Search box in the top right corner of the Workstation, type "Date and Time" and click Search (1) to find the date and time object of all connected servers. In the Search view select the servers (2) that require their Date and Time settings synchronized to the Enterprise Server, the Enterprise Server does not need selecting. Select the Time tab (3) and then click the triple dots (4) to navigate to and select the Date and Time object on the Enterprise Server (5)   You may need to stop and start the Enterprise server to get the configuration settings to pass down to the shadow Automation servers Note: To set up synchronization of the time zone settings follow the above search steps for date and time but search on Time Zone Tip/Tricks To see the time of on the Enterprise Server and multiple Automation Servers use the Search to find the Date and Time object (1). Individually select each server (2) and then drag the Date and Time object (3) into the Watch Window (4) It is the Automation Server that initiates the synchronization. To check the Automation Server communication settings select the Automation Server (1) and in the Communication tab (2) select the Enterprise Server (3) and make sure the Automation Server has the correct IP address (4) To check the Enterprise Server communication settings select the Enterprise Server (1) and in the Communication tab (2) select each Automation Server (3) and make sure the correct IP address is specified for each Automation Server (4).  If a firewall exists ensure that the ports are open so the Automation Server can connect to the Enterprise Server. Please search for the EcoStruxure Building Operation IT Reference Guide on Exchange for details Further Information Release 1.2.0 and higher Until the time is set, b3 data will not update in the Watch Window Until the time is set, BACnet COV will not be functional Automation Server time does not synchronize directly with the Enterprise Server. Instead, all servers can synchronize to the same accessible time server To adjust the Automation Server time, time zone, and DST, access to the Automation Server is through a WorkStation

Issue When trying to run webLauncher.exe, an unknown error occurs. An error popup with a red X appears, and the Application will fail afterwards.   Product Line TAC IA Series Environment I/A Series N4 Enterprise Server I/A Series N4 Jace 8000 / 9000 Cause With a recent migration to Web Launcher in 4.14 (launcher version 24.14.0.2), a bug has been reported in new installations. Any computer that is missing a folder named niagara storing the launcher's configuration info will encounter this issue. The folder is located, by default, in the following spot: C:\Users\<Windows username>\AppData\Local\niagara Resolution Go to the location of the launcher executable, and there will be a file named webLauncher_debug.exe. Running this once will create the necessary directory and the Web Launcher will be able to function normally. The default location of the executable is: C:\Program Files\Niagara Web Launcher This issue is known internally at Tridium as defect NCCB-68211, and it will be resolved with the release of Web Launcher 24.14.0.3 and later releases.