Building Automation Knowledge Base

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.

Issue Version 2.0a Error getting Key Id appears at bottom of the Hasp Key Utility when an attempt is made to activate the Continuum license using the v2c file.  Product Line Andover Continuum Environment Continuum Keyless Soft License Hasp Key Utility Sentinal HASP License Manager Cause The Sentinal HASP License Manager service has stopped. Resolution From Control Panel/Administrator Tools, launch Services. In the Services list look for either Sentinal LDK License Manager... ... or Sentinal Hasp License Manager Right click on the service and select Properties Under Service Status, if Started is not displayed, select the Start button. Under Startup Type, select Automatic. If neither Sentinal LDK License Manager nor Sentinal HASP License Manager appears in the list of services, you must install HaspRuntimeforContinuum.exe. Under the service properties, select a Automatic for Startup Type.

Issue Care should be taken when editing an Automation Server script program in a working system Environment Automation Server Script program Cause If a script program "Numeric Input",  "Numeric Output" or "Numeric Public" line is modified, but includes a syntax error or a reserved word, then saved, the binding for this line may be broken. As below  After editing the Numeric Input line using a reserved word, this line bindings are broken Resolution Always be extra careful when modifying scripts running live plant. In this case it would be better to add a new extra "Numeric Input", "Numeric Output" or "Numeric Public" line, rather than modifying an existing one. The binding below are not broken NOTE This issue was fixed in v1.7

Issue How to register a BACnet device as a Foreign Device with ES/AS Product Line EcoStruxure Building Operation Environment ES AS WS BACnet Cause Documentation Resolution Before a device can register with ES/AS, the ES/AS has to be configured to assume the BBMD role by creating the BBMD under the IP Network of the BACnet interface. You can then examine the BDT00001 entry for the IP address and port your foreign devices will use to register. Configure the device to register as a foreign device with the ES/AS, in this example we have configured a bCX4040 using its configuration web page. (Note, in order to configure a bCX as a foreing device you must first disable the BBMD option in the bCX) If the device registration was successful, the device's IP address will appear in the foreign device table (FDT) of the ES/AS    

Issue During Continuum installation error comes up that SQLncli_x64.msi file is missing. Microsoft SQL Server 2005 Setup An installation package for the product Microsoft SQL Server Native Client cannot be found. Try the installation again using a valid copy of the installation package 'sqlncli_x64.msi'. Product Line Andover Continuum Environment CyberStation Windows SQL Cause The Microsoft SQL Server Native Client has not been installed. It must be present before installing Continuum software. Resolution Before installing SQL Server, download and install Microsoft SQL Server Native Client x64 file (sqlncli_x64.msi) from Microsoft Download Center: Feature Pack for Microsoft SQL Server 2005.

Issue Description of the Parameters used in the 102-AX Plug-In Product Line EcoStruxure Building Operation, TAC Vista Environment LonMaker NL220 HTML 102-AX Plug-In Cause This may aid in finding the SNVT associated with each Plug-In field. Resolution nviBoxFlow nvoActualValue nviAplicMode nviOccCmd nviEmergCmd nvoLocalLatch   INPUT OBJECTS nvoUnvInput1 nvoEmergCmd nvoAuxTemp1 nvoUnvInput2 nvoLocalOccLatch nvoUnvInput3 nvoCO2ensor nvoAuxTemp2 nvoUnvInput4 nvoSetPtOffset VAV STATUS nvoOccpncyStatus nvoUnitStatusMode nviTerminalLoad nvoSpaceTemp nvoEffectSetPt nvoBoxFlow nvoFlowControlPt nvoAirPressure nvoHighSpaceTemp nvoLowStaticPress nvoLowStaticPress nvoOAirFlowRatio NETWORK BOUND INPUTS nviApplicMode nviOccCmd nviEmergCmd nviAirFlowReset nviCO2 nviDuctInTemp nviOutsideTemp nviRelStPt nviUnvOutput1 nviUnvOutput2 nviUnvOutput3    UCPTcooling Band SCPTsetPnts.unoccupied_cool SCPTsetPnts.Standby_cool SCPTsetPnts.occupied_cool UCPTheatingBand SCPTsetPnts.unoccupied_heat SCPTsetPnts.Standby_heat SCPTsetPnts.occupied_heat UCPTovrdDuration SCPTmaxRange UCPTresponseRate nviSetPoint nciVAVSelctnCntl.oP.ESS (UCPTvavSelection UCPTnormalPeriod.minute UCPTnormalOpen Airflow Setpoint SCPTminFlow SCPTmaxFlow SCPTminFlowStby UCPTunocAirFlow SCPTminFlowHeat UCPTminFlowWU UCPTmaxFlowWU UCPTfanOnFlow UCPTfanOffFlow Airflow Reset nviAirFlowReset UCPTco2LoReset UCPTco2HiReset Outside Air Requirement UCPToccOAReqd UCPTunocOAReqd nvoOAirRatio Airflow Setting SCPTgain UCPToffsetPress UCPTpressCutOff UCPTairFlowCoeff UCPTloStatPrior  

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue Confused by RF-Series sensor wiring instructions. Do the controller's input return and the supplied power ground connect to the same termination on the sensor? Environment RH-Series sensor Cause Documentation Resolution *** If connecting to a voltage input on the controller then use the VOUT termination instead of the 4-20 mA

Issue Have a Search object configured to find all BACnet digital values in an AS and all devices under its BACnet interface, but the digital values residing in b3 devices are NOT found by the search. Environment WorkStation AS b3s BACnet devices Cause BACnet values created in b3 have a specialized class BACnet Digital Value (Continuum) . Resolution To have a search show Digital Values from both b3 and third party devices add both classes to the filter as shown below:  

Issue Can additional mounting clips for the MNL-VxRVx or MNB-Vx controllers be purchased? Product Line TAC IA Series Environment MNL-VxRVx or MNB-Vx controllers Cause Each MNL-VxRVx and MNB-Vx controller includes one mounting clip that can be moved from the factory shipped location (bottom) to the side of the controller base.  The mounting clip is also known as the mounting foot or pivot bracket. Resolution Replacement or additional mounting clips can be purchased using part number DVAV-242.

Issue What happens when a device that SmartStruxure has COV subscriptions with goes OFFLINE for a while and then comes back ONLINE? Environment ES AS BACnet devices Cause Documentation Resolution QUESTION: What is the limit on number of COV subscription AS/ES support. ANSWER: There is no hard limits in the AS/ES for number of COV subscription, the server is limited only by resources. QUESTION: How often does the Automation Server subscribe (sends the subscription requests) for the very first time to the other devices? ANSWER: When the subscriptions are first established they are sent immediately to the devices, for example when you save a PE script program any COV created as a result of compiling the program are sent immediately to the device. QUESTION: In the case that the other device (the gateway) restarts or goes OFFLINE, how does the Automation Server handle the sending of the re-subscription requests? ANSWER: If a renewal fails due to device offline, it will be retried every minute indefinitely until it succeeds or the subscription is canceled. So if the device goes offline for a while some of the re-subscriptions will fail and will be re-tried once a minute, when the device is back, within a minute all the failed re-subscriptions will be sent again. QUESTION: Can the COVSubscriptionLifetime and the COVTimerPeriod  be set in the AS? or is it only in the ES ANSWER: They can be set in both the ES and the AS by editing the server.properties file in versions of SBO prior to 1.8.1 In SBO 1.8.1 and above, the settings can be accessed from the BACnet interface manager. QUESTION: Where is the server.properties file located in the server file system? ANSWER: AS: /opt/tac/etc (1.4.1 and below) AS: /opt/sbo/etc (1.5.0 and above) /opt/tac/db (1.4)   /var/sbo/db (1.5) /opt/tac/db (1.4)   /var/sbo/db (1.5) /opt/tac/db (1.4)   /var/sbo/db (1.5) ES:  "C:\Program Files\Schneider Electric StruxureWare\Building Operation 1.x\Enterprise Server\etc\  

Issue Following an upgrade to V1.5 from V1.4 the AS goes off/ online. Environment Automation Server AS Enterprise Server ES V1.50 and above. Cause Following an upgrade to V1.5 from V1.4 the AS goes off/ online caused by an incorrect setting of the Default Priority Level. Resolution This issue only occurs if the site has changed the BACnet "Default Priority Level" from the default value of 16, to 8 or a smaller numeric value in the Automation Server while running in V1.4. So before upgrading to 1.5 make sure the "Default Priority Level" within the Automation Server is set to 9 or higher. If the system has been upgraded with the incorrect values, then:  If the site uses single servers, or the ES/AS communication still operates correctly, then this can be corrected by changing the setting in both the AS and the ES to a value of 9 or higher. If after upgrading a multiserver configuration and the AS does not stay online, then a Hotfix can be used fix the problem using the following steps: 1. Apply the hot fix #1.5.0.4301; available from Product Support Services 2. Fix the multi-server (by detaching/re-attaching the servers) 3. Correct the two properties (AS and ES). WARNING: It is essential for any BACnet system at 1.5 or later that the "Default Priority Level" has a larger numeric value than the "Force Priority Level, otherwise some BACnet functions may not behave as expected, this also applies even if the hot fix is installed. The effects of not setting the Default above the Force Priority level are: 1. If Force Priority Level is equal to the Default Priority Level: Changing the Value of a BACnet value or a BACnet output object will cause the Value to appear Forced. This applies to the BACnet objects in both SBO servers and those in 3rd party BACnet devices. 2. If Force Priority Level has a larger numeric value than the Default Priority Level: Changing the Value of objects mentioned above will cause the Priority Override icon overlay to be turned on next to the Value property in the WorkStation’s property grid. Note: The Default and Force Priority Level are located/ defined in the Green "System" folder, "Interface Manager", "BACnet" for each Server.