Building Automation Knowledge Base

Issue A large number of "A Log Data Transfer Has been Missed" events are being reported by the AS. All events are associated with b3 points that have intrinsic logging configured (where log configuration is part of the point properties configuration) and a StruxureWare Building Operation Extended Trend Log is attached to the point. Product Line EcoStruxure Building Operation Environment b3 Log Data Transfer Extended Trend Logs Cause We have seen these events reported when the number of log records configured in the b3 point is not evenly divisible by the Maximum Log Transfer Interval in the Extended Trend Log object. When the Extended Trend Log retrieves data from the objects intrinsic log in the b3 controller, it grabs this data in batches or portions. The size of these portions is defined by the Maximum Transfer Interval in the Extended Trend Log configuration. For example, where a b3's intrinsic log is set to 1 hour Log Interval and the Log Records is set to 72 (three days), if its associated Extended Trend Log has a Maximum Transfer Interval of 1 Day, the it will grab the first 24 records during the first pass, the next 24 records during the second pass and the remaining 24 records during the last pass. If the number of Log Records defined in the point configured is 80 instead of 72, the same Extended Trend Log will grab the remaining data in a fourth pass. However, if the amount of data remaining to be grabbed does not represent a span of time equal to the Maximum Transfer Interval, the Extended Trend Log will not grab a full period of data. In some cases when this happens data from this fourth pass can be lost and this will be reported as an "A Log Data Transfer Has been Missed: event. Example: Using our example above, and an intrinsic log Record Count of 80, the Extended Trend Log will grab the first 24 records during the first pass, the next 24 records during the second pass, the next 24 records during the third pass. It will then grab the last eight log records in a fourth and last pass. It is during the transfer of this last smaller group of data where there may be a failure of the data transfer. Resolution The number of Log Records configured in the points intrinsic log times the Log Interval should equal a period of time that is evenly divisible by the Maximum Transfer Interval time period. For example, if the Extended Trend Log is configured for a Maximum Transfer Interval of 24 hours, and the b3 point is configured for a 15 minute Log Interval, the Log Records can be set to either... Log Records = 96 (4 samples per hour X 24 hours -- a full days worth of data) Log Records = 192 (4 samples per hour X 48 hours -- two full days worth of data) Log Records = 288 (4 samples per hour X 72 hours -- three full days worth of data) and so forth.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Upgrading the MPMs firmware through the boot loader was unsuccessful. 10.50.80.2 is pingable, but not the default IP 10.50.80.3. The LED's keep blinking in tandem (alternating one after the other), even after having the MPM powered over 10 seconds. Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager Cause This can be triggered by multiple events: - MPM was interrupted (powered off) while the firmware was still being upgraded. - Database does not exist; MPM was formatted and does not have firmware installed. - Database is corrupt (for any reason) Resolution It is strongly recommended that a firmware upgrade be done via the "File Manager" tab in Building Expert. However, if this is not possible, an upgrade can be performed through the bootloader using the following steps: 1 - At the top left part of the screen, make sure "Status" says "Connected". 2 - Format the SD card clicking on the "Submit" button next to "File System Format". "Format Done" will be displayed next to the button once the format has been completed 3 - Click on the "Browse" button and Navigate to the Firmware_update_V2.XX.bp" on your computer then click on "Submit Query". 4 - The previous step will upload the firmware file to the MPM's SD card. Once the file has been transferred, the following message will appear: or 5 - The MPM Must be kept powered-up for at least 15 minutes in order to allow the MPM some time to unpack the firmware file. The best way to determine whether the MPM is back online is to ping its IP address using a "Command Prompt" window. 6 - Once the MPM replies to the ping, Building Expert can be accessible though 10.50.80.3   If the above solution does not work; meaning that every time a new firmware is pushed to the MPM, the MPM keeps coming back to the bootloader, contact technical support

Issue The Pelco Endura system with cameras at a location and integrating with the TAC I/NET Seven system. Product Line TAC INET Environment Check the system requirements for the version of TAC I/NET Seven and Pelco Endura  Cause Configuration requirements of the Pelco Endura and TAC I/NET Seven are specific for the functionality in I/NET. Resolution Once your Pelco Endura system is configured and the Workstation has discovered all the devices and the System Manager is online with the cameras correctly configured, there are four basic requirements to connect TAC I/NET. Cameras have to have a unique friendly name other than default. Cameras have to have a unique camera number. Netframework 3.5 has to be installed. Windows Media Player 11 has to be installed.   If using I/NET Seven Release 2.40a then the following applies: Once INET and the requirements above are installed the Endura Install can be run. The installer for these files is located on the INET CD in the folder: Support\EnduraSDK. Note: Endura video does NOT work on Windows Vista or Windows 7.   If using I/NET Seven Release 2.40 or above: Dual NIC support is now available. For Endura, 100GB NIC and Router are suggested. 1 for I/O Server, 1  for video   Equipment used: NSMS200 Pelco Endura Network System Manager & Network Video Manager SM5000 Pelco Endura System Manager WS5070 Pelco Endura Workstation with Advanced Management Software WS5000 Pelco Endura Work Station Software package NET5301T Pelco Endura Video Encoder Spectra IV Pelco Camera Visit Pelco.com for more information. Click here to view an extended compatibility matrix for Endura and I/NET.

Issue Troubleshooting guide for ASD bus communications. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series Legacy Controllers ( GCM, MicroZone II, MicroFlo II, LIM, PEM, MN-ASDI) I/A Series R2 UNC I/A Series G3 ENC Building Operation Automation Server Premium ( Pre EBO 2022 ) I/A Series N4 Jace 8000 Cause Troubleshooting guide for ASD bus communications. Resolution This checklist provides several settings/configurations to review when faced with a communication problem at the controller level. The content was compiled from different resources, summarized, and laid out in an easy-to-use manner so as to provide a quick-reference document. NOTE:  The ASD protocol is not supported in EBO 2022 or subsequent versions

Issue The Enterprise Server service keeps stopping, and Windows restarts it right away. This is preventing WorkStation or WebStation from logging on. When viewing the Building Operation Software Administrator, the "Start Service" option is greyed out, and the server status is Stopped. Product Line EcoStruxre Building Operation Environment Building Operation Software Administrator Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Workstation Cause The Enterprise Server or Central service uses TCP port 80 by default.  If another service on the PC is using port 80 (e.g., Internet Information Services), this will cause the service to stop and re-start constantly. Resolution Two options: Stop the conflicting service from running (e.g., IIS, Dropbox, Skype) Change the HTTP or HTTPS port in Enterprise Server or Enterprise Central to a unique port (e.g., 8080) To change the ports, open Software Administrator and stop the server if it is not already. Then the port fields will no longer be grayed out, and they can be changed. Finally, restart the server. Refer to: Configuring Server Port Settings Note: Once the port has been changed to a unique one, this must be specified when logging into WorkStation, as seen below.

Issue Cannot find any installation instructions documentation for the WorkPlace Tech Tool software, versions 5.8 or 5.8.1. Product Line TAC IA Series Environment WorkPlace Tech Tool software version 5.8 & 5.8.1 Cause An updated version of the document "WorkPlace Tech Tool Version 5.7 Installation Instructions" has not yet been released by our publications group. Resolution The existing "I/A Series WorkPlace Tech Tool Version 5.7 Installation Instructions", F-27367 can be used for installing the release 5.8 or release 5.8.1 of the WorkPlace Tech Tool software. There are two items applicable to the newer versions of the WorkPlace Tech Tool software that are not covered in the published installation instructions. The WorkPlace Tech Tool software, releases 5.7.7, 5.8 and 5.8.1 will run on the 32 bit versions of Windows-XP, Windows Vista or Windows-7.  These releases of the software will also run in XP-Mode under the 64-bit version of Windows-7.  See I/A Series (Niagara) R2 Windows Compatibility Matrix and the linked PA-00163 product announcement for more information on Windows 7 compatibility.  Make sure that the computer meets or exceeds the recommended requirements, not the minimum requirements, for the operating system being used. Beginning with release 5.8.5 of the WorkPlace Tech Tool software, Windows 7 64-bit Professional and Microsoft Visio 2010 is supported (32-bit version only), in addition to the documented Microsoft Visio 2003 and Microsoft Visio 2007 (32-bit versions). The use of Visio 2010 and its ribbon bar menu system are described in the WorkPlace Tech Tool release 5.8 release notes.  This same version of the release notes (5.8) is applicable to the use of Visio 2010 with the WorkPlace Tech Tool software release 5.8.1.

Issue Using BQL query to extract data from a G3 station How to display data from the BMS system on their custom / third party application. Environment I/A Series G3 Cause A requirement to display data from the BMS system on their custom application. Resolution You can query for data using a BQL (Baja Query Language) query. The Baja Query Language (BQL) is an SQL-like query language that provides a mechanism for identifying various sets of data. It provides an ad hoc way to search for data based on some criteria. 3rd party applications which is capable of running a web query can be used to query data from a G3 station. One such application is Microsoft Excel. The Niagara BQL Query Examples PDF provides several examples of BQL queries as well as an example of using Excel web query. Most data in a station can be queried including point values etc. For detailed description of BQL usage, refer to the Niagara Help in Workbench ( as shown below).

Issue Customers may need a copy of their License Entitlement certificate Product Line EcoStruxure Building Operation Environment Building Operation Licensing Cause Missing Entitlement certificate  Resolution Customers have access to the following link, where they can use the Entitlement ID or Activation ID to login to the Licensing page: License Page information After logging in, select the “List Entitlements” under “Activation & Entitlements” on the top. Tick the checkbox in front of one Activation ID (ACT), select View/View certificate Now, a new page pops up which contains the Entitlement Certificate information. This can be saved or printed.

Issue BACnet Alarm User Actions, Attachment and Presentation Product Line EcoStruxure Building Operation Environment Alarm handling and Presentation Server BACnet User Action, Attachment and Presentation Cause If the BACnet Alarm User Actions appear to be working incorrectly, the "Alarm handling and presentation" setting may be incorrect Resolution BACnet Alarm Enrollments only If the User Action, Attachment and Presentation from the Alarm itself are required then Alarm handling and presentation should be set to "Intrinsic" as below If the User Action, Attachment and Presentation from the BACnet Notification are required then Alarm handling and presentation should be set to "BACnet Notification object" as below NOTES When a b3 is created or a 3rd party device uploaded within Building Operation, the Alarm Enrollments and Alarm Notification Objects include Alarm handling and presentation properties (Presentation, User Action(Cause note, Action Notes, Comments, and Checklist) and Attachments tabs). These properties are stored only in the Building Operation Server (AS or ES) database. To use these properties, the "Alarm handling and Presentation" (in "Properties" tab “Basic”) should be set to "Intrinsic", as above, top example. The settings are saved only in the Building Operation database - as part of the notification class proxy, or the event-enrollment (or point object in the case of intrinsic alarms) proxy. Cause notes, action notes, comments, and checklist are Building Operation specific data, not part of the BACnet protocol. So there is no way for it to be sent to the device (b3, 3rd party or otherwise).

Issue When attempting to register a system, an error page is shown indicating a server error in the /ebo application   Error Text: Runtime Error An application error occurred on the server.  The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security settings).  It could, however, be viewed by browsers running on the local server machine.  Product Line EcoStruxure Building Operation Environment WorkStation Registration Windows Server 2012 R2 and above Cause While the error message points to an error in the back end server, it is actually due to a setting on the client PC. Enhanced security configurations in Internet Explorer on Windows Server systems, is blocking required content from being run. EcoStruxure Building Operation WorkStation uses Internet Explorer as the built-in browser and is therefore affected by this. Resolution While the enhanced security measures can be disabled altogether, the resolution with the smallest impact is to add the URL of the registration portal to trusted sites in Internet Explorer. Open Internet Explorer Open Internet Options Select the Security tab Click Trusted Sites Click Sites Enter the registration portal URL: https://registration.smartstruxure.schneider-electric.com Click Add Click Close Click OK After doing so, restart WorkStation, and attempt the registration again. For more information, refer to the WebHelp topic EcoStruxure Building Operation Registration Page is not Displayed.

Issue Modbus device in hand does not have a pre-configured widget in the device list of Building Expert. A script is required to communicate with the device Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager Any modbus device Cause Pre-configured widget not available in the device list of Building Expert Resolution The MPM can only be a Modbus Master; meaning it can request information from other slave modbus devices, or write to them. Terminals A and B on the MPM correspond to modbus terminals (Serial +) and (Serial -) respectively. When using a script to communicate with modbus devices, the "Enable" box in the ModBus configuration object (MOD1) must be disabled to allow the MPM to communicate with the devices using a script. The modbus port should then be closed (in case it was left open) and re-opened using the following functions ******************************************************** @@@ Lua.modbus.close       (Description and example here) ******************************************************** @@@ Lua.modbus.open        (Description and example here) ********************************************************     The following are the standard modbus functions and their corresponding Lua functions used in the MPM Modbus Function Code Lua Function in MPM Function Code 01 modbus.coil_read Function Code 02 modbus.di_read Function Code 03 modbus.hr_read (16-bit) Function Code 04 modbus.in_read Function Code 05 N/A Function Code 15 modbus.coil_write Function Code 06 modbus.hr_write   The following are the 8 different modbus functions that can be used to read/write to registers from/to modbus devices ******************************************************** @@@ Lua.modbus.coil_read     (Description and example here) This function is equivalent to : [Function Code 01 (01 HEX)] ******************************************************** @@@ Lua.modbus.coil_write    (Description and example here) This function is equivalent to : [Function Code 15 (0F HEX)] ******************************************************** @@@ Lua.modbus.di_read      (Description and example here)   This function is equivalent to : [Function Code 02 (02 HEX)] ******************************************************** @@@ Lua.modbus.hr_read       (Description and example here) This function is equivalent to : [Function Code 03 (03 HEX)] ******************************************************** @@@ Lua.modbus.hr_write      (Description and example here) This function is equivalent to : [Function Code 06 (06 HEX)] ******************************************************** @@@ Lua.modbus.in_read      (Description and example here) This function is equivalent to : [Function Code 04 (04 HEX)] ******************************************************** @@@ Lua.modbus.fp_read     (Description and example here) ******************************************************** @@@ Lua.modbus.fp_write    (Description and example here) ******************************************************** To read a floating-point (32-bit) value, the fp_read() function can be used. (Download script) To read an unsigned long (32-bit) value the hr_read() function can be used, however, some data manipulation is required (Download script) To read a floating-point (64-bit) value, the hr_read() function can be used. (Download script)   Modbus errors can be found here

Issue Alarm email is not sent out and is discarded. The Last Discard Cause is 'BOutgoingAccount could not dequeue in-memory email: 501 Syntax error in parameters or arguments'.  Environment I/A Series G3 Cause 'Reply To' field in the Outgoing Account properties was left empty. This field specifies the contents of the 'From' field in the email that is sent. Resolution Configure the Outgoing Account 'Reply To' field with a valid email account. In the example below (G3 version 3.7), the valid account being used is my.account@gmx.com. 

Issue Receive "Initialization error" when trying to start I/NET with SQL 2008 When we installing SQL Server 2008 Standard for I/NET Filemaster, what are the main components we should include? When editing / adding a new I/NET Configuration Profile the Database Server section is blank DBCreate does not start.  Appears in task Manager but no user interface is shown. Within DBCreate the restore option is grayed out Product Line TAC INET Environment I/NET Seven 2.4x Microsoft Windows Server 2003, Windows XP, Windows Vista, and Windows 7 families of operating systems. (both 32 and 64 bit) Microsoft SQL 2008 Standard or Express Editions Microsoft SQL 2008 R2 Standard or Express Editions Cause I/NET must have the SQL 2005 Backward compatibility file installed.  If this is not installed I/NET will not locate the SQL Server and hence will issue an “initialization failure” error.  This is can also be identified in either the DBCreate or I/NET Configuration application editors which will show no entries in their "Database Server" settings. The document also details information that is necessary for a Standard or Express editions of SQL 2008 / SQL 2008 R2. Resolution Follow the instructions below extracted from the document called "SQL2008 Expr Install Inst.pdf".  This document is found on I/NET Seven CD under the 'SQLExpress' folder.  For SQL 2008 R2 installations refer to the following document SQL2008 R2 Expr Install.pdf, also found in this same folder .  Installing SQL Server 2005 Backward Compatibility SQL Server 2005 backward compatibility must be installed for SQL 2008. To install SQL Server 2005 Backward Compatibility Navigate to the SQLBcm directory on the TAC I/NET Seven installation CD. Launch the SQLServer2005_BC.msi file. Follow the prompts on each screen and accept all defaults. After the install check the SQL Server Services SQL Server Browser is RUNNING SQL Server (MSSQLSERVER) is RUNNING Check the SQL Server Network Configuration Protocols Enable Named Pipes Enable TCP/IP Completing the Installation Proceed with the installation of TAC I/NET Seven on your PC. For installation instructions, refer to TCON298, TAC I/NET Seven Getting Started. Note: Run Inetcfg.exe before starting TAC I/NET Seven for the first time. This is necessary to attach TAC I/NET Seven to the database and avoid an “Initialization failure” error. Note: Before file equalization will operate, the system must be rebooted or the INETEQZMERGE service must be manually started.   Also refer to Installing I/NET 2.42 or higher and Vista 5.1.7 or higher on a 64-bit operating system for additional details on installing I/NET with SQL 2008 R2.

Issue Where can I find standard Plain English programs for common HVAC and security applications? Product Line Andover Continuum Environment Continuum Plain English Cause Schneider Product Support Services does not issue sample Plain English code.  Resolution There are a number of PE programs available on the Buildings Business Community. Plain English programmers can post samples of their code that may fit your application. Buildings Business Communities: Area 360 Documents

Issue During the installation of Workstation on a PC that didn't previously had any SmartStruxure software installed, you can get the message: "Failed to install XXXX redist, error: 3010" Product Line EcoStruxure Building Operation Environment Workstation Cause One of the build in Microsoft Visual C++ Redistributeable (VCRedist) installers (2008, 2010, 2012) is failing for some reason. Resolution Restart the PC and start the installer again Note: There is a similar issue but with error 1603, if you get this please see Getting the error "Failed to install XXXX redist, error: 1603" during installation.

Issue Security Expert does not run correctly after installation Product Line EcoStruxure Security Expert Environment Security Expert Cause While Security Expert will install and run correctly on a supported platform, there are occasions when an installed security policy will prevent the correct operation of Security Expert.  In the example below, the installation went smoothly, but when the user tried to log in to Security Expert the error "Error - Exception has been thrown by the target of an invocation" is seen. Thus the install could not be licensed. This example had SQL, Security Expert Server and Security Expert Client all installed on the same PC. Exception has been thrown by the target of an invocation Resolution If the new install does not run correctly, then install the software on a clean Windows platform, this will allow the site to be set up and commissioned. In the above example, the customers extra security policies were applied one at a time until the policy that caused the problem could be isolated.  

Issue Lost MPM IP address Product Line EcoStruxure Building Expert Environment SmartStruxure Lite MPM Cause Forgotten IP address Resolution 1. Connect your PC directly to your MPMs Ethernet port and set your computer network configuration to access the MPM at the default address of 10.50.80.3 (example, set your PC to use address 10.50.80.99). 2. Disconnect and re-connect power to MPM. 3. The MPM goes to Bootloader mode for approximately 10 seconds at start-up. You will see Blue and Green indicators (UN2/VA2 MPMs) alternate steadily during that time according to the following. a. While the MPM is in Bootloader mode, you can access your config.db file at 10.50.80.2/root/ config.db. b. Enter address in browser window before you restore power to not to miss the 10 second window. It may require more than one refresh attempt before you enter Bootloader. 4. The browser prompts you to open or save config.db file once successful connection is made. 5. Open file using text editor. 6. Search “ETH1_ip” field for IP address of your MPM to right side of “ETH1_ip”. 7. Enter IP address to browser address bar to access your MPM.

Issue Using provisioning Niagara to schedule (automated) ENC station backup Product Line TAC IA Series Environment I/A Series G3 (AX) version 3.3 and above Cause The station in an ENC (Enterprise Network Controller) can be copied to the ENS (Enterprise Network Server) computer for backup. This can be done by a user using the ENC's Platform Station Copier. There is a need to have an automated process to back up the ENC's station periodically. Resolution Use provisioning Niagara and configure an automated station backup. Provisioning Niagara means an administrator can configure the Enterprise Network Server automation of the following: one or more pre-defined tasks (station backups, install software, update licenses, and copy files) against one or more (potentially many) stations in its Niagara Network done from the Enterprise Network Server in a way where results are recorded and can be referred to later. Refer to this document for a summarized procedure. You should refer to the technical document 'Niagara Ax 3.5 Provisioning Guide for Niagara Networks' for detailed information on using provisioning in Niagara. This document is included with the installation of the I/A Series G3 software and it is located in '\niagara\niagara-3.x.xx\docs\docProvisioningNiagara'. 

Issue Niagara G3 station fails to send out emails and discards to the email with this error message: "BOutgoingAccount could not dequeue in-memory email: null" Environment Niagara G3 (AX) ENC and ENS stations (all versions) Cause After watching the output with debug turned on, the station connects to the email server and authenticates. When it tires to send out an email there is a null pointer exception and it discards the email. There is a trailing semicolon in the To Field of the EmailRecipient under Alarm Service. The email handler is looking for another email address after the last semicolon and sees a null when trying to add the last non-existent email address.   Resolution Remove the trailing semicolon.  

Issue Users or engineers may be unsure of how to access the best support for issues with EBO Smart Connectors, especially where site specific Smart Connectors have been developed, or believe the issue is with the underlying framework. Product Line EcoStruxure Building Operation Environment Integration Cause Unlike EBO, which is a standard EcoStruxure product that falls under normal R&D, the Smart Connector (formerly known as Mongoose) was developed by Schneider Electric Buildings Labs and a separate R&D Team.   Resolution If using a Smart Connector developed specifically for a project by a separate Integration Team within Schneider-Electric, then it is always best to go back to that team with your technical issues. In all other cases, the Smart Connector Framework is now supported via normal Product Support channels by raising a support case with your local Customer Care Centre, just as you would for any other EcoStruxure Issue.   The  SmartConnector Developer Forum: can still also still be found on the community.