Building Automation Knowledge Base

Issue BACnet COV subscription system Product Line EcoStruxure Building Operation Environment BACnet Settings COV subscriptions v1.7 and earlier Cause A site will have a problem with the amount of traffic because of misconfigured COV Increments. The problem is that Building Operation, the  ES and AS resubscribes to values every 10 seconds and one by one. So for example: hh:mm:ss 00:00:00 Value1 00:00:10 Value2 00:00:20 Value3 00:00:30 Value4 ... 05:00:00 Value1800 If you have more than 1800 subscriptions the ES or AS is not able to do all subscriptions in 5 hours.   5 hours is used because Building Operation subscribes to the values with a lifetime of 5 hours.   Resolution BACnet COV subscription system is not influenced by the requested transfer rate in the edit bindings system (Subscriptions using BACnet). That is used in the case where the external device does not support COV, and read-property must be used instead. The design in 1.4 and 1.5 simply did not anticipate such large numbers of COV subscriptions. Workaround: 1.Exit Workstation 2. Stop the Enterprise Server Edit using notepad the server.properties file located in "C:\Program Files\Schneider Electric StruxureWare\Building Operation 1.x\Enterprise Server\etc\ Find at the bottom: # Set GenericConsume communication defaults Add the two following lines: NspServer.BACnetPlugIn.COVSubscriptionLifetime entry = 28800 NspServer.BACnetPlugIn.COVTimerPeriod entry = 5 Save your changes and close the server.properties file. This changes the default values from 5 hours to 8 hours and 10 seconds to 5 seconds. NOTE From version 1.8 the BACnet Interface manager (/Server 1/System/Interface Manager/BACnet) provides access to these settings (COV subscription lifetime (default 8 hours) and Server COV renew rate(default 5 seconds)) The settings will be controlled via the Enterprise Server if connected.

Issue Extended Logs have stopped updating on the Enterprise Server. Product Line EcoStruxure Building Operation Environment Extended Trend Logs Cause Extended Trend logs have been set up on the site for some time and have operated correctly. Now some of them have stopped updating.  Resolution This issue can be caused by a Server backup being restored. Trend logs and Extended Trend logs are allocated sequence numbers, and if the sequence numbers do not follow the correct sequence, the Extended Trend log may not update. To confirm that this is the issue; Trend Log. Navigate to the Trend log and open it in a "Trend Log List" view. Add an additional column to show the Sequence number. Note the highest sequence number used. Extended Trend Log. Navigate to the Extended Trend log that is referencing the above Trend Log. Open it in a Extended Trend Log properties. Press and hold down the "ALT" key and click where the dot is indicated on the screen shot below, (just below the Basic tab).       This will show some more properties for the Extended Trend Log, the one you are interested in is “Last transferred sequence number”.   If the last transferred sequence number on the Extended Trend Log is higher than the Trend log’s highest sequence number, then that is why the Extended Trend Log has stopped. How can this issue be resolved? Increase the sample interval of the Trend log until it has caught up. The Extended Trend Log will only fetch new records that has a sequence number higher than the last transferred sequence number. So until the sequence has caught up, you will not see any new records in the Extended Trend Log, and only records created after you have caught up in sequence numbers will be fetched. Re-create the Extended Trend Log. The new Extended Trend Log will fetch every record the log has and continue from there, but you will lose the records the old Extended Trend Log had that the log does not have anymore. Backup / restore on the AS. The Trend log will be cleared but the Extended Trend Log will start fetching new records.    

Issue What image formats are supported in a TGML graphic? Product Line EcoStruxure Building Operation Environment EcoStruxure ES, AS Vista Graphic Editor Cause Clarification of supported graphic formats required. Resolution When inserting a picture in a TGML graphic you can select the image file from the following file types: Bitmap, GIF, ICO, JPEG, Metafiles, PNG, TIFF  

Issue Is it possible to use Sysman Alert Server with EcoStruxure Building Operation? Product Line EcoStruxure Building Operation Environment Alarms and Events Cause Customers may wish to send important alarms to duty staff via SMS. Sysman Alert Server is one way of doing this and is easy to configure.  Resolution This is possible. The following document details the setup procedure: Sysman Alert Server with StruxureWare Building Operation The configuration will depend on the setup and location of the SysMan Server, but will generally involve "Write to File" Notifications if the Enterprise Server and Sysman Servers are installed on the same PC, or Emails to the SysMan Server (from Enterprise or Automation Server) More information can be found on Sysman's website. Part Numbers: SysManSMS ALERT SERVER: 900800600 SysManSMS GSM Modem: 900800610 In the UK when ordering please use the below part numbers. SysManSMS ALERT SERVER: 802000 SysManSMS GSM Modem: 100002

Issue Automation Server CPU Specifications Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Basic Cause Automation Server Family CPU specifications are required for projects requirements and specifications. Resolution There are three Automation Server models, each with unique CPU specifications:   Automation Server (AS): The Automation Server (AS) has been withdrawn from sale. CPU: ATMEL AT91RM9200, ARM9 core microcontroller. Processor: ARM920T. CPU Clock Speed: 160 MHz. Automation Server Premium (AS-P): CPU: STMicroelectronics SPEAr1380, ARM Cortex-A9 dual-core microcontroller. Processor: ARM Cortex-A9. CPU Clock Speed: 500 MHz. Automation Server Bundled (AS-B): CPU: STMicroelectronics SPEAr320S, ARM926 core microcontroller. Processor: ARM926. CPU Clock Speed: 333 MHz.

Issue SmartStruxure uses two different function block programs. Menta Editor is used for Xenta programmable controllers while Function block editor is used in the Automation or Enterprise server. The two programs are not interchangeable and do have several differences. Product Line EcoStruxure Building Operation Environment Function Block Editor Menta Editor Cause There are several differences between Function Block Editor and Menta Editor that are important to know. Resolution Download the relevant version of the Function Block Editor and Menta Editor Difference Guide from Exchange. This guide will cover the following topics: An overview of Function Block programming The programming differences Function Block Editor and Menta Editor differences Program Conversion Importing Xenta programmable controller programs Building function block programs to I/Os Binding values Binding values using a binding template Time schedule and alarm blocks Trend logs Overview of Function Block Editor Block differences

Issue Need information on how exactly SmartStruxure checks whether BACnet devices are still online or have gone offline. Product Line EcoStruxure Building Operation Environment Enterprise Server - ES Automation Server - AS BACnet devices Cause Understanding how communication status is verified can help with troubleshooting comm loss issues. Resolution After a device is discovered via the WHO-IS/I-AM service and moved into the SmartStruxure database, SmartStruxure uses the following scheme to check on the communication status of the device. For IP Device The server will send a Read Property message to read the devices's system status*** every minute, as long as a reply is received the device is deemed to be ONLINE. If no reply is received by the APDU Timeout the server will retry up to 3 times, if there is no response the device will be considered to be OFFLINE. For MSTP Device The server listens as the token is being passed around the bus and if a device fails to get the token it will be tagged OFFLINE. For both IP and MSTP Device Once the device is tagged OFFLINE, the server will check on the device once a minute by sending a WHO-IS message with the ID of the device, if an I am is received the device will be considered back ONLINE and the ReadProperty 'probe' check (for IP) or token pass check (for MSTP) will resume once a minute. ***In version 1.4 and below the ReadProperty will read the name property of the device. See sample Wireshark capture below, NOTE that in the sample below 10.169.90.31 is the Broadcast address of the sub net where the ES is located. NOTE: For efficiency the BACnet engine may combine the reading of the system status property with other read property requests into a single Read Property Multiple.

Issue Modbus write command setup and timing Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS, AS-P, AS-B) Building Operation Enterprise Server (ES) Cause The Modbus value keeps being sent to a Modbus register (when write code 06 or 16 used) Resolution Control of the write timing is via the binding to the Modbus point within the Modbus network. If the Communication type is set to "Periodic" then the value will be sent based on the Period Communication Interval. If the Communication Type is set to "Change of Value" then the value will only be written when the value changes by this amount. The Re-transmit Interval should also be considered, as the register will also be written to based on this timing value, regardless as to whether it has changed or not. This value may need to be increased if the value should not be re transmitted apart from when the value changes. Up to v1.3 v1.4 and later Some Modbus devices get over these sort of issues by having a mode that can be set so that re-transmission of the same value is ignored, as the example below NOTE Block (Batch, Multiple) Writes are not supported (correct as 2020 11 01 and up to v3.2) Although they are used to write to 32, 48 & 64 bit Register types (so "Write Multiple Registers" packets will be seen when writing to 32, 48 or 64 bit registers) 

Issue In applications where heating is not required is it possible to change the thermostat operation to cooling only? Product Line Field Devices Environment TC300 thermostat Cause By default the TC300 thermostat is configured for heating and cooling. It should be possible to lockout operation of heating in cooling only applications so that the user cannot inadvertently change modes. Resolution In thermostat model TC303-3A2DLS parameter item 7 allows selection of cooling or heating only mode.

Issue Need to activate an Output when access is denied to a User at a Door. Product Line Security Expert Environment EcoStruxure Security Expert Cause In the Door object, there is a facility for triggering Outputs on Pre Alarm, Door Left Open, and Door Forced Open but nothing for when a User is denied access. Resolution There were new Door commands added to SP-C firmware 2.08.1018 and newer to add this functionality. AccessDeniedTime = # has been added to the Door commands which will specify the duration in seconds that an output or output group will be activated for when access to the door has been denied. This must also be paired with one of the following 2 commands in order for the functionality to occur. AccessDeniedOutput = # has been added to the Door commands which will specify the output that will be activated when access to the door has been denied. The # will be the database ID of the output/output group. AccessDeniedOutputGroup = # has been added to the Door commands which will specify the output group that will be activated when access to the door has been denied. The # will be the database ID of the output group. As an example, if you wanted the Output with an Id = 3 to turn on for 5 seconds when access is denied at the Door, the following lines would need to be added to the Door object in the Commands section. AccessDeniedTime = 5 AccessDeniedOutput = 3 Door Command - Access Denied Output  

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue Introducing a previously commissioned Continuum IOU module such as an AC-1 to an Access Expert or Security Expert site can cause communication issues in the LON bus due to duplicated node id. Product Line Andover Continuum, EcoStruxure Security Expert, EcoStruxure Access Expert Environment Continuum AC-1 Continuum Net Controller Continuum Net Controller II Access Expert Controller Security Expert Controller Cause When IOU modules are commissioned in a Continuum system, the Net Controller assigns each module a Node ID, this is in addition to the LON Module ID that is unique to each module hardware, the purpose of the Node ID, is to decouple the identifier used by Continuum for communication from the specific piece of hardware, this in order to facilitate the replacement of a failed module without the need to change its Continuum identifier. The module stores the Node ID in nonvolatile memory so that it persists across power loss. If a Continuum IOU module is introduced to a LON network (Security Expert SP-AC1 or Access Expert AX-SSC) without clearing its Node ID, there is a risk of creating a duplicate Node ID condition that will prevent the LON network from operating properly. IMPORTANT This should not be an issue during the normal transition of Continuum site to Security Expert or Access Expert, as all the modules on the running LON bus should have unique Node IDs, this is only a problem when adding a module, or replacing a module with one that has been used before. Resolution In order to signal its presence on the LON network, each module will transmit on resetting its status network variable. If upon receiving this message, the Net Controller determines that the module is NOT in its local database, the controller will decommission the module by setting its Node ID to zero. Before introducing a Continuum IOU module that has been previously commissioned to the LON network of an SP-AC1 or SX-SSC controller, decommission the IOU module using the steps below: Attach the module to an empty Net Controller that is powered down with its battery removed. For a Net Controller II, in order to be absolutely sure that the Net Controller has an empty database, you may need to clear its backup in flash from a browser or by the use of the reset IP switch. See LL on how to use the controller's reset IP switch to clear its flash backup https://community.se.com/t5/Building-Automation-Knowledge/How-to-clear-the-controller-flash-backup-from-the-hardware-using/ta-p/5877 Power up the Net Controller Once the CPU led on the Net Controller starts blinking, press the 'Reset' button on the IOU module. Wait 30 seconds to make sure the decommissioning process has completed. Power down the Net Controller Remove the IOU module

Issue The documentation notes a TC900 can be changed from a 4-pipe system with a 2-wire motorized valve to a 2-pipe system with a 3-wire motorized valve. What parameter changes are required? Product Line Field Devices Environment TC907-3A4LAB TC907-3A4LMAB TC907-3A4DLSAB TC907-3A4DLMSAB TC907-4FMSAB TC907-3A4DPSAB TC907-3A4DPMSAB TC907-3A4DPMSA-24B TC907-4FMSA TC907-3A4LMA TC907-3A4LA TC907-3A4DPSA TC907-3A4DPMSA-24 TC907-3A4DPMSA TC907-3A4DLSA TC907-3A4DLMSA Cause Documentation is unclear in how a TC900 is configured to use a 3-wire valve actuator Resolution Access the parameter settings by pressing and holding the mode button for six seconds during thermostat power up. Press the mode button or Fan button to move forward or backward between the parameters until parameter 09 is displayed. Press the up and down buttons to set the parameter to 04.  

Issue How to associate BACnet IO points created under the BACnet Interface of the Automation Server with IO points on the Automation Server's IO bus. Product Line EcoStruxure Building Operation Environment Building Operation Servers 1.4 and above Building Operation Workstation Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Connect physical IO points to BACnet network controllers. Resolution BACnet Association Tool (EBO V3.0 or higher) BACnet Association Tool will map properties of a central IO point with corresponding properties of a BACnet point. The tool is capable of mapping a single IO point with a single BACnet point, optionally by also creating a BACnet point, and removing the association between IO and BACnet points. To open the BACnet Association Tool, Select the IO Bus or IO Module, BACnet Interface, Application Folder, or the BACnet point, then in the Actions menu, click BACnet Association Tool. Most useful is the ability to associate multiple IO points with their corresponding BACnet points in one operation. The tool can be run from a variety of different container types in the WorkStation Tree view, including an IO point, BACnet Point, CIO Module, or the entire IO Bus (as shown below). For more information refer to WebHelp articles: Creating and Associating BACnet Points to I/O Points (se.com) and Associating or Updating BACnet Point Associations to I/O Points (se.com) NOTE: Please be aware applying the BACnet Association Tool retrospectively, to an already configured site, can remove bindings to outputs.  For example output bindings in Script or Function Block programs.  As shown below, if the tool is used to create a BACnet Associated point for an output already bound to a program (1) the Requested Value will be replaced by the Associated Value of the BACnet point (2). This is due to how the BACnet Association Tool uses the bindings, where the newly created BACnet point should be used instead of the IO point.  The solution is to update the removed program binding (3) to use the BACnet Associated point value (4).   SBO 1.4 to 2.x To associate BACnet IO points created under the BACnet Interface of the Automation Server to points in the IO Bus in SBO 1.4 and above... The association is made via a read reference, so if we think of the two objects as one being the source and the other the destination you configure the association from the destination object so in the case of an output you configure the association from the BACnet object (in this example BO1). In the case of an input, you'd configure the association from the IO Bus input as that would be the destination object, in other words, the recipient of the value. (NOTE: for versions prior to 1.4 see Bacnet and StruxureWare Building Operation Central IO points) Create the points. In this example, we are associating an IO output point named 'Digital Output 1' with a BACnet Binary Output named BO1. From the properties page of the IO Bus point (Digital Output 1 in this example) click on the gear icon to the right of the 'Requested value' field. In the 'Requested value' editor click the navigation icon (...) to the right of the 'Reference' field and navigate to the 'Associated Value' of the BACnet point. Save the configuration changes. Now that the values have been associated setting the BACnet output value (BO1) will drive the IO Bus output (Digital Output 1)  

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 The MPM-UN controller comes with 100 AV's and 100 BV's. These may be added to the current database of the controller for various programming needs. However, when SE7000 controllers are added, they consume 14 of these AV's each (this is with the 2.5.6 firmware, which limits the ZigBee window to 14 AV points). The AV points are quickly gone from the MPM stock, and once 100 AV's are used, there are no more for further programming. If programming is done first, this is no problem, because the addition of SE7000 devices will continue to consume the remaining AV's from the original 100 available, then create AV's over 100 once the original are gone. How many AV's are available until the controller just doesn't recognize them, or stops allocating them to additional SE7000 controllers? Environment MPM-VA MPM-UN MPM-GW Cause As standard the library of objects in Building Expert displays 100 AV and 100 BV objects, however more are available but it is not clear how to access them. Resolution An MPM has capacity for up to 700 AV's and 700 BV's. Once the initial 100 are consumed, you can add Value Banks of 100 each AV and BV. Value Banks are added as devices and will be listed as sub devices under the main MPM. To add a Value Bank: 1. In the Building Expert Explorer panel, select the Add Devices icon . A new window opens. 2. Select Value Bank to add this your Controller. Added Device shows in Device to add column. 3. Click Add Devices button. 4. Repeat steps 2 - 3 to add any additional Devices. 5. Click Close

Issue The EcoStruxure Web Services Interface has been successfully setup in a Enterprise Server but cannot see the Vista objects / points in Workstation Product Line EcoStruxure Building Operation, TAC Vista Environment StruxureWare Building Operation 1.4.x TAC Vista SmartStruxure Interface TAC Vista 5 and above Cause The Web Services interface hosts the Vista objects in the System / Hardware / EcoStruxure Web Services / TAC Vista folder, these must be hosted to the Server to become visible within Workstation.  Resolution Once you have navigated to the System / Hardware / EcoStruxure Web Services / TAC Vista folder you will see the list of objects available associated with the TAC Vista user name setup in the TAC Vista SmartStruxure Interface. From the list of Vista objects select the required ones you wish to use within the Enterprise Server database. The right click on the selected folder and select the Host EWS Objects... option. The next option is to select the Vista EcoStruxure Web Service interface that will host these objects. The objects will now be visible within the Enterprise Server / Workstation.   For how to create Vista interface in SmartStruxure, refer to How to Create TAC Vista Interface to SmartStruxure. For additional details see Creating an EcoStruxure Web Service Object on the SBO WebHelp site. 

Issue What TAC Xenta I/O modules could act as a Stand-Alone LonWorks device? Product Line EcoStruxure Buildings Operation, TAC Vista Environment EcoStruxure Building Operation  LonWorks TP/FT-10 Network TAC Xenta 420A TAC Xenta 421A TAC Xenta 422A TAC Xenta 450A TAC Xenta 451A TAC Xenta 452A Cause It is only TAC Xenta 421A, 422A, 451A, and 452A that can act as Stand-Alone LonWorks devices. Resolution It is only TAC Xenta 421A, 422A, 451A, and 452A that can act as Stand-Alone LonWorks devices. TAC Xenta 400 I/O modules without -A, will not work as Stand Alone LonWorks devices. Once communication has been established with the Xenta I/O module the green status led will flash on for 1 second every 10 seconds indicating it is in Stand-Alone mode.   In Building Operation, the Lonworks devices list will show devices without an "A" after it. This may lead to the wrong conclusion that these devices can be added as stand-alone devices, but that is not the case. These devices are listed so that they can be added manually to a programmable Xenta device as an IO module.

Issue How do I setup and configure the database when using External log storage in EBO? Product Line EcoStruxure Building Operation Environment PostgreSQL TimescaleDB pgAdmin Building Operation Workstation Cause When using External log storage in EcoStruxure Building Operation(EBO) PostgreSQL server and TimescaleDB are installed on a computer where the trend log data and events should be stored. The database used for External Log storage needs to be setup and configured correctly. Resolution The EBO External Log Storage Installer tool available on the Community assists with installing and configuring the PostgreSQL server. But if you like to see how it is done manually please watch this video. The following steps are shown in the video: Create the database in the PostgreSQL server Create a user which will be used by EBO when it connects to the database Configure the database for use with EBO Configure EBO to be able to connect to the database  

Issue Configuring a Smart Sensor in SBO. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operations b3xxx Controllers Smart Sensor (LCD or LED) Cause Unsure how to program for a Smart Sensor in SBO. Resolution Some considerations to be aware of first; Object naming differences Programming of the Smart Sensor is very similar to the old Plain English programming used in Continuum. One of the main differences is that each input must be specifically defined at the start of the program. Depending on the version of SBO, there may be some other considerations with setting up/reading the LcdDisplay array by renaming of the BACnet AnalogValue's to remove the "_AV" from the BACnet name. This naming issue affects SBO v1.4. Specific variables for Smart Sensor to be used in Plain English programming. Here is an old Smart Sensor Installation manual that will help explain which objects need to be created and how they work in the controller to enable the LCD display. Create the LCDDisplay and SpaceTempSP as numerics and any other objects that are not already created as InfinitySystemVariables. See "Configuration and Programming" section in the manual starting on page 14. Also note that the sensor will not light up until values are written to it. Sample Plain English code. LCDDisplay (or LEDDisplay) is not automatically created. Create this numeric and assign it as an array with 8-elements.  If it is an LCD Smart Sensor, then create a numeric and name it "LCDDisplay" and set its logsize to 7 (this configures it as an array with 8 elements from 0 to 7). If it is an LED Smart Sensor, then create a numeric called "LEDDisplay" instead. After creating this numeric you should be able to create the PE Program successfully. The simple program below will show the current spacetemp (LcdDisplay[1]) in two decimal place format (LcdDisplay[2]) when the Display key (LcdDisplay[0]) is pressed. The degrees symbol (LcdDisplay[7]) is also shown. Consult the Smart Sensor Installation and User Guide starting on page 16 for more details on how these values are configured. Numeric Input SpaceTemp Numeric Output LcdDisplay Initialise: LcdDisplay[2] = 0 If LcdDisplay[0] = 4 then Goto ShowTemperature ShowTemperature: LcdDisplay[1] = SpaceTemp LcdDisplay[2] = 12 LcdDisplay[7] = 1024 If TS > 30 then Goto Initialise In SBO, do the following under the Application section of the b3 controller: Create a BACnet Analog Value object in the b3 called "LCDDisplay". Go to the Advanced tab and under the Log Settings section change Log Records to be 7. Save the changes. Create the program and add the above PE Script. Add the binds to the LCDDisplay object created in step 1, RoomTemp input, and any other objects used in the program.

Issue Unable to control the field device with a Triac output. Product Line EcoStruxure Building Operation, Andover Continuum Environment Continuum b3 Controllers Continuum i2 Controllers Building Operation Multi-purpose Controllers with Triacs Cause Triac outputs cannot switch DC loads. Triac outputs require a minimum 30 mA load in order to switch.  Resolution If the inductive load draws less than 30mA a resistor needs to be wired in parallel with the switched load.