Building Automation Knowledge Base

Issue Poor communications between AS-P and Deep Sea Electronics (DSE) generator and switchgear modbus RTU slaves. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Cause When upgrading from an AS to AS-P, poor Modbus communication is seen between the AS-P and DSE slave device. The communications when using the AS was seen to be good. Using an AS-P, poor communication is seen between the AS-P and the DSE slave device. Resolution Firstly, on the AS-P, ensure the release is v3.2.3.8000 to improve the modbus RTU polling. Then if the issue still persists, make the adjustments to the DSE device as below. If the AS-P cannot be taken to v3.2.3.8000 then continue with the adjustments to the DSE device.   On the DSE Modbus slave, there are additional parameters as well as the baud rate, parity and stop bits. Access to these parameters is by using the DSE software tool. The additional parameter is the Inter-Frame delay. Change the Inter-Frame delay from 0ms to 1ms.

Issue It is not possible to select a "Trend 10K3A1" Thermistor when configuring a central or onboard IO input point. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation Automation Server (AS-P) Central IO Building operation Automation Server Bundled (AS-B) Onboard IO Cause The specific thermistor type is not available to be selected. Resolution Configure an input as a resistive Input with reliability level, electrical scale and engineering scale set to: Upper/Top: 0 Lower/Bottom: 587628 Then use a Function Block 10K3A1-Ohm-To-C sample program or Script program to convert from resistance to °C. NOTE Satchwell and Trend both use 10k3A1 Thermistors but the shunt resistance used within it will vary.

Issue Is it possible to use existing in-built Custom Formats and the new Custom Credentials in Security Expert on the same reader at the same time. Product Line EcoStruxure Security Expert Environment Card Formats Custom Credentials Cause A library of inbuilt Card Formats has been in Security Expert for some time. Primary and Secondary Reader Formats allow 2 different inbuilt Card Formats to be used on the same Reader. What happens when a user tries to introduce the newer Custom Credential? Resolution Primary and Secondary Reader Formats can still be used in on the same Reader in Security Expert when using inbuilt Card Formats.  However once using newer Custom Credentials a Reader can either use an inbuilt Card Format OR a Custom Credential BUT NOT BOTH.  

Issue BBMD and BBDT Enterprise Server or Automation Server Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server and Automation Server BBMD (BACnet Broadcast Management Device) IP subnet, IP router  Cause Clarification for both BACnet Broadcast Management Device (BBMD) and BACnet Broadcast Device Table (BBDT) when used within Building Operation servers. Resolution A BBMD is needed when communicating to BACnet devices on another IP segment/subnet (across IP routers). One BBMD is required per subnet; this is because IP routers block broadcast packets and BACnet uses broadcast packets to initiate and maintain communications.  Continuum CyberStation (below) or bCX4 can act as a BBMD.     A BBMD can be created in a Building Operation Enterprise Server or Automation Server.    The BBMD on the other subnet should be as below   Now all the BACnet devices should be visible on both subnets Notes No more than a single BBMD should be created on each subnet for each IP port used. Additional information about BBMDs is available on WebHelp The Teach and Learn commands are useful for larger networks with multiple BBMDs  

Issue SpaceLogic SLA CO2 units prior to date code 2138 cannot be field calibrated and ABC (Auto Baseline Calibration) is not set to ON by default. Product Line Field Devices Environment Veris Models – Cost Down version: CWE2, CWE2C, CWE2D, CWE2H, CWE2K, CWE2M, CWE2N, CWV2 Firmware prior to REV1.05.23 Prior to 2138 DC   Schneider Electric + Veris Models: CW2LA2A, CW2LA2AV, CW2LAXA, CW2LAXAV SLABLC2, SLABLCV2, SLABLCVX, SLABLCX, SLASLC2, SLASLCV2, SLASLCVX, SLASLCX, SLAWLC2, SLAWLCV2, SLAWLCVX, SLAWLCX Firmware prior to REV2.08.41 Prior to 2138 DC Cause The CO2 sensors are calibrated during manufacture, but can develop an offset during shipment or storage. Units cannot be field calibrated other than by the Auto Baseline Calibration (ABC) algorithm.  The offsets can be greater than 200PPM.  The ABC only calibrates at 30PPM a week.  That would require wait times of greater than 6 weeks. Resolution Replace with a unit with a date code of 2138 or higher or make sure ABC is enabled and wait the necessary time for ABC to correct.

Issue Sigma BAS Cabling Guide Product Line Sigma Environment Sigma BAS Cause Cabling Guide Resolution Cabling guide for BAS and Sigma.

  Issue What is the purpose of modbus registers 35 and 36 in the TC900. Product Line Field Devices Environment TC900 Cause Further detail required for registers 35 and 36 and how they interact.   Resolution The TC900 allows either the onboard sensor or an external sensor or a value e.g. a temperature value binded to a modbus (16bit unsigned) value be written to the TC900 and be used.   Register 24 determines if the in-built sensor (00) or the external sensor (01) is displayed on the screen If register 35 = 00, then the sensor set in register 24 is displayed.   Register 36 has the ability to be the binded sensor and be written to (FC06) with a value x10. e.g 23.5 should be writte as 235. If register 35 = 01, then the value in register 36 is displayed on the screen.   However, if register 23 = 01, then the setpoint is displayed on the screen.   Note, in the TC900, registers start at 0000, therefore in EBO add '1'.  

Issue What TAC Xenta I/O modules could act as a Stand-Alone LonWorks device? Product Line EcoStruxure Buildings Operation, TAC Vista Environment EcoStruxure Building Operation  LonWorks TP/FT-10 Network TAC Xenta 420A TAC Xenta 421A TAC Xenta 422A TAC Xenta 450A TAC Xenta 451A TAC Xenta 452A Cause It is only TAC Xenta 421A, 422A, 451A, and 452A that can act as Stand-Alone LonWorks devices. Resolution It is only TAC Xenta 421A, 422A, 451A, and 452A that can act as Stand-Alone LonWorks devices. TAC Xenta 400 I/O modules without -A, will not work as Stand Alone LonWorks devices. Once communication has been established with the Xenta I/O module the green status led will flash on for 1 second every 10 seconds indicating it is in Stand-Alone mode.   In Building Operation, the Lonworks devices list will show devices without an "A" after it. This may lead to the wrong conclusion that these devices can be added as stand-alone devices, but that is not the case. These devices are listed so that they can be added manually to a programmable Xenta device as an IO module.

Issue Problem with Override control of BACnet Binary Output (BO) on IA Series BACnet Unitary, VAV and Zone controllers with firmware version 1.420 or earlier. When a BO override is released the value will not reflect the correct null state and may appear to still be in the previous state. After relinquishing the priority from the point, the actual Priority status shows up correctly as "Null". However, this is not reflected in the Building Operation Workstation "Watch" window. (Click on image below for larger view) Product Line TAC IA Series, EcoStruxure Building Operation Environment StruxureWare Building Operation 1.2 Automation Server BACnet Interface with MNB 1000 with MNB 300, MNB-Vx, or MNB-70. Cause When requesting the complete "Priority Array" for an output object, the values returned match their actual values, i.e. 0, 1 or "null". When requesting individual "priority array indexes" index numbers that are "null" will incorrectly return a 0 or a 1. Resolution MNB series V1.424 firmware for the VAV, Unitary, and Zone controllers resolves this issue. When an individual "priority array index" is requested, the priority input value of 0, 1, or “null” is returned. The issue only applies to the MNB-V1, MNB-V2, MNB-70, and MNB-300. The MNB-1000 does not have the "Priority Array" problem. The MNB series V1.424 firmware files are placed in the WorkPlace Tech firmware folder during the installation of WorkPlace Tech 5.8.2.

Issue Is it possible to rename an ES after an AS has been created? Product Line EcoStruxure Building Operation Environment StruxureWare/EcoStruxure Building Operation 1.9 and lower Enterprise Server Automation Server Cause Not possible to rename the Enterprise Server or Automation Servers once attached as a multi-server system Resolution It is not possible in the earlier revisions 1.9 and lower to rename an ES or an AS once created under an ES. From EcoStruxure 2.0 and above this is possible;  Refer to WebHelp for additional details: Server Rename

  Issue TAC Xenta I/O modules working as LonWorks device, indicates offline, flashes fast after power restore. Product Line TAC Vista, EcoStruxure Building Operation Environment XENTA421A XENTA451A Cause When the TAC Xenta I/O modules are used as Lonworks devices, this is indicated by the LED that flash once every tenth second. After a power failure, the device will indicate offline by 5 flashes per second.   The device will indicate offline until it gets an update to any nvi or nci variable. Resolution As soon as the device gets an update on any nvi or nci, it will again start to flash once every tenth second. This means, that if you only read variables from the device, that is, only uses its inputs, it may indicate offline until the next time the configuration is changed.   A workaround for this issue could be to just use a dummy output, that is updated regularly.  

Issue Receive an error, "Invalid Device " when trying to download an application to an I/A Series LonMark controller with Workplace Tech. Product Line TAC IA Series Environment I/A Series LonMark (MNL-5Rxx, MNL-10Rxx, MNL-20Rxx, MNL-11RFx, MNL-13RFx, MNL-V1RVx, MNL-V2RVx, MNL-V3Rvx) Workplace Tech Cause Typically, this situation occurs when a user runs the Hardware Wizard in Workplace Tech and then downloads a controller without recompiling the application. Resolution See Technical Bulletin TB06-01 for detailed information and a solution.

Issue Some of the fieldbus controller Output values presented on the Infinity controller's webpage do not agree with those values when viewed from Cyberstation and WebStation.  Product Line Andover Continuum Environment Continuum Cyberstation Continuum webClient Server Cause Some controller outputs configuration are limited to specific output types.  On the b3920 for example outputs 9 through 16 cannot be configured as digital outputs.   The ElecType (the outputs electrical type) stored in the Continuum database should match the output configuration in the controller's database.  But this is not always the case.  This can happen when the output configuration was imported from a text file.      Controller output configuration viewed while the workstation is in Online mode   Controller output configuration viewed while the workstation is in Offline mode     When the controller webpage is displayed in a browser, the parent controller (cx9900, cx9680, bcx4040, bcx9640) makes a call for the point value to the fieldbus controller.  If the ElecType for the output which is stored in the Continuum database is incompatible with the controller's output type, the parent controllers' call for the output value will fail. Resolution Switch CyberStation to Offline mode Correct the outputs ElecValue to an appropriate type for the controller output Return CyberStation to Online mode Reload the fieldbus controller

Issue SE7000/SE8000 controllers are randomly going offline or are undiscoverable on BACnet network. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE7000 SSL SE8000 Cause Improper terminations of the BACnet MS/TP communication cable.   Resolution The REF (reference) Terminal is a BACnet Reference which is a voltage reference required by BACnet testing lab (BTL) and it is rarely used in the industry. If not used as a reference, The Ref terminal should be left empty. It is not a terminal to land a shield nor a ground.    At each thermostat (Cable Junction) : Connect the (+) and the (-) wires Twist the shields together Tape around the cable to prevent short-circuit. Ground the shield at one end only (usually on the BAS side) and leave the REF terminal empty Ensure that the shield wire is not connected to the REF (Reference) terminal.

Issue SE7000s (all) and old hardware SE8000 (firmware <= 1.7.4) won't support EBO Zigbee. Product Line EcoStruxure Building Operation Environment SSL SE7000 SSL SE8000 Cause EBO Zigbee has Standard and High-Security levels. The SE7000s and old hardware SE8000 (firmware <= 1.7.4) only supports Zigbee Low Security. Resolution Replace the SE7000s and SE8000s old hardware using SE8000 with the current hardware that supports firmware 2.0.0 and newer.

Issue What does that controller/device look like Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Site with TAC or Schneider Electric Controller(s) Cause Questions concerning what a controller looks like, or if there are no labels on the controller which help identify. Are photographs or drawings available? (This is an article in progress. Have one that is not listed? Please help by taking a good picture(s) and including or send to Product Support) Resolution I/NET: 7728 7728 Left side 7728 Right side  7790 7790 side 7790 older model  7790 older model side  7798C Top 7716 7920 7920 side  MR-AHU MR-AHU left side MR-AHU right side P8UI8DO Expansion board  SCU1284 SCU1284 side Continuum: ACX5720 ACX5720 Open CX9702  b4920 b4920 Open BCX1 BCX1 open i2-600 Series i2.600 Series Open  i2_850 i2_850_Open i2_887_L_115  i2_920 i2_920_open CX9400 with three 32s and two 16s in 8 card rack CX9400 CPU front CAD Drawings for the Continuum controllers are also available on The Exchange Download Center: Link Here.

Warning Issue UNC-520 heartbeat LED had no activity but the UNC appears to be running without issues.  Environment I/A Series Universal Network Controller - UNC-520 Cause The UNC CPU idle is at 0% which resulted in the UNC heartbeat LED not having any activity (always off).  In this case,  this is caused by changing the ControlEngineService executionFrequencies to faster values and objects' executionParameters frequency set to faster or fastest. The station is using large amount of CPU resources.  Resolution To correct this make the following adjustments:  In the ControlEngineService properties, Config tab, change the executionFrequencies back to the default values of fastest at 500ms, faster at 1s, normal at 2s and slower at 5s.    Change the objects' executionParameters frequencies back to the default setting of normal. You can used the AdminTool object to perform a search and replace and changed all the executionParameters frequencies to normal.  There may be a need to change these values from the default values to optimize the UNC performance. Refer to the Niagara Capacities Engineering Notes for details. You should contact Product Support if you are unsure of these settings. 

Issue What OPC options does sigma support? Environment Sigma OPC DA AE ModBMS IC-GEN-OPC IC GEN OPC Cause Requested details Resolution There are two options available; 1. OPC Server:  ModBMS software available from Product Support London. This supports up to 5000 OPC DA tags and OPC AE events.  See release note for details 2. OPC Client:  IC GEN OPC software mimics a Sigma controller and is loaded onto the same PC as the OPC Server. This supports up to 1000 OPC DA tags only.  See datasheet for details.

Issue Receive the following error message within I/NET:  Default system page: File does not exist! Environment I/NET Seven all revisions Cause Under the Host Configuration Editor there is a setting for the Default system page.  The path and filename in this section must be correct. One or more points on a graphics page have the check box for Automatic page and / or Home Page options checked in their property settings when added to a graphics page.  (See boxed section below):   I/NET generates the above error when the alarm is triggered and this setting has been checked.  The other instance that generates the error is when selecting the Home Page option from within AMT, either by right-clicking on the point in alarm or using the Home Page icon .  The error is generated because the original graphics page has now been moved, renamed or deleted from its original state when these points were added to the graphics page.  This causes I/NET not to find the graphics page and hence display the error. Resolution  To remove this error check the following two possible causes: A.  Host Computer Configuration - Default page setting incorrect: Ensure that the Host Configuration is pointing to the correct path / filename for the default graphics page.  This is achieved as follows: Log in to I/NET Go to Edit > Host Computer > Configuration Within the Host Computer Configuration editor check within the Monitor section that the Default system page (as shown below) is valid.  If not use the browse button [...] to locate the default page you wish to use. Select the correct page, click Open then click OK to close the editor. Log out and back in to check that the correct page opens. B.   Home Page / Automatic Page display references are invalid: The resolution for this can be done in two ways:  1. Modification of Home Page references Note this method can not be used if the page has been deleted.  If you know or have some knowledge of which pages have been changed, then you can modify the path by editing a file as follows:  Locate the I/NET Seven Data folder, by default this is located in "C:\INET Seven Data\Data"  This folder should contain a file called: HOMEDIR Using a text editor open this file and carefully locate the relocated path and modify these entries (Note their may be multiple entries of the same graphics page). Save the file and confirm the Home Page or Automatic Page display option now works. If this does not work then the only solution is to recreate all the home page references as described in the below procedure.  2. Recreating all references to Home Page points: If the page names are not known or the graphic page has been deleted then the above process may assist to locate other graphic pages which have Home Page references, making this process somewhat shorter.  This method will correct the error by re-creating all links to the Home Page / Automatic Page display used within your I/NET system. The steps for this are as follows: Locate the I/NET Seven Data data folder, by default this is located in "C:\INET Seven Data\Data" This folder should contain two files called: HOMEDIR HOMEPAGE Delete these two files Now edit each page via the Graphics Editor and save each page.  The saving process will recreate the references to these pages back into the above file names. Note: If the graphics pages with references are known then you only need to visit those graphics pages; if not then all graphic pages will need to be edited / saved to ensure all references are re-created. Test its operation to confirm this process has functioned as expected. If the problem still persists then please email Product Support with the Graphics, SAV files along with the HOMEDIR & HOMEPAGE files mentioned above.