Building Automation Knowledge Base

Issue  Temporary groups can't get a PM time, only AM Environment I/NET Cause The time are using US settings AM/PM on for example a European PC Windows don't use AM/PM Resolution Enter Control Panel and choose Regional and Language Settings On first tab click Customize Choose tab "Time"  Set AM and PM symbol to AM and PM Click OK Restart I/NET IO server and try again.

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

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 EBO acts as a BACnet server and a BACnet client send SubscribeCOVProperty to get value updates of specific property of a BACnet object, ex. present value, but EBO respond with "NOT_COV_PROPERTY".   Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause Specified property does not support COV notifications. Resolution EBO only supports SubscribeCOVProperty (DS-COVP-B) for the following properties and object types: Status_Flags: AI, AO, AV, BI, BO, BV, MI, MO, MV, Loop, Trend Log Event_State, Reliability, Out_Of_Service: AI, AO, AV, BI, BO, BV, MI, MO, MV, Loop When a client attempts to use SubscribeCOVProperty for another property not listed above, the appropriate response is 'Not COV Property', as specified in BACnet standard. When getting this response from EBO, the client is expected to automatically use another method to acquire the property value (either via COV subscription or polling). If the client is attempting to read Present_Value, then using SubscribeCOV would be the preferred mechanism.

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 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 Replacement required for obsolete product. Environment SPD160 004700180 SPD360 004700360 Cause Replacement for obsolete product. Resolution SPD160 is replaced by SPD360. For more information ad details, please see the data sheet for each product.

Issue The Enterprise Network Server is licensed for 3 subordinates but when trying to add one it faults with the message "exceeded device limit of three"? Environment G3 Enterprise Network Sever Cause If stations had been added to the Niagara Network in the Enterprise Network Server and then deleted the subordinate count in the license does not reset. Resolution Restart the station and the subordinate count in the license will be reset to the correct number and allow the addition of more stations if the limit has not been reached.

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 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 MZ20A actuator stops controlling, and the Analogue Output remains at zero volts. Environment MZ20A MZ20A-R Actuators Surface Mount Cause If the controller power and battery switches are switched off, then when the power is switched back on, the Analogue Output remains at zero volts. Resolution To prevent is issue from occurring, it will be necessary to install a 2K2 ohm resistor between each channel and the common zero volt rail, as shown in the picture below.   Add the 2K2 Ohm resistors to the channels controlling the MZ20A actuators. These resistors do not need to be a close tolerance; a Carbon Film ¼ watt 5% is acceptable, (RS Stock No.135-881 or similar). Note – The MZ20A, are the only actuators that we are aware of that require this modification, therefore if the actuator is changed to another type, the resistor should be removed again.

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 Does the short yoke Forta actuators fit on the current portfolio of valves?  Environment MG600C Venta Forta Cause With the new short stroke actuator MG600C soon available, will it work with the regular valves? Resolution The MG600C is designed to be used with the VG210R / VG310R valves that will be released in the near future. 

Issue The Sigma Log configurations are not visible in the configuration window. Environment Sigma Logging Configuration LogCNF.rec Cause The LogCNF.rec file has not been upgraded when the site was upgraded to Sigma 4.05 SEB. Resolution Shutdown the Sigma client and server. Copy a backup of  the LogCNF.rec file to  the C:\Sigma\Data\Server???\ folder. Where ??? is the server number. Run C:\Sigma\BinUtils\SigUpgrade.exe Restart the Sigma server and client and check the log configuration.

Issue Unable to drag and drop the Application folder into the include types box while performing a search of application files.   Product Line EcoStruxure Building Operation Environment Building Operation Workstation v3.0.x  Building Operation Workstation v3.1.x  Cause Searchable interface not implemented on the Application folder (nor on other devices like b3). This is a known issue in v3.0.x and v3.1.x Resolution Rather than using the left mouse button to drag the application folder, right-click the application folder to drag and drop into the include types box. This is to be fixed in 3.2.1.x.

Issue When trying to browse for Areas to assign to the Area Inside Door and Area Outside Door fields in Door records, not all Areas are shown or available to be selected. Product Line EcoStruxure Security Expert Environment Security Expert Cause The Programming Mode selector is set to "Local" which is the default value. This will only show objects that are already attached to the controller this record resides in.   Programming Mode Resolution Change the Programming Mode to "Global" which will now show all Area records, including those unassigned or assigned to other controllers.   Programming Mode Global

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.