Building Automation Knowledge Base

Issue Controller Error Logs - How to gather Continuum Controller error logs if requested by Product Support for troubleshooting. Product Line Andover Continuum Environment BCX CX  CMX 9680 9900 i2 b3 9702 Controller Error Log Gerry Log Cause Troubleshooting controllers often time requires obtaining an error log from the controller Resolution The controller error logs contain useful diagnostic information when it is necessary to troubleshoot a controller or system problem. Much of what is logged are normal system operations that may assist an engineer in diagnosing a problem in the field. To get the error logs from various controllers follow the procedures below: NetControllers - 99xx  Dumb terminal in using HyperTerminal Sign into the NetController Press V then E and press Enter over the NetController you are attached to Press F2 Hit Alt + Print screen and paste into a Word doc Arrow down to single space or Ctrl+D to page down Hit Alt + Print screen and paste into a Word doc Repeat this process until you are at the end of the errors (up to 200) F4 Exits the error log See the CX Controllers Programmer’s Guide for all terminal keystrokes Email the file to Product Support Services   BCX/i2/B3 Controllers CX9680/ACX5720/ACX5740/9702 Controllers Note: You can not retrieve errors from NetController I (CX9900) using this tool Controller Error Log Tool Navigate to C:\Program Files\Continuum Double click on ControllerErrorLogTool.exe to open (This will do an install the first time) Note: The ErrorLogTool.exe is an older version of this utility and will work, but gives less information and does not contain the error lookup feature. Enter in the BCX or master CX IP Transport type = UDP or TCP depending on controller configuration CX Enode ID = AccNetId from the main CX editor Select Continuum in the Mode area, top right If the controller is a field device then enter the following: CX infinet port = Select the one you want to report on Infinet Node ID = port number of the i2 device you want the error log out of Once all the above required entries have been made: Click Get Log and the page will populate with any errors Once this runs, select SaveAs and name the file Email the file to Product Support Services Suppliment - To gather error logs from Continuum controllers transisioned to StuxureWare please see How to pull the error log from a b3 or Infinet controller in SmartStruxure.

Issue Scenario 1 Attempting to log in to Web Client you are presented with an error message "Error - SOAP connection failed". SOAP-ERROR: Parsing Schema: can't import schema from   Scenario 2 Upon successfully logging in to Web Client you are presented with "Thank you for logging in" and then immediately presented with another message saying "Log out successful".   This continues in a circuit until it may allow you in but displays a partially populated page with no data showing. Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Web Client   Cause The option "Use HTTPS to communicate with SOAP service" was enabled in the Web Client Installation Wizard and antivirus was dropping the connection because of this.   Resolution Uninstall and re-install Web Client without the  "Use HTTPS to communicate with SOAP service" enabled or Browse to the soap.connect.php located at C:\inetpub\wwwroot\SecurityExpertWebClient\include. Edit it using e.g. Notepad and change HTTPS to HTTP and change the port to 8030 so the Web Client uses HTTP to communicate with the SOAP service.

Issue PT1000 temperature sensors RTD Input Product Line EcoStruxure Building Operation Environment AS Classic, ASP  UI16, RTD-DI-16 - Central IO Module ASB, RPC, MPC Need for temperature to be extremely accurate PT1000 platinum resistance thermometer, RTD Resistance Temperature Detector Cause The AS Central IO Module Universal Inputs (UI16) were designed to interface to various thermistors that can have resistance values that are usually much higher than 1000 ohms. They were not designed to interface directly to a PT1000 RTD, and will not provide good accuracy when measuring these lower resistance sensors. The resistance input type was intended to allow for measuring the position of a 10K potentiometer that is used on some wall sensors. The accuracy specification for a resistance input is: +/-(7+0.004*R) ohms. This would result in an error of +/-11 ohms at 1000ohms – therefore a temperature measurement error approaching +/-3.0C. Resolution AS, ASP For RTD PT1000 (Pt100, Pt1000, Ni1000, LG-Ni1000, JCI-Ni1000) use RTD-DI-16 - Central IO Module, then choose 2 or 3 wire RTD Temperature Input ASB Choose 2-wire RTD Temperature Input (Pt1000, Ni1000, LG-Ni1000, JCI-Ni1000) RPC, MPC, MPV Choose RTD Temperature Input (Pt1000, Ni1000, LG-Ni1000)   For more details see SpaceLogic Hardware Reference Guide

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 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 In the LON Flow Balance program the k-factor calculated by the balance process can be displayed at the end of the procedure.  I cannot determine how to read it in the BACnet Flow Balance program.  The value is needed so that the application file can be updated so that if the controller needs to be re-downloaded, it will not need to be balanced again. Environment BACnet  MNB-V1 or MNB-V2 controller WorkPlace Tech Tool software release 5.7.2 or newer  (Optional, for backup) Cause The BACnet Flow Balance process uses a procedure that results in a more accurate flow calibration process. As a result of this process the rate box flow value does not get re-calculated during the balance process. Resolution The BACnet MNB-V1 & MNB-V2 controllers do not rely on a calibration constant (k-factor) stored in the application.  The Flow Balance calibration data is stored separately from the application data so that a revised application file can be downloaded to a controller without losing any of the recorded air balance calibration data.  The Flow Balance data is also saved as part of the file produced by the controller backup function of the Workplace Commissioning Tool.  Refer to the WorkPlace Tech Tool 5.7.2 release notes for more information. The Flow Balance calibration data can be displayed after balancing the BACnet MNB-V1 or MNB-V2 controller by clicking on "Balance Data" in the menu on the left side of the Flow Balance screen.  The Flow Balance Data screen shows the data entered and produced as a result of the flow balance process.  Refer to the figure "Flow Balance Reporting -- Flow Balance Details" in the Air Balancing chapter (Chapter 5) of the "MicroNet BACnet Commissioning Tool / Flow Balance Users Guide", F-27358 for more details.  In addition to being able to manually display the balance data for a single controller, both the BACnet Flow Balance program and the WorkPlace Commissioning tool can generate a flow balance for any or all of the BACnet VAV controllers on the jobsite. Refer to the section "Flow Balance Reporting" in the Air Balancing chapter (Chapter 5) of the "MicroNet BACnet Commissioning Tool / Flow Balance Users Guide", F-27358 for more details.  The resulting report is automatically saved when it is generated and the HTML version can be displayed / printed without the need to reopen it in the BACnet Flow Balance program. In addition to being able to manually re-enter the balance data into a replaced controller, Release 5.7.2 of the WorkPlace Tech Tool software introduced a software function that allows the complete application including COV subscription data and flow balance calibration data to be backed up.  Should it be necessary to replace a controller, the WorkPlace Commissioning Tool can be used to restore the backup into the new controller.  Refer to the "WorkPlace Tech Commissioning Tool Backup and Restore feature" section on page 10 of the release notes (F-27526-3) for more information.  The release notes are available here.

Issue When troubleshooting server issues, it can be helpful to look at the logs that are recorded within the Enterprise Server or Enterprise Central Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Cause Within the Enterprise Server and Enterprise Central logs are many records that are logged as a part of normal operations and unexpected events. Resolution Collect ES and EC Logs via EBO Workstation: Refer to the Workstation section of KB article: Collect logs from an Automation Server Collect ES and EC Logs via Windows Explorer, especially if ES or EC will not run as a service or keep crashing: The ES or EC database path is listed in Software Administrator.   For Windows 7, Server 2008, or higher, the default paths for the logs folder are: Enterprise Server: C:\ProgramData\Schneider Electric [EcoStruxure|StruxureWare]\Building Operation [n.n]\Enterprise Server\db\logs Enterprise Central: C:\ProgramData\Schneider Electric EcoStruxure\Building Operation [n.n]\Enterprise Central\db\logs In EBO V3.2 or higher, shortcut buttons can be found in Software Administrator to go to the folder for logs and database directly.    By default, the "Program Data" folder is hidden, so Windows needs to be configured to view hidden files and folders. For Windows 10 or 11, open Windows Explorer and select View > Show > Hidden items. For other Windows versions, please refer to this Microsoft help article: Show hidden files (microsoft.com). Using Windows Explorer, Navigate to the ES or EC logs folder to find System and Trace logs. Copy the Logs folder contents and send them to Product Support as a compressed file if required. To open a log file, Right-click on one of the logs and select Open with... Expand the window and select WordPad. For Windows XP:   Other ways to review site-specific issues: Is the issue site-specific regarding workstation being used or applications/programs running on these machines? Always try to keep the programs on a workstation to a minimum. Review the Windows Event Logs. What specifically happens when an error occurs? Follow this KB article to view and save the Windows Events: Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes - Communities Make sure that PCs and Windows OS used for WorkStation, ES or EC meet the requirements mentioned in Information Technology System Planning Guide (se.com) Make sure that the firewall and antivirus are correctly configured, and required ports are open for EBO, as explained in Information Technology System Planning Guide (se.com) Make sure that the current installed EBO version is supported, as per the Software Support Policy for EcoStruxure Building Operation - PA-00300. Check if Microsoft currently supports the installed Windows OS: Lifecycle FAQ - Windows | Microsoft Docs

Issue How to associate BACnet IO points created under the BACnet Interface of the Automation Server with IO points on the Automation Server's IO bus. Product Line EcoStruxure Building Operation Environment Building Operation Servers 1.4 and above Building Operation Workstation Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Connect physical IO points to BACnet network controllers. Resolution BACnet Association Tool (EBO V3.0 or higher) BACnet Association Tool will map properties of a central IO point with corresponding properties of a BACnet point. The tool is capable of mapping a single IO point with a single BACnet point, optionally by also creating a BACnet point, and removing the association between IO and BACnet points. To open the BACnet Association Tool, Select the IO Bus or IO Module, BACnet Interface, Application Folder, or the BACnet point, then in the Actions menu, click BACnet Association Tool. Most useful is the ability to associate multiple IO points with their corresponding BACnet points in one operation. The tool can be run from a variety of different container types in the WorkStation Tree view, including an IO point, BACnet Point, CIO Module, or the entire IO Bus (as shown below). For more information refer to WebHelp articles: Creating and Associating BACnet Points to I/O Points (se.com) and Associating or Updating BACnet Point Associations to I/O Points (se.com) NOTE: Please be aware applying the BACnet Association Tool retrospectively, to an already configured site, can remove bindings to outputs.  For example output bindings in Script or Function Block programs.  As shown below, if the tool is used to create a BACnet Associated point for an output already bound to a program (1) the Requested Value will be replaced by the Associated Value of the BACnet point (2). This is due to how the BACnet Association Tool uses the bindings, where the newly created BACnet point should be used instead of the IO point.  The solution is to update the removed program binding (3) to use the BACnet Associated point value (4).   SBO 1.4 to 2.x To associate BACnet IO points created under the BACnet Interface of the Automation Server to points in the IO Bus in SBO 1.4 and above... The association is made via a read reference, so if we think of the two objects as one being the source and the other the destination you configure the association from the destination object so in the case of an output you configure the association from the BACnet object (in this example BO1). In the case of an input, you'd configure the association from the IO Bus input as that would be the destination object, in other words, the recipient of the value. (NOTE: for versions prior to 1.4 see Bacnet and StruxureWare Building Operation Central IO points) Create the points. In this example, we are associating an IO output point named 'Digital Output 1' with a BACnet Binary Output named BO1. From the properties page of the IO Bus point (Digital Output 1 in this example) click on the gear icon to the right of the 'Requested value' field. In the 'Requested value' editor click the navigation icon (...) to the right of the 'Reference' field and navigate to the 'Associated Value' of the BACnet point. Save the configuration changes. Now that the values have been associated setting the BACnet output value (BO1) will drive the IO Bus output (Digital Output 1)  

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.

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 Need to backup or share the project with another user. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT)  Cause One way of sharing a project is to move it and another way is to Export the project. Resolution Move the project Stop all servers in each project and stop all projects. Close PCT application. Copy the “projects” folder from the PCT storage location and paste it to another storage location (suggested by WebHelp topic Move a Project) OR backup all servers through Workstation. Default PCT Project Folder Locations Versions prior to PCT 1.2 C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\storagemodule\projects PCT 1.2 or higher C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\storagemodule\projects Default PCT Template Folder Locations Versions prior to PCT 1.2 C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\templates PCT 1.2 or higher C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\templates   Export the project In Project Configuration Tool, in the Project view, select the project you want to export. On the Header toolbar, click the Export project button or right-click on the project and select "Export". On the Export selected project(s) dialog box, in the Folder box, browse to the folder on your hard drive where you want to save the exported project. Click OK. TIP: You can select multiple projects and export all of them at once. Note: In order to be more future proof, there is a new export/import format of PCT projects starting in PCT v1.3.2 with exports having an extension of '.pct_export'.  Projects exported at an earlier version have an extension of '.ppb' and they must be converted to '.pct_export' files before import into PCT v1.3.2.    Please refer to point 2.1 in the release notes.   Also prior to PCT v1.3.2 the project had to be stopped before export was possible.  In PCT v1.3.2 the project has to be running before it can be exported.    

Issue Does the entire SBO system need to be upgraded to 1.5.0.171xx, 1.6.2.12xxx or 1.7.2.111xx before upgrading to 1.9.1 if the network includes LON devices? Can SBO be upgraded directly to 1.9.1 from 1.5.X, 1.6.X or 1.7.X? Product Line EcoStruxure Building Operation Environment SBO Workstation 1.5.0/1.6.1/1.7.1 SBO ES 1.5.0/1.6.1/1.7.1 SBO AS 1.5.0/1.6.1/1.7.1 SBO AS-P 1.7.1 Cause In systems that have SBO servers that already are hosting LON devices based on LonWorks imported device templates (.XIF) or resource kits (.DRF), the servers need to be prepared before an upgrade from versions 1.5/1.6/1.7 to version 1.9.1. Even servers where device templates (.XIF) or resource kits (.DRF) are just imported, and no devices or network variables are created yet, the servers have to be prepared before the upgrade. Resolution Please see section 9.2.3 of SBO 1.9.1 Release Notes. Although it says "Steps to upgrade a 1.6.2/1.7.2 multi-server system" you don't have to upgrade the AS or ES etc, even if they run 1.6.1/1.7.1, it's only SBO Workstation that need to be hotfixed. Links to the different Workstation hotfixes can be found Server with LonWorks devices - TPA-SBO-17-0002.00 - Links to hot fixes. If there are no LON devices in the system, you may upgrade directly to 1.9.1 from 1.5.X/1.6.X/1.7.X

Issue Need to upgrade sites with Report Server to EBO 2022 or higher. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Report Server Building Operation Timescale Database Cause WebReports/Report Server isn’t supported in EBO 2022 (V4.0) or higher. Resolution Since WebReports/Report Server isn’t supported in EBO 2022 (V4.0) or higher, there is a Data Migration Assistant (DMA) tool available which read data from a WebReports 3.x and write it to External Log Storage. You use External Log Storage feature to store historical data from EcoStruxure BMS. The amount of stored data is limited only by the equipment you use, and not by the capacities of the feature.  When the External Log Storage feature is activated and configured, WorkStation and WebStation display the historical data in the event and trend views from the External Log Storage. Any server in the system can be configured to write historical data to the TimescaleDB database.   Data Migration Assistant (DMA) Tool can be downloaded from here. License required: External Log Storage requires license, refer to Software and Features that Require Licenses and Part Number Summary and Hardware Software Matrix  Hardware and Software requirement for External Log Storage: Ensure that the hardware and software requirements for TimescaleDB (www.timescale.com) and PostgreSQL (www.postgresql.org) are met. High-performance SSD storage is required and additional CPU/RAM capacity is required for larger EcoStruxure BMSs. As an example, at least 64 GB of RAM is recommended for systems with 100 EcoStruxure BMS servers. Refer to: Information Technology System Planning Guide (se.com) Merging Log data: External Log Storage decreases the amount of extended trend logs retained on the EcoStruxure BMS servers. You can merge log data from an extended trend log to the source log in External Log Storage. For more information, see Merging of Trend Log Data. Enhanced Reporting (XLSX Report Templates): The EcoStruxure BMS servers (3.2 or higher) provide built-in functionality for basic reporting that can deliver reports in any text format and XLSX, without any dependencies to other external software. Reports for XLSX can be enriched by using advanced functionality such as formulas, conditional formatting, charts and sparklines. If External Log Storage is configured and connected (PostgreSQL/TimescaleDB), then historical report data can be fetched from there. Refer to: Examples for the new native EBO Notification Reports - Communities (se.com)  

Issue Should automatic updates be turned on for Continuum workstation? Are there certain known issues of updates that have caused problems with Continuum or Webclient? Product Line Andover Continuum Environment Continuum Cyberstation Continuum webClient Server Windows 10 Windows XP  Windows Vista Windows Server 2003 Windows Server 2008 Cause Microsoft Windows has an automatic update feature and frequently releases updates which can potentially affect Cyberstation and Webclient Server. Resolution Automatic updates should not be turned on for a Continuum or Webclient workstation. The Continuum compatibility matrix indicates Windows Operating Systems, Windows Service packs, SQL Server, .Net and Internet Explorer versions that were tested by Quality Assurance at the time of product release. Continuum Quality Assurance does not perform regression testing where new Microsoft updates are tested with Continuum products released in the past. Product Support recommends setting Windows updates to one of the other two options to allow for testing of Microsoft updates: Additional details can be found at: http://support.microsoft.com/kb/306525 Download updates for me, but let me choose when to install them Notify me but don't automatically download or install them   There are several specific updates that have caused issues with Cyberstation or Webclient. This is not a comprehensive list. Occasionally updates will break certain features and we discover this from our internal testing or from reports from partners or branches. Here is a list of some updates that have caused issues. KB835732-  Pinpoint 1.52 crashes when installed on a machine and you are accessing graphics from a network share. If you remove the hotfix the problem goes away.  This is the same hotfix that caused the SmartHeap out of Memory errors that was fixed with SP5 for 1.6.  KB828741- IIS (Webclient) machines without this patch may receive “Unable to establish a link to the remote Infinity services” Webclient 1.73 - Any patches that will install .Net Framework 2.0 will cause problems with webclient 1.73 since we don’t start using .Net 2.0 until webclient 1.74. KB911280 - this update blocks the acc.scp script from setting controller to PPP mode. This will a cause a Cyberstation using RAS controllers to not allow a connection. It will authenticate, but not connect. KB928366 – Webclient machines that use .Net 1.1(Listed on the compatibility matrix) will receive the error "Could not connect to server cause; type missing for member of type object _context id'. Could not create acwppserverproxy."  when opening web pinpoint graphics.  Remove this hotfix or upgrade to webclient 1.74 or greater. KB929969 – this hotfix does not require a reboot by Microsoft, but can cause the Cyberstation install to fail, if the install is performed before rebooting after the installation of the hotfix. See the Technical bulletin. KB968749 - SQL Express install fails on XML6 SP2 See SQL Express install fails on MSXML 6.

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.   

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 [Invalid Address] Product Line TAC Vista Environment Vista Workstation Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Invalidate Resolved Addresses Cause If you view a controller in Vista Workstation and point values read [Invalid Address] instead of showing values, there are a number of troubleshooting techniques to rectify this. Unfortunately, [Invalid Address] is a bit of a "catch-all" error code. Since it can be difficult to determine the cause of the error, these troubleshooting suggestions will have varying degrees of success. The best course of action is to try each of these methods in the order of least to most disruptive. As new techniques and procedures are discovered, they will be documented here. Resolution Check the label for N/P Designation If a programmable controller has read [Invalid Address] on every point since it was installed (it has never worked properly) then there is a chance that this is not a Network Presentation controller. These are referred to as stand-alone controllers and each of the 280 and 300 series have a non-network presentation variety. Check the label on the controller to make sure it says "302/N/P" or "282/N/P." If it just says "302" or "282" then this controller cannot communicate on a network and will never report values to a front end. Also see Xenta 280 or 300 Controllers without /N/P (networking and presentation) designation cannot communicate in a Network. In the Vista Workstation Right-click on the controller and choose Advanced Operations > Invalidate Resolved Addresses Proceed? Select Yes. Right-click on the controller and choose Advanced Operations > Read Address Proceed? Select Yes. Wait up to about 30 seconds for the values to populate. Download the Controller In the System Plug-in, Download Applications and Parameters to the controller Recommission the controller In the System Plug-in, TAC Network > Commence Communication (skip to this step for LON controllers) You may want to follow this action with another attempt at the steps outlined in the section above "In the Vista Workstation" Repair or recommission the Routers in the NL220 or Lonmaker database repair or recommission the Routers. Re-Do Group Bindings & Commence Communication: In the System Plug-in, LNS network > Create Group Bindings In the System Pug-In right click on the TAC Network and commence communication Re-doing group bindings ensures that the LNS network interface, and LON to IP routers receive message can 0 for the main xenta address broadcast in the network. Monitor Sets If your monitor sets have become corrupted, then every controller you download from that point on will say [Invalid Address] on every point. Monitor sets are actually stored on the hard drive of the PC, not in the LNS database. If you have made backups and passed them back and forth between PCs, as you often do during the commissioning phase, this invites corruption of monitor sets. There were some known issues with monitor sets in LNS version 3.24 that have since been corrected in LNS version 3.26. This can be downloaded from Echelon's website in LNS Server/Turbo Edition Service Pack 7. Go to http://www.echelon.com Navigate to Support > Support Resources > Downloads Log in with a user name and password. If this is the first time logging in, register for a free user name and password. Search for software in the Recommended Downloads category Find LNS Server/Turbo Edition Service Pack 7 (this is the latest at the time of this article, a newer one may exist and should be downloaded) Prior to restoring a backup, you may want to resynchronize the drawing making sure to check the option for "Sync monitor sets between drawing and database." Usually restoring the last good backup will fix up the monitor sets. If you do not have a recent backup, there are a couple of procedures that may help resolve the corrupted monitor sets issue.   Note: Viewing and altering monitor sets is only available in Echelon LonMaker. There is no analogous menu item in Newron's NL220. Do not download any more controllers. Check your monitor sets in LonMaker by navigating to LonMaker > Network Service Devices Click on the NSS which should have the same name as the network Select the Monitor Sets button If you get "Monitor set cannot be found. (Subsystem: NS, #160)" then your monitor sets are corrupt. Close down Vista Server & LonMaker (if you don't you will get an error when you try to validate that says "The Network Interface, database directory, or NSS type, conflicts with the already active network. (Subsystem: NS, #149)") Navigate to Start > Programs > Echelon LNS Utilities > LNS Database Validator Navigate to the LNS Network to Validate Check the Repair Database checkbox Hit the Validate button If that does not find and repair the monitor sets, the following steps may help. Make backup of the LNS database. Start LonMaker. Do not start Vista Server. Go to the monitor sets (LonMaker > Network Service Devices > NSS > Monitor Sets) and right-click and delete the monitor sets Run the System Plug-in and create a brand new Vista database in a different location than your current database. Stop the Vista Server and start it again Check the monitor sets again, they should be right now Stop the server again and change back to your original Vista database Non-Latin Characters If you use a signal name or description in the XBuilder Device Editor with non-Latin characters (like Swedish åäöÅÄÖ) you will get [Invalid Address] when you view the signal in Vista. Value pages are displayed correctly. Do not use non-Latin characters for signal name or description. This issue has been confirmed in versions 5.1.2 - 5.1.4, and will be fixed in a future release. Classic Networks View the Address Tab under the controller's properties in Vista Workstation Check Address Table slots 0 and 1. If the "Domain Index" and "Member or Node" have been manually altered, set them back to 0. An applicationless controller will display [Invalid Address] in a classic network, whereas in an LNS network, it would simply fail to commission due to its applicationless state.  Direct download the controller through the Menta serial cable to see if it resolves the error. Xenta 700 Menta values See Xenta 700 Menta Object Values report [Invalid Address] in Workstation, Read operation failed. Delete, Destroy, Redo This is your last resort. If you have tried everything else possible, it is time to remove this controller from the database and start from scratch. The exact steps and methodologies may change based on your network and controllers, but basically you need to remove any mention of this controller and add it back in as though it were a brand new device. Decommission the controller Delete the device Delete the device template In the System Plug-in, remove the device from the TAC Network Update the Vista Database Create a new controller Browse in a Menta file Update Vista and download

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 Active sensors that have a 0-10V output can not be directly connected to a controller with a 0-5V input, what resistors and settings are required? Product Line Andover Continuum Environment All i2 and b3 controllers with 5V inputs, not applicable to the controllers with a 10V input i.e. the i2/b3920 & 810 which directly support the 0-10V sensors I/O Module UI8-10 XP Modules xPUI4, xPBD4, xPBA4.   Cause There is a requirement to calculate the appropriate potential divider resistor values and the settings for the upper and lower voltage in the input point configuration Resolution Download the Voltage Inputs LSM document, this document details the value of the 2 resistors to use in the circuit and the upper and lower voltage settings to enter in the Auto Conversion box in the input point, these will correspond to the sensor reading at 0V & 10V. For controllers that allow the pull up resistor to be switched out, ensure that it is in circuit for these setting to work correctly.

Issue Satchwell CD2201 Compensator Controller–Actuator requires replacement. Environment Stand alone discreet Satchwell CD2201 Compensator Controller–Actuator Cause Obsolescence of Satchwell CD2201 Compensator Controller–Actuator Resolution Replace Satchwell CD2201 Compensator Controller–Actuator with Schneider Electric Satchwell CSC Compensator Controller, compatible Temperature Sensors and MD Series Actuator and Linkage Kit. Replace Satchwell CD2201 Compensator Controller–Actuator with Schneider Electric Satchwell CSC Compensator Controller. N.B. Two models of the Schneider Electric Satchwell CSC Compensator Controller are available :- CSC 5252 Compensator Controller without Time Clock CSC 5352 Compensator Controller with integral Time Clock  Details of the Schneider Electric Satchwell CSC Compensator Controllers may be viewed here. It should be noted however that the CD2201 Compensator Controller–Actuator had no integral Time Clock. Replacement of Air Temperature Sensors It should be noted that the existing Satchwell Outside Air Temperature Sensor associated with the CD2201 Compensator Controller–Actuator is obsolete and should be replaced. Similarly, it should be noted that the existing Satchwell Inside Air Temperature Sensor associated with the CD2201 Compensator Controller–Actuator is obsolete and should be replaced. Details of replacement Schneider Electric STO600 Outside Air Temperature Sensor may be viewed here. Details of replacement Schneider Electric STR600 series Inside Air Temperature Sensor may be viewed here. N.B. It should be noted that the CSC Compensator Controller will perform entirely satisfactorily without the connection of an Inside Air Temperature Sensor. Replacement of Water Temperature Sensor. It should be noted that the existing integral Satchwell Water Temperature Sensor associated with the CD2201 Compensator Controller – Actuator cannot be re-used and should therefore be replaced. In order to minimise mechanical work it is suggested that a Surface Mounting Temperature Sensor is installed on the pipework, rather than an Immersion Temperature Sensor installed in a Pocket in the pipework. Details of replacement Schneider Electric STC600 Surface Temperature Sensor may be viewed here. Replacement of Actuator. Whilst the existing Satchwell MB Valve Body may be retained, a new Schneider Electric Actuator and Linkage Kit will need to be installed on the MB Valve Body in order to permit control from the CSC Compensator Controller. Details of the Schneider Electric MD10B Actuator may be viewed here. Details of the Schneider Electric LMD/AR-MB Linkage Kit may be viewed here. Please be aware: since July 2016 the CSC compensator and other descrete controllers were withdrawn from service. To see "PA-00479 - Discrete Controllers - Notice of Withdrawal - Satchwell" click here.