Building Automation Knowledge Base

Issue User keeps getting re-prompted for login for each station even though using virtual domain. Each station file has been edited to include the cookieDomain slot.  Also, each station’s “hosts” file has mapped every station’s IP address in the virtual domain to their hostnames. Everything seems to be configured correctly. Environment Niagara R2 Cause Host (station) names contained underscores. The hostname cannot contain underscores. Resolution The station must be renamed without underscores. Change the hostname to match the new station name.

Issue After an upgrade to EBO version 3 the  "Alarm State Sort Order" in EBO Webstation is not following the  "Alarm State Sort Order" set in Workstation for certain Alarm Views. Workstation:   Webstation: Product Line EcoStruxure Building Operation Environment Building Operation Webstation version 3.0 and later Cause This issue is only seen on Alarm views upgraded from a version earlier than 1.9 to EBO 3.0 or later The problem is that in EBO version 1.9 Webstation did not follow the sort order for Workstation, back then the sort order in the alarm view in Workstation and Webstation was separated. And the default sort order in Webstation was "Triggered time" when upgrading to version 3 the upgrade does not change the sort order for Webstation. So after the upgrade the sort order in the alarm view is "Triggered time" and it will not follow the sort order from Workstation.    Resolution In EBO Webstation version 3 click on the "Filter" button in the Alarm view. Click on "Sort" and remove "Triggered time", click OK In Workstation open the Alarm view and right-click, Open Alarm view settings and click on "Reset standard layout to standard default"  

Issue When a TGML graphic is opened from Webstation and the user right clicks on a value in the graphic to open properties, it can take up to 20 seconds before the properties dialog is displayed. During the 20 seconds the working area is just grey. Product Line EcoStruxure Building Operation Environment Building Operation Webstation 2.0.4 and earlier versions Cause This problem only occurs when the signals in the graphic resides in a TAC Xenta; The problem has not been observed with Modbus or BACnet signals, and is only present in Webstation, not in Workstation. Resolution This issue is fixed in EBO 3.0. There is also a hotfix for version 2.0.4. It is labelled 2.0.4.5801. Contact you local technical support organisation if you need the hotfix.

Issue In LonMaker, how do I get rid of multiple message tags within a base unit virtual function block? Environment Vista Site Cause In LonMaker, how do I get rid of multiple message tags within a base unit virtual function block? Resolution Right click on the VFB and select to delete NVs & MTs. All unconnected message tags will then be deleted.

Issue Should we recommend Message tag bindings be performed after the commissioning of the device? Environment I/NET Site Cause Should we recommend Message tag bindings be performed after the commissioning of the device? Resolution No, this should not be necessary. It may be preferable, however, for a dialed network as the 901 device must be added to the network when connected to the network.

Issue All NPRs on a site are giving 'Host Lost / Host Restore' alarms, but the TCP/IP network is functioning 100%. Environment I/NET Cause Changes to bin file revisions sometimes include updates to communication Resolution This can be caused by a mis-match in .bin file revisions on all downloadable controllers. Verify all the .bin files in each downloadable controller are from the current I/NET revision at the customer's site. The mis-match can come from a tech loading a .bin file from his laptop (with a different rev than the customer). It can also occur when I/NET is upgraded, but the controllers aren't.

Issue What is the Analog to Digital Output resolution of the MNB controllers? Environment MNB Controllers Cause Analog to Digital conversion resolution. Resolution The MNB BACnet controllers have 12-bit resolution on the inputs and 8-bit resolution on the analog outputs.

Issue Can the MNL controllers be powered by DC voltage? Environment MNL controllers DC voltage input Cause Using DC voltage is not recommended or supported. Resolution The MNL controllers are not specified for DC operation and all agency approvals were submitted using a power source of 24 VAC 50/60 Hz.

Issue When using PSI 4.1 in direct connect mode, the baud rate is modified and saved but it will not communicate at the new rate. Environment PSI 4.1 Cause A baud rate change in PSI direct connect mode does not take affect until the PSI program is closed and restarted. Resolution Closed the PSI program and restart the program for the new baud rate to take effect.

Issue When ordering an MNL-10Rxx, MNL-15Rxx, or MNL-20Rxx controller, is the controller base included? Environment MNL controllers; MNL-10Rxx, MNL-15Rxx, or MNL-20Rxx Cause The web pages on iPortal do not described whether or not the base is included. Resolution The base is included when ordering any of these MNL controllers.

Issue When trying to dump the Gerry Log from several controllers on the network, the header and errors appear to be identical. Environment CX99xx NetController Gerry Log Controller error log Cause Controller diagnostics. Resolution The Gerry log cannot be retrieved from a NetController without being physically connected to it via the RS232 connector.

Issue The setpoint values are displayed briefly and then change to 621.X on the Proview display? Environment All LON proview installations. Cause This occurs when the setpoints are being written into network variable inputs (nvi).  The nvi's default to using the receive heartbeat and will fallback to default after the timeout occurs.  Proview does not perform a send heartbeat function as the connection is an nv update and not an actual binding. The receive heartbeat mechanism in the MNL controllers cause the nvi values to fallback to NA upon heartbeat timeout. Resolution The heartbeat can be disabled for the setpoint nvi, however nvi values are stored in RAM (not EEPROM) and will return to default upon a controller power cycle.  The best solution is to use network configuration inputs (nci) for setpoint displays on the Proview.  These do not have the heartbeat issue and the values are maintained in EEPROM so they are not lost following a controller power cycle.

Issue Sigma AI objects could be seen to suddenly change in value through the system logging. Environment AI Objects Temperature Sigma controllers Cause This is caused by a fault on the processor card. Resolution Replace the CPU card.

Issue Slide stat or temperature offset values are incorrect when using a ETR-1xx sensor with Xenta 100 or Xenta programmable controllers. Environment ETR-1xx Xenta 100 Xenta 280, 300, 4xx Cause Similar to the STR-1xx line of sensors, there is a jumper that must be set depending on the controller the sensors is being connected to. This jumper removes or adds an extra resistor to the temperature offset value. Resolution Set the Jumper position according to the type of controller the sensor is connected to: Controller Jumper Position Xenta 100 J1 Xenta Programmable J2

Issue How to create a local String Variable in a Xenta 731. Data Type String is not allowed in this node. When trying to set data type to string. Environment TAC Xbuilder Cause The datatype string can only be used for SNVT str_asc and signals connected to SNVTs of this type. Resolution To get a String signal you have to use snvt_str_asc.

Issue Editing Multi-Stage control objects. Environment Sigma Control Multi-Stage Multi Stage Cause Multi-Stage control objects cause the controller to lock up when edited. Resolution The exact cause of this issue has not been located, but here are two suggestions. Download the complete object file periodically when editing these objects. If contingency logging is enabled on the multi-stage control object, it should be disabled before working on that object.

Issue What versions of Sigma does RAM Remote Alarm Manager work with? Environment Sigma RAM Cause RAM does not work with S-150 or S-400. Resolution RAM Remote Alarm Manager will only work with S-FULL. The site will need to be upgraded with S-UPG to the full version. 

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 How to combine multiple Continuum DBs into one DB Product Line Andover Continuum Environment Continuum Cyberstation Cause Multiple Continuum site databases need to be combined into a single site database Resolution Guideline for combining Multiple sites to one Database Executing this procedure requires a technician who thoroughly understands Continuum and how it works with SQL Server. This procedure does not encompass BACnet controllers. There is a multitude of decisions related to efficiencies and site preferences that are not documented here. The following procedure is intended for use as a guideline for combining multiple databases. This work must be done offline on a development database and validated on a test bench before Note:Before proceeding with this procedure you must do the following. Backup the Continuum database in SQL. Backup all the files and folder structure under New Graphic Files. Note that these files may be on the SQL Server or elsewhere on a mapped drive. Back all Cyberstation Profiles. Steps 1 – 11 must be done before any of the site exports are done. Preparation All sites must have the same revision software and CX firmware. NO EXCEPTIONS! Make sure that all the Alarm Enrollments and Event Notifications have unique names between all sites as these will wind up together in a single database. Make sure that all the Graphics in the Root directory have unique names between all sites. Make sure each Schedules in the Root directory has a unique name across all sites. Make sure each Custom ListViews in the Root directory has a unique name across all sites. Make sure each Groups in the Root directory has a unique name across all sites. Make sure each Reports in the Root directory has a unique name across all sites. Once steps 1-5 are completed, export each class in the root individually. Import files from step 6 into the new site The Local Site name on all the sites that will be combined must be named LocalSite. All workstations must have unique names and ACC IDs between the sites. All CX, ACX and BCX controllers must have unique names and ACC IDs between the sites. Note: The safest way to do steps 9 & 10 is to create a new controller in offline mode with the changed ID, then drag and drop copy from the original controller to the new controller. Panels, reports, and programs then must be edited to bind to the new controller. Another way to merge the panel, reports, and programs that are in the root is to copy all the panels, programs, and reports to their corresponding controller then export the controller. Doing this will keep all the bindings linked. Then once the controller is imported into the merged database they can be copied back up to the root. All Commports on all controllers and workstations must be named Comm1, Comm2, etc… Each site must have the default “ACC” user and password. All graphic files (.pin) under the New Graphic Files folder must have unique names between the sites. Merging the databases Install a standard multi-user Continuum system being sure to size the database big enough to accept all the other databases combined into one database.  After a clean installation is done, shut down the new workstation and the SQL server. Copy the empty database files to an area where they won’t get corrupted. Do a complete site export from each of the sites that will be combined. Back up all the Graphic files (.Pin) files from the site so that they can be transferred to the new server. Copy all the backed up Graphic files (.Pin) from each site onto a New Graphics Files folder in the location of choice. Note these files can reside on the SQL server or elsewhere on a mapped drive. Import each of the site text exports from the old systems into the new system. After each import check to make sure that each import went cleanly. Check all the Graphics, Programs, Alarm Enrollments, and Event Notifications to make sure that all the links were made during the import process.

Issue Can Satchsize the valve sizing software be used with Windows 7? Environment Valve sizing Satchsize Cause Customer wishes to use Satchsize on Windows 7. Resolution Satchsize is no longer available and is not supported with Windows 7, but a new program is available. TAC Valve 1.8 UK can be downloaded from the Buildings Business Extranet. Once installed please use the help files installed with the program.

Issue Sometimes the availability count for license features are displayed as double the actual available count for Entitlements. The problem has no functional effect on the system other than that the visual indication of the feature count is wrong. Issue seen in Entitlement View - Features inside a License Product are doubled. Issue seen in Server View. -The issue can be seen temporarily during activation on the server line. -The number of features inside the License Products available for activation under the server are doubled permanently. Server line view after activation. - After the license product has been activated the features on the server are shown correctly. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Secure Boot Building Operation Automation Server Bundled (AS-B) Scalable Cause AS-P Classic and AS-B Classic licenses are NOT affected. None of the Windows licenses are affected.   EBO releases affected: All EBO versions up to and including 4.0.3. The EBO systems that are already running licenses are Not affected. Customers that for any reason reinstall an Entitlement in DA will be affected by the issue. EBO 5.0.1 Resolution This issue is planed to be resolved in the following EBO versions: EBO 4.0.4 EBO 5.0.2