Building Automation Knowledge Base

Issue Need a quick way to find all the analog inputs under all the b3s in the system that are out of service. Environment Workstation Enterprise Server Automation Server b3s Cause Documentation Resolution Create a Search object at the ES or AS level and configure as follows...   In this example the search object is in the ES and it will search for b3 inputs in all of the Automation Servers under the ES.   The search can easily be modified to search for other types of objects that are out of service by changing the class filter.

Issue A huge number of BACnet Alarms stating Duplicate network identifier are being generated Environment BACnet Cause This has been seen when two Continuum bCX1-4040 units were inadvertantly connected together on to a single MSTP network Resolution Correct the wiring, restart the Enterprise Server and the alarms stop

Issue When opening the WorkPlace Tech Editor in Workstation the list of Applications is empty or some of the applications are missing. Product Line EcoStruxure Building Operation Environment WorkStation 1.5.0 and up Cause Buffer overflow condition Resolution When this condition occurs; with the Application list displayed hold down the ALT key and click on the refresh icon This will bring up the following information message. Due to a buffer overflow, the System Tree has been collapsed and your unsaved changes have been reverted back to what is currently saved in the server. To navigate to objects again, expand the tree as needed. Click OK and the Application list will be reloaded from the AS and all existing application files will be displayed .

Issue Untranslated infinity error when creating object in b3 or i2 device. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Infinet i2 Controller BACnet b3 Controller Cause b3/i2 devices do not support certain characters in their objects name. Resolution b3/i2 devices do not support certain characters in their objects name. For example, creating an analog input using the name AI-1 will cause the error is the BACnet field is left blank, the EBO name AI-1 can be used but a name needs to be specified in the BACnet name field that is consistent with the b3 naming convention such as AI_1.

Issue Card info read successfully at enrollment reader but unable to insert into Personnel because insert button is grayed out. Environment CyberStation Personnel Manager Cause Card is already in use by another personnel object. Resolution Free up the card or use a different one that has not been assigned to any user.

Issue What are the sourcing and sinking specifications of the analog voltage outputs on the different controllers? Product Line Andover Continuum, EcoStruxure Building Operation Environment i2 b3 XP IO modules Cause Sourcing and sinking refer to the ability of a DC circuit to PUSH or PULL a direct current through the circuit. Resolution Voltage Sourcing In a controller's voltage sourcing output, the output provides a voltage source that PUSHES a direct current through the load as indicated in the illustration below. The current flows from the output's positive (V/+) terminal through the load to the output's negative terminal (-/ RTN). Current Sinking In the illustration below, a controller's voltage output is sinking a current from the load. Note the voltage source in the load's circuit which is at 15 VDC. Because current always flows from positive to negative, the voltage coming from the controller's output (0 - 10 VDC) will ALWAYS be more negative than the load's source of 15VDC, thus a current will flow from the load's voltage source through the controller's output circuit to reach the negative (RTN) side of the output's circuit. The lower the voltage coming out of the controller's output the more negative it will be as compared to the load's voltage source, thus the output will be sinking the most current when it has a value of 0 volts. It is extremely important when using a controller's voltage output in a way that will make it sink current to know the maximum amount of current the output will be sinking and to ensure it does not exceed the current sinking capacity of the controller's output. The following table shows the sourcing and sinking capabilities of the voltage outputs of the different controllers. CONTROLLER VOLTAGE SOURCING CURRENT SINKING COMMENT i2/b3 814 Voltage output 0-10 V @5 ma max 1 ma max Exceeding the 1 mA sink limit will cause the IO readings to be incorrect. ie, inputs may read 999.99

Issue When using the Graphics Converter you get the error 'Failed to restore permissions to object' or 'Failed to restore permissions to parent object' one some or all graphics Environment Graphics Converter Cause At some point, an erroneous authority definition has been introduced to the database, making it impossible for the converter to restore the permissions. Resolution On all the folders containing graphics giving this error do the following: 1. Set the authority on the folder as below, overwriting the permissions on all sub objects 2. Restore special permissions on sub objects as required 3. Convert the graphics as normal

Issue When importing a XIF file generated by XBuilder a warning (that might look like it's an error) is shown regarding missing file name and generated date Environment SmartStruxure Xenta Server XBuilder Cause The XIF file generated by XBuilder doesn't completely follow the LONMARK Device Interface File Reference Guide Resolution The warning can be disregarded, but the XIF file can easily be altered to avoid getting the warning if desired Open the XIF in notepad or similar editor, and change the following. Note the colon before the filename. Original XIF header File generated by TAC XBuilder version 5.1.9, XIF Version 4 Copyright (c) 2000 by TAC AB All Rights Reserved. Run on 0000-00-00 00:00 Changed XIF header File: X913.xif generated by TAC XBuilder version 5.1.9, XIF Version 4 Copyright (c) 2000 by TAC AB All Rights Reserved. Run on Mon Nov 03 08:00:00 2014 File generated by TAC XBuilder version 5.1.9, XIF Version 4 Copyright (c) 2000 by TAC AB All Rights Reserved. Run on 0000-00-00 00:00File generated by TAC XBuilder version 5.1.9, XIF Version 4 Copyright (c) 2000 by TAC AB All Rights Reserved. Run on 0000-00-00 00:00

Issue Need help configuring ETR501/ETR503 setpoint feature. Product Line EcoStruxure Building Operation Environment AS IO b3 Cause The ETR50x Series sensors support a slider that can be used by the occupants to change the temperature setpoint of the controlled space. Resolution SENSOR CONNECTED TO AS IO MODULE Create a resistive input on an IO module such as the UI16 and wire the slider from the ETR50x unit to the resistive input on the IO module. Move the slider all the way to the left and take note of the value reading at the input. Move the slider all the way to the right and take note of the value reading at the input. Configure the input's conversion using the values noted from steps 2 and 3 as the bottom and top of the electrical scale (see screen shot below) Use desired setpoint values for the top and bottom of the engineering scale, in the example below the slider will allow changing the setpoint between 68 and 78, note that the units has been set to degrees F for readability. Heating/cooling application such as a PE Script can now use the value of the input as the setpoint. SENSOR CONNECTED TO b3 INPUT Same as above except that the input should be configured for VOLTAGE since the b3s do not support resistive inputs.

Issue Is it possible to change the subnet/node and domain for the Lon network in an AS? Environment StruxureWare Building Operation 1.5 and previous Cause The subnet/node for an AS is hardcoded Resolution No Subnet/node is not possible to change for an AS. But the Domain is possible to change.

Issue In rare occurrences, technicians may remove the bottom terminal from the AS or I/O Baseplate so that a power supply can fit. The backplanes inside the baseplates are not all the same and this will not work. Visually determine which baseplate is for each module. Product Line EcoStruxure Building Operation Environment SmartStruxure Power Supply SmartStruxure Automation Server SmartStruxure I/O module Cause Incorrect baseplate will not work on the SmartStruxure modules. Resolution See picture for representation of Power Supply backplane, the other configuration is for Automation Server (and I/O modules). For more detailed information please see the Hardware Reference Guide.

Issue When opening a project in Workstation for Projects, Unkown Exception error will pop up Environment SmartStruxure 1.5 Workstation for Project PCS Cause This is a defect for SmartStruxure 1.5. When there is no Internet connection on this computer, this error will happen. Resolution This issue will be fixed in SmartStruxure 1.6. Currently the workaround is to obtain the Internet connection for this computer, at least when opening the project. It should be OK to remove the Internet connection after the project is opened.

Issue In the past there was no way to calibrate the space temperature from a STR-150 when used with a Xenta 121 FC/HP.  Environment STR-150 Xenta 104A Xenta 120 Xenta Programmables Cause Any calibration applied to the temperature of a STR-150 had to be done downstream of the stat in the controller. In the past when the STR-150 room stat was wired up to a Xenta 121 there was no way to calibrate the space temperature as the Xenta 121 FC/HP had no kind of Temp Offset in the controller. Resolution Starting with version 1.4 (released September 2013) of the STR-150, there is a calibration feature built into the stat. This feature allows the calibration to be applied before the temperature is sent down to the controller (Example: Xenta 121 controller). Below you can find out how to check the version number of the stat and how to perform the calibration. There is not a way to upgrade older versions of the STR-150 to 1.4 or greater. Checking the STR-150 version number The version number of the stat can be found as parameter P0. View version: Push the fan and bypass button simultaneously for 2 seconds to display P0. The version number will be displayed here. Using the STR-150 Calibration Feature Enter Configuration: Push the fan and bypass button simultaneously for 2 seconds to enter P0.   In P0, hold down the bypass button and push the fan button three times to enter configuration mode. Note: the wrench symbol is lit when the STR-150 is in configuration mode.   In Configuration Mode: Press the fan button repeatedly until you reach parameter F0. Note: The two digits farthest to the left on the display show the parameter, while the two digits farthest to the right show the value.   Use the increase or decrease button to adjust the value. The offset scale ranges from 0-99 which corresponds to -5.0 to +4.9 degrees. If the STR-150 is setup for degrees C, then the offset is exact. If the STR-150 is setup for degrees F, then the offset is recalculated to a corresponding value.   Exit Configuration Mode: Push the fan and bypass button simultaneously for 2 seconds or allow the idle timeout to exit configuration mode on its own.

Issue When adding MNL controller in Workstation for Projects, it will show up an error: Object type is not supported. Environment SmartStruxure 1.5 Workstation for Project PCS MNL controller Cause When using the Project Configuration Server, you cannot create MNL LonWorks devices and applications. Accordingly, the WorkPlace Tech Editor option does not display in the Control Panel. Resolution MNL LonWorks devices can be added in an Enterprise Server or Automation Server after deploying a project to one of these servers.

Issue When deploying ES/AS, it will go through for a while until the end. Then it will show failed, and the cause is communication error. Environment SmartStruxure PCS Cause 1. First check whether there is any real network issue, like router setting, fireware or anti-virus software. If it is confirmed that the network is good, check whether the date/time setting match the current ones. 2. If both are checked for the first point, the cause is there is a defect for PCS when the project contains BACNet interface and objects. Resolution 1. Change the date/time to current ones. 2. If it doesn't work, contact PSS to ask for hotfix: R1.5.0.7201.

Issue The property list for an Analog Input / Output or Binary Input / Output object in the WorkPlaceTech application shows a "Process Time" parameter: OR instead of a "COV Increment" parameter" Note that for Binary I/O objects, the COV increment is implied as any change of binary value and is not displayed. Environment MNB series controller WPT application file MNB series controller with firmware release 1.4 or newer WorkPlace Tech Tool software, release 5.5 or newer Cause Prior to firmware version 1.4, the MNB family of controllers did not support COV Subscription functionality. Resolution The existing I/O object must be deleted and recreated, using the WorkPlace Tech Tool software release 5.5 or newer, to allow the use of the COV Increment parameter.

Issue Need to downgrade AS from 1.5 to 1.4,  quick press "reset" 3 time, AS geso to DFU mode, after select "new database", get an error "New database failed" Product Line EcoStruxure Building Operation Environment Automation Server AS Device Administrator SBO 1.4 1.5 Cause AS and PC connected with USB and Network cable USB port on laptop (leveno) has additional power on one of the USB ports, switch to different port Firewall was enabled and disabled firewall Resolution Disconnect Network cable, use USB connection only (May need to select a different port on laptop, see Cause Notes above) Quickly press "reset" 3 time to DFU mode Click "Update Device" Icon and select "New database" If the above fails, try another USB port and disable antivirus software. In some cases, you will need to: Place the device in DFU mode Power down the AS Let it sit for at least an hour to let the capacitors lose their charge.   Power up the device again, place it in DFU mode Use the USB connection to load the correct version

Issue What is the mechanism used by the Continuum system to determine the communication status of third party BACnet devices? Product Line Andover Continuum Environment CyberStation bCX BACnet Cause To maintain the communication status of third party BACnet devices Resolution Continuum sends a read property message to read the vendor id from the device once a minute by default (or whatever the probe time is set to), as long as a timely response is received from the device Continuum keeps it online, if no response is received the device will be marked OFFLINE (after a retry) Once a device is marked OFFLINE Continuum will perform a WHO-IS once a minute (ARP if CyberStation) until an I-AM is received which will cause the device to be tagged back online, once the device is back online Continuum will resume probing the device via the read property message once a minute. Note that Continuum allows several probe options for BACnet devices, the behavior explained above is for when the probe type is set to 'Probe' ProbeOnDemand - Probing does not occur unless a communications transaction with the target device fails. Once a transaction fails then probing occurs at the interval specified in Probe Time until the device comes back online. The advantage is that additional requests to the controller fail immediately. The disadvantage if that node failure is not detected  until a CyberStation application needs to communicate with a controller.  ProbeOff - Probing does not occur. The advantage is that there is never probe traffic to the device. The disadvantage is that each request to the device fails only after the transaction times out.

Issue References to objects and points are not easily understood Product Line TAC Vista Environment Xenta Server (511, 527, 701, 711, 721, 731, 913) Cause The references relates to the internal indexes in the project Resolution Here is an example of how to locate a Menta signal referenced in an error log. The procedure is the same for all other types, although the file names may vary. This is an example taken from an error log:   1337 03-09-2014 10:41:19 AM minor trend TLogNotifier 1 menta.5.62 Variable type disagreement (Error#:61971) 1336 03-09-2014 10:41:16 AM minor trend TLogNotifier 1 menta.5.60 Variable type disagreement (Error#:61971) 1335 03-09-2014 10:41:13 AM minor trend TLogNotifier 1 menta.5.61 Variable type disagreement (Error#:61971)   Here is how to locate the signals menta.5.62, menta.5.60 and menta.5.61 Navigate to the XBuilder location on your hard drive, and browse to the folder "TargetImage\configdb". If the XBuilder project is part of a TAC Vista database, either save the XBuilder project outside the database, or locate the zip file containing the project and un-zip it. Depending on the signal reference browse the folder appropriate folder - in this example "menta". Open the file "menta.xml" in notepad or similar - for a better overview you can paste the content of the file on this web page: XML Pretty Print Locate the program id and note the reference. In this case it's id 5: Open the file "mentablocks.xml" in notepad or similar - for a better overview you can paste the content of the file on this web page: XML Pretty Print Locate the signal id's under that program id, in this case it's: Open the file "BHP BILLITON/Mentas/Water Meters.aut" in notepad or similar Locate the ObjectId's, in this case it's: #1 "MUNIC_ABL" [124,32,0,1] '','','946C6EE5-4884-4c24-804F-F7E95BAF262D' = XPR {A-B-C-D-E} #2 "RAIN_ABL" [125,77,0,1] '','','1277F8E5-5451-4dad-BEBF-1461EC75AC30' = XPR {A-B} #3 "GREY_ABL" [124,122,0,1] '','','3FF1B614-2379-47a2-BFCA-782EEE4ADAC4' = XPR {A-B-C-D}

Issue A large number of "A Log Data Transfer Has been Missed" events are being reported by the AS. All events are associated with b3 points that have intrinsic logging configured (where log configuration is part of the point properties configuration) and a StruxureWare Building Operation Extended Trend Log is attached to the point. Product Line EcoStruxure Building Operation Environment b3 Log Data Transfer Extended Trend Logs Cause We have seen these events reported when the number of log records configured in the b3 point is not evenly divisible by the Maximum Log Transfer Interval in the Extended Trend Log object. When the Extended Trend Log retrieves data from the objects intrinsic log in the b3 controller, it grabs this data in batches or portions. The size of these portions is defined by the Maximum Transfer Interval in the Extended Trend Log configuration. For example, where a b3's intrinsic log is set to 1 hour Log Interval and the Log Records is set to 72 (three days), if its associated Extended Trend Log has a Maximum Transfer Interval of 1 Day, the it will grab the first 24 records during the first pass, the next 24 records during the second pass and the remaining 24 records during the last pass. If the number of Log Records defined in the point configured is 80 instead of 72, the same Extended Trend Log will grab the remaining data in a fourth pass. However, if the amount of data remaining to be grabbed does not represent a span of time equal to the Maximum Transfer Interval, the Extended Trend Log will not grab a full period of data. In some cases when this happens data from this fourth pass can be lost and this will be reported as an "A Log Data Transfer Has been Missed: event. Example: Using our example above, and an intrinsic log Record Count of 80, the Extended Trend Log will grab the first 24 records during the first pass, the next 24 records during the second pass, the next 24 records during the third pass. It will then grab the last eight log records in a fourth and last pass. It is during the transfer of this last smaller group of data where there may be a failure of the data transfer. Resolution The number of Log Records configured in the points intrinsic log times the Log Interval should equal a period of time that is evenly divisible by the Maximum Transfer Interval time period. For example, if the Extended Trend Log is configured for a Maximum Transfer Interval of 24 hours, and the b3 point is configured for a 15 minute Log Interval, the Log Records can be set to either... Log Records = 96 (4 samples per hour X 24 hours -- a full days worth of data) Log Records = 192 (4 samples per hour X 48 hours -- two full days worth of data) Log Records = 288 (4 samples per hour X 72 hours -- three full days worth of data) and so forth.