Issue Is there any limitation for the number of local program variables that can be declared in a script program located in ExoStruxure BMS servers or BACnet/IP controllers?   Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller (RPC) 24 V Cause A script program has a lot of variables declared. Resolution There are no hard limits imposed by the script compiler. for the number of local program variables. The limits are performance and device resources. The bigger a program is, the more memory and processor bandwidth it will consume and the longer it will take to execute. 

Issue The sequence numbers for Alarm Events are changing daily for all active alarms in the system. This can be a problem for applications using sequence number as alarm identifier. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server. Building Operation Automation Server Premium Cause Every night there is a cleanup in the alarm table and alarms can then get new sequence numbers. Every night historic updates with old time stamps are removed in the alarm table.   When this cleanup takes place, there is a reorganization of sequence numbers of current alarms. They all get a new sequence number.   The new sequence numbers are always higher than the latest sequence number before the cleanup. Resolution Do not use alarm sequence number for alarm identifier, use triggered time stamp instead.

Issue There is no information on how to create and prepare signed certificates for import in Building Operation. PEM file format has to be used. If another format is used or the certificate files are not correct, you get a message like this when importing SAXParseException: Reference to invalid character number in line X column Y Product Line EcoStruxure Building Operation Environment Certificates Cause There is no information on how to create signed certificates in Building Operation. Resolution Make sure that when preparing the pfx file that the full chain of trust is included in the pfx file. You have various options when preparing a pfx certificate export file, and the private keys and chain of trust are options that must be selected. Otherwise, you won't extract the intermediate certificate or the private key if not included. Complete a Certificate Request and then request a certificate in PEM format in a .pfx file "container".  Extract the CA certificate, Intermediate certificate, and private key using the following OpenSSL commands. After executing each command, enter the password if prompted. Make sure you reference the right pfx file. Below filename.pfx is used as an example Make sure you enter the commands manually and do not copy/paste from this article Download OpenSSL tool here or use OpenSSL installed with EBO  openssl pkcs12 -in filename.pfx -out host.pem -nodes -clcerts -nokeys openssl pkcs12 -in filename.pfx -out inter.pem -nodes -cacerts -nokeys openssl pkcs12 -in filename.pfx -out privkey.prv -nodes -nocerts The three files produced must then be parsed of any characters that aren't in the part of the certificate/key and in PEM format (or PRV if private key) - basically all the characters before "-----Begin Certificate-----" or after "-----End Certificate-----". Ensure each file ends with a blank line and that a blank line separates each section. This can be done in any text editor; however, this example uses Notepad++ with the "Show All Characters" button selected.  Import the files into SBO using the certificate manager in the Control panel. File type conversion If the host and intermediate certificate are in crt, cer or der format, you can convert them to pem format using the following method/command: openssl x509 -outform der -in certificate.cer -out certificate.der openssl x509 -inform der -in certificate.der -out certificate.pem Replace "certificate.cer" with the name of your file Determining certificate file type To determine which filetype a given certificate file has (PEM, DER, or pkcs12/pfx), you can use the following commands (replace "cert.crt" with the name of your file). A valid output will confirm the file type. PEM openssl x509 -in cert.crt -text DER openssl x509 -in cert.crt -inform DER -text pkcs12/pfx openssl pkcs12 -in cert.crt -info

Issue When using Project Configuration Tool (PCT) in Server mode and connecting from a remote PCT client, it is not possible to transfer backups or exports. The transfer gets stuck, and a complete reboot is required to start using the project again. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause In the "Settings for Project Configuration Tool" the Notification and Listening port defaults to 0. Port 0 means that PCT will ask the OS for an available port. But if network policies prevent PCT from communicating using that port, PCT cannot detect that.  Resolution In "Settings for Project Configuration Tool" Change the port number for the Notification port and Listening port to a port that is available to use.

Issue In TAC Vista, we had a function for the OGC graphics called standard graphic. Do we have something similar in Building Operation? Product Line EcoStuxure Building Operation Environment Building Operation 2.0 and above Graphics  Cause All graphics connected to the standard graphic in TAC Vista changed if the standard graphic was changed. This is a very useful function when having many similar graphics.    In Building Operation, a new object was implemented in version 1.8 labeled shared Graphics, Custom Types superseded this in version 2.0, and this function is similar to shared Graphics but not identical. Resolution There is no direct function like this in Building Operation.  Custom Types is the only similar feature available in the currently supported versions of Building Operation. Additional information can be viewed in the online help topic Custom Types Overview.  

Issue How to configure two room sensors in ZBuilder. Product Line EcoStruxure Building Operation Environment ZBuilder Cause It is possible to configure TAC Xenta 121 or TAC Xenta 122 to use two room sensors via the ZBuilder tool. Resolution In Zbuilder, under the tab Configuration, under Room unit, select the type of sensor you are going to use. Select the tab I/O Setup,  Right click on the sensor and select Duplicate. Move the sensors to the input you are going to use.   At the end of this session you will be able to: Configure TAC Xenta 121/122 to use two room sensors. Understand that the nvoSpaceTemp value is calculated as average value of the two sensors. Understand that it is not possible to see the actual value of a single sensor when using two sensors.    

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 Is it possible to let the ES directly write the write to file notification into the Windows event database? Is there a rotation for the Write To File Notification file so that a new file is written when the file is bigger than xMB?   Product Line EcoStruxure Building Operation  Environment EcoStruxure Building Operation - ES Cause Write to file notification can only be written to a file in the "db / notifications" folder on the server where the notification object is located. Unfortunately there is no rotation either. Resolution At this time it is not possible for an Enterprise Server to write directly to the Write to File notification in the Windows event database. There is also no rotation for the Write to File notification file so that a new file is written when the file is bigger than xMB.

Issue 3rd party BACnet device can send a reinitialize device request to an EBO server. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Cause EBO servers support the "ReinitializeDevice-B" Bacnet device management service. This allows BACnet clients, such as BACnet browsers or operator WorkStations, to initiate ReinitializeDevice requests, i.e. Warm Start or Cold Start. Resolution EBO currently does not support passwords for the ReInitializeDevice service. It is possible to create a whitelist for the EBO server and exclude a 3rd party BACnet device from that list, but this will block all communication with the 3rd party BACnet device.

Issue When changing values like Check-in interval (s) under Poll Control for Zigbee device SED-MTH-G-5045, the value seams not to have been change when opening the dialog again. Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Premium (AS-P) Building Operation Room Controller (RP-C) non-Greenpower sensors SED-MTH-G-5045 Cause Setting is sent to the sensor only once every tenth minute. Resolution Open the dialog box again after 10 minutes to verify your changes.

Issue Using Download Wizard 32 with Application set to Clear Memory, one will get an error that "The application file could not be found! Product Line EcoStruxure Building Operation Environment Building Operation Workstation Xenta Programmable Controller Cause EBO Workstation does not include the Lonm<Model Number>.MTA file. Resolution There are two solutions: Create a minimal MTA file for the device type. Open Menta Editor Change the device specification for the appropriate Xenta Type. Add one PVR block Save the file. In DWiz, change Application selection to Download New and Browse in the new file. Perform the steps again with the expected files in the same folder as DWiz. Download the attached Lonm.zip (derived from Menta 5.1.9) Extract the files in the zip to the same Workstation folder where Dwiz.exe is found. Sample Location: "C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation 3.2\WorkStation\DWiz.exe" Perform the download again with the same Clear Memory selection under the Application section.

Issue Steps on how to setup BACnet Time Synchronization to 3rd Party BACnet controllers. Product Line EcoStruxure Building Opertaion Environment SmartX Enterprise Server (ES) SmartX Automation Server (AS) BACnet Cause It is not always clear what is required to setup BACnet Time Synchronization and how to confirm that EcoStruxure Building Operation is actually performing it properly. Resolution To use the Time Synchronisation you will need to bring the 3rd Party BACnet device (Eg. Continuum bCX) under the EBO BACnet Interface -> IP Network: Go to the BACnet Interface Time Synchronization Recipients Tab. Add a new Local time synchronization recipient with the '+' button. Select recipient type as 'reference' In the Recipient device object reference field browse for your BACnet Device. Press OK and then save the changes. Right-click on the BACnet Interface and select send time sync now. This will send out an unconfirmed-req TimeSynchronization to that specific Device only.   Test Scenario with a bCX setup as a third-party BACnet controller You will see a unconfirmed-req TimeSynchronization packet being sent from the ES in WireShark but with no response from the bCX.  You may not see responses back from other 3rd party devices. The time in the bCX should be seen to change from within Continuum, (assuming it was incorrect in the first place) 

Issue Are there drawing templates available for AS’s, modules, RPC etc for use in BMS wiring diagrams. Product Line EcoStruxure Building Operation Environment Building Operation equipment Cause Need for CAD drawings of PS, AS, or I/O Modules Resolution Drawings in AutoCAD format (DWG, DXF) are available on the EcoXpert Extranet. DXF files are able to be imported into Visio.

Issue Content Types are not working correctly. A Content Type that was just created appears under the ES but not under the AS in which it was created in. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server Premium Building Operation Software 1.9 or greater Cause Problems with or changes to the network configuration are affecting both the function and the lead shadow relationship of Content Types. Resolution   The following video will help us, Understand the Lead/Shadow aspects of Content Types Diagnosis and correct possible issues regarding the Lead/Shadow Online help topic for further information is also available here: Content Types (se.com)  

Issue How to perform the activation of an embedded demo license Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Cause The embedded demo License is a temporary license used for demonstration purposes, training, site engineering, when waiting on a permanent license order, or license support. This license file has a .Bin extension and can be downloaded from the EcoStruxure Exchange (ecoxpert.se.com) and is valid for a limited time (3 months). Resolution This video will demonstrate where to download, and how to activate an embedded demo license on an Automation Server using the Device Administrator.

Issue MQTT data points are no longer published to MQTT broker with "MQTT - Buffer overflow" alarm. System alarm: Buffer overflow - Not all MQTT messages have been sent Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Cause Long MQTT queue can be caused by, too many variables define in MQTT data groups, fast publishing, i.e. low interval or low delta value, Low CPU and RAM resources, or slow network. Resolution Once MQTT Buffer overflow alarm is generated, the below configuration shall be checked: Data points interval value, if the interval is enabled, make sure it is not a very low interval. Data points delta value, for event driven, make it is not very low value, especially for fast changing variables. Review the network performance. Make sure that the EBO server has sufficient CPU and RAM resources, and check Architectural guidelines for the effect of the Number of MQTT Data Points on the CPU Load. For Automation Server, the system memory usage should never exceed 80% and CPU usage should stay below 60%.

Issue In EBO BACnet device discovery, how is the BACnet MAC address defined? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Cause A BACnet device is uniquely identified by a network number and a MAC address. Resolution BACnet MS/TP A BACnet MS/TP device supports device MAC addresses in the range 0-127 for masters and 0-254 for slaves. Device MAC addresses are often configured using DIP switches or a configuration tool.   BACnet/IP MAC addresses for BACnet/IP devices are a combination of the IP address and BACnet/IP UDP Port expressed in hexadecimal notation. For example, if a BACnet/IP device is configured with an IP address of 192.168.1.5 and a UDP port of 47808 then:   IP address expressed in hexadecimal is 192 = C0, 168 = A8, 1 = 01, 5 = 05 UDP port expressed in hexadecimal is 47808 = BAC0   Therefore the MAC address will be, C0:A8:01:05:BA:C0   BACnet/SC BACnet/SC nodes are identified by their 6-octet virtual MAC (VMAC) address in form of a IEEE EUI-48 identifier which is randomly generated. A BACnet/SC device attempts to resolve its own VMAC in the network. If it detects another device is already using this VMAC, it will generate a new Random-48 VMAC address and try again.

Issue Metasys® N2 Integration to SBO Product Line EcoStruxure Building Operation Environment Struxureware Building Operation Metasys N2 Cause This Quick Start Guide will assist the Schneider Electric branch or dealer installation team with the basic steps to bring the virtual BACnet devices emulated by the S4 Open: BACnet-N2 Router into the SmartStruxure environment as part of a Johnson Controls Metasys® N2 integration into SBO. This document is not intended to be a full tutorial or user manual for either the S4 Open: BACnet N2 Router or the SmartStruxure system. Refer to the manufacturer’s documentation for each of these systems for detailed information. S4 documentation, the complete Device Template library, and support utilities can be found on the support CD delivered with your S4 Open appliance. Please contact the S4 group for any questions on this process.  Resolution Step 1:   Follow the installation instructions provided with the S4 Open: BACnet-N2 Router to discover and publish the N2 devices in the Metasys® installation to BACnet IP. All operations in SmartStruxure will be against these emulated BACnet IP devices each representing the underlying N2 device. Investigate before you integrate! Validate the N2 bus to make sure that it is electrically in spec and that all N2 devices are working properly before starting the integration process. Assign a unique BACnet virtual network number to each S4 Open: BACnet-N2 Router. N2 devices connected to this S4 Open appliance are published as emulated BACnet IP devices under that network. The Configure Wizard in the S4 Open Management Console will assist you with generating a unique BACnet Device ID for each N2 device. Point instance numbers are included as attributes in our Device Templates for all application-specific controllers. Either of these can be manually overridden in the S4 Open Management Console to meet unique requirements. The S4 Metasys® Configuration File Conversion Utility can be downloaded from the S4 Group web site and will assist you in creating custom Device Templates for DX-9100 devices or application-specific controllers. You will need the corresponding .DMO or .PRN files as input to this utility. A detailed understanding of Metasys® N2 devices, the Metasys® system, and the associated configuration and commissioning utilities are necessary to support successful integrations. If you don’t have this expertise in-house, The S4 Group can recommend a consultant to assist you. NOTE: We highly recommend that you attend a two-day S4 Boot Camp to make sure that you have all the skills necessary to install and configure the S4 Open: BACnet-N2 Router. Step 2: Bring up the SmartStruxure BACnet discovery tab and select BACnet devices. In this example, you can see that the S4 Open BACnet-N2 Router was defined in Network 1 and the N2 devices are in Network 122. The other device in Network 1 in this example is a JCI NAE. The best practice is to assign the S4 Open: BACnet-N2 Router to the BACnet network that you are using as your BACnet backbone. As with any BACnet device, the BACnet-N2 Router must be assigned a unique BACnet device ID. Step 3: Expand the navigation pane to expose the BACnet Interface / IP Network folder. Then select and drag the N2 devices from the Device Discovery tab to the IP Network folder. SmartStruxure will tell you that an Upload is required. Respond OK. Step 4: Navigate to the IP Network folder, select the properties page for each device, and request an Upload operation. This will bring the device properties and point list for each N2 device into SmartStruxure. SmartStruxure will respond with the following confirmation as each upload is completed. Step 5: When the Upload process is completed for all N2 devices and the S4 Open: BACnet-N2 Router, you can continue your SmartStruxure installation process as you would for any BACnet device. Note that there will be no points published under the S4 Open: BACnet-N2 Router itself but you will be able to confirm the Operational Status of the system from SmartStruxure. The Schneider Electric support organization will supply pre-sales engineering support and first-level technical support for the Metasys® N2 to SBO integration solution. The S4 Group will be available to provide 2nd level support to these integration projects.  

Issue What is the difference between an EBO SmartDriver and Smart Connector? Product Line EcoStruxure Building Operation Environment Building Operation SmartDriver Cause SmartDriver and Smart Connector enhance the openness for the EcoStruxure Building Operation, EBO, BMS system. They enable integration between EBO and 3rd party systems, even via not supported or nonstandard protocols. Resolution SmartDriver: SmartDriver enables you to create a customized interface to monitor and control 3rd party devices from the EBO server. The following block diagram shows a SmartDriver Interface and a SmartDriver Driver. The SmartDriver Interface (similar in concept to other protocol interfaces such as Modbus and BACnet) is part of EcoStruxure Building Operation software and enables you to create SmartDriver objects in the System Tree pane. The SmartDriver Driver is installed on the server drive and provides the network communications control. More information at Web Help SmartDriver Overview. Smart Connector: A development framework that simplifies and accelerates integrations with third-party systems or other data sources. It is an open, extensible and configurable application framework that allows developers to create innovative new capabilities, applications, and solutions that extend and enhance EcoStruxure Building solutions. The Smart Connector itself runs outside the EBO server and consume or server data to EBO server via the EcoStruxure web services "EWS". Watch short explainer video for more information: https://www.youtube.com/embed/DXHvRRL4ycY   For more information, visit the Smart Connector Developer Community on the Exchange: https://community.se.com/t5/SmartConnector/ct-p/smart-connector   For developers wanting to get started using the Smart Connector framework visit: https://www.smartconnectorserver.com   Smart Connector shop at Exchange:  https://shop.exchange.se.com/en-US/home 

Issue Is it possible to print alarms automatically with SBO Workstation in matrix printer whenever there is an alarm? Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause A number of sites still prefer to directly connect a Dot Matrix Printer to their BMS to automatically print off incoming alarms rather than using more modern emailing of alarms available from EBO. Resolution The following File2Printer software has been made freely available on the EcoStruxure Building Operation Community for exactly this purpose. https://community.se.com/t5/EcoStruxure-Building-Operation/File2Printer/m-p/351127#M71948