Building Automation Knowledge Base

Issue When swiping card, the access is denied. The message shown in AMT is "Bad Card Read". Environment I/NET Cause There may be two causes for this message: The tenant code isn't correct when using Wiegand 26 format in the door parameter. The digit of card number exceeds the setting in the setting of card reader type. For example, the card format is Wiegand 35, but in the door parameter, the card reader length is set to 36 digits. Resolution For cause 1, enter the correct tenant code in the Tenant Editor. For cause 2, set the correct card reader type and digit.

Issue Before installing Access Expert on premise server software, the Mongo DB must be installed and the Mongo service started, this requires creation and editing of a configuration file where the data and log directories are specified. There have been many cases of YAML errors seen during V3 on premise installation when attempting to start the Mongo service. Product Line EcoStruxure Access Expert Environment V3 Mongo DB Cause The YAML parser that reads the "mongod.cfg" file is very sensitive to the format of the configuration file including some very strict rules about spaces, double quotes and back slashes. When editing the file, it helps to setup the text editor to display ALL characters which will show any hidden characters that might be causing a parsing error. Ex. In Notepad++: Select View>Show Symbol> Show All Characters Resolution Space is needed between key and value pair. Enclose paths in double quotes. Double back slash required in Windows systems.

Issue Not possible to get a Xenta Server / 911 online in TAC Vista. It is possible to ping it and connect to it via a Web browser using ports 443, 80, and Port 1068 is open, but it is not possible to get online in Vista. Product Line TAC Vista Server Environment TAC Vista TAC Xenta 911 TAC Xenta Server Cause The problem, in this case, was that another Vista server was connected to the Xenta Server / 911.  This could have been from a technician or the customer who started Vista with this database loaded and had the device online in their Database. The Xenta Server / 911 will only communicate with one Vista Server at a time and will close the connection if another Vista tries to communicate with it.    Using Wireshark it is possible to monitor this scenario as shown below:  Packet number 57439: Vista is trying to establish communication with the Xenta Server or 911( sending an SYN). Packet number 57440: The Xenta sends an acknowledgment on the SYN from Vista, but with the window size set to zero, this is because the Xenta can't buffer information as a computer does. Packet number 57441: Vista  sends an acknowledgment on the message from the Xenta Packet number 57448: The Xenta sets the correct window size. Packet number 57449: Vista starts to communicate Packet number 57452: The Xenta closes the communication to the Vista server  Resolution Ensure only one Vista server is started when the Xenta server / 911 is included in the database.

Issue The need to verify the proper wire positions on a Xenta Server device Environment Vista XBuilder Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause Installing a Xenta Server device on a network Resolution Table 2.1: Connections on the Xenta device Position Description 1-2 Power supply. Minimum cross-sectional area 0.75 mm2 (AWG-19). 1 (G) - 24 V AC (or DC+) 2 (G0) - Ground 3-4 LonWorks TP/FT-10 connection 3 (C1) 4 (C2) 5-8 Internal port A RS-485 A connection 5 (RX/TX+) 6 (RX/TX-) 7 (RX+) 8 (RX-) Note that the interface RS-232 A (position 21) and interface RS-485 A (position 5-8) are internally connected to port A on the processor. Only one should be connected. 9 Ground 9 (G0) 10 Fail-safe Note Jumping these pins together while cycling power will flash the device and load the minimum amount of drivers necessary for communication. If an IP address has already been assigned fail-safe will NOT remove it. 11-15 Unused 16-17 Ground 16 (G0) 17 (G0) 18 Unused 19-20 Internal port C RS-485 C (SDLC) connection 19 (RX/TX+) 20 (RX/TX-) 21 Internal port A RS-232 A connection. Note that the interface RS-232 A (position 21) and interface RS-485 A (position 5-8) are internally connected to port A on the processor. Only one should be connected. 22 Internal port B RS-232 B console connection 23 Ethernet 10Base-T connection 24 Service pin Caution G0 equals GROUND. Only G0 may be connected to protective ground.

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 for assistance. Issue In some cases, the event and trend databases can grow really big, although not all the space in the files is used. Therefore, one needs a way to verify that vacuuming the database will help. Product Line EcoStruxure Building Operation Environment SQLite Building Operation Enterprise Server Building Operation Enterprise Central Cause Frequent inserts, updates, and deletes can cause the database file to become fragmented - where data for a single table or index is scattered around the database file. Running VACUUM ensures that each table and index is largely stored contiguously within the database file. In some cases, VACUUM may also reduce the number of partially filled pages in the database, reducing the size of the database file further. Read further information here: https://www.sqlite.org/lang_vacuum.html Definitions are documented here: https://www.sqlite.org/pragma.html  PRAGMA schema.freelist_count; Returns the number of unused pages in the database file. PRAGMA schema.page_count; Returns the total number of pages in the database file. PRAGMA schema.page_size; Returns the page size in bytes (B), which must be a power of two between 512 and 65536. Resolution Stop the Enterprise Server or Enterprise Central. Open SQLiteStudio (link to download) Select "Databases" --> "Add database" Find the event.db or trend.db file from the "historical" folder of the EBO database folder. Use this article to locate for your installation - Clean db for Enterprise Server or Enterprise Central On the added database, right-click and select Connect to the database In the query tab, paste the following command: SELECT (SELECT freelist_count FROM pragma_freelist_count()) AS FreeList_Count, (SELECT page_count FROM pragma_page_count()) AS Page_Count, ((SELECT page_count FROM pragma_page_count()) - (SELECT freelist_count FROM pragma_freelist_count())) AS Used_Page_Count, ROUND(CAST((CAST((SELECT freelist_count FROM pragma_freelist_count()) AS REAL) / CAST((SELECT page_count FROM pragma_page_count()) AS REAL)) * 100 AS NUMERIC),2) AS Percent_Free, (SELECT page_size FROM pragma_page_size()) AS Page_Size_B, ROUND(CAST(((SELECT freelist_count FROM pragma_freelist_count()) * (SELECT page_size FROM pragma_page_size())) / (1024.0 * 1024.0) AS NUMERIC),3) AS Estimated_Space_MB; Click the blue play button above the Query tab.  Review the Percent_Free and Estimated_Space_MB, which will be returned at a minimum, to decide if you want to perform the 'vacuum' command. The vacuum process is slow, as it was designed to operate in the background. Shrink the SQLite event and trend databases. If the Percent_Free is above 80, this is the better option: Shrink the SQLite event and trends databases (Option 2) by creating a new file.

Issue EBO system was in sync with Building Advisor Portal and is now not. Product Line EcoStruxure Building Operation, EcoStruxure Building Advisor Environment Building Operation Building Advisor Portal Building Operation Enterprise Server Building Operation Automation Server Cause System ID changed and no longer matches in Building Advisor Portal. Resolution Check EBO Server Trace Log for nsp.pin.Cloud records and there should be one that shows "SystemId". Here is an example: 2023-11-19 12:37:30.437 [320] nsp.pin.Cloud.DspInterface Sending notification {"ProtocolVersion": "1.0", "NotificationType": "TimeSeries", "IotDeviceId": "urn:dev:ops:sebms-sbo-es-fb6b2834ba4749d89cdad333c12704a3", "SystemId": "4ba3db45-0235-7146-981a-c81dc08e39bf", "GeneratedAt": "2023-11-19T12:37:30.0437Z", "GeneratedBy": "SBO 3.2.4.22","Operation": "Update","TimeSeries": [{"TimeSeriesId": "d8e6b6fc-a472-4285-a56d-2d3e4a6915e1","Samples": [{"Timestamp": "2023-11-19T12:37:30.0437Z","Value": "Unknown [null]","Unit": "0x10001","Status": 20}]}]} 2023-11-19 12:37:30.437 [320] nsp.pin.Cloud.DspInterfaceReal edgeAgent_sendMessage: {"ProtocolVersion": "1.0", "NotificationType": "TimeSeries", "IotDeviceId": "urn:dev:ops:sebms-sbo-es-fb6b2834ba4749d89cdad333c12704a3", "SystemId": "4ba3db45-0235-7146-981a-c81dc08e39bf", "GeneratedAt": "2023-11-19T12:37:30.0437Z", "GeneratedBy": "SBO 3.2.4.22","Operation": "Update","TimeSeries": [{"TimeSeriesId": "d8e6b6fc-a472-4285-a56d-2d3e4a6915e1","Samples": [{"Timestamp": "2023-11-19T12:37:30.0437Z","Value": "Unknown [null]","Unit": "0x10001","Status": 20}]}]} (retCode = 0) In Building Advisor Portal, check the BMS System Identifier to ensure it is the same and update as needed. In this case, d057cfba-9fc0-11e4-a62a-3417ebbed129 needed to be updated to 4ba3db45-0235-7146-981a-c81dc08e39bf

Issue How can the AS-P be used as an LPA interface? Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Premium. Cause Working with Loytec LPA in  Building Operation and needing a remote interface for connectivity. Resolution To configure the AS-P as an interface in Loytec LonWorks Protocol Analyzer (LPA), follow the steps below: Ensure that you have the Loytec LonWorks Protocol Analyzer (LPA) software installed and licensed. Activate the AS-P as an LPA interface: Access the Loytec LonWorks Protocol Analyzer (LPA) software. Locate the settings or configuration section. Enable the option to "Activate AS-P as LPA" to designate the AS-P device as the interface. Add AS-P as a remote network interface in LPA: Within the Loytec LonWorks Protocol Analyzer (LPA) software, navigate to the network interface settings. Look for the option to "Add AS-P as Remote Network Interface" and select it. Keep in mind that by using the AS-P as the LPA interface, you will only be able to capture and analyze the traffic addressed to or from the AS-P device itself. Network traffic between other devices on the LonWorks network may not be captured using this configuration.   It's important to have the Loytec LonWorks Protocol Analyzer (LPA) software installed and properly licensed to perform these steps.  

Issue Are examples available to show how to write Plain English programs and create points for a Modbus RTU X Driver linked to Schneider Electric Power meters? Environment Modbus RTU X Driver Schneider Electric PM800 Power meters. Cause How can Modbus RTU X-Driver programs be written to poll for the data in a 3rd party Modbus device? Resolution The attached example show how to use the modbus RTU x-driver to read 4 16 bit data values from the PM800 meter, then using plain english to get the values to output to a single infinity numeric the total Power reading in kWH/mWH/gWH depending on the scaling factor of the meter. Create 4 Numerics reading the four registers that are used to store the data. Registers, 1716, 1717, 1718, 1719 are used in the PM800 Then create another numeric and via PE do the following calculation Energy Calc = (Register 4 x 1000000000000) + (Register 3 x 100000000) + (Register 2 x 10000) + Register 1. This will give you the value in wH. Then use a multiplier to give you the final reading in kWH etc.

Issue Licenses for MS SQL Server 2008 are becoming difficult to source, is MS SQL Server 2012 going to be supported? Product Line Andover Continuum Environment Continuum Microsoft SQL Server 2008 Microsoft SQL Server 2012 Microsoft SQL Server 2014 Cause As retailers deplete their old stock, it will become harder and harder to obtain licensing for MS SQL Server 2008 which is the most recent version of MS SQL Server that Continuum v1.94 supports. Purchasing SQL Server 2012 licenses to downgrade deployment rights does not seem to be an option with current Microsoft licensing as this option only applies to volume licensing and not retail license packages. (Refer to page 16 of the Licensing Reference Guide from Microsoft here.) Resolution Continuum v1.94 was not qualified with MS SQL Server 2012 at the time of release, this has since been tested and qualified with Service Pack 1 for Continuum v1.94. Please see the Continuum Compatibility Matrix in Software and Firmware compatibility matrix for older versions of the traditional product lines for details of supported environments. To use Microsoft SQL Server 2012 you will need to upgrade your installation to Continuum v1.94 SP1 or higher. You will be able to use MS downgrade rights to downgrade an SQL 2014 license so that SQL 2012 can be installed. See references from Microsoft below. http://www.microsoft.com/licensing/about-licensing/briefs/downgrade-rights.aspx http://www.microsoft.com/licensing/about-licensing/sql2014.aspx For sites using Continuum v1.94 or older that do not wish to upgrade, downgrade deployment rights can be used with volume licenses of MS SQL Server 2012 to deploy an older version of SQL Server (say MS SQL Server 2008 R2 that is currently qualified with the version of Continuum you have). Note: Continuum v1.94 SP1 has been qualified with MS SQL 2012 (SP1) but has not been tested with SQL 2014.

Issue AVU2201 Replacement Product Line Field Device Environment AVU2201 Cause AVU2201 obsolescence, replacement required. Resolution The replacement actuator is the MZ300S-24F actuator.

Issue MP/RP-x device is not pushing firmware down to Room Units (RU) when sensors are attached to the sensor bus. Disconnecting and re-connecting the RU does not help Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Cause The MP-X controller's file system has been re-initialized and the Room Units firmware files deleted. One case under which this will happen is when the MP/RP-X is factory reset.   The Device Report can be used to confirm whether the files exist in the device or not.   If Room Unit files are not shown in the report then no download to the RU will take place. Resolution Perform an upgrade on the MP/RP-X device, upgrading the device to the same version that is already running will resolve the issue.

Issue Can the DC1100 / DC1400 serve more than 2 boilers Environment DC1100 DC1400 Cause Can the DC1100 / DC1400 serve more than 2 boilers? Resolution The DC1100 or DC1400 is primarily designed for a 1 or 2 boiler installation. However in the case of 3 boilers. Note, 2 additional relays are required: Wire Boiler 1 to Boiler 1 terminals. Wire Boiler 2 to Boiler 2 terminals. Wire the coil of the 1st 230Vac relay to Boiler 1 terminals. Wire the coil of the 2nd 230Vac relay to Boiler 2 terminals. Either wire the relay contacts in parallel or in series, the feed for each contact will be wired from the Boiler 1 and Boiler 2 terminals respectively on the controller, the output of the relay contacts will be wired to Boiler 3. This is a workaround and does have its disadvantages: Boiler 3, when wired in parallel will always be a Lead Boiler and will do more work or when wired in series it will always be a Lag Boiler and will do the least work. In the case of 4 boilers: Wire the boilers in pairs to each boiler output on the controller. Note, the boilers will lead or lag in pairs. In the case of 5 boilers: Adapt both the solutions above.

Issue What configuration is required for a Multical BACnet heat meter Environment Schneider Electric (Kamstrup) heat meter connected to a Continuum or SmartStruxure system on MS/TP. Multical 61/62/601/602/801 Cause Setup information required Resolution With the BACnet interface card fitted in the Multical meter it is a native BACnet MS/TP device. Connect it to the AS or bCX1 depending on your system and Learn/ find BACnet devices. It should appear online and allow the objects to be uploaded. A typical unit like the Multical 602 will contain 12 Analog Inputs for all of the information from the meter. The Meter will operate at 9600, 19200, 38400, 57600 and 76800 Baud rates and autobaud to the connected system. For the Datasheet  Click Here. For the BACnet PICs statement Click Here. For help with Heat meter selection see the online selection tool: Online Heat Meter Selection Tool - PA-00216

Issue An AS has failed and there is no backup. Can the SD card from the broken AS be used in a new AS Product Line EcoStruxure Building Operation Environment Automation Server Cause AS has failed without any backup and there is a need to get the information to the new AS Resolution The SD card in each AS is encoded for that specific AS. The information on the SD card can only be read by that AS. AS's are now replaced by the AS-P, however if an AS can be obtained, then a backup can be recovered as follows:   It is possible to put the SD card from the damaged AS into a non damaged AS and do a backup. Then the backup can be restored into a new AS-P. The AS-P does not use a SD card. Important note: The version of the bad AS / SD card needs to match the donor AS used to make the backup. To remove the memory card push the metal retainer in towards the centre of the PCB The metal retainer will disengage its locking catches The metal retainer is hinged and can then be opened The memory card can then be lifted out for replacement Replacement is the reverse of the removal process.

Issue Internal counter stops counting. Product Line EcoStruxure Building Operation Environment Script Function Block Counter 167777216 Cause When this script is used it stops counting at 16777216. Numeric Output CountOut   Main: CountOut = 16777100 goto Counter Counter: CountOut = CountOut + 1   Resolution This issue was identified in the early days of Continuum and is regarded as a limitation, not a defect. Explanation - Internally the Script handles all numbers as IEEE754 single precision floats, which means that 16777216 is handled as 1.6777216E7. Adding 1 to 16777216 is unrecognizable in that representation. Using an IEEE754 converter at https://www.h-schmidt.net/FloatConverter/IEEE754.html, one can see that 16777216 and 16777217 have the same binary representation. The point at which the counter will stop, will depend upon the value being added each time, so adding 0.9 will count to a different number than adding 1. The counting range can be extended by two or more variables as shown below. Numeric Output CountOut Numeric CountOut1 Numeric CountOut2   Main: CountOut1 = 16777100 goto Counter1   Counter1: CountOut1 = CountOut1 + 1 CountOut = CountOut1 if CountOut1 = 16777216 then goto Counter2   Counter2: CountOut2 = CountOut2 + 1 CountOut = CountOut1 + CountOut2  

Issue There are a couple of part numbers available for the expansion module cables, which ones are for which devices? Environment xP modules Cause Not sure which cables are for which xP modules. Descriptions and documentation on iPortal is inadequate. Resolution There are three xP module cables available: The 01-0100-484 cable is a replacement for the xP-Display module cable and this is meant to be for the xP-Display only, not for any of the other xP I/O modules. The xP I/O modules such as xPDO4 require either the xP-Mod-Cable-3 or xP-Mod-Cable-10. Be aware that you will only be able to extend the xP network for a maximum of 10Ft. See this iPortal datasheet or on Exchange Extranet for details.

Issue Deleting BACnet objects using a BACnet Operator Workstation (BOWS) can permanently remove those objects from the BACnet device.  The effected devices can be Building Operation BACnet devices, e.g. Automation Server or third party BACnet devices. Environment Building Operation Enterprise Server Building Operation Automation Server 3rd Party BACnet Controllers Cause The BACnet controller(s) in question support BACnet create and delete services on the specific objects.  Resolution Functions as Designed If the device supports create and delete services for the object it is designed to function this way. In general the BOWS should provide as much as possible a complete and accurate image of the contents of the device.  For example using the Enterprise/Automation server as a BOWS:  Creating new objects will automatically send a create-object request and attempt to create the object in the device. Deleting objects will automatically send a delete-object request and attempt to delete the object in the device. Upload and Download of object commands attempt to synchronize the database with the actual contents of the device.  Download will attempt to create any objects that are in the database (but not in the device), and also attempt to delete any objects from the device which are not in the database. Upload adds or removes objects from the BOWS database. Please see Protecting EBO/SBO BACnet objects from being deleted by 3rd party BOWS for a method of preventing BACnet points being deleted from an Enterprise/Automation Server.  Consult third party documentation to identify preventing creation/deletion.   Offline Workaround If the device supports the Device Communication Control service, and allows disable, a work around is to make changes to the database while the device is offline. For example, using the Enterprise/Automation server as a BOWS, right click the device and select Device->Communication->Disable.    Open the property grid for the device and it should take about 12 seconds before the device is reported as offline.  Any other break in communication should also work to get the device offline.  Once offline, objects can be deleted from the database without affecting the device.  But, after changing the database this way, the device's "upload" or "download" commands should not be used, as it will re-synchronize the device and database (either deleting objects from the device, or adding them back to the database).  It is important to note using this method the BOWS will not fully represent the objects in the device and also remember to re-enable the communication to the device.

Issue Installing and Configuring Email Service Accounts in Niagara G3 Environment Niagara G3 Cause The need for a quick reference guide Resolution The following document can be found at Niagara-Central.com as well.

Issue How to use RoamIO to set the Infinet ID of Infinet device to zero before re-deploying the device. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum Service Tool Cause Need a way to set the Infinet ID of Infinet device to zero before re-deploying the device. Resolution  This video demonstrates… Tell if the i2 device has an Infinet ID assigned by observing the TD/RD LEDs on the device. Use the RoamIO to connect directly to the i2 device and reset its Infinet ID to zero. Confirm by visual observation of the device's TD/RD LEDs that the ID has been successfully set to zero.

Issue Not sure how to configure sending emails to multiple recipients when an Input or Area goes into alarm. Product Line Security Expert Environment Security Expert SP-C-WEB Cause Correct formatting must be used when sending alarms to multiple email recipients. Resolution Separate each address with a semi-colon and surround the entire string with double quotes, see examples below.   Security Expert Navigate to Events | Actions, create a new Send E-mail Action and add your multiple addresses to the E-mail Address field. "address1@email.com;address2@email.com" Email Addresses The email address field is limited to a maximum of 128 characters. All email addresses must be within this 128 character limit to be sent correctly. SP-C-WEB To add multiple recipient addresses, navigate to Programming | Areas or Programming | Inputs. For an Area, select the Configuration tab and add a recipient email address to the command window and use the format:email:"address1@email.com;address2@email.com" For an Input, navigate to the Commands window for your selected input and use the format: email:"address1@email.com;address2@email.com"