Building Automation Knowledge Base

Issue Contact info for Schneider Electric Buildings Business Order Entry in the UK Environment Purchasing UK Price and Delivery information Cause For all questions from end users, pricing and delivery information. Resolution UK CCC in Telford: Phone 0870 608 8608 Email OrderEntry.UK@Schneider-Electric.com

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 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 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.  

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 Enabling Scattered read for Modbus device that doesn't support it can lead to poll fail, with Point Modbus Error: Illegal function code. Product Line EcoStruxure Building Operation Environment Building Operation Workstation (1.5 and above) Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Building Operation Enterprise Server Cause Requirement to optimize communication over Modbus to improve performance. Resolution The following is an extract from Web Help. The complete section can be viewed at  Modbus Batch Read Function:   'Scattered read is an enhancement to the batch read function that enables multiple, non-contiguous slave device registers to be read in a single Modbus query. By using the scattered read function, you can enable the Enterprise Server or Automation Server to avoid reading a large block of contiguous registers when it is only necessary to read a few registers. Also, using scattered read avoids the multiple use of group function codes 03 (analog output holding registers) and 04 (analog input registers) in order to read non-contiguous registers. Group function codes 01 (discrete output logic coils) and 02 (discrete input contacts) are not supported for scattered read.   Scattered read is available only for supported devices, for example, Schneider Electric branch circuit power meters with split core CTs. Furthermore, the scattered read function applies only when the Enterprise Server or Automation Server is operating as the client, not as a server. You can enable the scattered read function in the properties of all Modbus devices. If a device does not support scattered read: In V6 or higher: the polls will fail with an Illegal function code, so scattered read needs to be disabled if not supported by the Modbus device. In V5 or below: the device is polled by the master device in the same way as if you had not enabled scattered read.'   The image below shows the properties dialogue window for a Modbus device and the corresponding setting.  The left is version 3.1 and above, the right is version 3.0 and below where it is referred to as 'Non-contiguous read'.  Refer to the Modbus TCP Device  section on Web Help for more information.     

Issue Managing communication between I/NET and StruxureWare Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Enterprise server level integration I/NET Automation server level integration StruxureWare Building Operation 1.6.1.5000 and above. Cause Users should manage data flow on the controller LAN in order to maintain efficient communication. Any binds to objects under the I/NET interface follow the settings for the INET Global device scan rate (min) and the INET Global point scan rate (s). By default, this is set to 60 minutes for device status and 5 seconds for point bindings. The INET Global device scan rate (min)  is used to monitor online devices. A device will show offline sooner than the configured setting as all points would show offline.  The  INET Global point scan rate (s) is applied to all binds between StruxureWare and I/NET.  Opening a graphic or watch window will ignore this rule and immediately request values. After that, the scan will update according to the configured setting. A controller can either follow the Global scan rates as by default or use its own setting.  When a controller has the property DCU scan rate or point scan rate set to 0, it will follow the scan rate configured for the I/NET interface. An I/NET 19200 speed Controller LAN will handle a maximum of 10 token cycles per second. Each cycle allows a single packet of information to be passed from a single controller to the server. 1 Packet can contain all data for up to 18 points on a single controller. This means binding to manual, value, and PvControl for 18 points on a single 7718 will take one packet. Binding only the value of 5 points on 5 different controllers will take 5 packets. Adding devices to the controller LAN and adding additional polling will slow down the number of cycles per second on the controller LAN. Resolution All active binds will poll every scan interval. Graphic binds are only active when the graphic is open. Trend Logs will poll every scan interval regardless of the log configuration options.  Whenever possible, use the I/Net Alarm and Trend objects rather than creating separate StruxureWare alarm and trend objects. Trend Log Best Practices: Use the I/NET Trend Extension as outlined in Using I/NET trends in StruxureWare Building Operation please refer to the online help guide for complete information. Create Extended Trend Logs of this information for long term storage. I/Net Alarm Best Practices: Use the I/NET point extension to configure the alarm to be triggered by logic within the I/NET controller. I/NET Alarms have 3 priority options which are Routine, Priority, and Critical. This can be globally assigned to any priority using the I/NET interface messages tab. Other StruxureWare Alarm enhancements are available to I/NET objects as well. Scheduling and programming I/NET from StruxureWare Whenever possible, bind values to a single I/NET controller per controller LAN and then create I/NET Global/Indirect point relationships to distribute this value to other devices on the controller LAN. Using a single controller allows more information to be sent per packet. I/NET Global points will only broadcast on change. In this scenario, the server is polling a single controller ever scan interval and then on change all other controllers are updated. Increase the Point scan rate Using the information above you should be able to calculate how many packets are required for your system for each token pass. If this number increases to the point that more packets are required than are possible in the default 5 seconds, increase the scan rate. You can increase it on specific over loaded controllers or on all controllers together.

Issue What is the correct procedure for replacing a Continuum bCX 4040 controller Product Line Andover Continuum Environment CyberStation bCX 4040 Cause Considering both Continuum and BACnet 'sides' replacing a bCX4040 can seem a complicated process. Resolution Commission new/replacement bCX through its default webpage just as the as old bCX except for the BACnet Configurable Properties section. Set the BACnet Device ID = The same ID in the old bCX (serial number of controller by default) Set the BACnet Port Number UDP = same as old bCX (BAC0 by default) Set the BACnet Network ID UDP = same as old bCX (1 by default) Set the BACnet Network ID Comm2 = same as old bCX (2765 by default) Set the BACnet MAC ID Comm2 = Same as old bCX (0 by default) Set the BACnet MS/TP Enhanced Mode = Same as old bCX (TRUE by default) Set BACnet BBMD Enabled/Disabled = Same as old bCX (False by default) Bring the bCX online in Continuum Explorer, Select menu item Options | Send to Controller options Select "Reload attached objects, but not attached controllers" - select ok Verify the bCX Comm2 settings and baud rate speeds. In Continuum Explorer, right click on the bCX and perform a "send to controller" Verify points and communications.

Issue Procedures and processes to secure I/A Series G3 (AX) Systems Environment I/A Series Niagara G3 (AX) Systems Cause Users accessing system without permission Potential damage done by malicious entry to the system Resolution The attached document describes how to implement security best practices in an I/A Series Niagara G3 system. While it is impossible to make any system completely impenetrable, there are many ways to build up a system that is more resistant to attacks. In particular, this document describes how you can help make an I/A Series Niagara G3 system more secure by carefully configuring and using.  Passwords Accounts and Permissions Authentication TLS and Certificate Management JACE-8000 Settings Additional Settings Please note that while all of these steps should be taken to protect your I/A Series Niagara G3 system, they do not constitute a magic formula.  Many factors affecting security and vulnerabilities in one area can affect security in another; it doesn't mean much to configure a system expertly if your JACE is left physically unsecured where anyone can access it.  Note: Schneider Electric strongly recommends upgrading to the latest I/A Series G3 version 3.8 maintenance build that implements numerous security updates.  Before updating any system, make sure to review the build included documentation to understand the behavioral impacts of the security enhancements. Download the Niagara AX Hardening Guide for more details.

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 After rebooting the PC, TAC Vista Server (TACOS) doesn't get a license. You need to restart TACOS after each reboot to get a license. Product Line TAC Vista Environment TAC Vista License Server TAC Vista Server Cause TAC Vista Server (TACOS) starts up before the license system is ready to serve licenses, and therefore everything is offline until you restart TACOS. Resolution Download these tools TAC Vista Run Mode TACLicenseServer Settings (only for TAC Vista 5.1.8 and later) First of all, make sure that you have a system that is working normally and has the appropriate default settings. For more information, watch this video on YouTube Make the following setting in TACLicenseServer Settings [1] Set the startup type to "Automatic" and the taclic port to 2170 [2] Click the "License Setup" button, and write the name or IP address of the local PC. Don't use "localhost" or 127.0.0.1 but the actual name or IP.   [3] Click the "License Files" button, and check that only valid license file(s) is present in the license files folder - no other files can be in this folder. [4] Start the license server Make the following setting in TAC Vista Run Mode [1] Enter the username and password of a user with local administrator rights that have at some point been logged in on the PC. LocalSystem can be used, but it is not recommended. [2] Set TACOS to run as a service [3] In "Service Tools" set the service to start type "Automatic Delayed" [4] Start the service Now reboot the PC If TACOS still doesn't get a license after a reboot, try making this additional setting in TAC Vista Run Mode [1] Stop the service [2] Make the service depend on the license server, and also the Loytec driver if it is used in the system. Now reboot the PC If TACOS still doesn't get a license after a reboot, try adding this environment variable to Windows [1] Open the properties for the computer (Click the Windows start button, right-click "Computer", click "Properties") [2] Click on "Advanced system settings" [3] Add a new system variable called "TCP_NODELAY" and give it the value 1 Now reboot the PC If TACOS still doesn't get a license after a reboot, contact Product Support Services and reference this article Now reboot the PC If TACOS still doesn't get a license try making this additional setting in TAC Vista Run Mode Now reboot the PC If TACOS still doesn't get a license try making this additional setting in TAC Vista Run Mode

Issue Getting the error "The RPC server is unavailable" when attempting to write to a Vista Database.  This error can also be shown in the plug-ins output pain as "Error: Failed to access object xxxxxxxxxx." Product Line TAC Vista Environment TAC Vista System Plug-in Cause Incorrect DCOM or Firewall settings. This often occurs when installing a new system or restoring an existing Vista Database to a new PC. Computer is running out of memory. Resolution If it is cause due to computer memory shortage, please restart the TAC Vista Server. If the restart does not solve the issue, please follow the steps below. Install the DCOM utility located in Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET. or manually set the DCOM settings as instructed in the TAC Software Installation Unzip and execute the utility. If the problem persists and Vista Server is not on the local machine, ensure there is not a Firewall preventing a connection. If steps above does not resolve the issue, please reinstall TAC Vista software.

Issue Necessary steps to successfully install a "Stand Alone" versions of the Vista suite where a full Vista installation is not required. Product Line TAC Vista Environment Menta XBuilder Graphic Editor TGML MTA XBP Cause Sometimes a site may not require a full Vista package but will require the ability to edit associated Vista programs. This is the proper way to install only a portion of the Vista Software Suite. Resolution Create a account to the Download Center. Download the needed "stand alone" programs of the desired version, download here: Menta XBuilder Graphic Editor Download a matching version of the "stand alone" License Server, download here. Execute the downloaded programs on the host PC Order appropriate licenses using following program part numbers to validate the software (links to iPortal) Menta 000882401 XBuilder 000882411 Graphic Editor 000882221 (For an existing site requiring an upgrade from older Vista IV or Vista 5.0) Menta Upgrade Pricing 000883401 XBuilder Upgrade Pricing 000883411 Graphic Editor Upgrade Pricing 000883221 An Entitlement will be mailed which must first be Hosted to the PC. This is performed on the schneider-electric.flexnetoperations.com website by following How to Host a Vista Site License. License the Software on the License Server (Stand-alone Licensing for Vista 5 Applications)

Issue How to filter in a listview AlarmEvent based on the EventNotification Environment Continuum Cause Continuum pre 1.91 did not allow filter in a listview AlarmEvent, based on the EventNotification Resolution See Continuum CyberStation Release Notes Version 1.91(Downloadable here) Fixed Problems 4.007 Cannot filter an AlarmEvent table based on the EventNotification using the query wizard (21101) Find another way to filter or upgrade your version of Continuum.

Issue Does the Xenta Server firmware version have to match the TAC Vista Server version? Product Line TAC Vista Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 Vista Server Cause This situation usually occurs when upgrading a site. After the Vista software has been brought up to the latest version, does each Xenta Server also have to have its firmware upgraded to match? Resolution Whenever possible it is best to have the Xenta Server firmware version match the Vista Server version. However, if this is not possible, then ensure that the Vista Server is always of a later version than the Xenta Server. For example: a Vista 5.1.5 Server is okay with a Xenta 5.1.4 server, but a Vista 5.1.5 Server may not operate correctly with a Xenta 5.1.6 Server. The table below describes the compatibility between the TAC Vista Server, TAC XBuilder and TAC Xenta Server applications/firmware; third party dependency, e.g. java, not considered. More information about the table above including footnotes can be found in the document TAC Vista v5.1.8, TAC Xenta 500 700 900 v5.1.8 - Release Notes section 12.3. Consult the release notices for release software to identify defect corrections, new features, and potential changes in compatibility. If the versions are compatible then the decision to upgrade is up to the user, scheduling, and access to the units in the event of a failed upgrade units are remote. To upgrade a Xenta Server in Vista right click on the Xenta Server and select properties. Change the XBuilder Version property to the version of System Program and XBuilder being used. Note: In a specific situation there has been issues with the Xenta Server password in the properties window in Workstation. In this situation the Workstation was at version 5.1.8, the Xenta server was upgraded to 5.1.9, and then the XBuilder project was downloaded to the Xenta Server again. The Xenta Server was offline in Workstation. When the properties window was opened, the Xenta server password was much longer then it should have been. By reentering the password and clicking Okay, the Xenta Server came back online.

Issue What HID Corporate 1000 card formats are supported by Security Expert? Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Controller Security Expert Smart Card Reader Cause Information about HID Corporate 1000 card formats is needed to configure the card readers correctly. The existing documentation does not mention this. Resolution HID Corporate 1000 35-bit format has been validated with Security Expert. To use this go to Expanders | Reader Expanders | Reader 1 and set the Reader 1 Format setting to HID Corp 1000 as shown below. Other HID Corporate 1000 formats may work however they have not been validated. If the format specification is known, it is possible to program the cards in a custom format. As an example, below are the custom format settings used for the HID Corporate 1000 48-bit format cards. Go to the Custom Reader Format tab of your controller and enter the following values. HID Corporate 1000 48-bit format 1 HID Corporate 1000 48-bit format 2 If the format is different from the above two examples or is not known, please provide support with the site code, card number and raw data output for Any Bit RAW card reads from at least three different cards to help determine the format. Refer to article Show raw card data of a badged card in Security Expert for further details on this.

Issue After a successful commission of MP-x SmartX controller, the device is online and operating properly but fails to come back online after a warm start. The issue is seen more often when MP-x device is configured for DHCP but can also happen when configured for static IP address. (See the attached video which demonstrates the issue) Product Line EcoStruxure Building Operation Environment Building Operation SmartX IP Multi-purpose Controller (MP-X) Building Operation SmartX IP Room Controller (RP-C) Building Operation SmartX Controller IP-IO Series Cause Communication settings out of sync between the physical device and configuration database Resolution To synchronize the IP settings between the device and the configuration database follow these instructions from the online help  Discarding MP Series Controller IP Network Settings Changes

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 Poor communications between AS-P and Deep Sea Electronics (DSE) generator and switchgear modbus RTU slaves. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Cause When upgrading from an AS to AS-P, poor Modbus communication is seen between the AS-P and DSE slave device. The communications when using the AS was seen to be good. Using an AS-P, poor communication is seen between the AS-P and the DSE slave device. Resolution Firstly, on the AS-P, ensure the release is v3.2.3.8000 to improve the modbus RTU polling. Then if the issue still persists, make the adjustments to the DSE device as below. If the AS-P cannot be taken to v3.2.3.8000 then continue with the adjustments to the DSE device.   On the DSE Modbus slave, there are additional parameters as well as the baud rate, parity and stop bits. Access to these parameters is by using the DSE software tool. The additional parameter is the Inter-Frame delay. Change the Inter-Frame delay from 0ms to 1ms.

Issue Need information on securing a building automation system. Environment Best practices Cause End user has requested assistance for their IT department to secure the building automation system. Resolution Click here to get a copy of Best_Practices_for_Securing_an+IBMS_WP.pdf,  a white paper written by Schneider' Electric's Buildings BU IT Security Group. This also located on the Download Center here