Building Automation Knowledge Base

Issue After moving the License server to another computer the license server address in the License Administrator is changed to the IP address of the new computer, but EBO Workstation gets a license error when trying to login to it. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The License Administrator can be used to select which license server EBO uses. This is done by going to the License Server Address tab and entering the license server address in the License Server Address field. Note that the license server address must be preceded by an @ in order for it to work, e.g. @servab48. The License Server Address in The License Administrator is not always used when Workstation or the Enterprise server asks for a license, Resolution The request for a license is handled in the following order:   If there are licenses located locally on the machine running WorkStation/Enterprise server (activated from ASR files), those are used first. This means that the license server set in License Administrator is not used in this case. If there are no licenses located locally on the machine running WorkStation/Enterprise Server, the registry key HKEY_CURRENT_USER\Software\FLEXlm License Manager\TACLIC_LICENSE_FILE is used. This registry key contains all license server addresses that have been successfully used to obtain a valid license previously. If this key is not empty, each server contained in the registry key value is asked for a valid license until one is obtained. This means that the license server set in License Administrator is not used in this case. If there are no licenses located locally on the machine running WorkStation/Enterprise Server, and the registry key HKEY_CURRENT_USER\Software\FLEXlm License Manager\TACLIC_LICENSE_FILE is empty, the license server set in License Administrator is used. The license server address is stored in the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Schneider Electric\StruxureWare\License Administrator\TACLIC_LICENSE_FI

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 Services for assistance. Issue During certain situations, it may be required to remove and re-install PCT to address software conflicts with other software applications. While trying to remove/install PCT you may receive an error preventing you from completing the installation. The setup had detected that no version of SBO Project Configuration Tool is installed.  The specific command-line options require that the application be installed to continue. The setup will now terminate. Error: -1603 Fatal error during installation. Consult Windows Installer help(Msi.chm)or MSDN for more information. Error 1722. There is a problem with this Windows Installer... Product Line EcoStruxure Building Operation Environment Client versions (64 Bit Only): Editions: Pro, Home, Enterprise Windows 10 Windows 8.1 Windows 8 Windows 7       Server versions (64 Bit Only): Editions: Standard, Enterprise Server 2008 R2 Server 2012 Server 2012 R2  PCT versions (64 Bit OS Only): SBO Project Configuration Tool v 1.0.0.487 - SmartStruxure Solution - Software SBO Project Configuration Tool v 1.0.0.510 - SmartStruxure Solution - Software SBO Project Configuration Tool v 1.1.0.47 - SmartStruxure Solution - Software SBO Project Configuration Tool v 1.1.1.49 - SmartStruxure Solution - Software SBO Project Configuration Tool v 1.1.2.57 - SmartStruxure Solution - Software Cause In order to get past a possible installation loop, you will need to locate and delete the following Windows registry key: [HKEY_CLASSES_ROOT\Installer\Products\B2A4F0AEC8BB0E2438706F07E2E2560B] Resolution Note: Always make a backup of your registry before making any modifications.   Run regedit.exe Locate/Search: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\B2A4F0AEC8BB0E2438706F07E2E2560B Delete Registry Key entry: B2A4F0AEC8BB0E2438706F07E2E2560B  

Issue Values sent from a 102-AX via SNVT bindings are not making it to the receiving controller. Viewing the outbound SNVT on the 102-AX shows a value, but the inbound SNVT on another controller is invalid or a default value. Product Line TAC Vista, EcoStruxure Building Operation Environment Xenta 102-AX LNS SNVT bindings LonMaker NL220 Cause The Node Configuration parameters are set with a send heartbeat of 0 seconds, which tells the controller to never send an update on the output SNVT.  All 102-AXs come with a default send heartbeat of 0 seconds, so for them to function in an LNS network where they must send data to another controller, the send heartbeat must be set to something greater than 0 seconds. Resolution Open the Xenta 102-AX device Plug-in Go to the Node Configuration Tab Set the Node Minimum Send Time (SCPTminSendTime) to a non-zero value. The range is 0-6553.4 seconds. nvoSpaceTemp nvoStatOccBtn nvoSetPtOffset nvoLocalOccLatch nvoEmergCmd nvoUnitStatus nvoBoxFlow nvoTerminalLoad nvoEffectSetPt nvoFlowControlPt nvoOccpncyStatus Set the Node Send Heartbeat (SCPTmaxSendTime) to a non-zero value. The range is 0-6553.4 seconds. nvoAirFlow nvoAuxTemp1 nvoAuxTemp2 nvoUnvInput1 nvoUnvInput2 nvoUnvInput3 nvoUnvInput4 nvoCO2sensor nvoFanLoad nvoHeat1Load nvoHeat2Load nvoMotorPositn nvoActualValue nvoOAirFlowRatio nvoAirPressure It is typical to set the Node Minimum Send Time and the Node Send Heartbeat to 60 seconds and the Node Receive Heartbeat to 0 seconds.  

Issue Step-by-step instructions for calibrating airflow on a Xenta 102-AX (or I/NET MR-VAV-AX) using the M/STAT. Test and air balance procedure for balancing airflow Product Line EcoStruxure Building Operation, TAC INET, TAC Vista Environment Xenta 102-AX MR-VAV-AX M/STAT Cause The preferred method for calibrating airflow in Xenta 102-AX or MR-VAV-AX is through the plug-in.  However, this is not always an option, especially when the responsibility for calibrating is given to a third party test and balance company.  Pocket references exist for navigating through the M/STAT menu, but there aren't clear step-by-step instructions to tell exactly how to perform the calibration. Resolution Click here to download this document in Microsoft Word format Connect M/STAT Plug the M/STAT into the jack on the thermostat. The initial display shows the set temperature.   Enter Password Press the Service button. This prompts you to enter the service mode password. Default password is 183. Use the +/- keys to set each digit and the enter key to submit. If the password is incorrect, the display will blink. Airflow Parameters If the password is correct, the first menu option – Unit Parameters (UP) – is displayed. Hit the select button down twice until Airflow Parameters (AP) is displayed. Press enter. Cooling Low Flow Setpoint The first option is Cooling Low Flow Setpoint (CLF). Press enter to view the setpoint (divided by 1000). Record this value. Press the service key to escape out of the menu. Cooling High Flow Setpoint Navigate to Cooling High Flow Setpoint (CHF). Press enter to view the value (divided by 1000). Record this value. Press the service key to escape out of the menu. Reset Factory Calibration Navigate to Factory Calibration Settings (FCS) and press enter. Use the change keys to display “YES” and press the enter key. This will set the box back to default settings. This is a good idea to do prior to every calibration. Press the service key to escape out of the menu. Calibrate Low Airflow Navigate to Calibrate Low Airflow (CPL). Press enter and the current airflow is displayed. Wait for the airflow to reach the CLF and level out. Once the value is steady at setpoint, press the enter key only once. The display does not change. Enter Actual Low Airflow Measure the actual airflow. Use the change keys to set the display value to the measured value. Press the enter key. Choose One or Two-Point Now Calibrate High Airflow (CPH) is displayed. If one-point (offset only) calibration is desired, press the service key to escape out of this mode and calibration is complete. If two-point (gain and offset) calibration is desired, press enter to continue to the next step. Calibrate High Airflow The current airflow is displayed again. Wait for it to rise to meet the CHF and level out. Once the value is steady at setpoint, press the enter key only once. The display does not change. Enter Actual High Airflow Measure the actual airflow. Use the change keys to set the display value to the measured value. Press the enter key. CPH is displayed again, this time as a general menu item. Escape Service Mode Press the service key to escape out of the menu. If you are finished configuring the box, escape all the way back out of the service menu before disconnecting the M/STAT. Disconnecting in configuration mode can leave the stat displaying “00” or other incorrect numbers.

Issue ES connect to 3rd party BACnet devices in StruxureWare Building Operation Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with Enterprise Server. Connection to BACnet devices such as ACX. Cause Desire to use ES rather than AS Resolution As of StruxureWare Building Operation 1.1 the ACX with BACnet I/P xDriver with the ES, we can see the points, load them into the BACnet interface, and view them in tgml. The BACnet IP xDriver and User Guide is available on The Exchange Download Center. The following screen captures are from the ACX where a simple Infinity Numeric is setup called ACXdevice:   Next the xDriver for the ACX is loaded and setup as Server with the following settings: (Note the IP Address references the IP of the ACX controller)   Next a simple Numeric is setup called BacTest1 with the following settings: (Note the IP Address is left blank)   Next another Numeric is created called CocaCola1 with the following settings:   Next from the Enterprise Server, a 'Find New BACnet devices' is done to find the ACX and the two Numerics created:  

Issue When creating a localized SEBA naming convention EBO displays local characters as a question mark (?) Product Line EcoStruxure Building Operation Environment Building Operation WorkStation version 3.2 (and later)  Cause The CSV file used is in ANSI format and EBO requires UTF-8 format Resolution Ensure the file is saved in "CSV UTF-8" format rather than generic "CSV".      

Issue RTD-DI-16 temperature input range is -50C to 150C, some applications require a wider range. Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation I/O Module 16 Ch RTD Cause Script program sample and guidelines needed for implementing resistance to temperature table lookup and further temperature calculation using linear interpolation. Resolution We will present two solutions, the first solution is very simple to implement but at the expense of accuracy. The second solution retains the 0.3C accuracy of the native RTD inputs. For simplicity, both solutions implement a range of -50C to 250C using the RTD Resistance electrical type to convert resistance to temperature, the program can be easily modified to implement a wider range.     SOLUTION #1 This solution simply uses the conversion settings of the RTD-Resistive input to convert from Ohms to Degrees C. Because the change in resistance is not exactly linear across the temperature range, the accuracy of the converted value varies across the range as much as +/- 4 degrees C      STEPS TO IMPLEMENT SOLUTION #1 Under the RTD-DI-16 IO module, create RTD-2W-Resistive input. Change the units to degrees Celsius. Select the sensor class, in this example, we are using the pt100 sensor. Look up the resistance value in the table for -50C and  250C and set the upper/low-level reliability. (see attached R versus T table from Omega) Use values from step #4 to set the input's conversion electrical scale.  Set the engineering scale top/bottom to 250 and -50 respectively.    STEPS TO IMPLEMENT SOLUTION #2 Under the RTD-DI-16 IO module, create RTD-2W-Resistive input. Look up the resistance value in the table for -50C and  250C and set the upper/low-level reliability. (see attached R versus T table from Omega) In the Automation Server, create an Analog Value object. This object will receive the calculated temperature value from the Script program. Set the AV units to degrees C In the Automation Server create a Script program, this program will read the resistance from the input object, look up the corresponding temperature range in the table, and then using linear interpolation calculates the temperature to an accuracy of +/- 0.3C. To ensure the program when runs when necessary, configure the program's flow type for fall thru and trigger the program off of the RTD-2W-Resistive input. Bind the RTD-2W-Resistive input and the Analog Value in the Script program as Numeric Input and Numeric Output respectively.  Here is the code for the script program   'This program uses RTD temperature vs. resistance table combined with linear interpolation 'to implement RTD temperature input over the range -50C to 250C 'Program Flow Type is FallThru 'Program is triggered by the RTD resistance input. 'This program is provided as a sample for illustration purposes, it is not intended to be a complete solution 'SE PSS v1.0 101010111110 Numeric Input RTD_Raw 'the RTD Resistance input where the RTD sensor is connected Numeric Output RTD_Temp 'Analog Value that receives the calculated temperature Numeric RTD_R[31]'Resistance to Numeric RTD_T[31]'temperature table for 100 Ohms based sensor 'NOTE: Since the resistance value changes in a nearly linear way over any 10 degree section 'of the table, we can use 10 degree increments of resistance/temperature values and apply linear 'interpolation to calculate readings in between those values, this method greatly reduces the size 'of the table in the program while maintaining very good accuracy. 'Accuracy is +/-0.3C for 100 Ohms based sensors and can be improved to +/-0.03C if 1000 Ohms based sensor used. Numeric n, sLow, sHigh,sMid Line INIT 'Due to limitations in Script we will use 2 arrays to implement the resistance to temperature table. RTD_R[1]=80.31 RTD_R[2]=84.27 RTD_R[3]=88.22 RTD_R[4]=92.16 RTD_R[5]=96.09 RTD_R[6]=100 RTD_R[7]=103.9 RTD_R[8]=107.79 RTD_R[9]=111.67 RTD_R[10]=115.54 RTD_R[11]=119.4 RTD_R[12]=123.24 RTD_R[13]=127.08 RTD_R[14]=130.9 RTD_R[15]=134.71 RTD_R[16]=138.51 RTD_R[17]=142.29 RTD_R[18]=146.07 RTD_R[19]=149.83 RTD_R[20]=153.58 RTD_R[21]=157.33 RTD_R[22]=161.05 RTD_R[23]=164.77 RTD_R[24]=168.48 RTD_R[25]=172.17 RTD_R[26]=175.86 RTD_R[27]=179.53 RTD_R[28]=183.19 RTD_R[29]=186.84 RTD_R[30]=190.47 RTD_R[31]=194.1 'The temperature array could be easily omitted since once we have the first array index (n) we could easily calculate 'the corresponding temperature value, I have kept it for the purpose of simplicity. RTD_T[1]=-50 RTD_T[2]=-40 RTD_T[3]=-30 RTD_T[4]=-20 RTD_T[5]=-10 RTD_T[6]=0 RTD_T[7]=10 RTD_T[8]=20 RTD_T[9]=30 RTD_T[10]=40 RTD_T[11]=50 RTD_T[12]=60 RTD_T[13]=70 RTD_T[14]=80 RTD_T[15]=90 RTD_T[16]=100 RTD_T[17]=110 RTD_T[18]=120 RTD_T[19]=130 RTD_T[20]=140 RTD_T[21]=150 RTD_T[22]=160 RTD_T[23]=170 RTD_T[24]=180 RTD_T[25]=190 RTD_T[26]=200 RTD_T[27]=210 RTD_T[28]=220 RTD_T[29]=230 RTD_T[30]=240 RTD_T[31]=250 n=0 sLow = 1 sHigh = MaxItem(RTD_R) 'Initialize to the size of the table Line calculateTemp 'Bottom of range If RTD_Raw <= RTD_R[1] then RTD_Temp = -50.0 Stop Endif 'Top of range If RTD_Raw >= RTD_R[sHigh] then RTD_Temp = 250.0 Stop Endif 'Find the resistance input reading in the table using a binary search 'NOTE: 'In our case, what we are looking for is the lower value of the resistance range in the table that 'the input reading falls under. 'EXAMPLE if input value is 160.9 Ohms then it is in the range of RTD_R[21]=157.33 AND RTD_R[22]=161.05 'so the binary search will give us 21 While(1) If sHigh < sLow then n=sHigh 'the input value is not in the table but we now have RTD_R[n] of the range it is within break Endif 'calculate the mid point sMid = Round(sLow + (sHigh - sLow) / 2) if RTD_R[sMid] < RTD_Raw then sLow = sMid + 1 'if read value is larger then look again in upper half if RTD_R[sMid] > RTD_Raw then sHigh = sMid - 1 'if read value is smaller then look again in lower half if RTD_R[sMid] = RTD_Raw then n = sMid 'we've located the input value in the table, this is actually the exception Break endIf EndWhile 'Now, use linear interpolation to calculate the temperature If n > 0 Then RTD_Temp = (RTD_T[n+1]-RTD_T[n])*(RTD_Raw-RTD_R[n])/(RTD_R[n+1]-RTD_R[n])+RTD_T[n] Endif Stop Line E stop   NOTE: The accuracy of the temperature reading can be further improved by the use of 1000 Ohms based sensors as well as the use of 3 wire sensors so that the resistance of the leading wires can be taken into account. If 1000 Ohms based sensors are used then the resistance values in the table implemented in the Script program must be multiplied by 10

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 When Data Import is used in the Sigma Interface, the Data Importer fails to connect with the Sigma server. Product Line EcoStruxure Building Operation, Satchwell Sigma Environment Building Operation Workstation Sigma Cause Sigma requires the correct release of Sigma software to be installed as well as the Sigma Transition Tool. Installing the Sigma Transition Tool onto a Sigma server machine can mask the true version of Sigma server and client installed. Resolution The release of Sigma client and server that is to be transitioned into EBO should be Sigma 4.08 (build 3.46.nnn) before the Sigma Transition Tool is installed. However installing the Sigma Transition Tool will overwrite the Sigma version in the Sigma application and in the Sigma splash window when launched.   To check the true version: 1. Go to Windows Explorer and locate the directory c:\sigma\bin. 2. Identify SigOp.exe (or other files) and hover over or right click and open 'Properties' and the tab 'Details',  3. The version number should be at least 3.46.57     If the version identified is below e.g. 3.45.nnn, then Sigma needs to be upgraded to the correct release. The Sigma Transition Tool will need to be uninstalled first, the Sigma upgraded and the Transition Tool reinstalled.   When complete, rerun the Sigma Data Import in EBO.   Note: Remote Sigma clients that are connected to the Sigma server will also need to be upgraded.

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 Elements in Sigma Graphics within EBO are not displaying correctly when its bound object commands the element to display or not to display. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Webstation Cause The issue arises on a machine that has a Windows Language Pack e.g. Norwegian Bokmål installed where the decimal separator uses a comma (,) rather than a dot (.).   In the example, using the EBO Graphics Editor, it can be seen that the decimal separator in 0,5 is a comma in the 'condition' command, other commands are also effected e.g. Bitmap, Alarm etc; Resolution When a Sigma graphic Data Import is undertaken the decimal separator dot (.) used by the Sigma machine is replaced by a comma (,).   On the Sigma server machine using Registry Editor. Registry Edit can be run by typing RegEdit in the Windows search box on the Task Bar. 1. Goto > Computer\HKEY_USERS\S-1-5-18\Control Panel\International\ 2. Locate sDecimal. 3. sDecimal will be set to a comma (,). Change to a dot (.). 4. Re-import the Sigma graphics using the Graphics Data Import in EBO. 5. Select a graphic and edit using the EBO Graphics Editor, select an element and check that a .(dot) is used.   Finally, check operation by changing object states on the graphics and the respective element changes state too. Note: This will be auto checked and be incorporated into the Sigma Transition Tool in the future.

Issue Can TAC BACnet (Viconics) thermostats have identical names or device ids within sub networks using their default names? Product Line Andover Continuum, EcoStruxure Building Operation Environment Viconic BACnet Thermostats BACnet BCX B4 MSTP Cause Viconic stats need a unique address and unique name across the entire BACnet network. Resolution BACnet Viconics thermostats must have a unique name and device id across the entire BACnet network. The BACnet data link layer has two key parameters: the device object name and the device object ID. The device object name must be unique from any other BACnet device object name on the BACnet network (i.e. not just the MS/TP sub-network). Typically this question comes up because a thermostat will not come online. Run an acctrace during the Find and you will probably see a duplicate MAC address. Once you have given unique names and comm addresses to each of the thermostats on the entire BACnet network, these devices should communicate and come online properly. Each of the Viconic stats are given a unique name that includes the address (once it has been made unique) To change the communication address: Hold down the menu button until the option for menu comes up Answer the questions for the various options and eventually you will be brought to change comm address. Change Comm address, select Yes and then use the up or down arrows to give this MSTP Viconic stat a unique address. There is a Configuration Tool to access and edit the name and device id unique naming scheme. Click here for ViconicsConfigurationTool.zip. Installing and using the Viconics Configuration Tool on a Windows Laptop  You will need a serial adapter connection to tie into the MSTP bus that the thermostat(s) are connected to Select the Viconics folder > ViconicsConfigurationTool.zip You can install this ZIP file in any directory you wish, but the bacdocm.ini file must be installed on your C:\Windows directory. Use the bacdocm.ini file to configure your network settings at the Configurator Tool level. You can set the MAC address of your tool, the baud rate of your connection (max 38400 - limited by the RS-232 to RS485 port and Windows) etc. The "Our Device Instance" value represents the MAC address of the tool which must be unique on the MSTP network. Also the "MaxMaster" value must be set to a higher value than the highest MAC value on the MSTP network. You can edit this INI file to modify your settings OR you can modify the settings by going though the BACdoor Configuration Tool. Once you launch the Configuration Tool, you'll notice a white applet appearing at the right bottom of your screen. That is the BACdoor MSTP sniffer that actually looks for devices and objects. If you click on that icon, and select the "Configure" tab, a configuration window will be displayed. Select the baud rate at which you want to communicate with your device. This BACdoor configuration does the same thing as changing the BACDOCM.ini file (if properly located in C\Windows). Launch the Configurator Tool application. It automatically looks for devices on that network (at the baud rate set in the bacdocm.ini file or in the BACdoor Configuration window). If no device is detected an error message will pop-up after 1-2 minutes. All discovered devices will show up in the "Device List" you have to "Connect to device" in order to list all the objects of that device. After you changed the Baud Rate, you have to click on the "Apply changes" button. Don't forget that the max speed of this tool is 38400. For the first connection, you need to power cycle the thermostat (if it was running at 76800 previously) so that it auto-detects the 38.4 network. Once you set it to 76.8, you can not connect to that thermostat with the tool because of that 38.4 limitation. Also this tool does not support Read Multiple Property so it reads every property of every object one at a time. In its default mode of operation, the device will automatically match its baud rate to the baud rate of the network. Automatic baud rate detection will occur when the MS/TP communication port is initialized (on power up). If the network speed is changed, the device will keep listening at the previously detected speed for 10 minutes before resuming auto-bauding. Re-powering the devices will force right away auto-bauding. SE7xxx series requires the tool. The SE8xxx series does not as access is available through the menu on the device.

Issue Problem changing values in Echelon LonMaker Product Line EcoStruxure Building Operation, TAC Vista Environment Echelon LonMaker Echelon Browser Plugins Cause When using Echelon Lonmaker, verify the PC's regional settings have the decimal sign set as a dot (period) and not a comma. Resolution Go to Start > Control Panel > Region and Language Click the Additional settings... button Under Decimal symbol, make sure this is a period and not a comma.

Issue Create smooth rotation for an object in a Vista TGML graphic Product Line TAC Vista, EcoStruxure Building Operation Environment TGML Graphics Editor Cause If the "CalcMode" is set to "Discrete" the object will rotate the full specified range instead of taking the duration time to slowly move around it.  Resolution Add a <rotate> tag to the object that will be rotating. Add an <animate> tag to the rotation. Set the properties for the animation: Animation = default state (Start/Stop), if a binding is ultimately used to control when the animation occurs, bind to this attribute. AutoReverse = should the animation continue in one direction or get to the end of the animation and then come back to the beginning? (True/False) CalcMode = determines whether the animation is smooth or jumps from end point to end point of the animation. For rotation, choose Linear. (Linear/Discrete) Duration = the amount of time in seconds that the animation should take. Higher numbers result in slower animation. Freeze = if true, the animation will pause at the last position when Animation is set to False. Otherwise it will revert back to the starting position. (True/False) Repeat = how many times should the animation occur. Default value is "Forever" but this value can also be set to any integer number (1, 2, 3, 4...) From, To = depend on the desired animation and target attribute. For rotation 0 to 360 is typical. Attribute = for rotation, the Angle property of the <rotate> tag is animated from 0 to 360 degrees. For more information on CalcMode see ‘Animation Overview’ in the Help.

Issue How to upgrade an Automation Server if Port 80 is closed and the Automation Server is placed behind a NAT router. Getting error message when upgrading: Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Cause The problem is that the certificate are generated with the IP address off the Automation Server, and not the NAT Router IP. Resolution The Device Administrator has the option to add SAN's (Subject Alternative Name) and not just the address of the server. So add both the LAN and the WAN addresses in the SAN field when you generate the certificate and transfer to the server.

Issue Upon rebooting an MP-V, that has not yet gone through a Flow Balance, the Box Flow data goes to zero. Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose VAV Cause When a box is not yet balanced, the Balanced K-Factor is zero. Part of the calculation of Box Flow is based on the Balanced K-Factor. Resolution There are two workarounds for this issue: Workaround 1: Balance the box Workaround 2: Enter in a number for the Box measured maximum flow and the Hood measured maximum flow. Either option will update the Balanced K-Factor to being a non-zero value.   This has since been fixed and first consolidated in IPC Hotfix 3.01.02.02000 (CP1), and fixed in release firmware release v3.02.01. See details in Box Flow goes to zero on restart, warm start, or cold start in the Known Issues and Solutions community page.

Issue Can Strings be used in all controller types? Product Line Andover Continuum, EcoStruxure Building Operation Environment All Continuum Controllers b3, i2 Controller (EcoStruxure Building Operation) Cause Some Controllers do not support strings Resolution The String class of object are supported in the following products: CX series (including all Netcontrollers), bCX series, CMX series, ACX series, i2 series (except i2885, i2887), BACnet series (except b3885, b3887), DCX 250, CyberStation.

Issue What binding methods can be used and how is the data transferred when binding objects between two b3  or Infinet controllers? Product Line EcoStruxure Building Operation Environment Automation Server, AS, ASP, ASB BACnet b3 Infinet controllers i2 Cause When binding objects between b3(infinet) devices/controllers, the type of Objects being bound will effect the properties of the binding. Resolution When binding between two Controllers, several methods can be used: Value/Point to Value/Point - The data goes via the Automation Server and the speed/rate is set in the Transfer Window, thus more bandwidth used and communication is lost if the Automation Server fails. Script to Value/Point - The data goes direct using BACnet COV subscriptions, thus less bandwidth is used. NOTE - The BACnet b3 and Infinet controllers, have no facility for direct binding of Value/Point to Value/Point, thus if a direct binding is made within the same controller, an EBO binding will be created. This will cause data packets on the MSTP or Infinet network. This should usually be avoided, as it can easily overwhelm the network. Bindings should usually be made from scripts. See Infinet under the hood for more details on Infinet setup

Issue In the SmartX Server, there is a system alarm "Shadow update failed" which will not reset What is the procedure to get rid of this alarm? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Cause The SmartX Server subscribes to the global security settings in the ES, this alarm indicates that there is something wrong with that subscription.  Resolution To reset alarm Navigate to the ES control panel->Document policy. Remove .vsd extension. This should reset the alarm in the SmartX Server  Once the alarm is reset, you can acknowledge it to clear it off the alarm view. Then add the extension .vsd back to the document policy on ES if it is relevant for the customer.

Issue Unable to connect to the detected RPCs using Engage app v1.2.1 or later and RPC 3.02.01 Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) (all types) v3.02.01 Building Operation Engage Application Cause EFR32 BLE chip needs to be upgraded to fw3.01.00.00012 but looking at the device report you see there is a Failure to upgrade EFR32 error. Resolution From workstation open the control panel and select the Firmware upgrade view. Right-click the RPC from the list of available SmartX controllers > Device> Upgrade Firmware>Select Device Firmware Select 3.01.02.00046 Firmware package Wait for the RPC to fully upgrade and return to an online state before going to the next step. This may take 6 to 9 mins which is normal. Right-click the RPC from the list of available SmartX controllers > Device> Upgrade Firmware>Select Device Firmware Select 3.02.01.00247 Firmware package Wait for the RPC to fully upgrade and return to an online state before going to the next step. This may take 6 to 9 mins which is normal Once the RPC is online Right Click the RPC > Device> Download All Objects If not upgraded in this order, the Bluetooth Chip isn't correctly upgraded and will fail.    

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Issue Need for a dual redundancy power supply for the Automation Server. Product Line EBO EcoStruxure Building Operation. Environment Building Operation Automation Server. Cause Understanding how to create a fail-safe power supply for an Automation Server.  Resolution To provide dual power redundancy to an Automation Server, a possible solution can be to use a Phaseo ABL4_ABL8RED24400. This will allow the connection of two 24V PSU's to be connected to the inputs. Then connect the output of the Phaseo ABL4_ABL8RED24400 to the AS's PS-24V See the attached document and diagram for more information.

Issue b3 i2 going offline and logging multiple 0x1408s in its error log. Product Line EcoStruxure Building Operation Environment b3 Controllers i2 Controllers Cause Excessive traffic on the network causes controller to run out of message buffers. Every time a controller receives a communication packet it has to allocate a block of memory (a buffer) to place the packet until it can be processed. Under normal network conditions the packets are processed at a rate that exceeds the rate at which they are coming in, in some cases typically associated with network configuration issues or malfunctioning nodes on the network, (i.e. broadcast storms) the firmware in the controller is unable to keep up with the amount of packets being received which exhausts message buffers available and renders the controller unable to communicate properly. In many cases the condition is temporary and does not result in a major problem, it is not unusual to see sporadic 0x1408s in the error log but when the condition persists for longer periods it will have an impact on the ability of the controller to communicate properly on the network. Resolution Use LAN captures to identify and remove the root cause of the excessive traffic.  Take steps to reduce the occurrence of many concurrent trend data requests being made of the b3 i2 controller such as staggering trend collection times, varying log-intervals or configuring some logs as COV (interval = 0).   Adjust the configuration to collect fewer trend records more frequently.