Building Automation Knowledge Base

Issue How can the IP address of an MPX controller that is configured for DHCP be determined when there is no attached display Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Cause It is necessary to know the IP address of an MPX that does not have a display for troubleshooting and commissioning multiple MPXs,  Resolution

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 When a TGML graphic is opened from Webstation red crosses is shown on the whole graphic or sometimes over certain components. After a few seconds the red crosses disappear. Product Line EcoStruxure Building Operation Environment Building Operation Webstation version 2.x and 3.0.x Cause The red crosses only appear when values from field bus devices are displayed in in the TGML graphic, and only in Webstation version 2.x and 3.0.x. When the graphic is opened from Workstation no red crosses are shown in the graphic. Resolution This issue is fixed in EBO version 3.1.1

Issue The system memory usage for an Automation Server slowly increases over time and finally the AS restarts with a system alarm "Server restarted because of low memory"  System memory usage for the AS (In this case an AS-B): Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Building Operation Automation Server (AS) Cause One reason for this issue to occur is that two Enterprise Servers (ES) are running with the same database and are connected to the AS at the same time. This is not a common scenario but can happen by mistake if for example an old computer with an ES installed is switch on. The ES runs as a service and can be running in the background on the computer with no one noticing it.  Resolution Stop the Enterprise Server that is started by mistake.

Issue Analog consumer values referencing the temperature of a SmartX Sensor shows in metric units when setup to display imperial units. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Building Operation Multi-Purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller Building Operation IP-IO Building Operation SmartX Sensor Cause SmartX Sensor is configured in the device as metric measurements (SI System). Setting Fahrenheit in Display of SmartX Sensor does not convert the values from metric to imperial. Consumer values are configured to use the object being referenced and do not convert measurements. Unit conversion is done within the binding and not the device itself. Resolution There are two workarounds: Option 1: Create an analog value and then bind to consumer value Step 1: Create an Analog Value. Setup unit settings to (°F) and Save.  Step 2: Bind Analog Value to temperature from SmartX Sensor and Save Step 3: In the created Consumer Value, bind the Analog Value to the input binding reference and setup unit settings to (°F) and Save   Option 2: Bind to Consumer Value directly and keep the value in metric Step 1: In the created Consumer Value, bind the SmartX Sensor temperature to the input binding reference Step 2: Setup unit settings as configured in the object (°C) and Save.

Issue During startup of the Lon FlowBalance software, an error is displayed indicating that the program "cosmo.exe" failed to register Product Line TAC IA Series Environment MNL-FLOW-BAL 3.0 - MicroNet Software Microsoft Vista, Windows 7, and Windows 10 (64-bit installations) Cause The software installer installed the software into the C:\Program Files (x86) folder on the Windows system drive. When the software is started up, it needs to initialize some internal driver and data modules. These modules are expected to be in the C:\Program Files\TAC folder, however, that folder was not created during the installation of the software. The LON FlowBalance version 3 software is not supported on 64-bit versions of Windows because fully-supported Echelon (LON interface) drivers are not yet available. Resolution Reinstall the LON FlowBalance software on a computer or virtual machine running Windows XP, Windows Vista (32-bit) or Windows 7 /10 (32-bit).

Issue Some connectors appear in red on the Workplace Tech Visio drawing.  Connectors cannot be bound to objects. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech Building Operation Workstation (Workplace Tech Editor) Microsoft Visio  Cause Drawing objects become placed off the normal boundaries of the Visio drawing page causing file corruption.  This can occur during improper file saves, Visio crashes or for unknown reasons. Resolution

Issue Workplace Tech or Workplace Tech Editor is crashing when accessing a specific Visio file. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech Building Operation Workstation (Workplace Tech Editor) Cause There are a number of possible issues with the Visio 2013 and Visio 2016 files when running in Compatibility Mode.  Compatibility Mode is required for Workplace Tech and Workplace Tech Editor since they are both designed to use the older .vsd file format.  The mentioned Visio versions both use .vsdx as a native file format. Resolution

Issue All efforts to move a Continuum Virtual License from one host machine to another are unsuccessful. Product Line Andover Continuum Environment Continuum Cyberstation Cause The license type is not shown as Re-hostable in the Sentinal Admin Control Center webpage.   The license type is not shown as re-hostable after applying the Re-hosting upgrade activation file received from Andover Upgrade Services.   The error Invalid Recipient information, process canceled! is displayed when entering the recipient id file (.id) in the RUS Key Utility.   The HaspRuntimeForContinuum.exe is the wrong version. Resolution Contact Andover Upgrade Services and provide them with a new host information file (.c2v) produced using the RUS Key Utility. On the host from which the license is to be transferred... HaspRuntimeforContinuum.exe is the most current version available on Exchange. Rus Key Utility is the latest version available on Exchange. Contact Product Support Services for assistance. On the host the license will be transferred to... The most current version of HaspRuntimeForContinuum.exe must to be installed prior to using the RUS Key Utility to generate the recipient fingerprint file (.id). The HaspRuntimeforContinuum must be installed As Administrator. On the host licensed host… HaspRuntimeforContinuum.exe is the most current version available on Schneider Electric Exchange.   A demonstration of the rehosting process can be viewed here.

Issue Changed MNL controller application engineering units to Metric (Celsius temperature) using the hardware wizard. After downloading the modified application, the setpoints and setpoint range on the MN-Sx sensor are still reading in degrees Fahrenheit. Product Line TAC IA Series Environment I/A Series WorkPlace Tech Tool software. I/A Series MNL I/A Series MNB Cause Changing the engineering units from English to Metric using the Hardware Wizard does not alter the values already configured for the setpoints or setpoint ranges in the MN-Sx sensor. The standard applications have predefined setpoint values and setpoint ranges based on the application type and MN-Sx type. These setpoints and setpoint ranges are configured with values appropriate for the operation of the controller using English engineering units (Fahrenheit temperatures). When the controller's engineering units have been changed to Metric, the appropriate temperature setpoint values and temperature setpoint ranges must be entered via the appropriate screen of the Resolution After using the WorkPlace Tech Tool Application Wizard to change the controller's application engineering units, the entered values for any setpoints and setpoint ranges must be reentered as numbers appropriate for the new engineering units. The application template files are configured for English (standard) engineering units with temperatures in Degrees Fahrenheit. For example, the default space temperature setpoint is 70 degrees. By default, the controller is configured for English engineering units, resulting in the space temperature setpoint is 70 degrees Fahrenheit. Changing the controller engineering units to Metric will result in the default space temperature setpoint being 70 degrees Celsius unless the setpoint and setpoint range is redefined using the Hardware Wizard.

Issue When attempting to start the Enterprise Server, the user receives the following error message: "Windows could not start the Building Operation Enterprise Server service on Local Computer: Error 216: 0xd8" Product Line EcoStruxure Building Operation Environment Microsoft Windows Building Operation Enterprise Server Building Operation Enterprise Central Cause Windows error 216: 0xd8 means "The version of %1 is not compatible with the version you're running. Check your computer's system information to see whether you need an x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher." It is likely that this error is being received due to the EBO Enterprise Server/Central being installed on a 32-bit Windows Operating System. Resolution Beginning in EBO 2.0 it is no longer supported for the Enterprise Server to run on a 32-bit Operating System. Reference the Enterprise Server Specification Sheet for the appropriate product version you are using to find the list of supported Operating Systems. The Enterprise Server/Central should then be installed on one of the supported 64-bit Operating Systems.

Issue Need to perform a damper calibration using eCT Product Line EcoStruxure Building Operation Environment Building Operation eCommissioning Tool (eCT) Cause There is no documentation on how to perform this via eCT. Resolution Ensure your MP-V is not in a hosted state within EBO. Connect to your MP-V device using Windows 10, iOS, or Android via Bluetooth, WiFi, or ethernet connection Expand the menu in the top left corner and select "Browse Objects"  Scroll down until you find the DamperCommand object, select it and tap/click OK  In the Initiate damper calibration Property ID, select False and type in True then click Save

Issue While trying to login to either WorkStation or WebStation, or during the startup of the Enterprise Server, an error "Error -25: License server system does not support this version of this feature." appears. Product Line EcoStruxure Building Operation Environment Building Operation Workstation version 2.0.x or later Building Operation Webstation version 2.0.x or later Building Operation Software Administrator version 2.0.x or later Cause The activated license is not at an appropriate version for the corresponding software. The licenses activated in the EBO License Administrator need to be at a version greater than or equal to the version of the Building Operation software being used.  Resolution 1. Workstation - If the Workstation license activated in License Administrator is at Version 1, this license will need to be upgraded to be compatible for any system EBO 2.0 and beyond. To do this, simply notate the Entitlement ID and then return the Workstation License. Once returned, reactivate the license from the previously recorded Entitlement ID. This will upgrade the 1.X License to be used with newer systems. 2. Enterprise Server - If the error is received on an ES, verify that all ES licenses are in place. If the system was upgraded, it is necessary for all previous versions of ES/AS licenses to remain activated in the License Administrator. 

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 Integrating MNL-VAV controllers into the EBO system successfully Product Line EcoStruxure Building Operations, TAC IA Series Environment Building Operation Automation Server Building Operation Automation Server Premium I/A Series MNL VAV Cause Lost flow balancing values during integration Lost S-link offset calibrations Resolution Use the following steps to bring a controller into the Automation Server with all data intact. Using WorkStation connected to the AS/AS-P; right click on the LonWorks Network and select New then Device. Choose the appropriate device object type from the list for the MNL-VAV controller being added, give it a name and click Next. Type in the Neuron ID or use the Service pin method to identify the controller. Check the box next to “Commission” and the radio button next to “Keep current configuration in the device” and click “Create” then click “Close” when complete. Right-click on the new device object in the tree and select MNL and then “Backup flow balance information”. When this is complete notice the blue circle with a white checkmark next to the nciHighFlowCal and nciLowFlowCal SNVT’s indicating the AS-P DB contains the balance data from the controller. If special S-link offset values exist in the controller right click on the device object in the tree and select MNL and then “Backup S-link offsets”. Right-click on the controller device object and select MNL and “Assign application” and click on the appropriate application file for this controller and click on “Assign”. Right-click on the controller and select MNL and “Download application”. Click on “Close” when complete. Right-click on the controller and select MNL and “Restore the flow balance information” Right-click on the controller and select MNL the “Restore S-link offsets”. Verify all data is correct and the controller is functioning properly.

Issue A message that can be intercepted by a guard at a monitoring station. When you configure your access control system to accept PINs, I/NET has the ability to detect PIN entries When you configure your access control system to accept PINs, I/NET has the ability to detect PIN entries made under duress conditions. For example, if an employee is being forced to provide an unauthorized individual access into a secure area, the employee can substitute the final digit of their PIN with a digit that indicates a duress condition. In this case, I/NET will allow access but will also silently generate a duress message that can be intercepted by a guard at a monitoring station. Product Line TAC INET Environment TAC I/NET Seven with Access Control using a pin pad. Cause Duress entrance causes a security guard to be notified that there is a situation to be resolved. Resolution Duress detection is active anytime a door is operating in a mode that requires the entry of a PIN. I/NET supports selectable duress schemes that you can assign on a per-tenant basis. The following duress schemes are available: Default — I/NET's default duress scheme detects when an individual substitutes their PIN with a substitute number. The default duress last pin is 9. The duress code is the user's PIN number with the last digit changed. For example, 12345 becomes 12349. Add n (where n is a value from 1 to 9) — I/NET detects when an individual substitutes a digit of their PIN with a predetermined digit. For more information on this sensitive topic, contact Product Support to begin a conversation about Duress Notification in I/NET.

Issue What speed and type of comms do Sigma controllers communicate using Ethernet. Product Line Satchwell Sigma Environment Sigma V53 type controllers e.g. UNC496/596, UNC532, IC, DNN ARM7 type controllers e.g. UNC696/796, UNC632, IC3, DNN3 Cause What speed and type of comms do Sigma controllers communicate using Ethernet. Resolution V53 type controllers communicates at 10MB and is half duplex. ARM7 type controllers communicates at 100MB and is half duplex. 

Issue When importing Lon variables from Excel, all variables are created as Inputs, even though the "Direction" column in the Excel file says "Output".   Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause A defect creates all Lon variables as inputs even if the variable is assigned direction as output. Resolution  Create Lon variables with output direction manually.

Issue Is it possible to determine when a Continuum Security Key was removed from a Continuum Cyberstation? Product Line Andover Continuum Environment Continuum Cyberstation Continuum Security Key Cause A Security Key is removed from the Continuum Cyberstation. Being able to pinpoint when it was removed may help in investigating who has taken the key. Resolution It is not possible to determine when the key was physically removed from the PC with the Continuum or Windows Logs. There is no information in the Continuum Error Logs on this removal and in the Windows logs, the disconnect/connect messages for USB devices don't indicate what the device actually is.

Issue Using an EP1501 as a controller and unable to add reader one. Product Line Access Expert Environment Access Expert Server 2012R2 and above Cause Using an EP1501 as a controller as well as a card reader controller. Resolution To resolve the issue, please follow the steps listed: Wire the RS-485 bus to reader port 1, Clock and Data Wire the reader being used on port 2 When programming the reader on the device, it needs to be added as Reader 1 The Door Address needs to be set as 0 as well