Building Automation Knowledge Base

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

Issue After Sigma transition into EBO, upon alarm and alarm clear there is no requirement to acknowledge the alarm. In the Sigma Interface, the object alarm 'Type of Acknowledgement is set to 'No' and cannot be changed. Product Line Ecostruxure Building Operation, Satchwell Sigma Environment Building Operation Enterprise Server Satchwell Sigma Cause Alarm Priorities are incorrectly set in Sigma Alarm Manager. Resolution During the Data Import into EBO, the settings of the Sigma Alarm Manager is checked and the alarm acknowledgement type is set to a specific type. If no alarm priorities are set for acknowledgement in Sigma, then this is repeated in EBO.    To change to 'Single' so that alarms and alarm clears are able to be acknowledged, in Sigma: Open the Alarm Manager and go to the menu options: Configure > Acknowledgement Groups   Redistribute the alarm priorities into the the different acknowledgement groups as per the site requirement. The image below shows the default view on a new install of Sigma.   Redo the Data Import, the 'Type of Acknowledgement' is now seen to be set to 'Single'. However, If it is now showing 'Extended', then the KB article Type of Acknowledgement set to 'Extended' on Sigma Interface object alarm will explain how to change this.

Issue Importing Security Expert controllers' serial numbers will break the import process and result in only creating default templates for the controllers. Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Data Sync Service Cause Security Expert controllers' serial numbers are displayed in hexadecimal. However, in the SQL database they are  stored as decimal values. So the Data Sync Service is expecting a decimal integer and is instead receiving a string.  Resolution Convert the serial numbers in the .CSV import file from hexadecimal to decimal. This can be done in excel using the  "HEX2DEC" function. E.g. if the controller serial number is "ABCDEF12", it must be converted to decimal value "2882400018" before importing to Security Expert. 

Issue Subnet/Node address shown in Local Node Properties dialog is not what is used on the LonWorks Network. Product Line EcoStruxure Building Operation. Environment Building Operation Workstation. Building Operation Automation Server Premium. LonWorks . Cause When using External Managed Network, an external binding tool is used to address LonWorks devices, and the external tool sets the address in the Neuron chip, that is used for communication. This information is not tranfered to the database. Resolution When using External Managed Network, the correct address information could be read in the Domain table of the device.

Issue Access which allows a value to be changed, also allows other changes to be made. Environment Users User accounts Cause A user account is created to have read only access, but this user must also have access to view Graphics, and on these graphics, be able to change values. How can this be achieved without allowing the user access to delete or edit these objects?   Resolution At StruxureWare Building Operation release 1.3 there are no available options that will achieve this configuration, the most appropriate configuration is to create a Workspace for the user, in which they will see only the Graphics, the user would have Read/Write access to the values they are allowed to change.

Issue Replacements for Schneider Electric SmartX MF41 Damper Actuator Product Line Field Devices Environment SmartX MF41 Cause Replacement of SmartX MF41 Damper Actuators within the Schneider-Electric range Resolution Outgoing Actuator Model         Replacement Model (Part Number)        MF41-6083-G00                         MD10B-24 (875 1015 000)      MF41-6083-G02                         MD10B-24 (875 1015 000) + Aux Switch (914 1061 000)      MF41-6153-G00                         MD20B-24 (875 1025 000)      MF41-6153-G02                         MD20B-24 (875 1025 000) + Aux Switch (914 1061 000)

Issue Is the MZ20B suitable for use in an On/Off application? Environment MZ20B 230V: 8455003000 MZ20B 24V: 8455001000 Cause Depending on control signal type and construction, some actuators are better suited for On/Off applications. Resolution Yes, the MZ20B can be used in an On/Off application. For connection details and more, please see the MZ20B data sheet. 

Issue Does the JACE-645 come with 128 MB or 256 MB like the ENC-520? Environment I/A Series, JACE-603/645 Cause Not sure what it comes with after reviewing announcement PA-251. Resolution A JACE-603 or JACE-645 comes standard with 128 MB of RAM with the option to upgrade to 256 MB.  The part number for the optional memory upgrade is TRD-NPM-256. This part number modifies the license which enables the factory-installed memory (license line:  maxHeap=true).

Issue How to upgrade an Automation Server if Port 80 is closed and the Automation Server is placed behind a NAT router. Getting error message when upgrading: Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Cause The problem is that the certificate are generated with the IP address off the Automation Server, and not the NAT Router IP. Resolution The Device Administrator has the option to add SAN's (Subject Alternative Name) and not just the address of the server. So add both the LAN and the WAN addresses in the SAN field when you generate the certificate and transfer to the server.