Building Automation Knowledge Base

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 Locating and downloading latest images Product Line Satchwell Sigma Environment 3.46.57 3.46.66 3.46.80 3.46.89 3.46.100 3.46.104 3.46.105 3.46.106 3.46.107 3.46.108 3.46.110 3.46.111 3.46.131 Cause Identifying the correct image version for different hardware versions. Resolution Sigma UNC/ (V53) = Firmware 6b Sigma Firmware UNC596 6.b - Release note   Sigma UNC3 (ARM7) = firmware build 1.p.0 Sigma Firmware 1.p.0 UNC3 - Release note   UNC 532 V25 = Firmware 6b Sigma Firmware UNC532 6.b - Release Note   IC-Modbus = Firmware V5h IC-Modbus v5h Release Note   IC3 Modbus = Firmware1.n.2 IC3 Modbus - Release Note   IC SNP = Firmware 5d IC-SNP Integration Controller v5d for Sigma Rel 3 - Release Note   IC3 SNP = Firmware 1.g.1 Sigma 4.05 Firmware Supplement - Release Note (there is no release note specific to SNP Firmware 1g.1).   IC York = Firmware V3e - Not available to download. IC-York Integration Controller v3e for Sigma - Release Note   IC3 York = Firmware 1.d.0 IC3 York = Firmware 1.d.0 – Release Note   Sigma IC3 Unifact 1.d.0 – Firmware Sigma IC3 Unifact (RTC) - Release Note Sigma IC3 Unifact pro 5h – Firmware Sigma IC3 Unifact pro 5h - Release Note  

Issue ENC / JACE is licensed for MS but gets error "Unlicensed: javax.baja.license.FeatureNotLicensedException:" when attempting to access the MS Network property sheet. Environment I/A Series G3, ENC-520 or JACE-645 with TAC-LLC license installed. Cause When displaying the I/A Series G3 Platform details via the Platform Administration screen in the Workbench, the display shows the following for licensing: Licenses Tridium.license (Tridium 3.5 - never expires) TAC_LLC.license (TAC_LLC 3.5 - never expires) Certificates Tridium.certificate (Tridium - never expires) This information shows that the Tridium and TAC_LLC licenses have been installed but only the Tridium certificate. The TAC_LLC license will not be recognized unless the TAC_LLC.certificate is also installed (as shown in the following platform details display. Licenses   TAC_LLC.license (TAC_LLC 3.6 - never expires)   TAC.license (Tridium 3.6 - never expires) Certificates   Tridium.certificate (Tridium - never expires)   TAC_LLC.certificate (TAC_LLC - never expires) Resolution There are two ways to resolve this issue depending on network connectivity of the G3 Workbench computer. If public ethernet connectivity is available, the licenses and certificates can be downloaded from the I/A Series G3 (Tridium) license server, using the Workbench "License Manager". Open Workbench and connect to the subject ENC / JACE. Open the Platform then select License Manager. In the License Manager, select [Import] then check "Import licenses from license server".  This process will download any available licenses for the selected device, along with any available certificates.  After the download is complete, the licenses and certificates downloaded will automatically be installed.   If public ethernet connectivity is not available or the certificate is not found, download the TAC_LLC certificate from The Exchange Download Center.  Use Workbench to import the downloaded file.  A reboot of the ENC / JACE may necessary.

Issue In firmware 2.19.1, the MPM Modbus Generic Driver feature has been introduced with little to no explanation on how to use it Product Line EcoStruxure Building Expert Environment Multi Purpose Manager (MPM) Cause Sample CSV file not available on MPM Resolution In order to establish communication with a modbus device, a CSV (comma separated values) file of a certain format must be uploaded to the GMC1 object. Once uploaded the file will be visible in the drop-down list.   Requirements and Limitations Only holding registers are supported at this time (Modbus function codes 3 and 16) The CSV file mast be renamed Modbus_[label].csv where label is the name of the device or a label to help identification (e.g. Modbus_SE8000.csv) Write only registers are not supported It is not possible to use a more than 32 bits variable in write mode It is not possible to leave a blank column in CSV register configuration file except the last column It is not possible to create a continuous register table using different variable types   The CSV file must have the following format: modbus_addr,register_type,label,access,factor,unit Download example here (The text file can be viewed in a text editor but its extension must renamed to csv before uploading it to the MPM) modbus_addr: modbus register address (Decimal number between 1 and 65535) register_type: "uint" (UI16) "int" (SI16) "float" (F32) "ulong" (UI32) "int64" (SI64) "uint64" (UI64) label: name for this register, this will also be used to populate the associated object in the MPM Alphanumeric value between 1 and 32 characters. No special characters (comma, simple quotes, double quotes,%,&,@,#, etc.) access: read or read_write. read will only poll register based on driver availability (30 seconds typical) read_write will monitor for a change of value of the associated point, which will then generate a write event to the device with this new value factor: multiplier / gain Float number, typical between 0.001 and 65535. Typical use are factors of 10: (1,10,100, etc) This factor is multiplied when reading and is divided when writing.     unit: BACnet unit, used for the object units in the MPM. Number from the following list: 169 ampere square meters 3 Amperes 167 amperes per meter 168 amperes per square meter 55 bars 20 BTUs 50 btus per hour 117 btus per pound 24 btus per pound dry air 179 candelas 180 candelas per square meter 118 centimeters 60 centimeters of mercury 57 centimeters of water 79 cubic feet 84 cubic feet per minute 142 cubic feet per second 80 cubic meters 135 cubic meters per hour 165 cubic meters per minute 85 cubic meters per second 105 currency1 114 currency10 106 currency2 107 currency3 108 currency4 109 currency5 110 currency6 111 currency7 112 currency8 113 currency9 25 cycles per hour 26 cycles per minute 70 days 65 degree days celsius 66 degree days fahrenheit 90 degrees angular 62 degrees celsius 91 degrees celsius per hour 92 degrees celsius per minute 64 degrees fahrenheit 93 degrees fahrenheit per hour 94 degrees fahrenheit per minute 63 degrees kelvin 181 degrees kelvin per hour 182 degrees kelvin per minute 14 Degrees Phase 120 delta degrees fahrenheit 121 delta degrees kelvin 170 farads 33 feet 77 feet per minute 76 feet per second 38 foot candles 28 grams of water per kilogram dry air 155 grams per minute 154 grams per second 133 hectopascals 171 henrys 27 hertz 51 horsepower 71 hours 158 hundredths seconds 81 imperial gallons 86 imperial gallons per minute 32 inches 61 inches of mercury 58 inches of water 183 joule seconds 16 Joules 127 joules per degree kelvin 128 joules per kilogram degree kelvin 23 Joules/Kilogram Dry Air 147 kilo btus 157 kilo btus per hour 39 kilograms 186 kilograms per cubic meter 44 kilograms per hour 43 kilograms per minute 42 kilograms per second 129 kilohertz 122 kiloohms 17 Kilojoules 151 kilojoules per degree kelvin 125 kilojoules per kilogram 149 kilojoules per kilogram dry air 75 kilometers per hour 54 kilopascals 9 Kilovolt Amperes 12 Kilovolt Amperes Reactive 19 Kilowatt Hours 48 kilowatts 6 KVs 138 kw hours per square foot 137 kw hours per square meter 82 liters 136 liters per hour 88 liters per minute 87 liters per second 36 lumens 37 luxes 148 mega btus 130 megahertz 126 megajoules 152 megajoules per degree kelvin 150 megajoules per kilogram dry air 140 megajoules per square foot 139 megajoules per square meter 10 Megavolt Amperes 13 Megavolt Amperes Reactive 146 megawatt hours 49 megawatts 123 megohms 31 meters 164 meters per hour 163 meters per minute 74 meters per second 166 meters per second per second 78 miles per hour 2 Milliamperes 134 millibars 30 millimeters 59 millimeters of mercury 162 millimeters per minute 161 millimeters per second 145 milliohms 159 milliseconds 124 millivolts 132 milliwatts 72 minutes 68 months 7 MVs 153 newton 160 newton meters 187 newton seconds 188 newtons per meter 95 no units 172 ohm meters 4 Ohms 97 parts per billion 96 parts per million 53 pascals 131 per hour 100 per minute 101 per second 98 percent 143 percent obscuration per foot 144 percent obscuration per meter 99 percent per second 29 percent relative humidity 56 pounds force per square inch 40 pounds mass 46 pounds mass per hour 45 pounds mass per minute 119 pounds mass per second 15 Power Factor 102 psi per degree fahrenheit 103 radians 184 radians per second 104 revolutions per minute 73 seconds 173 siemens 174 siemens per meter 116 square centimeters 1 Square Feet 115 square inches 0 Square Meters 185 square meters per newton 175 teslas 21 Therms 22 Ton Hours 41 tons 156 tons per hour 52 tons refrigeration 83 us gallons 89 us gallons per minute 8 Volt Amperes 11 Volt Amperes Reactive 5 Volts 176 volts per degree kelvin 177 volts per meter 18 Watt Hours 47 watts 189 watts per meter per degree kelvin 34 watts per square foot 35 watts per square meter 141 watts per square meter degree kelvin 178 webers 69 weeks 67 years

Issue When trying to log in to WebStation Version 1.7.1 using Internet Explorer 11 you get the following error message: Wrong domain, user name or password Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Webstation Cause The cookie sent from the SmartStruxure server has an old expiry date. This can be confirmed by tracing communication using Fiddler or similar. Resolution Set the correct date and time in the Automation Server or Windows PC where the Enterprise Server is installed. Refer to Web Help #4388 for instruction on how to set the time in an Automation Server

Issue Setting up the override value to show the damper feedback on an i2/B3 866-v Product Line Andover Continuum, EcoStruxure Building Operation Environment i2/B3 866-V Plain English Script Cause Activate the damper position feature in the 866-V. Resolution SBO: See this video on creating a program that calculates damper feedback position.  Also reference the article How to show damper feedback for an i2/b3 866-V which describes what needs to be done to show damper position and calibrate the damper. Sample objects, code and images showing configuration are supplied.   Continuum: There is a description in the 866-V installation manual on how to activate the damper position feature, but there are some additional pieces of information that this article has been created to address. This was initially to just get the feature working as mentioned in the next section below. Getting the damper feedback operational: Once the end stops are determined initially during the Learn process, the controller can then determine the position of the damper. Create a PE program to set the DamperOutput LCDState = Disabled and back to Enabled in the next line. This will run through its stroke to determine the end stops. ‘Example program named "damperstate" Fall thru, auto start ‘a 2 line program to initialize the stops Line 1 Set damper LCDstate to disabled goto 2 Line 2 Set damper LCDstate to enabled stop To run from the command line Run damperstate Note that the Feedback will not start working until the Damper has gone full stroke in both directions. This will take several minutes. Set the damper point to on or –on depending on the position so it will move Print Damper OverrideValue from a command line or display it on a listview of the damper output after adding the overridevalue column Self Calibration - The LCDState toggle actually activates the "self calibrate" process. It doesn't just enable the feature. It is necessary to know this because you will need to activate the self calibration again whenever the damper is manually moved using the red actuator clutch release button. Using the clutch can cause the damper position to be reported incorrectly. Periodic re-calibration should be as a part of normal procedure for the controller. Once the clutch is used, the damper position will still report, but the value may be incorrect. Re-calibrate recommendation- Use a PE program that recalibrates the damper (i.e. LCDState as mentioned in Section A) on manual command by the service technician on a power cycle or at the end of an occupancy period. Note: For controlling the Damper motor output create an Infinity Output point of type Triac on Channel 1. It can then be opened / Closed like any other Triac output with the use of On, -On or Off commands

Issue After a find new BACnet devices in Continuum or EBO, 3rd party devices may come in and that we do not know the IP address of. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum Cyberstation BACnet Operator Workstation EcoStruxure Building Operation Cause BACnet devices IP addresses in Continuum explorer and EBO are encoded in HEX per BACnet Standard. BACnet IP addresses in BACnet are described as BACcnet MAC address. Resolution 3rd party IP level device is already in the BACnet side of Continuum, the IP address in HEX located as BACnet MAC address. Right-click and edit the third party device and use the BACnet MAC address to decipher. That is the IP address plus the port used to communicate For instance: The BACnet MAC address on the device editor is 0A9F1ACFBAC0 That would be 0A = 10, 9F=159, 1A=26, CF=207  The IP address would be 10.159.26.207 and BAC0 is 47808 on the port.   If you have exported to Excel and need a solution to covert, please reference IP address from BACnet MAC Address (SBO & Continuum)

Issue Drayton Theta ll ES4 Optimiser Controller requires replacement. Product Line Field Devices, Satchwell Sigma Environment Stand alone discreet Drayton Optimiser Controller Theta ll ES4 Cause Obsolescence of Drayton Theta ll ES4 Optimiser Controller. Resolution Please note that the Satchwell SVT controller is no longer available, and that the only possible replacement is the DC1400. Please refer to What is the replacement for the SVT controller range? for more details.  Replace Drayton Theta ll ES4 Optimiser Controller with Satchwell SVT Optimiser Controller.  N.B.  Two models of the Satchwell SVT Optimiser Controller are available :-  SVT 4201 with Analogue Timeswitch  SVT 4251 with Digital Timeswitch, Details of the Satchwell SVT Optimiser Controllers may be viewed here. It should also be noted that the associated Drayton Theta ll ES4 Optimiser Controller Sensors are obsolete.  These Sensors are not compatible with the Satchwell SVT Optimiser Controllers and must therefore be replaced.  Unlike the Drayton Theta ll ES4 Optimiser Controller, which requires the installation of both an Outside Air Temperature Sensor and an Inside Air Temperature Sensor, the Satchwell SVT Optimiser Controllers require the installation of a Inside Air Temperature Sensor only.  A STR 614 Inside Air Temperature Sensor is packed with the Satchwell SVT Optimiser Controller when supplied new :-   Details of the STR 614 Room Temperature Sensor may be viewed here.

Issue Modbus integration to Schneider Electric's PM1200 Power Meter Product Line TAC IA Series Environment I/A Series R2 Modbus Async (asynchronous) Integration Cause Requires the correct settings / configuration for Modbus integration to PM1200 power meter Resolution In WorkPlace Pro, open the UNC station and make changes to the following settings to integrate to the PM1200 power meter via Modbus Async (asynchronous). In the ModbusAsyncService properties, 'Comm' tab, ensure that the COM port settings matches the communications settings in the power meter. In the ModbusAsyncService properties, 'General' > 'Config' tab, change the floatByteOrder to 'order_1_0_3_2'. In the ModbusGenericAI object, the dataType should be set as 'Float'. dataAddress > addressFormat should be set as 'Modbus'. Use the register address as per the PM1200 documentation. Refer to the following documentation for details. PM1000 Series Power Meters Users Guide Modbus basics

Issue What is difference between valve rangeability and turndown ratio? Product Line Field Devices Environment Valves Cause Definition of the terms helps explain the flow outcomes. Resolution Rangeability - maximum controllable flow divided by minimum controllable flow Turndown ratio - normal maximum system flow divided by minimum controllable flow.   Rangeability is the inherent characteristic of the valve and turndown ratio is the installed characteristic.

Issue Installation and configuration for SE8600 heat pump application Product Line EcoStruxure Building Expert Environment  SE8600 Cause Installation and configuration errors for heat pump application Resolution SE8600 terminal identification In typical HP application, you shall connect to following terminals below: Y2 = Compressor 2 | Y1 = Compressor 1 | G = Fan | RC = 24 Vac positive | C = Common << 24Vac common >> W1 = Auxiliary Heating stage | W2 = O/B = First stage heating | UI22 = Supply temperature sensor | UI23 = Outdoor temperature sensor Depend on specification document, the application may require addition controls and connections. Application shall be set to: HP for heat pump From winter to summer season, high BP is the outdoor temperature value ABOVE which the system transfer from auxiliary heat <> and maintain heating setpoint with the heat pump << default 32°C >>. Temperature shall be set per system geographical localization. From summer to winter season, low BP is the outdoor temperature value BELOW which the system transfer from heat pump <> and maintain heating setpoint with the auxiliary heat << default -24.5°C >>. Temperature shall be set per system geographical localization. * Outdoor temperature sensor shall be installed   Heat pump reversing valve operation O: energize valve in cooling operation << default position >> B: energize valve in heating operation Heat pump system

Issue This is the description of what the Continuum Analyzer does that is also available on the service release CD. Product Line Andover Continuum Environment Continuum Analyzer Windows 7 Windows 2003 Windows Server 2008 Cause The Continuum Analyzer description and what it does is in the service release CD. Resolution The Continuum Analyzer is designed to provide installers and troubleshooters with a point of reference for discovering problem areas within their installations. The software is proactive in that it enables you to 'clean' orphaned and mismatched objects from the database, thereby recovering from a minimal amount of database corruption. Continuum Analyzer also performs a system information check and provides full reporting on all aspects of the installation, as well as alerts regarding deficiencies. This article is provided to you as a guideline and an operational reference for use of the Continuum Analyzer. It is of the utmost importance that you review the current, Continuum Cyberstation Release Notes, before using this product. This document refers to specific changes made to the operation of the Cyberstation software in its new release. Installation Requirements Continuum Cyberstation software must also be installed on the given computer, and meet its hardware and software specifications as detailed in the, Continuum Getting Started Guide. Uninstall Previous Analyzer Versions If a previous revision of Continuum Analyzer is installed on the computer, it is important to remove it before installing a newer version. This is easily accomplished using the following procedure. Close all open applications before proceeding. Select Start, then Settings, and then Control Panel. Once inside the Control Panel, select the Add/Remove Software icon and select, Continuum Analyzer. When prompted, select Yes to remove all application components, and Remove All once uninstall begins. Close the Add/Remove applet and reboot your system. You may now proceed with installation of a newer version, below. Setup Procedure Close all open applications before proceeding. Setup will begin unpacking necessary files. Older versions of Windows workstation may require system file upgrades. An alert message will display asking you to confirm this operation. You may be required to reboot your computer. If this is the case, rerun setup after the computer restarts. The installation awareness screen prompts you for the location in which the files are installed. We recommend allowing the default installation directory. (C:\Program Files\Continuum\ContinuumUtilities\Continuum_Analyzer) When you are satisfied with the location, click on the large installation icon towards the left of the dialogue box. Figure One, below, details this screen. When prompted for creation of the program group in which the Analyzer will reside, select the default, or choose an existing program group for these icons. Setup will copy the necessary files into the installation directory on the hard drive. When finished, you are prompted that setup is complete and need to click, OK to verify. Setup is complete. Operation Modes Continuum Cyberstation software allows the user to define the type of database used to house the system information. Typical system configurations rely on the implementation of Microsoft SQL Server. LAN Mode This operating mode provides the user with all available information about the system installation, including SQL parameters used on the database server. This additional information can help reconcile issues that exist within the configuration of the SQL server. Stand Alone This mode diagnoses problems and lends the equivalent information presented through SQL implementation. Password Confirmation Continuum Analyzer requires the user to enter a password before launching the GUI. The password used should match the password of the SQL account used by Continuum. If all installation defaults were followed, the password is, pyramid97. Navigating the Interface The Analyzer uses an intuitive interface to easily collect and return data from Continuum installations. The interface is broken into 5 parts; a function toolbar, system toolbar, status prompt, report explorer, and the report window. Appendix B contains a screen shot of the analyzer display. Several toolbars located throughout the graphical interface permit point and click operation of the software. Function Toolbar This toolbar is located to the upper-left hand side of the Analyzer interface. Each toolbar feature is explained below. Button descriptions will also appear When the mouse is held idle over the selected feature. Save Reports to File Activating this button saves the Main and Suspect generated report to a *.csv file at the location specified by the user. The Save dialogue box prompts the user for the report destination. This file is required for proper technical support from Andover Controls Corp. Word Wrap This button wraps each line of output data to fit within the parameters of the display window. Run Begins data collection on the system. Clean The clean button removes references to suspect objects found during the initial database screening. After the items are removed from the database, the analyzer is automatically rerun to ensure that no remaining corruption exists. System Toolbar The System Toolbar features shortcuts to many of the same features as the Function Toolbar. This feature group also contains a button to close the program and a display window that monitors the integrity of the database and indicates corruption when found. Status Prompt The analyzer status prompt displays the progress of a current session. During an active session, the status indicator bar will fill to indicate that the analyzer has completed its review of the system. It may take Analyzer several minutes to complete its system scan. The status bar is located in the center of the system toolbar. Please refer to figure four for a detail of the system toolbar and status prompt. Log Selection Windows Analyzer allows a technician to specify log collection dates independently for both the Error and Activity logs using calendar menus as detailed below. This feature is helpful in reducing the amount of time necessary for the completion of an Analyzer scan, and identifying the point at which problems first occurred. The user may choose not to report on log collection by selecting one day ahead of the present date. Report Explorer Navigation The report explorer allows navigation through each report feature in a manner akin to the windows explorer file manager found in Windows. Navigate by double clicking on the desired report folder and selecting the appropriate report from the file list. Figure Seven details the report explorer below. The root of the Analyzer’s report explorer indicates to the user the mode in which the analyzer is running (LAN Mode or Stand Alone.) Each folder displayed below the root contains a report(s) on the system. Continuum Logs These log reports display two kinds of activity. The first report, Continuum Activity, displays all system user actions on the system during the period specified in the calendar selection window. The second report, Continuum Errors, shows the continuum error log during the dates specified within the parameters of the calendar selection window. Cyberstations This report area displays each workstation’s properties as detailed by the device table, and all Plain English programs that are installed at each workstation. Database Integrity This report allows a technician the ability to quickly identify an area of data corruption within the various link tables of the Continuum database. Each of the following reports specifies the type of link verified and a numeric display of how many broken links appear within the system. Typically, broken links detected by Continuum Analyzer can be cleaned from the system, using the clean feature. The clean feature removes all references to the orphaned item. Distributions Pending and failed distributions are monitored from within this report area. Failed distributions detail the name of the object and its status. The Pending distributions monitor the type, content, and numeric statistic of distributions waiting to complete. Field Devices Field device reports detect the variable parameters for different classes of objects configured in the field. This gives the technician a holistic reference point for determining any conflicting parameters within the system. Please refer below for information regarding the content of each report. Report Name Description CommPorts Infinity Controller communication port configurations InfinityControllers CX controller parameters InfinityInfinetControllers Defined parameters for infinet devices InfinityPrograms Details programs that reside on the CX controllers IOU Modules Parameters for each IOU configured within the system Networks Network Object parameters Each field device report displays values as an enumeration from within the database. Troubleshooting with the Analyzer requires that a technician be able to correlate each reported value of an attribute to the software value that Continuum displays within the object editor. Please refer to Appendix A for a definition and value range for variables discussed in the reports. General Continuum These detail all Continuum installation parameters, providing the technician with the ability to troubleshoot any problems that might occur at the software installation level. Aspects covered in this report segment include ODBC client connector details, connection status, domain user account information, and installation path. Workstation Workstation reports provide system information on the workstation hardware and operating system configuration. These reports help clarify any Continuum software compliance issues. SQL Server SQL Configuration information is provided through two reports, Database Configuration and Server Configuration. These values are used to trace possible problems back to a server configuration variable. Summary Report The summary report issues system details that provide a quick overview of the Continuum configuration in use at a particular facility. One set of data in particular is worth discussion, as the values here can lead to problems with the workstation performance of the system. The summary includes a section labeled Windows Registry Check. If the software installation was performed correctly, registry keys will be entered in the Local Machine hive of the registry. It is possible under abnormal installation circumstances that these registry entries are placed under the Current User hive. The Analyzer retrieves these registry values and displays them as follows in figure eight. If the machine is properly configured, the values will only display once, to the right side of the definition text. This indicates their presence in the appropriate location. If the values are located on the left-hand side of the definition text, the installation did not put the appropriate values in the correct location. Suspect Objects The suspect object report details three categories of data corruption detected within the database. If data corruption is discovered, the system toolbar and the report explorer will indicate such. The first category, Suspect Objects Correctable, contains any corrupt data that the Analyzer can repair using the clean command. Suspect Objects Manual Fix details configuration issues which require manually editing the erroneous variable. The final category, Suspect Objects Uncorrectable requires the assistance of Andover Controls TSD staff to remedy the problems. Please be aware that support for these issues requires that ACC TSD staff have a copy of the Analyzer report from the system in question. Figure nine details the report explorer icon displayed when corruption is detected. It is recommended that all suspect objects are saved as a file to aid in recreating the broken link objects. The Clean button is used after the Save Suspect Objects to File button to remove the broken objects from the database. Analyzer Report This report details all areas of data collection and is saved in a *.csv format. You may save a report in one of the following ways. Saving your Analyzer Reports The Continuum Analyzer generates two reports that can be saved for review. Both reports can be saved simultaneously, or individually using the reports menu option at the top of the Analyzer window. Suspect Objects Report The suspect object report is optionally generated when data corruption is discovered. If you do not see the visual indicators that suspect objects are present in the system, then there is no report to generate. However, if corruption is present, the report must be saved. All Cyberstation Workstations Invoke the analyzer by selecting the Continuum Analyzer icon from the Start Menu. You are prompted for a password. This password is the same as the password used to access your database from the ODBC connector. Figure Ten displays the password dialog box. If Continuum was installed with the default options, the database login password is Pyramid97. You may change the start date for log collection through the calendar menu, if necessary. Select, “Run” to begin analysis. The program will run for several seconds, an active display in the system toolbar details its progress. Save the report generated by each machine. Repair Data Corruption IMPORTANT! Note that this is option is NOT always available! If the Continuum Analyzer reports that data corruption was found, a stop sign icon appears in the report explorer and a Database Integrity Failed message appears at the top of the system toolbar. Select the option button labeled, Save Suspect Objects to File. Upon completion, select the Clean option. You’ll notice that after this button is selected, the database is cleaned and the Analyzer is run a second time, to ensure there is no remaining corruption within the database. Submit Analyzer Report The Continuum Analyzer Reports should be sent to our technical support department before upgrading if uncorrectable errors were found. Schneider Electric has a technical support address designed for this purpose. The email should include the following information. Subject: / Body: Dealership name Site Name File attachments: Analyzer Reports (each workstation) File attachments: Suspect Object Reports (each workstation) This email should be sent to Product Support All workstation analyzer reports and suspect object reports should be attached to a single email. Run Analyzer before Upgrade The Analyzer must be run again prior to the upgrade installation to verify that database integrity is stable. Using the Primary Access Server, run the analyzer, save the generated reports, and clean any suspect objects if necessary. Uninstall Continuum Make a note of the workstation and database settings within the Database Initialization Program. Uninstall earlier versions of Continuum from the workstations through the Add/Remove Programs icon located in the Control Panel. Select Continuum from the menu of programs and follow the automated procedure. You must reboot after un-installing. Install Continuum Refer to the Continuum Cyberstation Getting Started Guide for installation instructions. The first workstation upgraded should use the database initialization program to UPDATE an existing database. Ensure that the server name and authentication information is entered correctly. Verify that the workstation settings are IDENTICAL to those used in the previous installation of Continuum Cyberstation. Rerun Continuum Analyzer Rerun the Continuum Analyzer to verify that data within the tables is stable, and that all workstation settings are properly configured. If database corruption is present again, we recommend contacting our Technical Support Department for further information. Appendix A Field Translation Guide The Continuum Analyzer report references the exact table and column names used within the Continuum database. This appended reference should be used when trying to correlate settings and values from the analyzer report against values within the Cyberstation software. Please direct any further inquires to our Technical Support Department. Field Name Description Typical Values Autostart autostart on/off True/False Baud Enumerated value starting with 0 for 300. Each rate of speed has its own enumerated value 0=300, 1=1200, 2=2400, 3=4800, 4=9600 and 5=19.2 Command Whether a program can execute from command line on/off DefaultBaud When a Commport is created it is assigned the default baud of 9600 which is equal to 4 0=300, 1=1200, 2=2400, 3=4800, 4=9600 and 5=19.2 DefaultMode This is the mode the CommPort is configured to use. i.e., Infinet, printer 0=Printer, 2=Command, 3=Infinet, 5=Autoset, 6=Tanknet,11=Xdriver Description Text string entered into the object description field user defined DialPrefix Standard Commport initialization settings ATDT DialSuffix Standard Commport initialization settings |013 DirectConnect User selectable checkbox definition True or False. True if checkbox is selected Filesize Size of the program file in bytes 18 FlowControl UART data stream control 0=NoFlowControl, 1=XonXoff, 2=CtsRts, 3=XonXoffCtsRts HangUpCmd Standard Commport termination request @@@+++@@@ATH0|013 InfinetID Unique Identifier assigned to infinet controllers   IOU Number reference ID attached to the current module 1-32 Location Controller to which an object is attached User Defined MaxResponse Time Maximum amount of time to wait for a response in seconds Default 5 Sec ModelName Value obtained from hardware hardware/software type and version ModemInit Modem initialization string AT&F|013@@@@@@@@@@@ATEQ1&C1&D3S1S0=1W3\J\Q3%C1&W|013 Module ID Unique module identifier; hardware encoded in each module Not user Definable NetworkID Workstation's Energy Net identification number 1-190. 1-64 are recognized by the CXs and NetController. Ids above 64 are recognized by Workstations only. NetworkUTCOffset GMT offset of the network objects User Defined in minutes Owner Name of attached controller object User Defined Parity Standard Commport entries 0 PortNum Enumerated value of commport number to which a device is attached 0=1, 1=2, 2-3, 3=4 PrimaryAccessLogger Workstation computer designated as the primary access server 0=Not Primary, 1=Primary ProbeTime Probe Frequency time between TTL pings Default 60 Sec Program ID Internal Firmware reference ID 4th digit from the left represents IOU firmware revision SecondaryAccessLogger Workstation computer designated as the secondary access server 0=Not Secondary, 1 = Secondary SendToACX Whether or not the object must be sent to the corresponding ACX controller 0/1 SendToCX Whether or not the object must be sent to the corresponding controller 0/1 SerialNum Serial number of the network controller object 527853 Shareflag Whether program is able to run on any workstation on/off State Determines whether an object is active within the system or not TRUE StopBits Commport initialization setting 0 SynchDB Whether or not the object must be synchronized with the database 0/1 TerminalType Determines Commport emulation 0=VT100, 1=VT220, 2=Wyse TimeOutValue No user definition 0 TrackCxd Changed through checkbox selection True or False. True if checkbox is selected UiName Object name in database User Defined UTCOffset Number of minutes offset from GMT User Defined in minutes VersionNum Firmware revision number Ex. 1.53x, 1.2x, 2.1x, 4.5x XDriverFile Location of and name of any Xdriver assigned to the port User Defined

Issue Connection issues come in a variety of flavors, narrowing them down is important to help resolve the issue. One of the causes of connection issues could be general network problems. Product Line EcoStruxure Building Advisor, EcoStruxure Building Operation Environment Building Operation Building Advisor EBO Health Module Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Premium Cause There are some steps that can be done to eliminate network issues as the cause of Building Advisor Cloud connectivity problems Resolution For the ES or EC: On the server running the ES/EC, start a WireShark capture then open up the command prompt running as admin and run the following commands. Make sure to note the responses received after each command: ping app.schneider-electric.com ping cnmiothubappstna.blob.core.windows.net ping cnm-ih-na.azure-devices.net curl -X POST https://app.schneider-electric.com/ecostruxure-building-advisor/diagnostics/Initialize -k -v --header "Content-Length: 0" Open the PuTTY application and telnet to the same 3 sites you pinged above over port 443. PuTTY is installed with Device Administrator and can be found in a folder similar to: C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation 3.2\Device Administrator\bin If connection is successful, then you will only see PuTTY show blank black screen and it will remain without error pop-up for over 15 seconds. If unsuccessful, PuTTY will pop-up error for time out or network error, like:   PuTTY: Network Error For an AS-P/B: Connect to the server using Device Administrator and select the console option Run the following commands: ping app.schneider-electric.com ping cnmiothubappstna.blob.core.windows.net ping cnm-ih-na.azure-devices.net curl -X POST https://app.schneider-electric.com/ecostruxure-building-advisor/diagnostics/Initialize -k -v --header "Content-Length: 0" Curl response should look like the following (2 screenshots to show all): Command and Response Response (continued)

Issue It is not clear how to register a SmartStruxure system, and what information to write in case it's not a customer site (For example a test bench/controller or engineering PC). Product Line EcoStruxure Building Operation Environment S2Connect Workstation Cause Guidelines are needed regarding how to properly register a system. Resolution Starting in SmartStruxure 1.5, we have introduced a registration process to know more about SmartStruxure systems. In order to know our customer and/or partner better and provide better services we should register our SmartStruxure system with correct information. The SmartStruxure registration process requires a Buildings Exchange account. If you have issues creating, activating or using a Buildings Exchange account, refer to Register for The Exchange. Please make sure below points while registering SmartStruxure system. Test site: If you are registering a test site to test registration process, write "[Test]" keyword in Site note*. Demo site: If you are registering a site which is for demo, then write "[Demo]" keyword in Site note. Training site: If you are registering a site for training or you want to explore registration process, then write "[Training]" keyword in Site note Customer site: if you are installing an actual site for customer then DO NOT use above keywords in Site note field *Site note field can be found under Site Administrator tab (Shown below in screen shots) New system registration: If you are registering new system then you continue enter all information in Step 1 and continue to Step 2. In Step 2 you will find a Site note field. Fill the Site note field as explained above.  Already registered system: If you have registered your site without providing above explained details then you can browse to below website https://registration.smartstruxure.schneider-electric.com After successful login; Navigate to Systems -> Site Administrator and click on Edit button, now you can edit Site note field. Registration Process Does Not Complete In some cases after registering either the Enterprise or Automation server, it still prompts you to register when you log back in. There are two different procedures that can be taken to correct this issue. Procedure 1 - By editing the registration and clicking submit again, it can help the system complete the registration. Log into the sever again and either click Register now on the initial prompt or go to Help > Registration once you are in Workstation. Log into the Registration Portal. If you have issues creating, activating or using a Buildings Exchange account, refer to Register for The Exchange. Select the server that is experiencing the issue on the right side of the window. Click Edit. Click Submit. Procedure 2 - If procedure 1 still does not work, then the registration can be completed manually by entering the Registration code in the offline mode. Log in to the Registration portal directly through this link (registration.smartstruxure.schneider-electric.com). Select the server on the right hand side of the screen that has the registration issue. Take note of the Registration code. Insure that the Enterprise or Automation server does not have internet access and log into the server with Workstation (In the case of an Automation server you will need to connect directly to it via Ethernet). Click to Register now (Since the server does not have internet access, it will automatically launch the offline registration). Insert the Registration code the three fields provided and click Register now. Also check out the SmartStruxure Solution Connect (S2C) - SmartStruxure Product Registration Registration Quick-help video on the Exchange.

Issue When should the APDU Timeout setting on a BCX be increased? Product Line Andover Continuum Environment BCX4040 BACnet APDU Timeout Cause Some BACnet devices are taking a long time to respond to BACnet controller requests. Resolution If the device takes too long to respond to a request, it is possible that the response may be ignored by the BACnet controller. Increasing the APDU timeout setting will cause the BACnet controller to wait longer for a response from a field device. 

Issue Using the SIM-MTECH manual (F-26133-2) for reference, the Read/Write range of "Space Static Pressure Setpoint' on page A-45 displays as 0 to 5.0 "WC.  But the displayed setpoint does not match the value in the McQuay controller.  And, in general terms, any space static is never as high as 5.0 "WC. Environment SIM-MTECH Cause The manual contains a typo. Resolution The above-mentioned space static pressure setpoint range is actually -0.25 to +0.25 "WC. Keep this in mind as calculations are done to convert the unitless range of 0-250 to a value in "WC.

Issue What is the recommended method to upgrade a Niagara R2 station to a newer version? Product Line TAC IA Series Environment I/A Series Niagara R2 Cause Unsure how to upgrade station databases. Resolution The published upgrade procedure is provided in F-27334. Below is a modified method that also works. Doing station upgrades on the server first is preferred. If there are any errors, they can be addressed without operational interruptions. Using the existing version of WorkPlace Pro (WPP), backup ALL of the UNC and Server databases into XML format. Methods of backing up and converting databases. Open the Enterprise server in WorkPlace Pro. Double click the station name. Select "Commands" and "Backup XML to save the server in XML. Then select "Backup Subordinate XML" to pull all of the UNC databases as XML into the server stations folder.   If not on site but the UNC and Server databases are available, use the DB Admin tab of the Admin tool to convert the databases locally to XML. Now install the newer Niagara revision onto the Server. Copy the stations containing the XML files to the desired WPP revision station folder. Enable and open the new revision of WPP. Use the Admin Tool to convert locally all of the stations from XML to DB. (If there are any errors, they can be addressed without affecting the running installation.) After all the databases have successfully converted to DB, convert them to SNS. (This saves time later if the UNCs need reloading) Use the Enterprise Server to upgrade the UNC. During the upgrade process of the UNC it will ask to backup the database. If the database had upgraded with no issue in the previous step, enter the username and password to proceed with this backup. This will backup the station, upgrade the UNC, and then upgrade and reinstall the station. The previous station upgrade will be needed only if there is an issue. If after following this procedure the station still fails to start, contact Product Support Services.

Issue Binding to a Graphic, what is the correct method? Product Line EcoStruxure Building Operation Environment Bindings Graphics Cause In the chapter "Binding Templates - Binding Values Using a Binding Template" in the "EcoStruxure Building Operation - Technical Reference Guide" it states "When creating bindings, follow the recommended general guidelines: create binding between Inputs and Outputs only, and do not create binding to Public Signals". Does that mean that you should not bind constants used in e.g. curve block or time delays or outputs from expression blocks to a graphic? Does that mean that you should not bind constants used in e.g. curve block or time delays or outputs from expression blocks to a graphic? Resolution Bindings from public signals to graphics is appropriate. When dealing with directional bindings (i.e. in from a schedule, out to an alarm, in from or out to another program, etc.), it's best to bind to input blocks or output blocks.  Graphics bindings are a different animal, though.  Among other things, they are bi-directional and only affect the system when the graphic is displayed.  They also exist to give the user access and control to values throughout the system (rather than to control routine data flow). Our primary reason for communicating this best practice is to help with the binding process.  Programs will operate with un-bound points, but we're encouraging users to simplify the binding process by relying on just inputs and outputs to interconnect a program with other logic and alarms.  In this way, you can visually scan the list of inputs and outputs to see which points still need to be bound. Since most programs typically have a much longer list of public signals, it's easier to overlook a missed public signal binding. Missed graphics bindings should be easier to catch but bindings to another program or alarm may be difficult to identify.

Issue 7790A LAN Interface Unit and Information. Why is the 7790A not shown in my Network Configuration Product Line TAC I/NET Environment I/NET Seven Software v2.45 7790A LAN Interface Unit (LIU) 7791A Door Processing Interface (DPI) 7792A Micro Regulator Interface (MRI) 7793A Micro Control Interface (MCI) Cause Information about the 7790A LAN Interface Unit or LIU Confusion is usually with the Hardware Model when purchasing. Once installed and configured for one of the three common options above, firmware (software) is downloaded to the hardware device (7790A) to become one of the three indicated interfaces, DPI, MRI, and MCI. In the later release of I/NET Seven Software only supports the 7793 MCI.  Resolution Refer to TCON109 attached for further information.    The 7793 has two channels and will handle 32 devices on each channel if addressed correctly. This gives a total of 64 SCU units on a single 7793. The 7790A can be addressed using the HHC to a 7790, 7791, 7792, 7793, 7797.  The 7790A replaces the 7797A-C as of January 1, 2013. The original 7791 was primarily for Access Control. The original 7792 was primarily for HVAC. The 7793 is a combination for both and the most popular of the 7790 series. To clarify, when purchasing a 7790A, you would address as a 7793, then put up to 32 SCUs on each of the channels giving you a total capacity of 64 SCUs.     For access control, the model 7798C has more memory but only one Channel, which means it can handle up to a maximum of 32 SCU controllers and the recommended interface for larger access control sites.  

Issue Script Program bindings added to the Watch window or the Binding Variables pane in Script Editor show NULL or a previous value compared to the value in the objects they are bound to. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Building Operation Enterprise Server Cause Consider the script program below: The bindings (1) are as follows along with the current values (2) in the Watch pane: The source objects all have a value, but the output Bind Value are NULL except for the first Bind Value. Resolution Since SBO 1.5 script program bindings are only updated when they are processed in the program body. In the following picture, only BINDtest1 has a non NULL value since the program is sitting at line 1 which has a reference to BINDtest1. The next picture shows the bindings after the script program has run through all the program lines. Notice that BINDtest5 is still NULL since it has never been referenced in the program's body. Program bindings that are not been processed in the program body will have a value of NULL. or Program bindings that were processed in a previous line inside the program will not update to the latest value until the program goes to a line that references the binding again at which point its value will update.

Issue Satchwell ALi series Linear Actuator requires replacement. Environment Satchwell ALi series Linear Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body. Actuator type :- ALi series. Cause Obsolescence of Satchwell ALi series Linear Actuator. Resolution Replace Satchwell ALi series Linear Actuator with S-E M800 Linear Actuator and Linkage Kit :- ALi = M800 + L2SV (880-0124-000) Linkage Kit. N.B. Should the Satchwell ALi series Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the S-E M800 Actuator as appropriate :- S2 - Two independent 24 volt 4amp AC-1 rated SPDT Auxiliary End Point Switches. (880-0104-000)   Particular care should be taken when selecting an S-E Forta M800 Actuator to replace an existing Satchwell ALi series Actuator. The S-E Forta M800 Actuator may be used to replace an existing Satchwell ALi series Actuator but it should be noted that where an existing Satchwell ALi series Actuator has been connected directly to a Satchwell Controller, an independent Transformer rated to provide the greater level of power required by a single S-E Forta M800 Actuator (50VA) will also be required. (e.g. S-E Transformer Type TR60) Where an existing Satchwell ALi series Actuator has been connected via an independent Transformer, it is possible that the Transformer may have been rated to provide the level of power required by a single ALi series Actuator (16VA) only. In such circumstances the existing independent Transformer will also require replacement by another independent Transformer, rated to provide the greater level of power required by a single S-E Forta M800 Actuator (50VA) (e.g. S-E Transformer Type TR60) Details of the Schneider Electric M800 Actuator may be viewed here Details of the Schneider Electric TR60 Transformer may be viewed here Details of the Schneider Electric L2SV Linkage Kit may be viewed here