Issue Is there a way to specify the priority that the system should use by default when writing to the value of BACnet objects in EcoStruxure Building Operation (EBO)? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation WorkStation BACnet Cause It may be necessary, especially in a legacy b3 environment, or third party BACnet network integration, to write by default to a priority other than 16 in the Command Priority stack. Resolution The default Command Priorities within a system used when writing to BACnet objects are governed by the Interface Manager in the ES.  These settings are then inherited to all AS. Command Priority 16 is used by default writing to the Value Property of a BACnet Object Command Priority 8 (Manual Operator) is used by default when Forcing the Value BACnet Object in EBO. Both defaults can be changed but care should but be taken here as any changes will ripple through the entire system and may have unforeseen consequences. Script programs created in a b3 will still use Command Priority 10 by default. It is still possible to write at any other priority in EBO by Binding directly to the desired command priority.

Issue If a SmartX Server is using External Log Storage how often are new trend log data and events sent to the TimescaleDB? Product Line EcoStruxure Building Operation Environment Building Operation Timescale Database Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause When a SmartX server is using External Log Storage many of the trend logs and all new event records are sent to a TimescaleDB for storage. Resolution New event records in the SmartX Server will be sent to the TimescaleDB when 500 records are collected but the SmartX Server will wait a maximum of 10 seconds before sending them. Some records as "Edit" and "Comment" are sent immediately. New trend log records in the SmartX Server will be sent to the TimescaleDB when 500 records are collected but the SmartX Server will wait a maximum of 10 seconds before sending them.

Issue When mapping the EcoStruxure Building Operation (EBO) Trend Logs to EcoStruxure Energy Expert, not all trend logs are visible in the ETL Tool 'Load Sources'. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Energy Expert Cause The EBO user credentials entered into ETL for connect to the EBO Database must have access to BOTH the trend log itself, and the point which the trend log is logging. Resolution Edit the EBO user which the ETL is using to connect to EBO and give a minimum of Read Only access to both the Trend Log in question and the Point being logged  and then in the ETL re-run 'Load Sources'.  The additional points which were missing before should now be available for mapping

Issue Is it possible to include the Comments field from Extended Logs into Report Server Reports? Product Line EcoStruxure Building Operation Environment Building Operation Reports Server Cause Regardless of the new Reporting Features in EcoStruxure Building operation (EBO) 3.2, users of existing systems up to and including EBO 3.1 are asking if it is possible to include the Comments field in Extended Logs within the Enterprise Sever to enhance the data in RS Reports? Resolution Extended Log Comments within the ES are not available to Report Server reports today and given the move to new Reporting Features now available in EBO 3.2 it is unlikely that an Enhancement Request for such a feature would be implemented quickly. Therefore, the suggestion here would be to migrate the Extended Logs to External Storage via TimeScaleDB where all the Extended Log data (including the comments) can be freely manipulated by 3rd party Reporting Products.

Issue From a legal Microsoft Licensing point of view, it is important to be clear how many Client Access Licenses (CALs) are required when using a Report Server with SQL in EcoStruxure Building Operation (EBO). Product Line EcoStruxure Building Operation Environment Building Operation Report Server Cause While Microsoft Client Access Licenses are not required to make a Report Server installation function, ANY system which makes use of Microsoft SQL must consider the provision of sufficient purchased CALs to remain legally compliant and avoid potential fines. Resolution The Report Server Reporting Agent Service which is responsible for reading the data from the Enterprise Server (ES) and storing it the Microsoft SQL Server Database, will use one connection to the SQL Server. and therefore, requires one CAL. 

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

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

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

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. 

Issue After connecting a new Optimum Living Space Sensor, the LCD is blank other than being backlit. Product Line EcoStruxure Building Operation Environment Building Operation SmartX Living Space Sensor Optimum Building Operation Multi-purpose VAV fw 2.00.03.02000 or older Cause Only Living Space Sensor bases running application version 1.0 or later can read the Optimum cover models Resolution Upgrade EBO to v3.1.x or later and SmartX controller to fw v3.01.x or later. At the time of this being published, firmware revisions prior to 3.01.x are not compatible with the Optimum Living Space Sensors (SXWSCDPSELXB, SXWSCDPSELXW, SXWSCDXSELXB, SXWSCDXSELXW).

Issue "Ethernet 1 Configuration" of a SmartX Server in the Device Administrator for EBO version 3.2.1 or higher shows "Dynamic DNS" as enabled and grayed out. Is it possible to disable "Dynamic DNS"? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium version 3.2.1 or higher Cause The Dynamic DNS service procedure supports the assignment of dynamic IP addresses to a particular domain. A comparison with the internet provider's DNS databases takes place automatically. The Dynamic DNS automatically ensures that changes to the IP address are detected and DNS entries are updated accordingly. Resolution In EBO version 3.2.1 or higher it will not be possible to disable Dynamic DNS, it will always be enabled.

Issue BACnet Interface has "!" with unresolved references Product Line EcoStruxure Building Operation Environment Building Operation Automation Server v2.0 or later Building Operation Multi-purpose VAV Building Operation Multi-purpose Controller Cause During the startup of a Smart-X controller, the auto-association feature fails and the data becomes corrupted Resolution Go to BACnet Interface -> Time Sync Recipients Find any devices listed as DEVICE_<Instance ID>, select & delete Verify all devices listed are configured as follows: SmartX controllers Recipient Type: Reference Recipient Device Object Reference: <Device in System Tree> If Recipient Name does not match, copy from Object Reference and paste in the field. This helps humans troubleshoot the issue. DO NOT set Recipient Type = MAC Address, Network ID = Global Network or Local Network, Mac Address = Broadcast. This will set time on other ES/AS with BACnet Interface on the BACnet System.

Issue Are multiple Enterprise Servers in same system/site supported with Building Operation?  Product Line  EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central  Cause Large sites or customers may request a multi-tiered configuration to support multiple Enterprise Servers. Resolution A three tier server support containing multiple Enterprise Servers are not supported until Building Operation 2.0 and above.  The top tier of this EcoStruxure BMS been the Enterprise Central.  Refer to the following online help topic for further information: EcoStruxure BMS Server Hierarchy