Building Automation Knowledge Base

Issue Replacement for Satchwell DWT0001 or DWT1701 by the STP660 Immersion Temperature Sensor due to obsolescence. Product Line Field Devices Environment DWT1701 DWT0001 Cause Obsolescence of Satchwell DWT0001 and DWT1701 Immersion Temperature Sensor. Resolution The STP660 Immersion Temperature Sensor is the replacement for the DWT0001 and older DWT1701 The STP660 provides the same functionality as the Satchwell DWT0001 and DWT1701, differing only in its appearance, dimensions and terminal identification. A pocket or well is also required and is sold separately. 9121066000 - Brass 9121060000 - Stainless Steel N.B. In the case of a DWT0001 and only the sensor part is required, then the STP660 will fit into the existing pocket (and adaptor). or In the case of a DWT1701 and the sensor part is only required, then a pocket adaptor 9121058000 is needed.

Issue Accessing WebPinpoint graphics from a web browser causes one of the following errors…   Failed CreateDNWACServer. Cause:Object reference not set to an instance of an object. URL:HTTP://eceheatsrvr/DNWACServerFactory DNWACServerFactory /WACServerFactory.soap   Failed creating remote objects. DotNet framework is missing.      Product Line Andover Continuum Environment Continuum webClient Server MicroSoft Windows XP MicroSoft Windows Vista MicroSoft Windows 7 MicroSoft Windows 10 MicroSoft Windows Server 2003 MicroSoft Windows Server 2008 Cause User Account Control redirects files to a different folder than expected by WebClient. User permissions are interfering with the WebClient. A variety of other configuration issues may cause this problem. Resolution User Account Controls Redirection The WebClient installation guide goes into detail about why MicroSoft Windows includes User Account Controls redirection. Follow the procedure outlined below.   Give "Everyone" permissions to the C:\Program Files\Continuum and C:\Program Files\Continuum\DNWACServerFactory folders In Windows Control Panel > User Accounts and Family Safety > User Accounts, select an Administrator user on the PC and select User Account Control Settings. Move the slider all the way to the bottom to Never Notify and select Ok. Follow the instructions in the webClient Installation guide section called "Configuring Graphics for webClient: Windows Server 2008, Windows Vista and Windows 7". Site may be setting User Account Control with group policy and setting it upon reboot of the PC to a setting other than Never notify. A batch file may be used to turn User Account Control off before launching WebClient. A Google search for doing this would be needed and is beyond the scope of this article. Each host that will be running a web browser WebClient session should have also have User Account Control settings set to minimum.       Web.config has not been correctly modified   Using Windows Notepad as an Admin user, modify the web.config file which is located in the c:\program files\continuum\dnwacserverfactory folder. Delete the text and replace with the text below, replacing WORKSTATION1 with the host name of the host computer.  This must be done on all hosts which will run WebClient browser sessions. <configuration> <system.runtime.remoting> <application> <service> <wellknown mode="Singleton" type="DNWACServerProxy.WACServerFactory, DNWACServerProxy" objectUri="WACServerFactory.soap" /> </service> <channels> <channel ref="http" machineName="WORKSTATION1"> </channel> </channels> </application> </system.runtime.remoting> <system.webServer> <security> <requestFiltering allowDoubleEscaping="True"/> </security> <directoryBrowse enabled="true" /> </system.webServer> </configuration>     Allow Double Escaping   If for some reason editing this file is still not working. Try the following: In Start >Control Panel > System and Security > Administrative Tools > IIS Manager (Not IIS6) Expand the tree on the left for the webserver name. ie. Webclient1 Expand Sites Expand Default Web Site Click DNWACServerFactory Double Click Request Filtering In the right-hand column select Edit Feature Settings Check Allow Double Escaping and click OK Click on the Default web site and in the far right column click Restart     Test Authentication pass-through for SOAP errors   In IIS Manager; Expand Server> Sites> Default Web Site Left-click on the DNWACServerFactory, on the far right column Select the Basic Settings link Click the Test Settings button. If Authentication pass-through is showing red follow this procedure Click Close Click Connect As> Add a windows user and password that will be used for WebClient Click the Test Settings button Authentication pass through again and it should now show green Perform a local reboot on the WebClient server Test Webclient Graphics     Make sure that the browser PCs are logged in as a Local Administrator for the WebPinpoint and ActiveX installation   Internet Explorer>Tools>Internet Options>Security>(select Zone i.e. TrustedSites)>Custom Level button Make sure that 'Download signed Activex controls' and 'Download unsigned Activex controls is set to prompt or Enable, since the default setting on many web browsers is Disabled.       Add the Webclient PC as a trusted site to the browser PCs   In some configurations, you may need to add the IIS computer into Internet Explorer as a trusted site for each browser. In Internet Explorer: Select Tools > Internet Options > Security > Click Trusted sites > Click Sites Type in http://yourservername/WebClient and click Add (Ex. http://tacweb/WebClient) Deselect the checkbox for Require server verification (https:) for all sites in this zone.  Click OK and then OK again Close Internet Explorer and retry accessing WebPinpoint     Be sure to configure the application pool for 32-bit applications on 64-bit operating systems.   On 64-bit Operating Systems perform the following steps: Open IIS Manager. Expand the computer name in the left-hand pane and click on Application Pools in the system tree view. Select DefaultAppPool and click Advanced Settings. In the Advanced Settings dialog box, change the Enable 32-bit Applications option to True. ** When using 1.94 SP1 and above, check the application pools .net version selected and make sure that the Identity is set to "Network Service" Name                           .Net Version ASP NET v4.0 4.0 ASP NET v4.0 Classic  4.0 Classic .NET AppPool  2.0 Default AppPool   2.0 WebClient 4.0       DNS issues   Even when you may not be seeing red x’s in Pinpoint View>Options>Web locations and you are able to browse to pin files though IE, WebPinpoint may be giving you a graphic URL error. Try entering using the IP of the WebClient server in place of its DNS name for Pinpoint View>Options>Web locations. Also try using the WebClient Servers IP address in places of the its DNS name and also for accessing WebClient through the browser. For example http://10.159.100.125/WebClient       WebPinpoint fails to register the DNWACClientProxy.dll and tlb files when installed.   On the from the client (web browser) host, perform the steps below:  Close WebClient browser if it is running. Open command line in Administrator mode. Run the batch file C:\Programs Files (x86)\WebClientPinpoint\WPPRegistrationClient.bat     Other items to check:   Disable Windows Defender Turn off all 3 firewalls Shut off SPS software protection service when installing. Run Internet Explorer as an Administrator to make sure the ActiveX controls are being installed

Issue How to Set Up BACnet Enabled ABB Variable Frequency Drives for Use With Continuum Product Line Andover Continuum, Other Environment ABB Variable Frequency Drives Continuum Cause ABB VFDs must wired and configured properly to be used with a BACnet Continuum network. Resolution When wiring an ABB drive up to the Continuum BACnet MSTP network make the following connections: Terminal X2 Type (+) (-) Reference Drive Only 29 30 31 Bypass 27 28 29  ABB recommends that when using a two conductor cable with shield that the shields not be connected  to any pin (Note that pin 29 would be unused) but simply connected together with a wire nut. However, they do say that the shields can be connected to pin 29 if the drive communication is intermittent.  If the ABB drive does not have an E-Clipse bypass (E-Clipse is the ABB brand name for the bypass portion of the VFD) use the following settings:  Parameter  Setting Notes 9802  BACNET  Sets the communications protocol of the VFD. 5302  MAC ID Create a unique ID. A good practice is to set this to the Infinet ID + 1000. For example, if the Infinet ID is 5 then set this to 1005. 5303  Baud Rate  Set the baud rate being used on your BACnet network. 5311  Device Instance ID                   This is the Infinet ID and should be set to an available number between 1-127. This will display as a hexadecimal value in the BACnet side of Cyberstation. 1001  COMM  Set this if you want to start & stop the VFD over BACnet. 1103  COMM  Set this if you want to control the drive speed over BACnet. 1604  COMM  Set this if you want to reset VFD faults over BACnet. If the ABB drive does include a bypass the following settings must all be entered (notice that 5302 and 5311 are now specific to the VFD portion of the unit whereas the 5002 and 5011 are specific to the bypass portion) All of these parameters as well as the parameters listed above must be entered at the bypass. Parameter Setting Notes 5302  Drive MAC ID  Create a unique ID specific to the VFD. 5311  Drive Device Instance ID  This is the Infinet ID specific to the VFD. 5002  Bypass MAC ID  Create a unique ID specific to the bypass. 5011  Bypass Instance ID  This is the Infinet ID specific to the bypass. NOTE If the ABB drive is ACH550. Then the parameter below need to be set as a minimum. Other points will also need to be set depending on your site requirements, but the ones below will get communications up and running    Parameter  Setting Notes 5301   x5xx -This parameter indicates the active protocol and its revision. It should read x50xx if BACnet is properly loaded. If this is not the case, confirm that drive parameter 9802 = BACNET (5). 5302  MAC ID -This parameter sets the drive’s BACnet MS/TP MAC ID. A temporary value of 0 places the protocol channel in reset. 5303  Baud Rate -Set the baud rate being used on your BACnet network. 5304 Set to 0 -This parameter sets the BACnet MS/TP character format as follows: 0 = 8N1 1 = 8N2 2 = 8E1 3 = 8O1. 5311 EFB PAR 11  - Instance ID part1 This parameter, together with parameter 5317, EFB PAR 17, sets BACnet instance IDs: • For the range 1 to 65,535: This parameter sets the ID directly (5317 must be 0). For example, the following values set the ID to 49134: 5311 = 49134 and 5317 = 0. • For IDs > 65,535: The ID equals 5311’s value plus 10,000 times 5317’s value. For example, the following values set the ID to 71234: 5311 = 1234 and 5317 =7 5317 EFB PAR 17  - Instance ID part2 This parameter works with parameter 5311 to set BACnet instance IDs. See parameter 5311. 1001  COMM -Set this if you want to start & stop the VFD over BACnet. 1103  COMM -Set this if you want to control the drive speed over BACnet. 1604  COMM -Set this if you want to reset VFD faults over BACnet.

Issue When using CIDR (Classless Inter Domain Routing) or Supernetting it is not always obvious what range of IP addresses can be used. Product Line EcoStruxure Building Operation Environment Device Administrator Building Commissioning Tool Cause When subnet masks with values other than 255 are used it is not always obvious what is the range of valid IP addresses allowed.  There is a need for an easy way to determine the range of valid IP addresses for the Subnet Mask being used. Resolution The IP address range can be calculated mathematically but the simplest method is to use a subnet calculator.  The website links below are both examples that will calculate the range of valid addresses for any specified subnet value.   http://www.subnet-calculator.com/cidr.php https://www.calculator.net/ip-subnet-calculator.html   Visit either of the websites for a CIDR / Supernet calculator, enter an IP addresses in the network along with a subnet mask and the calculator will provide the range of addresses that can be used within the subnet.   In addition to online calculators, a number of different subnet-calculator programs are available for Android, Apple and Windows Smartphones.  

Issue What are the fields in the FIPS-201 PIV FASC-N? Product Line Andover Continuum Environment CyberStation NC2 (9680) ACX2 (ACX5720, ACX5740) Cause Documentation Resolution The Federal Agency Smart Credential Number (FASC-N) consists of 40 total characters encoded as Packed Binary Coded Decimal (BCD) format with odd parity creating a 200 bit (25 byte) record.

Issue After 9 straight failed Workstation login attempts the SmartX Controller will be locked out. See Workstation lockout message below.   After 3 failed attempts to add an SmartX Controller to the device administrator the SSH connection will be locked out for the amount of time set in Workstation.    Product Line EcoStruxure Building Operation Environment Building Operation Device Administrator Building Operation Workstation Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Automation Server Putty Cause In order to protect the EcoStruxure system from potential security threats, there have been login lockouts put into place. Both scenarios of lockouts are only temporary. Resolution Locked out of SmartStruxure Workstation Once there has been 9 consecutive Workstation login attempt failures for a single user, that user will be locked out of Workstation for 1 minute.  Locked out of an Automation Server in Device Administrator Once there have been 3 consecutive SSH Automation Server login failures through Device Administrator (Adding an Automation Server into Device Administrator via IP address), the Automation Server will be locked out for a default of 15 minutes.   The SSH Console Lockout time is configurable and can be changed in the Security Manager section in Workstation.   

Issue SPU 1201 Universal Pressure Switch – Specification No. 131-1-201 SPU 1202 Universal Pressure Switch – Specification No. 131-1-202 Product Line Field Devices Environment Site requesting a Universal Pressure Switch Cause SPU1201 and SPU1202 obsolescence Original PDF specification sheet is available here: DS21602-0203.pdf. Resolution The SPU1201 and SPU1202 have been made obsolete per the supplier. The closest replacement options that we have are listed below: SPU1201 is a 0.2 – 4.0 Bar device. The replacement options are SPP920 Series SPU1202 is a 12 – 250 mBar device. The replacement options are SPP920 Series Refer to Product Announcement PA-00166 for the SPP920 series Differential Pressure Switches for neutral and slightly aggressive liquids and gases.

Issue Receive error "Property value out of range" when creating a BACnet interface on the Enterprise Server   Following problems after upgrading SmartStruxure servers to 1.5: Attaching an Automation Server to or detaching it from an Enterprise Server will fail with “Property value out of range” error. Changes to the ~/System/Interface Manager/BACnet fail to be propagated lead-shadow functions through to the child servers. Automation Server controllers dropping offline following an upgrade to 1.5 (BACnet command priority related  also may see numerous "Changeset Rollback errors") Product Line StruxureWare Building Operation 1.1, 1.2, 1.4, 1.5 and above Environment Enterprise Server (ES) BACnet IP Interface Windows XP, Windows 7 and Windows Server 2008 R2 Cause Their may be various items that generate this error, checking the Enterprise Server (ES) system log in the Software Administrator may assist in pin pointing the error.  If you see an error that ends with ~/BACnet Interface/IP Network, then this error is generated when their is no valid IP Network.  For SmartStruxure 1.5 or above or planning to upgrade from 1.4 to 1.5 (and above)  This issue only occurs if a BACnet interface is used and 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. The "Property value out of range" message relates to the new Force priority level in 1.5 and the Default priority level in 1.4.1 being mismatched. Resolution The ES must be connected to an IP network. To resolve this error follow these steps: Close all Workstations (if running) Connect the Enterprise Server to a valid IP network (with a valid IP address). Stop and Restart the Enterprise Server service through the Software Administrator application. This should now allow the BACnet Interface to be created successfully For SmartStruxure 1.5 or above or planning to upgrade from 1.4 to 1.5 (and above) Please refer to TPA-SBO-14-0005.00 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 multi server configuration and the AS does not stay online, then a Hotfix can be used fix the problem using the following steps: Apply the hot fix #1.5.0.4301; available from Product Support Services Fix the multi-server (by detaching/re-attaching the servers) 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" must have a larger numeric value than the "Force Priority Level, otherwise some BACnet functions may not behave as expected. Note: This also applies even if the hot fix has been installed. The effects of not setting the Default above the Force Priority level are: 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 SmartStruxure servers and those in 3rd party BACnet devices.   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.   

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 How to truncate event tables in Continuum databases. Product Line Andover Continuum Environment Continuum 1.xx SQL 7 SQL 2000 SQL 2005 Cause Stand Alone Continuum Databases use Microsoft MSDE and SQL Express databases which have size limitations. Once these databases reach full capacity they will need to have data truncated from tables to try and reduce the size of the database. Databases should never exceed their size limitations, but if they do, reducing the size of some of the tables will in most cases allow the database to be functional again. Microsoft SQL MSDE database size limit is 2 gig Microsoft SQL Express database size limit is 4 gig Resolution Once logged into the SQL MSDE or SQL Express database, the queries below will reduce the size of the database. As with any database, make sure you backup the database before running any queries. The Usernames and Passwords used below are defaults, your UN/PW may differ. To log into SQL MSDE use the following commandline. osql -Usa -P To log into SQL 2005 Express us the following commandline with your servername sqlcmd -Sput_server_name_here\sqlexpress -Usa -Padminadmin Once logged in you'll be prompted with a 1> at which time you'll change the context of the database you'll be truncating information on. For example if your database name is ContinuumDB you would use the following. 1>Use ContinuumDB 2> Go 1>Now put in one of the queries below 2> type in Go to execute /****** Replace 90 with the number of days to maintain in each log ********/ delete from accessevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from activityevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from alarmevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from errorevent where DATEDIFF(day, timestamp, getdate()) > 90 ** To gain back the space after deleting rows SQL Express Right click on Continuumdb>Tasks>Shrink>Database MSDE(osql) dbcc shrinkdatabase ('your_database_name',0) (enter) go (enter) dbcc shrinkdatabase ('your_database_name',0) (enter) go (enter)   To truncate from the Full SQL server or SQL Express non command line interface, see Removing unwanted entries from an Alarm log, Access Event log, Error log, and Activity log automatically.

Issue Supplemental Documentation on the Menta OPT block for optimized start and stop. Product Line TAC Vista, EcoStruxure Building Operation Environment Menta Function Block Cause The document below is intended to clarify the inputs and configuration parameters of the Menta OPT block and when/how to use them. Resolution Click here to download the example Menta macro A Brief Overview of Optimized Control Optimal Start Optimal Start measures how long it takes a room temperature to reach setpoint each morning when the air-handling unit is enabled. These measurements are then used to predict how long it will take the next time. As time goes on, the predictive algorithm is refined until it becomes quite accurate. An optimally started unit saves energy by only starting as early as is needed, not just an arbitrary hour or two before occupancy. Optimal Stop Optimal Stop is less common. An optimally stopped unit stops running prior to the end of the day. It measures how long it takes before the measured room temperature drifts outside of an acceptable range around the setpoint. This saves energy on cooling a building until 5:00pm (for example) when the occupants are just about to walk out the door. The example in this document will not implement Optimal Stop. Inputs to the OPT Block RoT Room Temperature. If there is just one room temperature sensor being served by the optimally started unit, then this is where it would be used. However, if the unit has several room temperatures or serves many VAV terminal units, consider the following options: Average all temperatures Pick one interior zone Highest room temperature for cooling/lowest room temperature for heating Use return air temperature In all of these scenarios, some consideration should be made for if the input sensors fail: Averaging all temperatures is the most robust method. However, if SNVT inputs are used, it may be necessary to discard invalid values (621.8°F) from the averaging calculation. If one interior zone is used and the temperature sensor fails, the unit will eventually revert to starting as early as is allowed every day. The default value for this is 12 hours early; the example in this document uses 2 hours. If the primary sensor fails, use a secondary, or disable optimal start on a failed condition. Instead of the highest and lowest room temperatures, it may be wise to use the second highest and the second lowest room temperature. This allows for one failed sensor in each direction before the Optimal Start calculation is affected. Using return air theoretically is a lot like using the average of all room temperatures. Adjusting the setpoint to get the desired result might be required. A failed sensor input should disable the Optimal Start calculation. SP Setpoint. Using two OPT blocks – one for Optimal Start cooling, one for Optimal Start heating – allows each to be fine tuned. If there is a morning warm-up sequence, then the heating Optimal Start may be much quicker than the cooling. Using one block requires the internal calculation to adjust as the needs change from cooling to heating, and can be less agile when switching from cooling to heating requirements. OuT Outdoor Temperature. Resets to the curve occur based on the outside air temperature. If it is very cold or very hot outside, the unit will start sooner. This curve is reset automatically as time goes on to better predict the effect outside air temperature has on the controlled space (if AutoAdjust > 0). OpI Operation Indication. In the example of an air-handling unit, OpI would be the fan status. If the configuration parameter OperIndicF is set to 1, then this will be used for internal calculations. Otherwise, it will just use the command as status. This prevents a mechanically failed unit from affecting the calculation. A good rule to follow is if fan status is available, use it. TmL Time left. A time schedule (TSCH) input goes here. This tells the calculation how much time is left before the unit is scheduled to turn on (or off). The OPT block then starts the unit early based on this number. It also ensures that the unit always runs during the scheduled occupied time. Mode Mode is for heating/cooling or enabled/disabled. It is advantageous to always program in a method for disabling Optimal Start through a public variable (PVB). Many times the seeming complexity of Optimal Start is found to be undesirable by building operators and they will ask to have it disabled. Mode could be programmatically set for heating/cooling based on outside air temperature (or some other factor), but in the example in this document, two separate OPT blocks are used and are hard-coded for their respective modes. Configuration Parameters of the OPT Block AutoAdjust AutoAdjust refers to whether or not the OPT block gets smarter by adjusting the curves set initially on the first download. If AutoAdjust is set to 0, then the OPT block will still adjust the start time every day based on the room temperature and outside air temperature, but it will not adjust those early start times based on past experience. Set the AutoAdjust to 1, and the curves will adjust a little every day. Set AutoAdjust to 2 and the OPT block will also adjust the holiday compensation (the unit will start a little earlier after a 3-day weekend, but may need to learn exactly how much as time goes by). To maximize the potential of the OPT block, it is suggested to set this value to 2. RoomTempF Room Temperature Flag. Is a room temperature sensor present? Without a room temperature sensor, it is not possible for the OPT block to adjust its curves. It is guessing at that point based on pre-determined curves. It is not recommended to use OPT without a room temperature sensor. OperIndicF Operation Indication Flag. If OperIndicF is set to 1, then the OpI input will be used for internal calculations. Otherwise, the OpI input is ignored and the command is used as status. This prevents a mechanically failed unit from affecting the calculation. A good rule to follow is if fan status is available, use it. StartTimeLo Start Time at Low Outside Air Temperatures. When it is cold outside, how much earlier should the unit start? This will change between a cooling and a heating optimal start block. If AutoAdjust is set to 1 or 2 then this is just a default value. It will adjust as needed each day, but a good default value is important. StartTimeHi Start Time at High Outside Air Temperatures. When it is hot outside, how much earlier should the unit start? This will change between a cooling and a heating optimal start block. If AutoAdjust is set to 1 or 2 then this is just a default value. It will adjust it as needed each day, but a good default value is important. HolidayComp Holiday Compensation. This is the default compensation for a holiday (longer than 48 hours of continuous unoccupied time). The value is a percentage. If there is a 3-day weekend, how much earlier should the unit start on the following Tuesday? If AutoAdjust is set to 2 then this is just a default value. It will adjust it as needed each day, but a good default value is important. MaxStartTi Maximum Start Time. This is the maximum amount of hours the unit is permitted to start prior to the occupied time. The default value is 12 hours. The first time the unit is downloaded, it will start this early and measure how long it takes to achieve setpoint. 12 hours is very early. The example in this document uses 2 hours. Even if something goes wrong with the internal calculation (failed sensor input, for example) the earliest it could start would be 2 hours early. ETol Error Tolerance. How close to the desired setpoint does the temperature sensor need to be to be considered at setpoint? An error tolerance of 0.5°F is default and is usually acceptable. StopLoTemp, StopTimeLo, StopHiTemp, StopTimeHi, StopTimeErr All of these parameters refer to the Optimal Stop portion of the OPT block. Setting them to 0 disables the Optimal Stop functionality. Output of a OPT Block There are three possible output values of an OPT block: 0 = The unit is off, unoccupied 1 = The unit is on, occupied 2 = The unit is on, optimally started Putting It Into Practice The example below is a Menta Hierarchy Function Block (HFB) and shows HFB inputs to the blocks. The top OPT block is set to heat mode and looks to a heating setpoint. The bottom OPT block is set to cool mode and looks to a cooling setpoint.   OPT_START_HEAT OPT_START_COOL AutoAdjust 2 2 RoomTempF 1 1 OperIndicF 1 1 StartTimeLo 60 0 StartTimeHi 0 60 HolidayComp 0 0 MaxStartTi 2 2 Etol 0.5 0.5 StopLoTemp 0 0 StopTimeLo 0 0 StopHiTemp 0 0 StopTimeHi 0 0 StopTimeErr 0 0 Using the hints and tips suggested will allow not only for proper programming techniques, but also for creation of macro libraries that can be reused and shared to improve effectiveness across business units.

Issue Alarm code, configuration code passwords for DC1100 and DC1400 Product Line Field Devices Environment DC1100 controller DC1400 controller Cause Configuration Resolution Passwords are: 0112 for configuration mode 0402 for fast run mode

Issue Tooltip feature for TGML Graphics was hotfixed in Vista 5.0.3 (Hotfix 20) and was disabled later versions of TAC Vista based on customers requirement. Refer to TPA-MALI-08-0007.01 for more details Product Line TAC Vista Environment TAC Vista 5.0.3 and later versions. Cause By default, the tooltip feature in TGML Graphics was removed. Resolution To enable the Tooltip option in TGML graphics following these steps: The Tooltip snippet is available under Snippets > Basic Functions > Tooltip. If the editor does not have this snippet, download the attached Tooltip.zip snippet. Close all the TGML windows and Install the tooltip snippet Open the TGML editor and you can find the tooltip snippet under My Snippets Drag and drop the tooltip snippet on to the graphic objects window to see the tooltip feature. After drag and drop the tooltip snippet on to the graphic, the Metadata – TooltipContainer will be added to the object properties. Tooltip will now be available for this graphics Object. Repeat steps 4 and 5 for each other graphics Object.

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 After starting upgrade from Device Administrator AS hangs during initialization. Automation Server has a solid red status light. Unable to connect through Workstation. Product Line EcoStruxure Building Operation Environment Device Administrator Automation Server Cause Solid red LED indicates a critical error detected in the AS. It may be software or hardware related. Resolution Start Device Administrator and establish USB connection between PC and AS. Try to reinstall the firmware through the Device Administrator. If that does not work, put the unit into DFU mode: Quickly press the reset button on the AS three times in a row to place it in DFU mode. The AS will disappear from the Device Administrator and re-appear in DFU mode. Be patient to wait for this happens. Download new firmware, choose new Database. Once it goes online, restore a backup. If the LED returns back to a solid red state, this indicates a hardware failure. Contact Product Support for further assistance.

Issue The ability and procedure to identify the version of Sigma software on a system. Product Line Satchwell Sigma Environment Release number: 1, 2, 3, 3.1, 3.3, 3.4, 3.6, 3.7, 3.7 SP2, 3.7 SP3, 3.10, 3.11, 4.00, 4.00 SP2, 4.00 SP4, 4.01, 4.01 SP1, 4.01 SP3, 4.01 SP4, 4.01 SP4a, 4.01 SP5, 4.02, 4.03, 4.03 SP1, 4.04, 4.04 SP1, 4.04 SP2, 4.04 SP3, 4.05, 4.05 SP1, 4.05 SP2, 4.05 SEB, 4.06, 4.07, 4.07 SP1, 4.07 SP2, 4.08 Build number: 1.52, 2.13, 3.12, 3.17, 3.3, 3.31.1, 3.32.10, 3.33.9, 3.33.11, 3.33.13, 3.34.11, 3.34.11, 3.36.11, 3.36.16, 3.36.20, 3.37.08, 3.37.09, 3.37.12, 3.37.13, 3.37.16, 3.37.18, 3.39.09, 3.40.06, 3.40.09, 3.41.14, 3.41.15, 3.41.16, 3.41.18, 3.41.19, 3.42.34, 3.42.43, 3.42.48, 3.43.18, 3.44.14, 3.44.16, 3.44.18, 3 45 48, 3 45 51, 3 45 58, 3.46.57, 3.46.62, 3.46.70, 3.46.72, 3.46.73, 3.46.79, 3.46.80 3.46.81, 3.46.85, 3.46.86, 3.46.89, 3.46.98, 3.46.104, 3.46.105, 3.46.107, 3.46.108, 3.46.110, 3.46.111 Cause Software installed is identified with a build number and not a release number. Resolution To view the Sigma build number, using a Sigma client running locally on the Sigma server, select About System Manager from the Help menu. The displayed window shows the Sigma release and build number Refer to the table below to find the Release No. Sigma Release No. Build No. Software/Firmware File Date   SigmaX   Release 1 1.52 Software/Firmware 22.06.2001 SigmaX 4.5 Release 2 2.13 Software/Firmware 14.02.2002 SigmaX 5.2 Release 2 3.12 Supplement 14.02.2002 SigmaX 5.2 Release 3 3.12 Software 31.07.2002 SigmaX 5.2 Release 3.1 3.17 Software 17.09.2002 SigmaX 5.2 Release 3.3 3.3 Software 30.07.2003 SigmaX 5.2 Release 3.4 3.31.1 Software 03.10.2003 SigmaX 5.2 Release 3.6 3.32.10 Software 19.11.2003 SigmaX 5.2 Release 3.7 3.33.9 Software 22.12.2003 SigmaX 5.2 Release 3.7 SP2 3.33.11 Software 27.01.2004 SigmaX 5.2 Release 3.7 SP3 3.33.13 Software 19.02.2004 SigmaX 5.2 Release 3.10 3.34.11 Software 21.04.2004 SigmaX 5.2 Release 3.11 3.34.11 Supplement 31.08.2004 SigmaX 5.2 Release 4.00 3.36.11 Software 16.12.2005 SigmaX 6.0.1 Release 4.00 SP2 3.36.16 Software 02 03 2006 SigmaX 6.0.1 Release 4.00 SP4 3.36.20 Software 23.05.2006 SigmaX 6.0.1 Release 4.01 3.37.08 Software 07.09.2006 SigmaX 6.0.1 Release 4.01 SP1 3.37.09 Software 26 09 2006 SigmaX 6.0.1 Release 4.01 SP3 3.37.12 Software 20 10 2006 SigmaX 6.0.1 Release 4.01 SP4 3.37.13 Software 13 08 2006 SigmaX 6.0.1 Release 4.01 SP4a 3.37.16 Software 17 11 2006 SigmaX 6.0.1 Release 4.01 SP5 3.37.18 Software 05 01 2007 SigmaX 6.0.1 Release 4.02 3.39.09 Software 26 01 2007 SigmaX 6.0.1 Release 4.03 3.40.06 Software 06 06 2007 SigmaX 6.0.1 Release 4.03 Sp1 3.40.09 Software 09 08 2007 SigmaX 6.0.1 Release 4.04 3.41.14 Software 27.02.2008 SigmaX 6.0.1 Release 4.04 SP1 3.41.15 Software 09.05.2008 SigmaX 6.0.1 Release 4.04 SP2 3.41.16 Software 15 09 2008 SigmaX 6.0.1 Release 4.04 SP3 3.41.18 Software 08 01 2009 SigmaX 6.0.1 Release 4.04 SP4 3.41.19 Software 08 01 2009 SigmaX 6.0.1 Release 4.05 3.42.34 Software 06 11 2009 SigmaX 6.0.1 Release 4.05 SP1 3.42.43 Software 22 03 2010 SigmaX 6.0.2 Release 4.05 SP2 3.42.48 Software 26.08.2010 SigmaX 6.0.2 Release 4.05 SEB 3.43.18 Software 08 12 2010 SigmaX 6.0.2 Release 4.06 3.44.14 Software 01 12 2011 SigmaX 6.0.2 Release 4.06 SP1 3.44.16 Software 01 12 2011 SigmaX 6.0.2 Release 4.06 SP1 3.44.18 Hotfix 01 02 2012 SigmaX 6.0.2 Release 4.07 3 45 48 Software 20 08 2012 SigmaX 7.0.6 Release 4.07 SP1 3 45 51 Service Pack 09 12 2012 SigmaX 7.0.6 Release 4.07 SP2 3 45 58 Service Pack 20 12 2013 SigmaX 7.0.6 Release 4.08 3.46.57 Software 10 04 2014 SigmaX 7.0.7 Release 4.08 3.46.62 Hotfix 21.05.2014 SigmaX 7.0.7 Release 4.08 3.46.70 Hotfix 23 07 2014 SigmaX 7.0.7 Release 4.08 3.46.72 Hotfix 04 08 2014 SigmaX 7.0.7 Release 4.08 3.46.73 Hotfix 12 08 2014 SigmaX 7.0.7 Release 4.08 3.46.79 Hotfix 08 10 2014 SigmaX 7.0.7 Release 4.08 (**1) 3.46.80 Software 10 04 2014 SigmaX 7.0.7 Release 4.08 3.46.81 Hotfix 17 02 2015 SigmaX 7.0.7 Release 4.08 3.46.85 Hotfix 19 03 2015 SigmaX 7.0.7 Release 4.08 3.46.86 Hotfix 19 03 2015 SigmaX 7.0.7 Release 4.08 (**2) 3.46.89 Software 10 04 2014 SigmaX 7.0.7 Release 4.08 3.46.98 Hotfix 14 12 2016 SigmaX 7.0.7 Release 4.08 (**3) 3.46.104 Software 28 02 2017 SigmaX 7.0.9 Release 4.08 3.46.105 Hotfix 10 03 2017 SigmaX 7.0.9 Release 4.08 (**4) 3.46.106 Software 28 03 2017 SigmaX 7.0.9 Release 4.08 3.46.107 Hotfix 08 08 2017 SigmaX 7.0.9 Release 4.08 3.46.108 Hotfix 01 05 2018 SigmaX 7.0.9 Release 4.08 (**5) 3.46.110 Software 13 05 2019 SigmaX 7.0.9 Release 4.08 (**6) 3.46.111 Hotfix 15 11 2019 SigmaX 7.0.9 Release 4.08 (**7) 3.46.131 Software 29 01 2020 SigmaX 7.0.9 Notes:   **1 Sigma build 4.46.57 with StruxureWare Building Operation v1.5 or 1.6 transition support program installed. **2 Sigma build 4.46.57 with StruxureWare Building Operation v1.8 transition support program installed. **3 Sigma build 4.46.57 with StruxureWare Building Operation v1.9 transition support program installed. **4 Sigma build 3.46.57 with StruxureWare Building Operation v2.01 transition support program installed. **5 Sigma build 3.46.57 with StruxureWare Building Operation v3.0.1, v3.0.2 and v3.0.3 transition support program installed.. **6 Sigma build 3.46.57 with StruxureWare Building Operation v3.0.4, v3.1 and v3.2 transition support program installed. **7 Sigma build 3.46.57 with StruxureWare Building Operation v3.2 or later transition support program installed.   Notes: 1. SigmaX version 7.0.9 is now available and can be used on any Sigma version that supported SigmaX version 7.0.6. 2. This information can be downloaded as a PDF file: Sigma Build Numbers 2023 3. When SigmaX 6.0.2 is installed, the build information provided by Sigma (Help > About) can be wrong (later than the actual version). This arises because SigmaX installs a file with Build 3.42.47 in the c:\sigma\bin folder. This is only a problem prior to Sigma Release 4.05 SEB.

Issue How to add Web Service and create SOAP Web Service with Graphic Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with release 1.2 or later Cause What are Web Services and how to add to my existing StruxureWare Building Operation site. How to add SOAP Web Service files and how to add to a project or site How to create values from SOAP Web Service Files How to add values to graphic that uses the values from SOAP Web Service Resolution Wikipedia: A Web Service is a method of communication between two electronic devices over the web (internet). W3C: A "Web Service" as "a software system designed to support interoperable machine-to-machine interaction over a network." Web Services: are hardware, programming language, and operating system independent Applications written in different programming languages and running on different platforms can seamlessly exchange data over intranet or the internet using Web Services Web Service interfaces are supported in both the AS and ES(does not support connection over a ProxyServer) Like BACnet, Lon, and Modbus, you can create a Web Service interface. EWS Interface - EcoStruxure Web Services Script Web Service - Generic Consume via Script (Web Service addition Script Web Service) Simple XML Web Service - Rest Generic Consume via Binding Tool (Web Service addition Simple XML Web Service) SOAP Web Service - SOAP Generic Consume via Binding Tool This article explains adding Sunrise and Sunset for a particular location data using SOAP Web Service: Select New > Interface > Web Service > SOAP Web Service Next Paste the URL which has the SOAP Web Service feature ((to find sunset/sunrise for your area, Google WSDL data) and location coordinates Get Operations button pulls in the data. Select Next  which shows the values and times and then select Create Create values by highlighting SOAP Web Service then File > New > Value Choose Next and highlight the specific for the values then select Create Here are the SOAP Web Service sunrise/sunset values If desired, Bind those values to a graphic Lastly for SOAP Web Service a graphic is created and the values which come from the SOAP Web Service are place on the page

Issue Site looking to add some WorkStations with the ability to show Graphics but without the Graphic editor. Not sure which part number to order. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Cause Documentation Resolution V2 or higher, Enterprise Server or Enterprise Central license includes three concurrent client licenses (WebSation or WorkStation). For additional clients, order one or more of the licenses below. These licenses do not include any editors, the WorkStation will show the graphics but will not allow editing, order below part numbers:   If graphic or programming editing is required, you can order professional WorkStation license, which will add extra WorkStation with editors, or order Programming & Graphics Editor licensing, which will add editors to existing WorkStation Standard license.  

Issue Getting an Error 1001 near the end of the EcoStruxure WebReports Installation Reports not functional from WebReports Product Line EcoStruxure Building Operation Environment Web Reports SQL 2008 R2 Windows Server 2008 Windows Server 2012 Cause This error is caused when the WebReports installer is unable to reach SQL Server Reporting Services to configure the WebReports Interface Resolution After a failed install of WebReports you will need to follow the general workflow:   Clean of the Pieces of the failed install. Use the uninstall process listed in the WebReports Reference Guide or Uninstall Process for Web Reports. Correct all possible causes of the failed install Verify that you can connect to the ES using http from the Reports Server PC Verify that you can connect to http://localhost/Reports_SQLInstanceName  Re-install WebReports. NOTE: You may be able to correct the issue without having to remove and re-install WebReports. Possible Issue: The Microsoft Reporting Service SQL databases are not registered Check through SQL Management Studio that the 2 databases "ReportServer$instance" and "ReportServer$instanceTempDB" are registered. If not, the SBO Web Reports installed have nowhere to place the report pack files. If they are not there, you need to add them through "Reporting Services Configuration Manager". Click "Database" and then "Change Database". Here you can chose to create new databases. Possible Issue: Insufficient User Access Log out of Windows and Log back in using a PC admin account. The account logged in for the installation should have full access to Windows and be a DB admin in the SQL Server. Set the User Account Control Settings to Never notify. Possible Issue: PC Configured as a Domain Server In the Server Manager, check that the IIS Role is configured and that there are no Domain Roles assigned to this PC Possible Issue: Another Application is using a Required SQL function Uninstall any application which use SQL on this PC. (The Enterprise Server does not Use SQL) As a Best Practice, the Reports Server should be installed on its own, dedicated PC. Possible Issue: Incorrect Version of SQL Server or Windows Server Check the Reports Server Specification Sheet for your build and verify that you are on the Correct Version of Windows and SQL. Possible Issue: Secure Connection Level set too high This issue typically also results in not being able to log into http://localhost/Reports_SQLExpress. Log into the Reporting Agent Configuration Manager Application Click on the Report Manager URL on the left-hand column Click on the HTTP URL This will give you the correct URL for your installation of SQL If this fails, browse to C:\ProgramFiles\Microsoft SQL Server\MSRS10_50.SQLEXPRESS\Reporting Services\ReportServer (this may vary based on SQL Installation)   Modify the CONFIG file "rsreportserver" Change the Secure ConnectionLevel to "0" Save the file and attempt to log into http://localhost/Reports_SQLExpress again. For more details on this property see: http://technet.microsoft.com/en-us/library/aa179559(v=sql.80).aspx Possible Issue: .NET Framework is not operating correctly. Download the correct version of .NET framework for your version of EBO (The correct required version can be found on WebHelp Reports Server under EcoStruxure Building Operation Software Requirements) Run the installer in "Repair" mode Possible Issue: The Windows account "appuser" is not created because the default password does not meet password policy requirements Temporarily disable password policy on the server and try reinstalling. For clarification of the use of 'appuser', refer to the following article, Report Server "appuser" clarification 

Issue There is a need for a single Compatibility Matrix that shows EBO, PME, Energy Expert and relevant software versions all in the same location.   Product Line EcoStruxure Building Operation, Other   Environment EcoStruxure Energy Expert (formerly Power Manager) ETL tool Cause Energy Expert version compatibility information is currently available but is stored in many different places such as release notes and online documentation, rather than one single matrix.   Resolution The full ETL for EBO compatibility matrix is shown in the following table. Energy Expert  PME EBO ETL Integration Utility .NET Framework Power Manager 1.0 7.2.3 1.6.1 3 1.0.14304.2 4.5 Power Manager 1.1 8 1.6.1  1.7.1 4.1 1.0.15306.1 4.5 Power Manager 1.2 8.1 1.6.1  1.7.1  1.8.1 4.3 2.1.16081.1 4.6 Power Manager 1.3 8.2 1.8.1 1.9.x  4.6 2.2.17056.2 4.6 Energy expert 2.0 9 2 5 3.0.18215.3 4.6 Energy expert 3.0 2020 3.0 3.1 6 3.1.19319.1 4.6 Not commercialized  - (n/a) 2021 3.2.3 6 Integrated - (n/a) 4.8 Not commercialised - (n/a) 2022 4.0.2/2022 6 Integrated - (n/a) 4.8 Not commercialised - (n/a) 2023 5.0/2023 6 Integrated - (n/a) 4.8   Great care must be taken when choosing the correct version of ETL to use when integrating Energy Expert and EBO, as there are actually two families of ETL in production.  One ETL designed and tested for PME use only and ETL for EBO designed and tested with an EBO Extract Task specifically for integrating the two systems.  (For example, a version of ETL 4.7 exists, but this is not ETL for EBO and therefore does NOT contain an EBO Extract Task, even though it is a valid version of ETL for the Power Community) New PME 2023 now offers EWS Client 1.2 which can be used to transfer data from EBO to PME instead of ETL.  The merits for and against using this new EWS Client rather than ETL are discussed at length in the PME 2023 System Guide

Issue What is enabled on a Continuum Security Key? Product Line Andover Continuum Environment Continuum Security Key Cause There's a need to know what version of Continuum is enabled on the key. Resolution Note: The Excel method for viewing enabled key features mentioned below no longer works with Windows10 or greater and because of CyberSecurity issues ActiveX controls have been deprecated by Microsoft in favor of more secure web technologies.  This feature will not be updated for Cyberstation.   The supported version of the keys and what options are available on the key can be verified by doing the following using Microsoft Excel on a Workstation with Continuum and the key installed: Open MS Excel Select Insert> Object Select SecurityKeyreader Control and then Ok You will see an object inserted into the spreadsheet with a list of products on the left and options on the right. Example: Serial Number 1016019 Options Number of Points -1 Adv.WebServerEnable Number of Personnel -1 EpiSuiteEnabled Platform Lan(Multi) OPTxtLoggingEnabled Type Prog.Intg. PESourceCntlEnabled Max Version 1.79 Global 1 0 Global 2 0 Global 3 0 Global 4 0 Windows 7 64 bit will not support the MMC.exe option (mentioned below)   Use the command       mmc.exe /32     This will allow the ActiveX snap-in to be added and will work on a 64 bit PC   ActiveX controls in Excel 32 bit are not exposed by default. Use the following Excel spreadsheet (zipped) to read the security key instead. (Excel must be installed and must be on a 32 bit PC(64 bit shows this as blank) Security Key Reader Excel File You may be prompted to enable the ActiveX control Excel 2003 - The application is about to initialize ActiveX controls that might be unsafe. If you trust this document, select Yes and the control will be initialized. Excel 2007/2010 - Notice the Security Warning below the Toolbar                                   Click options                                   Select Enable this content Upgrading a key requires a call to repair (978-975-9464) for a cookie to update the key. In order to install the cookie, you must use the program, CyberKeyWriter2.exe to enter the new key which is on every Cyber CD in the Continuum\bin folder.    Note: Also see Accessing Continuum Security Key information using MMC instead of Excel that describes another method to see this information using MMC. This feature does not work with newer versions of Windows 10

Issue The Drayton Theta YBM2 Valve Body / Actuator assembly is to be replaced. Environment Replacement Drayton Actuator Valve YBM2 Cause The Drayton Theta YBM2 Valve Body / Actuator assembly is obsolete. Resolution OVERVIEW The Drayton Theta YBM2 Valve Body / Actuator assembly is obsolete, and there is no purpose built replacement. The Valve Body was available in 1.1/4", 1.1/2" and 2" B.S.P. sizes and was normally installed as a mixing valve in variable temperature, constant volume, compensated heating circuits. No Valve Body / Actuator assemblies are currently available in these sizes. Details of the YB Valve Body may be viewed here.   VALVE BODY REPLACEMENT To replace the YBM2 Valve Body the following is required:- S-E Satchwell MB Valve Body of appropriate size - MB1552 (1.1/4"), MB1602 (1.1/2"), MB1652 (2") Details of the MB Valve Body may be viewed here.   ACTUATOR REPLACEMENT The YBM2 Actuator comprised a 3-wire electrical connection enabling it to be operated by a Mains Voltage changeover contact device as follows :-  Terminal M1 – Open signal Terminal M2 – Close signal Terminal M3 – Common  The YBM2 Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-230 MD20B-230 (if MD10B-230 not available) Details of the MD10B-230 Actuator may be viewed here. Details of the MD20B-230 Actuator may be viewed here.   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here In such 3-wire installations the YBM2 Valve / Actuator assembly only will need to be replaced, while any associated Controller and Sensors may be retained.