Building Automation Knowledge Base

Issue An alarm goes on and off several times in a short amount of time. Each time the alarm condition clears and reasserts itself, by default, another email will be sent. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation SMTP alarms Cause Every time an alarm goes off, the email notification checks its parameter and, if true, sends an email. Resolution Filter the email notification by "count." Set it to "from 0 to 1" and you will only get a email on the first alarm (count).

Issue What is spacing for the screw terminal blocks of the SP-MRDM2 2 Door Mini Expander, and what do the terminal blocks look like? Product Line Security Expert Environment Security Expert 2 Door Mini Expander Cause Screw terminal block details needed for ordering spare parts. Resolution The 2 Door Mini Expander uses two different screw terminal blocks. The lower is the normal terminal with 5.08 mm pitch labelled 2EDGK, and the upper is upside down, also 5.08 mm pitch and labelled 2EDGKF. See also data on the manufacturer's website.

Issue When importing an XIF into SmartStruxure, errors can be generated that vary in nature. Product Line EcoStruxure Building Operation Environment SmartStruxure Enterprise Server SmartStruxure Automation Server Building Operation Workstation Cause The XIF does not import successfully for a variety of possible reasons: There exists a device template in the server already that contains the same device ID as the XIF that is being imported.  The XIF does not comply with the LonMark Device Interface File Reference Guide published by LonMark. Resolution Before performing any of the steps below: Import the XIF file provided by the manufacturer of the Lon controller - if the manufacturer did not provide a XIF, try searching the LonMark product catalog If the provided XIF does not work, upload the XIF from the device to ensure that it is the correct file by following How to extract an XIF out of a Lon controller. Use the SBO SNVT Support tool found on The Exchange to identify unsupported SNVT's. Work through the troubleshooting steps below.   Device Template Fails without an Error This issue has been seen in some of the older versions of SmartStruxure (1.5 and older) and upgrading to the latest version will resolve the issue in many cases. If the issue occurs at the latest version of SmartStruxure: Use the SBO SNVT Support tool located on The Exchange to identify unsupported SNVTs. If the SBO SNVT Support tool does not identify any unsupported SNVTs, then send the XIF in to Product Support for further investigation.    Device Template Already Exists In order to complete the import of the XIF, follow these steps. Delete all controllers in that database that are using the device template that has the same device ID as the XIF file you are trying to import.  Now import the XIF again. Select the server in the system tree on the left and go to File > LonWorks import > Device Template. Click the Browse button and select the XIF you want to import. Click Import. Note: When the import is complete it will have overridden the old device template with that device ID. Two device templates with the same device ID will not be able to reside in the same database. For more information about device templates see Delete Device Templates.   Detailed Error Prompt with Specific Fields Listed Some examples of the detailed errors include but are not limited too: "Field X has error(s). The string must between X and X characters. nvoActualCapacity has X characters" on row X. "Field X has error(s). The number must between X and X. Field X has value X." on row X. "Field X has error(s). The value must be X but was X." on row X. Space or tab are not allowed in field 0Node Object on row X.   To Address these issues: Download Notepad++ to be able to better navigate the XIF by row number. Using Notepad++, open the XIF. NOTE: Backup the original XIF just in case there is a mistake when modifying. Find the row and field number prompted by the error messages and modify them accordingly. All the rules can be found in LonMark Device Interface File Reference Guide published by LonMark. Import the XIF again to verify whether it works. If not, contact Product Support for further investigation.

Issue Lua Program for measuring EnOcean Signal Strength Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Cause Requirement to measure and alarm from the EnOcean Signal strength. Resolution Download either the txt file or c2g import file. The file is set to monitor 3 EnOcean devices, either copy the relevant sections to add more devices, or remove to reduce the number of devices. An AV is required for each EnOcean Device. In the Lua program, edit the EnOcean Device ID, this can be found in the "EnOcean Device Configuration" properties. In the Lua program, edit the AVs to those that are to be used. Edit the AV and add the ID in the description and any other description required. How the Lua program works: The Lua script is set to assign each AV an abnormal value (10000) after a time period in (3600) seconds. The EnOcean device will overwrite via the program the value in the AV when a value is received from the device. For an alarm, create an Event, set the high limit (9999) and a time period set to a value beyond that a signal is received from the EnOcean device. Set the low limit to -200. Notes: EnOcean devices send packets at varying times, some at change of state. The timer needs to reflect how often a packet is sent. Several Lua programs may need to be used and the EnOcean devices grouped with similar packet broadcast times. e.g. an infrequently used switch would be different to a temperature sensor.

Issue Tolerances for resistors when used for RS485 bus termination and EOL for double balanced inputs. Product Line Security Expert Environment Wiring Cause Resistor specification required for ordering purposes. Resolution 330 ohm EOL resistors are required for the RS-485 bus and 1K ohm resistors for EOL zone (input) configuration. 330 ohm = 5% tolerance, Metal film 1000 ohm = 1% tolerance, Metal Film

Issue Unable to upgrade a JACE 8000 to I/A Series Niagara 4.8 or later due to insufficient memory allocation. Product Line TAC IA Series Environment I/A Series Niagara 4 I/A Series JACE 8000 Cause I/A Series Niagara 4.8 or later running on a JACE 8000 will consume approximately 40 MB more memory than Niagara 4.7 due to new features including a new OS (operating system) and JRE (Java Runtime Engine). Resolution The following information will help identify if there is sufficient system memory to upgrade to Niagara 4.8 or later and if not, how to tune memory parameters to increase required system memory. Use the following analysis to determine if a Niagara 4 platform, operating at release 4.7 or earlier, requires a memory allocation adjustment PRIOR to upgrading to version 4.8 or later. Determine the amount of Free Physical RAM in the embedded platform while running the current release (prior to a 4.8 or later firmware upgrade) Open the embedded platform with the Niagara Platform Administrator tools. Check the amount of Free Physical RAM that is currently available. The image below displays where the information is located. If the amount of Free Physical RAM is greater than 40,000 KB (40 MB), the JACE 8000 platform is ready to perform an upgrade to Niagara version 4.8.  If the amount of Free Physical RAM is less than 40,000 KB (40 MB), the platform will require adjustment to the NRE Memory allocation using the steps below. Determine the amount of memory allocation required Subtract the current amount Free Physical RAM (MB) from the required 40 MB allocation. In the example above, 40 MB – 26.3 MB = 13.7 MB. Round this value up 14 MB. Next, add a buffer value of 10 MB to the previous result for a new total of 24 MB. System memory will be freed by reducing size of RAM disk used for histories. Ensure that /mnt/aram0 contains at least this “allocation adjustment” free space.  Using the above example, there is 326,944 KB (approximately 326 MB) of available memory that can be re-allocated to satisfy the additional 24 MB requirement.  Note: If there is not enough free space available in the /mnt/aram0, please contact Product Support for more options. Adjust the NRE Memory allocation Use the Platform Administrator tool to locate and select the Configure NRE Memory button as shown below. Record the current memory allocations for Heap Space and Meta Space by reviewing the memory sizes shown below. Increase the Meta Space by using the Meta Space slider to provide additional working space. Slide the Meta Space adjustment shown below to add 40 MB to the existing value of 48 MB increasing the Meta Space to 88 MB. Increase the System Reserve by the required 24 MB calculated in the example above. Slide the System Reserve adjustment shown below to set the value to 24 MB. Return (increase) the Heap Space back to the original 384 MB size by adjusting the Heap Space slider shown below. The final adjustment will bring the Meta Space back the original 48 MB size by adjusting the Meta Space slider shown below. Save the changes and reboot the JACE 8000.  Using the information from Step 1, verify that the Free Physical RAM is now above 40 MB.  If confirmed, the JACE 8000 platform is ready to perform an upgrade to I/A Series Niagara version 4.8 or later.

Issue Automatic Database SAV's occurring each time I/NET is started, this is causing I/NET to become slow to respond to other actions. Why are Automatic Database (DCU) SAV's occurring during daytime operating hours?  Environment I/NET Seven 2.44 and above Cause This is a new feature added so that the Network Functions; DCU Time Synchronization,  Automatic Database Save and Special Day Broadcast no longer require I/NET application to be running, only the InetIoSrv is required to have these features activate.  Additionally each time the InetIoSrv.exe is started and after a nominal delay (approximately 60 seconds) these are also all activated. Resolution At this time there is no mechanism to stop these initial features from activating each time the InetIoSrv.exe is started.  If you are starting the InetIoSrv on multiple or regular occasions it may be best to either disable these Network Functions (in particular the Automatic Database SAV) during this time or ensure that the SAV files are all current in the nominated SAV directory as defined in the active Configuration Profile.

Issue After a power failure, the Automation Server has a designed procedure to restore script programs in to a particular state. This process should be taken in to consideration when designing the system.  Product Line EcoStruxure Building Operation Environment Automation Server Cause Automation Server loses power and restarts, unsure where script programs will start from once the Automation Server comes back online. Due to the onboard "super cap" saving the database to flash on power loss, are the last script program line and variable values retained for when the Automation Server starts back up? Resolution The Automation Server saves it's current active database to flash before losing power completely, the super cap has enough power for it to do this one last task before the Automation Server loses power completely. See AS Power supply interruption or failure on how this is accomplished. On startup from power fail, any script Programs in the Automation Server will start scanning at the first program line. Make sure to keep this in mind and write your programs so that the first line sets your control values to the default "safe" value before moving on to further control logic.

Issue A method of offline database engineering is needed for SmartStruxure.  Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Project Configuration Server (PCS) Cause System integrator wants to engineering expansions and new automation to the site offline. What is the procedure if the client already has the ES and AS devices onsite, but wants to engineer offsite? If not can we only add one AS per project then restore / deploy just the AS and how is point referencing managed on bindings to the original site server? Resolution Beginning with the release 1.5 version of Project Configuration Server(PCS) is a 'deploy once' version, meaning that it allows you to make the first configuration offline. It is a full deployment meaning it may only be the ES or AS or the ES with AS connected. There are no partial deployments with bindings intact with existing servers. For deployment to include bindings between the ES and AS or other devices, they must be added to the initial deployment, which will overwrite existing configuration. Note: the 64 AS limit is a performance issue. 64 fully loaded AS in a project takes a long time to open. Once a server in the PCS project is deployed on site, you cannot deploy it again without manually erasing the database in the online server using the Device Administrator or uninstall and re-install the Enterprise server. Consider the following scenario where an office wishes to use the PCS on a project with staged installation and an ES with 15 AS: Create the ES and all 15 AS in my project. You may not have the project’s communication information because none of the final IP addresses are available. So put them in with 192.168.1.x Configure all of what is needed in 5 of the AS (AS1 – AS5). Configure all of the IO and other objects in another 5 AS (AS6 – AS10) Do nothing with the last 5 AS (AS11-AS15). Create some read references in some of my programs in AS1-AS5 that are referencing objects from AS6 – AS15. Create extended trends and alarms categories at the ES. Create alarms in AS1 - AS5 that use the alarm categories. Go to the site and deploy AS 1 to AS5 (after modifying the communication parameters for those 5 so that you can bring them on line.) The alarm categories will be deployed to the AS in spite of the fact that the PCS would have had them configured as lead and shadows from the ES, which was not deployed. However, there would likely be an offline alarm generated because there was no ES and there might also be a lead/shadow alarm. The alarms will be correctly configured, however, and operational. The references to the objects from AS6 – AS15 will appear as unresolved in the AS1-AS5 reference managers. Go back to the office and finish everything needed in AS6 – AS10 Create graphics at the ES referencing objects from all 15 AS. Create trend charts showing log data from all AS. Create users, domains, workspaces, etc. Go back to the site and adjust the communication parameters for all the remaining 10 AS and for the ES Deploy AS6 - AS10 and the ES. Initially, the AS1-AS5 have empty/wrong communication settings to the ES. It requires a manual “Repair Com-settings” from the user logged on to ES (at the site). When the Com-settings are ok, then the bindings from AS1- AS5 to AS6-AS10 will be resolved after a few minutes. When the Communication settings in AS1-AS5 for the ES are correct, the synchronization for lead/shadow relationships starts updating the alarm categories that we discussed in step 8a. The graphics in the ES will have resolved bindings for objects from AS1 – AS10, but unresolved bindings from AS11-AS15. In fact, they will be resolved to AS1-AS5 even if you haven't corrected the Com-settings in AS1-AS5. The ES knows all the AS. Go back to the office and finish up my work on AS11-AS15. Part of this process is the creation of programs that reference objects in AS1 – AS10. Go to the site and deploy AS11 – AS15. All of the read references to objects from AS1 – AS10 will automatically fix up once the Com-settings for the ES in AS11-AS15 are correct. It might, however,  take a few minutes. All of the references in the ES graphics for AS will be operational.   Further information can be found on Building Operation WebHelp.

Issue Does the Operating System + the SQL Server needed to install the reporting package for the SmartStruxure platform only allowed to be English versions Environment StruxureWare Building Operation site with Reports Server Cause Help.SBO states: Microsoft provides a number of versions of SQL Server. In order to install and run WebReports with Building Operation, you need to download and install SQL Server 2012 Standard, 64-bit (or Express with Advanced Edition, 64-bit). Do not install any other version of SQL Server. You can download the executable file for 64-bit operating systems: SQLEXPRADV_x64_ENU.exe. Does the Operating System + the SQL Server needed to install the reporting package for the SmartStruxure platform only allowed to be English versions or we could go for an Spanish/German/etc. version for both of them? Resolution WebReports is not supported on non-English platforms.

Issue Is it possible to change the number of PIN code attempts for a door in Security Expert?  Product Line Security Expert Environment Security Expert Server 4.2.x Security Expert Smart card Readers (any with a keypad) Cause By default, the number of PIN code attempts is set to three.  Resolution In the Security Expert Client, go to Programming - Doors Select the door that you want to change and open the Commands field under the General tab Enter the command "LockOutAttempts=x", where x is the number of attempts (max number of attempts is 15) Save and download the changes to the Controller

Issue If more than 3 Operators are created in Security Expert, the License page of the Thick Client will show more Licenses in use than the maximum three (3) clients provided with the standard SX-SRVR License. To see what the site is using, select About > License and scroll down to the Feature: Web Operators. As shown below, there are four web operators active out of the three (4/3) allowed. Product Line EcoStruxure Security Expert Environment Licensing Cause A Web Operator is defined as any Operator who can log onto the Security Expert Server using a browser.                           In the example shown below there are four Operators: admin 2nd Operator 3rd Operator 4th Operator The system allows each to log in successfully: The License option SX-WEB-OPR enables 'x' number of browser connections depending on customer needs and should effectively ensure that the correct number of Operators are purchased. However, the feature is currently in development and is not yet enforcing limits on the number of web operator connections.  This allows the number of connections to exceed the maximum limit (I.e.4/3) for the time being. Resolution Note: The Operator does NOT even need to be logged on for the count to register 4/3, the fact that 4 operators have been created is enough. The restriction of operators via Web Client could be enabled/enforced at any time in the next release of the software, so it is strongly advised to purchase the correct number of Licenses required at the time of installation, to prevent a loss of user connectivity going forward.

Issue When comparing values of Modbus registers within WorkStation and Modscan the values do not match. Product Line EcoStruxure Building Operation. Environment Building Operation Enterprise Server. Building Operation Automation Server. Cause The third-party Modbus device does not support single register requests. Modscan was set to poll 10 registers as a group poll and giving the correct responses. The Modbus request in the Enterprise Server or Automation Server was polling individual register one at a time. This resulted in incorrect responses from the third party device Resolution Add a Modbus register group to the Server then add the Modbus points to this group. This will cause the Server to poll multiple registers in 1 request and get the correct response from the third party Modbus device.   For more information on Modbus grouping refer to the EBO Webhelp Modbus Register Groups topic

Issue Is it possible to command the outputs on an MP-C controller before it has been commissioned in EBO? Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Cause It is necessary to verify the field device wiring and control prior to the MP-C controller being brought online. Resolution The following video demonstrates how temporary outputs can be created and controlled in an MP-C controller without the use of a front end system.

Issue Upgrading from EBO 2.0.x to 3.0.x causes I/NET to become incompatible. After upgrading to 3.x the I/NET controllers do not come online. Product Line EcoStruxure Building Operation, TAC INET Environment EcoStruxure Building Operation (version 3.0.1 and later) I/NET Seven Software (version 2.44 and above) Cause I/NET Seven Software is built using a 32-bit interface. Starting with EBO 3.0.1, EcoStruxure requires the use of a 64-bit interface. Resolution For INET seven to operate with EcoStruxure Building Operation 3.0.1 it is necessary to obtain a 64-bit DLL from the Exchange and install it in the INET installation prior to the upgrade. Search for INET IPortAPI64 - Software on Exchange.  Download the IPortAPI64_EBO.dll. Unzip the DLL and copy the DLL to the same folder as the 32bit INET install, by default this will be C:\Program Files (x86)\INET Seven folder. Note: if INET was installed in a different folder this can be found by examining the Windows registry key ”INETSevenPath” at HKLM\SOFTWARE\WOW6432Node\CSI - Control Systems International\I/Net 2000/Configurations. Install EcoStruxure Building Operation 3.0.1 When the ES restarts the InetPlugIn will connect to InetIoSrv via the 64-bit IPortAPI64_EBO.dll.

Issue What is the maximum size Card Number and Facility Code Number supported by Security Expert? Product Line EcoStruxure Security Expert Environment Security Expert Controller Security Expert Smartcard Reader Cause Adding a card to one of the Card number slots on the General tab of a User page allows for a maximum of a ten-digit facility code and ten-digit card number. Resolution The currently supported size of the Facility/Card number allows a maximum of a ten-digit facility code and ten-digit card number as can be seen below.  Facility/Card Number This Facility/Card number is entered when adding a credential to a User on the General tab of the User page. The size of the allowable facility code and card number can be increased beyond ten-digits by using Credential Types instead. Once the Credential Type has been created, it can then be used in the CREDENTIALS section for those users. For additional details on Credential Types see the AN 276 Security Expert - Configuring Credential Types - Integration Guide.

Issue Advanced Display V2 (Samsung T580s) are not charging properly and eventually running out of power Product Line EcoStruxure Building Operation Environment Advanced Display Version 2.0 Cause If a single straight through USB cable is selected and connected to the USB port on the SmartX controller, it will supply both data and power to the AD V2. The SmartX controller does not have a high enough power rating to sufficiently charge the AD V2 correctly under all conditions and the battery charge level may dwindle and eventually go flat over time. (The AD V2 Tablet requires between 0.5A - 1.3A depending on its settings while an AS-P/AS-B USB port supplies a maximum of only 0.5A) Resolution There are 2 possible USB cables which can be ordered for use with an AD V2. The Y-shaped 'Y-Cable' and a Straight Through cable.  Both can be used, but with different configuration changes to the tablet settings as detailed below: Straight Through 3m USB cable (Data and Power): AD V2 is connected directly to SmartX USB port for Data SmartX USB also provides minimum 0.5A supply Tablet brightness must be set no higher than 50% Tablet display timeout must not be set to 'Always On' Y-shaped USB cable (1 x Data and 1 x Power) AD V2 is connected directly to SmartX USB port for Data Separate USB socket is required to ideally provide 1.3A supply Tablet brightness must be set no higher than 50% Tablet display timeout may be set to 'Always On''

Issue Function Block Alarm on delay value reverts back to a value of 0 after you save the Function Block application. Product Line EcoStruxure Building Operation Environment Building Operation Workstation 3.0.2 and below MP-x controllers (MP-C, MP-V) Cause This is a known issue and is due to be fixed in an upcoming release of Building Operation. Resolution The workaround of adding a delay object in the Function Block program (as shown below) and connecting this before the Alarm is currently the only option until this fix is released.

Issue It seems like SNMP is supported but there is no information on how this feature is enabled or used. Product Line Security Expert Environment Security Expert SNMP (Simple Network Management Protocol) Cause The SNMP Feature is seen on the Security Expert license page, showing "Feature : Number of SNMP". Feature : Number of SNMP Resolution SNMP is not supported in Security Expert. The SNMP license item that is showing in the Security Expert Client license page has never been enabled and will be removed in a future release.

Issue Importing a User CSV file with special characters (i.e. PEÑA or DÍAZ) ends up with unknown characters. Example showing Imported Users with unknown characters Product Line Security Expert Environment Security Expert Client Security Expert Data Sync Service Cause The Security Expert Data Sync Service requires UTF-8 encoded CSV files. Resolution Import the CSV file again with it re-encoded as UTF-8. Follow the below steps to re-encode the file: Open the CSV file in Excel. Then select Save As. In the Save As Type drop down menu, select CSV (Comma Delimited)." Click the Tools menu and select Web Options. In the new dialog box, select the Encoding tab. Find the Save this document as dropdown menu and select Unicode (UTF-8), then click OK.