Building Automation Knowledge Base

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

Issue UPC Barcodes and EAN Barcodes Environment Site ordering parts from Schneider-Electric Cause What are UPC Barcodes and EAN Barcodes Resolution The EAN contains a 13 digit number and the UPC contains a 12 digit number. EAN = 0012345678905 UPC = (0)012345678905 or 012345678905 GS1, the original source for barcodes has created the confusion between UPC (Universal Product Codes) and EAN (European Article Numbers also called International Article Numbers) Below is an example of a Schneider Electric SHR110 room RH/Temp sensor:

Issue Right after successfully creating a simple XML Web Service all the values show 0 and the Web Service is offline Product Line EcoStruxure Building Operation Environment Simple XML Web Service Workstation Enterprise Server Automation Server Cause Possible cause 1: SmartStruxure Workstation can handle URL's both with and without the final forward slash even if the URL is just an IP address and a port number. The ES or AS can't handle that, and so after creating the variables through Workstation, the Web Service goes offline after it is added to the server. Possible cause 2: The XML file or response is not UTF8 encoded but "UCS-2 LE BOM" encoded or something else. Resolution Solution 1: Add a final forward slash to the Web Service URL - e.g. http://localhost:8000 should be http://localhost:8000/ Solution 2: Make sure the XML file is correctly encoded in UTF8 - you can check and change the encoding with e.g. Notepad++

Issue In some cases, if the block connected to reset (rs) of a Run Time (RT) block is a trigger (TRIG) block, the RT block will never reset. Environment Menta Xenta Cause If the order of the TRIG and RT block is not correct, the RT block will miss the pulse from the TRIG block. This only seems to happen when the block connected to the TRIG block is a PV block such as PVB. If the block connected to the TRIG block is e.g. a physical input such as DI the problem doesn't occur. Resolution There are two solutions to this problem Solution 1: Create the blocks in the correct order First create the "TRIG" block and then create the "RT" block. If you already have both, then delete the "RT" block, save and create a new "RT" block. Solution 2: Add a DELB block Add a "DELB" block before the "TRIG" block. This will make the "TRIG" block hold the signal long enough for the "RT" block to detect it.

Issue Sigma controllers that have been cold started do not recover correctly. Product Line EcoStruxure Building Operation, Sigma Environment Sigma Server Building Operation Enterprise Server Cause Having imported a Sigma database into the Sigma Interface on the Enterprise Server, and following a controller cold start, Sigma controllers fail to fully recover. The controller correctly receives the Backup server number, but fails to request the data from the Sigma Server. Resolution This issue is resolved as follows; Data Import the Sigma Data. Stop and restart the Enterprise Server using the Software Administrator Cold start a controller to confirm that it fully recovers. Note: A  restart of the Enterprise Server will be required again if any new additional controllers are to be added to the Enterprise Server. This workaround only works for ARM7 controllers, for V53 devices, the Sigma 4.08 (3.46.79) Hot Fix is available on the Download Centre and needs to be installed at the Sigma Server machine. Note; this hotfix is a separate item to any other Sigma hotfix and the correct Sigma Transition Tool version needs to be installed.

Issue Importing of AutoCAD .dwg files fails to import into StruxureWare Building Operation Grahics Editor Environment StruxureWare Building Operation site Cause Importing of AutoCAD .dwg files fails to import into StruxureWare Building Operation Grahics Editor Resolution It is the third party library Leadtools that fails to convert the file. The files in question are constructed with version post 2010 but our Leadtools library is from 2006. To fix this issue the Leadtools library needs to be updated. This will be fixed in a future release. The dwg drawings will need to be saved in an earlier release for compatibility with Graphics Editor.  

Issue While in "Edit in spreadsheet" mode for a Modbus device, changes made to the gain value are not accepted and cannot be changed.  Environment Workstation Modbus Network Devices 1.5.0 and prior Cause When the gain value of a Modbus point is changed to a decimal value in spreadsheet mode, the value will not be accepted if there is an integer in front of the decimal.  Resolution The workaround for this issue is to right click on each modbus point and go to properties of each modbus point to set the decimal gain value. Or you can copy and paste values from Excel into the SmartStruxure spreadsheet. For additional detail on this issue, see the below sections.   Edit in Spreadsheet All whole numbers can be entered using spreadsheet mode. If the gain value to be entered is greater than -1 and  less than 1 then it can be entered using the spreadsheet as well but the value must be entered by typing the decimal first. For example instead of typing 0.1 you would type .1 into the gain field. If the value 1.26 is typed into the gain field it will actually save it to 126. In this situation reference the bottom section "Edit in properties of Modbus point". Edit in properties of the Modbus point If the decimal value to be entered is less than -1 or greater than 1, then it must be changed in the properties of each individual Modbus point. For example if you need to change the gain to 1.26 then it must be entered as seen below. Right click on the modbus point and go to the properties.

Issue Graphics not working in Webstation. Only the menu bar is shown. Some graphics might work. The graphics are working fine in the Workstation and in the editor. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Webstation TGML Cause Some images (PNG, JPEG, BMP) can have wrong information in the image file. In some cases, this corrupted image information will block the graphic from being rendered in Webstation although it works fine in the editor and in Workstation. Resolution Make a copy of a graphic that is not working and delete all the images in the graphic. If the graphic can now be viewed in Webstation, delete the images one at a time viewing the graphic in Webstation after each save.  This will allow the location of the image(s) having the issue. Open the image in a graphics editor such as PaintBrush and save it with a new name. Import the new image and save the graphic. Check that the graphic can be viewed in Webstation Another option to easier find the file image having the issue, is to extract the images from a graphic that is not working in Webstation with the "TGML Image Extract" tool, and run all the images through an image checker, such as "Bad Peggy" or "Corrupt JPEG Checker"

Issue Unable to get modbus to communicate with the automation server and LC&D GR2400 lighting controller. Environment Modbus Automation server LC&D GR2400 SmartStruxure Solution 1.5 Cause The LC&D GR2400 lighting controller will ONLY allow 1 stop bit in it's modbus communication. Normally the stop bit setting in a modbus slave device is an "at least number", meaning the GR2400 should except 1 or more stop bits, but it does not. The problem comes from the automation server by  default sends the 1 stop bit and addition "guard bits" for modbus communication. The guard bit setting was not available in versions prior to 1.5 and by default the automation server would send 3 stop bits causing the modbus communication to fail with the GR2400lighting controller. Resolution In SmartStruxure 1.5 right click on the Modbus Master Network and select properties. Click the advanced tab:         3. Here you see the guard bit setting. This value should be a 0 if the automation server is to ONLY send 1 stop bit. If this number is left at default the automation server will add the number of guard bits to the user       setting of stop bits. By default that makes 3 stop bits from the Automation Server. To properly communicate to the GR2400 the guard bit setting should be a 0 and the user selected stop bit should be a 1 in order to ONLY send 1 stop bit.

Issue When installing I/NET on a 64 bit machine, two parts will be installed: main part and 64 bit part. Sometimes when attempting to uninstall the 64 bit part in the Control Panel, it will show an error: There is a problem with this Windows Installer package. A problem required for this install to complete could not be run. Contact your support personnel or package vendor. It cannot be solved even when trying to reinstall the whole software. The software installer goes into continuous loop and does not complete. Environment I/NET 64 bit OS Cause The main part of I/NET on 64 bit machine is under C:\Program Files (x86)\INET Seven\ and another 64 bit part is under C:\Program Files\INET Seven\.The cause of this issue is when you tried to uninstall the main part in Control Panel first, it will also delete the files under C:\Program Files\INET Seven\, which makes the uninstall program unusable for 64 bit component. When trying to reinstall the software, I/NET will regard the 64 bit part has been installed and skip this step, which forces the software installer into a continuous loop. Resolution The correct order to uninstall I/NET on 64 bit machine should be to uninstall 64 bit component first, and then the main part in the Control Panel. If the main part has already been uninstalled, try to download MyUninstaller from here. After opening the software, right click on the I/NET 64 components and choose Delete Selected Entries. That will force uninstalling this component.  After that, try to install another version and it should be fine.

Issue Sometime it is hard to trace the File Equalization process, especially when issues happens. Environment I/NET File Equalization Cause There is a log file under C:\INET Seven Data\ called INetEqzConfig.log. This will record the whole process of file equalization. But it is not so accurate if I/NET shows the equalized client finished the equalization although it is not. Resolution There is a function in SQL management tool called Replication Monitor. This can monitor the current SQL replication status of all the clients, which is file equalization, on the filemaster. 1. Open SQL management tool on Filemaster, and right click on Replication to Launch Replication Monitor. 2. In the monitor, after you start the Filemaster, you will see the local SQL server. If there is no equalized client, the list will be empty. 3. If the equalized clients appear, they will show up in the list. If it shows Synchronizing, that means file equalization is working. 4. If it shows Not synchronizing, it means the file equalization doesn't start or has been finished.

Issue On a SmartStruxure workstation PC how can the Menta communication port be changed. Environment SmartStruxure 1.5 Cause The Menta setup application is not added in the start menu. This exe is located in the StruxureWare install files and can be run to change the communication port for a direct RS232 connection This file is located in the following directories 64bit systems C:\Program Files (X86)\Schneider Electric StruxureWare\Buildings Operation 1.5\Workstation\Menta Setup.exe 32 bit system C:\Program Files\Schneider Electric StruxureWare\Buildings Operation 1.5\Workstation\Menta Setup.exe Resolution Run the Menta Setup.exe and add the communication port that Menta will use. For the first time the other settings must be entered as detailed in this image.

Issue Creating a StruxureWare Saved Search which functions as an Inet Off Normal Point Summary Environment StruxureWare Building Operation Workstation Cause This tool can be used for troubleshooting and as an example of how to use the search features found in StruxureWare Resolution In StruxureWare, click on the Magnifier Icon next to the search field to open the Advanced Search Window Set the Search field to an asterisk " * " Set "In folder" to the I/NET Interface Uncheck the Include properties option Click on the ellipsis next to "Include types" Select INET Point Click on the Ellipsis next to Conditions Add conditions so that the search will show when Alarm is true OR Test is True OR Manual is True OR Old Data is True OR Alarm Acknowledge is False As an option, you can include offline items as well. Click on the Save Search Criteria Icon Name the Search and choose a destination folder You can now perform the same search with one click from the System tree.

Issue How to add b3 devices to EcoStruxure. Product Line EcoStruxure Building Operation Environment Building Operation Workstation b3 BACnet Cause List the methods of adding b3 devices to EcoStruxure Building Operation Resolution The following information can be found in the EcoStruxure Building Operation - Technical Reference Guide. Use the guide relevant to the release of EBO installed.   Discovering b3 BACnet Devices with the Device Discovery View Using the Device Discovery view to search deployed Automation Servers for b3 BACnet devices. For more information, see section "b3 BACnet Device Overview". To discover b3 BACnet devices with the Device Discovery view In WorkStation, click the Device Discovery view. In the System Tree pane, click the Automation Server to be searched. In Select device type, click on BACnet devices. Select the b3 BACnet device you want in the Device result pane. Map a device by dragging that device from the Device result area and dropping it in the System Tree pane. When prompted, copy the device only or copy the device and all of its children.   Learning b3 BACnet Devices b3 BACnet devices van be learned and to automatically assign the node IDs and initiate communication with devices on the MS/TP network. Tip: It is possible to learn b3 devices when the b3 devices and the Automation Server functioning as the BACnet interface are connected and online. If the b3 devices are not physically connected to the network, it is also possible to manually create and configure the devices offline in Workstation. For more information, see section  "b3 BACnet Devices. To learn b3 BACnet devices In WorkStation, in the System Tree pane, select the MSTP Network In WorkStation, on the Actions menu, click b3 devices and Learn When the b3 BACnet devices are learned, click Close If necessary, perform a download operation to eliminate any old points and programs stored on the b3 BACnet device.