Building Automation Knowledge Base

Issue How to display the date as an object in Sigma. Environment BAS SIGMA Cause How to display the date as an object in Sigma. Resolution For Day and Month only, the following programmable point needs to be configured: 10 XFlo = FLOAT ( MONTH ) 20 XFlo = XFlo / 100.000 30 YFlo = FLOAT ( DAY ) 40 RETURN VIA TEXT 449 VALUE XFlo + YFlo The date will be displayed in the dd.mm format. Shorttext will need to be created as below: %2.2f and will be displayed as 17.07 or Date:%2.2f and will be displayed as Date:17.07 If Day, Month and Year is required the following can be configured: 10 XFlo = FLOAT ( MONTH ) 20 XFlo = XFlo * 100.000 30 YFlo = FLOAT ( DAY ) 40 YFlo = YFlo * 10000.0 50 ZFlo = FLOAT ( YEAR ) 60 RETURN VIA TEXT 449 VALUE XFlo + YFlo + ZFlo The date will be displayed in the ddmmyy format. Shorttext will need to be created as below: Date:%2.0f and will be displayed as Date:170712        

Issue Controller Error Log shows error code 5128. Environment Error Log Error Code NetController BCX ACX Cause An Infinity Controller is dropping offline. Resolution Controller error code 5128 (0x00001408) is an indication that the controllers network comm buffer is out of memory.  Normally the network transceiver will shut down when this happens to protect the controller.  This is generally an indication that the controllers comm buffer is being overtaxed.  This can happen when there is a data storm present on the network. 

Issue Standard Applications for I/A Series Micronet BACnet (MNB) controllers Product Line I/A Series Environment I/A Series WorkPlace Tech 5.x and above I/A Series MNB controllers Cause A library of standard pre-engineered applications for MNB controllers is available. These can be modified and used as a reference for creating MNB applications. Resolution The library of standard applications can be downloaded from Exchange Extranet. Below is a list of the applications available for downloads.  DUI Application Stencil Operation Guide Application Objects Visio Stencil (Includes DUI_App) Applications - BACnet Zone, VAV, and Unitary Applications using SP and SPP Momentary Start/Stop Object Application Operation Guide Application - BACnet Zone Controller Applications Application - BACnet VAV Box Applications Application - BACnet Unitary Applications Stencil - Application Stencils Application - VAV_Staged_Heat.vst Application - FC_1DX_1EH.vst Application - FC_1PropCL_1PropHT.vst Application - FC_2Pipe_2PosHC_wCO.vst Application - All BACnet Unitary Applications.zip Application - All BACnet VAV Box Applications.zip Application - VAV_Cooling_Only.vst Application - VAV_Floating_Heat.vst Application - AHU_HeatPump.vst Application - VAV_Parallel_Fan_Staged_Heat.vst Application - VAV_Parallel_Fan_Floating_Heat.vst

  Issue PCT v1.3.3.75 fail to start SmartX server in versions 1.8.x and 1.9.x Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Defect, user can create SmartX server v1.8.x and 1.9.x but the servers can't start properly. Resolution Uninstall PCT v1.3.3.75 Install PCT v1.3.2.110 (Download), (Client Installer) Install server packages 1.8.x and 1.9.x

Issue Using CARD + BIOMETRIC credentials at an integrated Suprema reader for user access. Product Line EcoStruxure Security Expert Environment Security Expert Suprema Biometric Reader Cause Security Expert does not support CARD + BIOMETRIC credentials being read at the integrated Suprema reader. Only BIOMETRIC credentials are supported to be read at the Suprema reader. Resolution For situations where CARD and BIOMETRIC credentials are required to authenticate users a supported solution is to install a Security Expert reader in conjunction with a Suprema reader at the door. The Security Expert reader will read the Security Expert Mifare/DESFire tags, compare this to the credentials configured in Security Expert user and then wait for the proper biometric to be provided before allowing access through the door.

Issue 3rd Party RS485 to Ethernet or other connection types are available. Will they work with Infinet? Product Line Andover Continuum Environment Infinet networks Infilink 200, Infilink 210 Cause Sometimes existing cabling is available on a site, using this could reduce install costs. Resolution Third party converters and extenders are not supported on Infinet networks. It is not possible to use most 3rd party devices as the latency (delay) times will be too long for the protocol to operate correctly. This will include: RS485 - Ethernet converters RS485 Tied line Modems Any other type of Modem Any GSM packet modems Other RF devices

Issue All of the nodes are yellow and when they are clicked on the error below is displayed even though the database is attached to the network (OnNet), the network interface is on the correct channel, and the network interface passed all applicable tests. Environment NL220 Cause When the nodes appear yellow, this means that the LNS database has been corrupted. Resolution It can be attempted to repair the database using the Echelon LNS Database Validator. Follow these steps. If NL220 is still running, shut it down. Go to the Start menu > All Programs > Echelon LNS Utilities > LNS Database Validator. Select the corrupt database in the "Network to Validate" drop down box. Check the box next to Repair Database. Now click on the button called Validate.   If these steps do not repair the database, send the LNS database backup to Echelon support to see if they can correct the problem.

Issue The EBO license is activated on a virtual machine, need to make sure that it will not get damaged. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Workstation Cause Scenarios leading to broken Trusted Storage (license damage), when license is activated on a Virtual Machine. In some cases, the License Administrator can be used to repair the license, and in other cases, product supported will need to be contacted. Resolution FlexNet documentation explains how licensing in virtual machines works, what causes license damage, and how to avoid license damage. Make sure that documentation is related to the FNP version (FlexNet publisher) used by installed EBO, ex. EBO V4.0.2 uses version 2021 (11.18.1) and EBO V5.0.2 uses FNP V2022 R3 (11.19.2).  You can also check the FNP version by checking the properties, details of lmadmin.exe file located in C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation x.x\License Server Binding elements for licenses activated on a virtual machine: FlexNet publisher documentation lists three binding elements for virtual machines, all of which are deal breakers: MAC address, UUID, and Generation ID, refer to Binding in a Virtual Environment (revenera.com)  Scenarios that can cause license damage (Trusted-Storage Breakage): In the attached FlexNet White Paper: Understanding Virtualization Features in FlexNet Publisher, Page 9, details binding variables and which scenarios can change each binding element. Page 11 in the same white paper, Recovering from a Binding Break in TS, explains common scenarios leading to broken TS and if a license can be repaired.  WebHelp article EcoStruxure Building Operation Software License Repair, explains other reasons for license damage, for physical or virtual machine.  Please contact your local support if the License Administrator can't repair the license. Best Practices to avoid Trusted-Storage Breakage: To minimize license damage, follow the below steps before making changes to the bindings elements or moving EBO to a new VM. Make a backup of EBO, Backing Up EcoStruxure BMS Servers Manually Return all licenses, Returning an EcoStruxure Building Operation Software License. Verify that all licenses have been returned for all used Entitlements by logging in to https://licensing.se.com. Perform your operation. Activate the licenses again, Activating EcoStruxure Building Operation Software Licenses. FlexNet lists best practices that can also be followed to avoid trusted storage breakage: Best Practices (revenera.com)

Issue System memory usage stays high after exporting projects in PCT (Project configuration tool) Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause The exporting process increases memory usage but is still withheld by the project after the process finishes.   Resolution Close the project exported.

Issue Receive “Timeout while waiting for server to get ready” error when starting PCT Product Line EcoStruxure Building Operation Environment Project Configuration Tool, PCT Cause PCT can't reach DHCP server from the virtual machine. Resolution To change the Notification Address in the "Setup for use with remote server" to "localhost". 1. Select "Setup for use with remote server" after PCT start. 2. Update the "Notification address" to localhost  

Issue When trying to open WorkPlace Tech Editor the following error is shown in a pop-up window.   The following error occurred while trying to launch the WorkPlace Tech Ribbon Bar: The add-in could not be installed. Product Line EcoStruxure Building Operation, TAC IA Series Environment Building Operation Workstation (Workplace Tech Editor) I/A Series WorkPlace Tech Cause An installation of the Visio Ribbon has not closed correctly from previous use of WorkPlace Tech Editor or standalone WorkPlace Tech. Resolution Open the Add and Remove function in Windows Select "Program and Feature" Look for an instance of the SE.WorkStation.IA.VisioRibbon when no WorkPlace Tech Editor is running. Right-click and uninstall. Open Workstation and launch WorkPlace Tech Editor  There are other conditions that can cause the ribbon not to run as well.  They are detailed in other articles Similar Error Message Regarding Ribbon Bar  Unable to Load Ribbon 

Issue Technical support contact information for Design 360 and Studio 360 Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Design 360 Studio 360 Cause Design 360 or Studio 360 has issues requiring technical support assistance which is not provided by PSS. Resolution Schneider Electric Employees should contact PSS who will provide you with your Branch Administrator and Technical Expert contact information. Partners may contact Smartware directly for any support of the tool at: Email: techsupport@smartwaretech.com Phone: (716) 213-2222

Issue Is there an I/A Series G3 Modbus object that converts a PM820 three register date and time format value? Environment I/A Series G3 - all versions Cause The Schneider Electric (Square D) PM820 Power Meter provides date and time in a 3 register (6 byte) compressed format. The three registers provide a single timestamp consisting of month, day, year, hour, minute, second.  For example, if the date was 01/25/00 at 11:06:59, the Hex values would be 0119, 640B, 063B. Hexadecimal High Byte  Low Byte 0119 01 = month 19 = day 640B 64 = year  0B = hour 063B 06 = minute 3B = seconds Note: Date format is a 3 register (6 byte) compressed format.  Year 2001 is represented as 101 for the year value. Resolution Program object PM_ConvertDateTime.bog decodes and converts the register values to date and time.  The object will split the bytes and decode to individual outputs as well as provide a dateTime output.  Connect the three sequential registers to in, in1, and in2. Download object: PM_ConvertDateTime.bog  

Issue An Enterprise Server or Automation Server is unsuccessful at sending email notifications to a Gmail recipient.  Email messages from ES are marked as spam by Gmail SMTP service. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server (AS-P, AS-B or AS) Building Operation Workstation Gmail Cause Unable to successfully configure the ES to send an Alarm Notification to a Gmail recipient. Resolution The following describes how the ES can be set up to use Gmail for Email delivery. 1. Log into the ES; designate the Sender E-mail address and E-mail Host properties. 2. Create a notification on the ES; set the destination E-mail address and type of alarms to be included. 3. Log into destination E-mail account; notice there don’t appear to be any E-mails received. Select the “More” dropdown. 4. Select the “SPAM” folder. 5. Navigate to the E-mail Selection Tab and choose all E-mails from the correct sender. 6. Select the “Not Spam” button and from now on all email notifications will be sent to your inbox! 1. Log into the ES; designate the Sender E-mail address and E-mail Host properties. 2. Create a notification on the ES; set the destination E-mail address and type of alarms to be included. 3. Log into destination E-mail account; notice there don’t appear to be any E-mails received. Select the “More” dropdown. 4. Select the “SPAM” folder. 5. Navigate to the E-mail Selection Tab and choose all E-mails from the correct sender (SxW). 6. Select the “Not Spam” button and from now on all email notifications will be sent to your inbox!

Issue Need to connect MicroNet system to EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Automation server Enterprise Server MicroNet interface Cause MN-Mi interfaces are obsolete, need to find another way to connect to EcoStruxure Building Operation system. Resolution A MicroNet system uses one of two communications protocols, Native Communications Protocol (NCP) and Attached Resource Computer Network (ARCnet). If the protocol being used is NCP, the MicroNet LAN can be connected directly to the AS-P/ES, A MicroNet interface can be added and configured. If the protocol adopted is ARCnet, this does require the MN-Mi, to convert from RS 232 to ARCnet, the MN-Mi would be connected to the AS/ES using an RS232-485 converter. If the MicroNet controllers are the older 100 series version, it may be possible to remove the auxiliary ARCnet cards, and reconfigure the MicroNet controllers and LAN to use NCP protocol. If the MicroNet controllers are the 50 series type the cannot be re-confirmed as the communications components are on the main board. PA-00246 provides more information on the possible connections.

Issue Attempting to log in with WorkStation and receive the following license error: No license available. Error -83: Version of vendor daemon is too old The following error is seen in System Log / Trace log:  Error Code: -83 Error message: Version of vendor daemon is too old Building Operation Software Administrator Product Line EcoStruxure Building Operation. Environment Building Operation License Administrator Building Operation License Server Cause The most common cause is that the License Server is older than the current release of Building Operation software.  This occurs during upgrades and if the License Server used for the product has not been upgraded.  Ensure both components of the License Administrator are selected (as shown below) when performing the upgrade/installation.     Resolution To confirm the issue open the Windows Services and check that the version shown in the services is valid for the products installed.  The version shown should be at the same version or higher than the other Building Operation software installed.     To resolve the issue, upgrade the License Server component of the License Administrator installation software. 

Issue When opening a dashboard graphic, the system operates very slowly.  Navigation to other links with the Dashboard displayed, and clicking on a linked graphic does not display immediately.  Product Line EcoStruxure Building Operation Environment Building Operation 3.2.3 and higher Building Operation Automation Server Bundles (AS-B) Building Operation WebStation  Cause Typically when a large number of stored values (100,000 per trend log) is needed to be displayed within the Dashboard widget (e.g., Period Chart) with a significant number of trend logs to be displayed (five or more) in the Dashboard, this will put excessive load on the AS-B and hence stops any or all navigation thereafter.   Dashboard widgets typically continue to read data required to be displayed after closing (or navigating away). This is to keep those logs cached for a few minutes after the dashboard is closed, so if the same logs are loaded again, then the data is available. Any calculations are always done on the client, regardless of whether a chart, dashboard, or trend list is shown. The same is also true for WorkStation. Resolution Below are some considerations to look at improving the overall performance when dealing with this issue: Reducing the number of storage records from 100,000 to something more reasonable for the dashboard to display (5,000 - 8,000) Having these logs stored on the Enterprise Server and Dashboard operated from the Enterprise Server.    If large storage is necessary, then create or use different logs for display within the Dashboards widgets.  If the intention is always to show calculated values, use log processor trend logs. Log Processing Trend Log. These can be pre-calculated and thus contain only a fraction of the full source log's data amount. Upgrade to the later version (EBO 2023) as many optimizations have been made for Dashboards since 3.2.        

Issue Communication issues caused by improper grounding of the BACnet MS/TP shield connections to the B-LINK-AC repeater.   Environment BACnet MS/TP installation with B-LINK-AC repeaters. Cause The shield connection on port 1, labeled "(Input)", of the B-LINK-AC repeater is internally wired differently than the four other ports. Resolution Due to the differences in how the shield terminals are wired, the following techniques must be followed when wiring the B-LINK-AC BACnet MS/TP repeater. Port 1, marked (Input), must have its MS/TP bus shield connected to the SHLD terminal, which is isolated from Earth Ground. The incoming MS/TP shield must be grounded at only one point, at a location other than the repeater. Typically this is at the opposite end of the bus, or where the MNB-1000, UNC, ENC or other BACnet parent controller resides. All four of the other repeater ports, # 2 - 5, have their SHLD terminals tied together, and tied to Earth Ground internally, through the power supply's Earth Ground connection. For each MS/TP bus cable connected these ports, the single point of ground for the shield is at the repeater and, therefore, the shield must not be grounded at any other point on the bus. None of the five MS/TP ports on the repeater have internal termination resistors.  If a MS/TP trunk ends at the repeater, a 120 ohm terminating resistor must be connected between the MSTP+ and MSTP- terminals on that port of the repeater.  Likewise, the far end of each MS/TP trunk must also be terminated with a 120 ohm resistor between the MSTP+ and MSTP- terminals of that last controller. None of the five MS/TP ports on the repeater have internal bias resistors.  Standard practices, regarding the biasing of the MS/TP trunks, should be applied, as described in the I/A Series MicroNet BACnet Best Practices Guide, F-27360. Additional information on the use of these repeaters can be found in the "Approved MS/TP Repeaters" section of Chapter 5 of the I/A Series MicroNet BACnet Smoke Control Systems manual, F-27419.

Issue In an environment where the Security Expert database is installed on a remote SQL server (i.e. not on the same machine as the one where Security Expert Server is installed), can I use SQL Authentication for the connection between SX and SQL Server? Product Line EcoStruxure Security Expert Environment Security Expert Server Cause SQL Server supports two authentication methods: Windows Authentication and SQL Authentication. Security Expert supports Windows Authentication only. Resolution No, Security Expert does not support SQL Authentication. You must use Windows Authentication, i.e. a domain user account must be setup with permissions both to the machine where SX Server is installed and the one where the SX databases are installed. Please refer to the SX-SRVR Security Expert - Client Server - Installation Guide for more information on the installation pre-requisites. See also KB article Security Expert Multiple Machine Installation for Windows Authentication with Active Directory for further information on how to setup SQL Server and SX on different machines.

Issue BACnet/IP port supported with EcoStruxure Building Operation 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 Edge Server - Standard Cause Which BACnet/IP ports are supported with EcoStruxure Building Operation, and can there be more than one port? Resolution By default, the BACnet/IP network uses UDP port 47808 (0xBAC0), this is adjustable higher or lower. The BACnet/IP network supports a single BACnet UDP port, Additional IP networks can be created in the BACnet system as long as each network has a unique identifier (network Id and name) and UDP/IP port number. Refer to: Creating an Additional BACnet IP Network (se.com) and Best Practices When Configuring BACnet IP Networks and BBMDs for EcoStruxure BMS Servers Please note that BACnet/IP uses UDP as its transmission protocol. For more information read the BACnet/IP basic design criteria.