Building Automation Knowledge Base

Issue The user installed the PCT on a machine and after running it, the following error pops up: “VM Module INITIALIZING_ Failed to refresh versions”     Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT)  Cause An installed and enabled antivirus may have corrupted the PCT installation. Resolution By verifying the PCT Virtual Box logs, we can see the folloiwng error:    ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={xxxx-xxxx-xxxxx-xxxx-xxxx} aComponent={MachineWrap} aText={The virtual machine 'Project Name' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005)}, preserve=false aResultDetail=0   This indicates that the antivirus may have corrupted the PCT installation if it remained enabled during the installation. Now the PCT cannot communicate with the Virtual Machine. To resolve this, users will need to re-install the PCT while the antivirus has been disabled temporarily.

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 During the installation of the EBO package, an error is displayed about PCT_temp.vbox already in existence.   ERROR_(3), UNABLE_TO_EXECUTE__COMMAND(99), reason=VBo xManage.exe: error: Machine settings file Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Leftover folder/file from previously failed installation Resolution Close PCT if running Take note of the folder/file that the error refers to, in this case "C:\Users\sesaxxxxxx\.VirtualBox\PCT_temp\PCT_temp.vbox Make a backup of the folder/file as a precaution (in case it has to be put back) Delete the folder or file, in this case, delete the PCT_temp folder Re-launch PCT and attempt to install the EBO package once again

Issue Can not logon with the Mobile App Building Operation Technician Tool.  Logon screen appears but app closes after selecting Logon No objects are displaying in my Custom View folder or other locations  Can not view or acknowledge alarms My alarm display colors as set in Workstation are not displaying correctly in the mobile app  Product Line EcoStruxure Building Operation Environment Building Operation Technician Tool 1.0.0 / 1.1.0 Building Operation Enterprise Server and SmartX Server 1.9.3 and below Cause May be various cause that are not allowing the Mobile App to connect to the server (Enterprise or Automation Servers), including EcoStruxure Web Services (EWS) Configuration Setting, folder names, User permissions and Alarm configuration.  Please review the different options below for assistance. Resolution Please note: Mobile experience to be replaced with EcoStruxure™Building Operation v2.0 WebStation For further information, please refer to Notice of Withdrawal of the Building Operation Technician Tool   When logging into the Technician Tool it times out This has been seen before and was caused by the Windows Firewall. If you are able to ping back and forth between the enterprise server and iPad/iPhone, then it may be a firewall issue. You can either shut down the Windows Firewall or use Creating Windows Firewall rules to allow StruxureWare Building Operation to communicate on the TCP port to set up firewall rules.  Unable to connect to server or "Contact  technical support" message given When logging in to the Technician Tool, specify the HTTPS port in the SERVER field (EX: 192.168.10.20:446).   The mobile app uses the feature from Building Operation StruxureWare call EcoStruxure Web Services, as such a majority of issues can stem from this setting.  If you are having issues logging into the Enterprise Server or Automation Server using the Technician Tool check the following: Software installed on both the Enterprise and Automation Servers must be 1.3.0.938 or later? Ensure the EWS Server Configuration settings are enabled in the server. As a minimum Serve Value and Serve Alarm must be set to true Browse allows object to browsed if not set, no objects will be displayed Ensure the user has sufficient permission to log in and MUST be member of the default domain Values are not displaying in the Custom View folder or other locations Custom View folder must be located in the root directory of the Enterprise Server Check the EWS Configuration settings and ensure Browse is set to true - refer to item 2.2 above. In the EWS Configuration there is a tab labeled "Filter Hardware Folder"; Filters can be assigned By Path or By Object, check that the nominated folder or object has been filtered. Can not view or acknowledge alarms In the EWS Configuration settings ensure that the Alarm Acknowledge setting is set to true. Also check that the Alarm has no additional 'Enforcement', such as Cause / Action - these alarms can only be acknowledge through Workstation. My alarm display colors as set in Workstation are not displaying correctly in the mobile app Unfortunately the Alarm colors are hard coded within the Mobile App - this feature may be provided in a future release.  Date for this is currently unknown.

Issue Where can I find information on EWS? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled SmartConnector Cause Documentation required Resolution Documents can be downloaded from The Exchange Download Center - EcoStruxure Web Services EcoStruxure Web Services Specification can be found at: SmartConnector Server

Issue Incorrect settings in the BCX will prevent BACnet communication. Product Line Andover Continuum, TAC INET, TAC Vista Environment BACnet MSTP BACnet IP BCX Xenta 913 Cause Because the Xenta 913 has a limitation of 127 addresses, the default BACnet Address will most likely be out of range. Resolution The BCX4040 must be addressed properly to allow BACnet communication to the Xenta 913. The setting can be changed on the BCX's Controller Configuration page by accessing the controller via IP address to its web interface. On this page, you will see a setting for BACnet Network ID Comm2 which is the device's BACnet address. This number must be unique on the BACnet Network and must range from 0-127.   To Enable BACnet IP communication: Modify the BACnet Ethernet settings from the web interface. Set the BACnet Ethernet Enabled to Yes Set the BACnet Network ID Ethernet. This is the device's BACnet address. This number must be unique on the BACnet Network. The BACnet Device Id is by default the last 7 characters of the BCX serial number and must be unique to all devices in the Continuum network. Many people try to set the BACnet Device Id field to represent a BACnet address but this is not correct. This setting does not affect the Xenta 913 in any way.

Issue Converting the Velocity Pressure measured by the pressure sensor to Flow velocity (CFM) Product Line Andover Continuum,TAC INET,TAC Vista Environment Air flow measurement / balancing Cause Requirement for converting the velocity pressure to flow velocity (CFM) Resolution To calculate Air Flow in Cubic Feet per Minute (CFM), determine the Flow Velocity in feet per minute, then multiply this figure by the Duct Cross Sectional Area. Air Flow in CFM (Q) = Flow Velocity in Feet Per Minute (V) x Duct Cross Sectional Area (A)   Determining Flow Velocity The easiest way to determine Flow Velocity is to measure the Velocity Pressure in the duct with a Pitot Tube Assembly connected to a differential pressure sensor. The Pitot Tube Assembly includes a Static Pressure Probe and a Total Pressure Probe. A Total Pressure Probe, aligned into the airflow, senses the duct velocity pressure and the static pressure, which equals the total pressure. A Static Pressure Probe aligned at a right angle to the airflow senses only the static pressure. The difference between the total pressure reading and the static pressure reading is the Velocity Pressure. If you connect the Total Pressure Probe to the HIGH port on a differential pressure sensor and the Static Pressure Probe to the LOW port on the differential pressure sensor, then the sensor’s output will be the Velocity Pressure, as shown in the figures below. The Flow Velocity is then determined with the following equation: V = 4005 x Sqrt(ΔP) V = Flow Velocity in feet per minute. Sqrt() = Square root of the number in the parenthesis. ΔP = The Velocity Pressure measured by the pressure sensor Example: Measuring a Velocity Pressure of .75” W.C. equals a Flow Velocity of 3,468 Ft/Min. V = 4005 x Sqrt(0.75) Sqrt(0.75) = 0.866 • 4005 x 0.866 = 3,468 • Flow Velocity = 3,468 Ft/Min   Determining Duct Cross Sectional Area After obtaining the Flow Velocity from the previous procedure, that figure is now multiplied by the Duct Cross Sectional Area to determine the Air Flow in CFM. There are two different equations for determining the Duct Cross Sectional Area, one for round ducts and one for square or rectangular ducts. The equation for a round duct is: A = π x r 2 A = Duct Cross Sectional Area π = 3.14159 r = radius of duct in feet The equation for square or rectangular ducts is: A = X x Y A = Duct Cross Sectional Area X = Duct height in feet Y = Duct width in feet. Example: An 18” diameter round duct has a Duct Cross Sectional Area of 1.77 Ft 2 A = π x r 2 or A = 3.14158 x .5625 18” diameter is 1.5 feet, therefore the radius is .75 feet • r 2 = 0.752 = 0.5265 • π = 3.14159 A = 3.14159 x 0.5625 = 1.77 Ft 2   Determining Air Flow in CFM After obtaining the Flow Velocity and the Duct Cross Sectional Area from the previous two procedures, the Air Flow in CFM is determined by multiplying the two: Air Flow in CFM (Q) = Flow Velocity in Feet Per Minute (V) x Duct Cross Sectional Area (A) Example An 18” diameter round duct with a Velocity Pressure of .75” W.C. has an Air Flow of 6,128 CFM The Flow Velocity is 3,468 Ft/Min. V = 4005 x Sqrt(ΔP) V = 4005 x Sqrt(0.75) Sqrt(0.75) = 0.866 • 4005 x 0.866 = 3,468 • Flow Velocity = 3,468 Ft/Min The Duct Cross Sectional Area is 1.65 Ft 2 A = π x r 2 π = 3.14159 • r 2 = 0.752 = 0.5625 Duct Cross Sectional Area (A) = 3.14159 x 0.5625 = 1.77 Ft 2 The Air Flow in CFM is 6,128 Ft 3 /Min Air Flow in CFM (Q) = Flow Velocity in Feet Per Minute (V) x Duct Cross Sectional Area (A) Air Flow in CFM (Q) = 3,468 Ft/Min x 1.77 Ft2 = 6,128 CFM

Issue Inovonics Wireless Interface problem Product Line Andover Continuum,TAC Vista Environment Inovonics FA7403 receiver Inovonics EN4000 Universal Serial Receiver Cause Inovonics provides an interface to access wireless temperature sensors. The FA7403 receiver can be used to interface with Xenta equipment or Continuum equipment, however these interfaces use different protocols. Resolution The Xenta equipment requires a hexadecimal protocol which corresponds to the FA7403 receiver. The Continuum equipment requires an ASCII protocol which corresponds to the FA7403-ASC receiver. If you have the wrong receiver for the equipment you are trying to interface with then contact Product Support for steps to reconfigure this device. Note: Inovonics EN4000 Universal Serial Receiver**, REPLACES FA7403  

Issue Xenta 913 Device Template cannot map to "native" BACnet using 485 Virtual Link Layers. Product Line Andover Continuum,TAC Vista Environment Xenta 913 BACnet Cause The Xenta 913 cannot connect to anything below the IP layer. "Virtual Link Layer" is not able to be used if the points are not exposed at the IP level there is not a way to address defined modules below. Resolution Any point that needs to be exposed at the IP level must have the ability to be mirrored in the BACnet IP device. If the IP device does not have the ability to mirror the 485 layer points, the 913 will not be able to map them.                              

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 Want to change the sound that is played in Workstation when an audible alarm is triggered Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause Need to attach individual alarm sounds to different alarms. Resolution EBO V2.0 or higher: You can add a custom audible alarm alert to EBO, which is an audio file that is played when an alarm is triggered. Refer to: Custom Audible Alarm Alert Workflow   SBO V1.9 or lower: The alarm sound is hard coded to the file C:\Windows\Media\notify.wav, and can't be changed from Workstation. The solution is to replace the notfify.wav file with another wave file. Please be aware that if the file is deleted, Workstation will crash when an alarm triggers. To change the file, you need to take over the ownership of the file as described here. The procedure is also described below. Browse to the folder C:\Windows\Media Right click the file "notify.wav" and click "Properties" Click "Advanced" Click "Edit" Select "Administrators" and click "Save" You get the following dialog. Click "OK", and close the properties. Open the properties again, and set the "Administrators" group to have full control Now rename the "notify.wav" file, and paste the wave file you want into the Media folder and rename it to "notify.wav"

Issue In applications where heating is not required is it possible to change the thermostat operation to cooling only? Product Line Field Devices Environment TC300 thermostat Cause By default the TC300 thermostat is configured for heating and cooling. It should be possible to lockout operation of heating in cooling only applications so that the user cannot inadvertently change modes. Resolution In thermostat model TC303-3A2DLS parameter item 7 allows selection of cooling or heating only mode.

Issue Confusion in documentation of the output type of an STR300 temperatire transmitter Product Line Field Devices Environment STR300 series transmitter Cause The STR300 is an electronic living space transmitter that converts a measured temperature into an electric current signal. The transmitter is delivered as a complete unit, comprising a Pt100 classB sensing element and an amplifier mounted in a housing. STR300 is intended either for surface mounting on a wall or installation in a standard switch box in dry, dust free rooms.   The HVAC Sensors Catalogue incorrectly shows that the STR300 Series has an Output of 0-10V while  the datasheet correctly shows the output as 4-20ma. Resolution The STR300 has an output signal of 4 to 20 mA corresponding to a temperature range of 0-40°C

Issue What is pneumatic actuator spring range shift and how can it be eliminated? Product Line Field Devices Environment Pneumatic Actuator Cause Spring range shift is an inherent feature of all spring return pneumatic actuators without positive positioners. The nominal published spring range of a pneumatic actuator without a positive positioner is the air pressure required to fully stroke the actuator WITH NO EXTERNAL LOAD. In the extend direction against an opposing load as provided by a damper or a valve, the supply air pressure must be increased above the spring range of the actuator to overcome the spring and the opposing force. In the retract direction against an opposing load as provided by a damper or a valve, the supply air pressure must be decreased below the spring range of the actuator so that the spring can overcome the air pressure and the opposing force. Under constant load conditions, the range of the actuator is offset by the amount of air pressure required to provide close-off of the damper or the valve. Resolution When is "Spring Range Shift" a concern? It is a concern when two or more pneumatic controlled devices should be sequenced from one pneumatic signal without an overlap. An example would be a normally open heating valve and a normally closed cooling valve being sequenced from a direct acting thermostat, In this example the spring range of the normally open valve will shift upward and the normally closed valve will shift downward which means the two valves may overlap. Another area of concern is that pneumatic control signal provides proper pressure span to operate the control device and provide "tight" close-off of damper or valve. Examples of limited pressure change would be: pneumatic controllers maximum output which is limited by main air pressure; the low pressure output capability of a pneumatic controller; and electronic to pressure transducer which can have a limited output such as 3 to 15 psig.   What can be done to overcome "Spring Range Shift" when sequencing devices? Sequencing can be accomplished in a pneumatic system by selecting actuators with appropriate spring ranges, utilizing positive positioners (AK-42309-500 or N800-0555) or ratio relays with bias adjustment (2378-501) or controllers with separate outputs for each actuator. Positive positioners on damper and valve actuators provide the versatility of start point and span adjustment plus the availability of full pneumatic power for positioning. This is the ideal way to provide precision sequencing, since variable loading on the actuator will not effect the sequencing. Biased start ratio relays may be used to provide a method of sequencing by amplifying or shifting the pneumatic signal. For applications involving sequencing a pressure to electric (P.E.) switch with a pneumatic actuator, the P.E. can often be adjusted to operate outside the operating range of the actuator. Sometimes larger actuators will help the sequencing problem. Using full actuator stroke to rotate the damper less than 90 degrees increases the force delivered to the damper and therefore reduces control signal change required to control the actuator. Rotating the damper 60 degrees usually provides almost full flow through the damper. If the actuator has an adjustable start point, adjusting the start points can help prevent sequencing problems. Normally open valves or dampers should have start point adjusted to the minimum and normally closed adjusted to the maximum. Sequencing problems can be eliminated by providing controllers with separate outputs for each actuator and do the sequencing in the controller. What can be done to increase the close-off of a damper or valve actuator due to limited or insufficient pneumatic control pressure to the control device? Proper control and close-off of the control device can be accomplished by selecting actuators with appropriate spring ranges, utilizing positive positioners (AK-42309-500 or N800-0555) or ratio relays with bias adjustment ( 2378-501). Positive positioners on damper and valve actuators provide the versatility of start point and span adjustment plus the availability of full pneumatic power for positioning (0 to main air pressure to the actuator). Biased start ratio relay provide a method of amplifying or shifting the pneumatic signal. Selecting larger actuators will increase close-off pressure. Using full actuator stroke to rotate the damper less than 90 degrees increases the force delivered to the damper. Rotating the damper 60 degrees usually provides almost full flow through the damper. If the actuator has an adjustable start point, proper adjustment of the start points will increase close-off. Normally open valves or dampers should have start point adjusted to the minimum and normally closed adjusted to the maximum. Provide electronic to pneumatic transducers with sufficient input span to obtain maximum or sufficient pneumatic output.

Issue TC303 Time and Day of the Week Settings Product Line Field Devices Environment TC303 Series Fan Coil Thermostat Cause The time and day displayed on the thermostat is incorrect Resolution Press and hold the M button on the thermostat for approximately 3 seconds and the time's hour will start to blink. Use the Up/Down arrows to change the value. Press the M button again to switch the focus to minutes and the day of the week. 

Issue In this specific instance the site was upgraded to Continuum v1.94 and the Cyberstation OS upgraded to Windows 7 64 bit, fresh install. Local Administrator account was logged on to perform Database Initialization which succeeded and Continuum was able to start-up and connect to the SQL Server. Restarting and logging in with another windows user with administrative privileges results in being unable to connect to the database. Logging out and then in as Administrator and re-initializing the Workstation into the Database re-establishes the connection and Continuum is able to be run again. This fails again when another user is logged on. Product Line Andover Continuum Environment Andover Continuum Cyberstation Windows 7 64-bit Cause Windows administrative privileges are required to initialize and make a connection to the database. Resolution Run Database Initialization as an Administrator and re-initialize the Workstation into the Database. Shut down all Cyberstations. Right-click Database Initialization and select "Run as... Administrator".  In Win7 you may need to "Shift-right-click" and select 'Run as a different user...' Select Workstation, confirm details, input password and select OK.

Issue Is it possible to monitor the status of a Modbus interface/device from within a TGML graphic? Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation WebStation Building Operation Server Serial Modbus device Cause It's a very common requirement to monitor Modbus devices and interfaces and show this value on a TGML graphic page. Resolution The attached TGML graphic gives a simple example of how to do this. The screenshot below shows the property to bind the TGML binding to. To see the property "NetworkStatus" for the Modbus network in the binding view double click on Modbus Master Network. To see the property "Status" for the Modbus device double click on the Modbus device in the binding view.   

Issue Is it possible to have different stop bit settings in different Serial Modbus devices on the same bus? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Modbus serial communication Cause In Building Operation there is an "Auto" setting for the Serial Modbus communications "Stop Bit" setting. This could be interpreted as "automatically" detecting the Serial Modbus devices stop bit setting. Resolution The "Auto" setting is only designed to detect how many stop bits are required in certain circumstances, such as when the parity setting is set to none and therefore 2 stop bits must be used. The settings used are the Serial Client settings for the entire bus and all the Modbus devices have to be set to match the Serial Client.

Issue The Modbus Server / Client is unable to read the values from address of a 32 bit Modbus register in a Building Operation server Product Line EcoStruxure Building Operation Environment Building Operation server Modbus Cause The original Modbus/JBUS protocol specifies the use of 16-bit integer registers for Analogue Inputs and Analogue Outputs. The number range able to be represented in 16-bits is: Unsigned: 0 to 65353 Signed:     -32768 to 32867    In order to represent larger numbers, it is common for 16-bit registers to be combined to represent 32-bit or 64-bit numbers. When a Modbus Client or Server reads a 32-bit Modbus value, it will be reading two consecutive 16-bit registers. An error will occur if  two 32-bit Local Modbus registers are created in Building Operation using consecutive register addresses since only the starting modbus register address is used for the request.  Resolution When configuring 32-bit Local Modbus registers in Building Operation, the next register address should not be used. Create the next Local Modbus register using the 3rd available Modbus register address. 

Issue What register type should be used for the type called INT64 in the documentation Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Modbus PM Energy meter Cause It is not clear what  Modbus register type should be configured for INT64 Resolution For reading the INT64 on this range of power meters the register definition you need to apply is the "64 bit signed swapped".   Note that this register type is not available in Building Operation versions earlier than 1.5. For further information on Modbus Register Types see the Point and Value Configuration EBO Webhelp topic

Issue When numerically evaluating in a program, what day = 1? Is Sunday or Monday the first day of the week? Product Line EcoStruxure Building Operation Environment Building Operation Script Editor Building Operation Builder for Function Block Building Operation Function Block Editor Cause What is the first day of the week in EBO, this may be required when using ">" or "<" logic in the program. Resolution Script programs handle this differently from Function Block programs.  Function Block programs use Monday as the first day of the week and therefore assign a value of 1 to Monday. Refer to: WDAY – Week Day Script program uses Sunday as the first day of the week and therefore assigns a value of 1 to Sunday. These differences are not handled by the regional settings of the local workstation. WEEKDAY *Exercise caution when using Script or Function Block programming which relates to the first day of the week. 

  Issue The shadow schedule in subordinate AS-Bs is not following the lead Schedule in the ES. When ES transitioned to occupied all of the Shadow Schedules went into Fault and did not transition, leaving the required spaces unoccupied. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Bundled Building Operation Workstation Cause The "Gameday Schedule [Shadow-Read only]" configuration shows that the Exceptions at Priority 10 do not have names.  As such, don't have access to the 'properties'.   Resolution By detaching the server and deleting the binding to the 'Lead object', we can delete these events and the fault condition will disappear. As a workaround, delete these exceptions from the Lead Schedule, save, and then add them back (with a name)