Building Automation Knowledge Base

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 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 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 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 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 addition in a JavaScript, but it is performing a string concatenation. Example: The value in the database is 3. value = value + 1; The resulting value is 31, not 4.  Comparisons are returning unexpected results NaN (Not a Number) resulting from a JavaScript function Product Line TAC Vista Environment TGML JavaScript Vista 5 Graphics Cause Values that are read into a JavaScript in a TGML graphic need to be cast to the correct data type. Some values may be read in as an ASCII string, and this can cause unexpected results. Resolution Cast the value being read to the desired data type. There are three options for casting values to numerical values that can then be used in mathematical operations. In the example below a variable named "value" reads a database value from a binding. No type casting is performed, so this value may be interpreted as an ASCII string. function OnSignalChange(evt){ value = evt.getValue(); } To ensure that the data are represented as numerical value, select one of the three options below. Replace the variable declaration (highlighted) with one that utilizes the appropriate type casting. Number() value = Number(evt.getValue()); The Number() function will treat the whole object as a number. Non-numerical characters will return NaN. parseInt() value = parseInt(evt.getValue()); The parseInt() function will convert the beginning of a string to an Integer value, ignoring any decimal points or any trailing non-numbers. parseFloat() value = parseFloat(evt.getValue()); The parseFloat() function will convert the beginning of a string to a floating point decimal value, ignoring any trailing non-numbers. Also check out the JavaScript Essentials - Episode 3 - Value Types Quick-Help video on the Exchange.

Issue TGML graphics to display "OFF" and "ON" instead of "0" and "1" Product Line EcoStruxure Building Operation, TAC Vista Environment TGML Graphics Editor Cause Data in the Vista database is stored as 0,1 but may be displayed using paired texts. Those paired texts can be set to show up on the graphic, or a unique conversion can take place in TGML. Resolution If you use default snippets that come provided with the editor, you have the option of displaying a value with either NumericPresentation or TextPresentation. The only real difference between the two is that TextPresentation defines the binding's behavior format as "Presentation" rather than "None." This will only display built in presentation formats -- an alarm state will show up as "Alarm" or "Normal" -- or if you've defined paired text within a binary point in the Vista database, that will show up instead of (0,1). This does not, however, explicitly give you the option from within the Graphics Editor to convert decimal values into text. The example TGML code below describes how to take a value that is showing up as "0" and "1" and make it read instead as "OFF" and "ON." <Text>Value   <Bind Attribute="Content" Name="Value">     <ConvertValue SignalEqualTo="0" AttributeValue="OFF"/>     <ConvertValue SignalEqualTo="1" AttributeValue="ON"/>   </Bind> </Text> Cut and paste this TGML code into the editor's Source view to view it in the editor. Just be sure to paste it between the opening tag and closing tag. If all you see in the Source view is one self-closing tag, that is because the page is empty. Either add separate opening and closing tags, or go back to Design view and add one object to the page to automatically split them.You can see here that a Text object has a binding associated with it. That binding's target attribute is "Content" because this will alter the content of the Text. (We could also change the text's stroke color, background color, font size, position on the page, etc., by changing our binding's target attribute.) ConvertValues underneath the binding tell the binding how to alter the Text's content. A SignalEqualTo 0 will write "OFF" to the content and a SignalEqualTo 1 will write "ON" to the content. The number of ConvertValues is not limited to only two. There could be a third one to say that a value of 2 should read "STANDBY."

Issue How do you reset the Viconics VT7200, VT7300, & VT7600 LON series thermostats back to factory default values? Product Line Field Devices Environment SSL SE7000 Cause There's no button or command that sets the thermostat to its default parameter settings. Resolution Either set them manually or through the snvts available via a LON integration.  The Viconics Lon Integration Manual will help with identifying the proper snvts to use.

Issue Unable to connect to a G3 ENC or JACE after attempting to downgrade or install a station. One of several different errors may be displayed in the serial shell console output.  The following are examples: Could not find library libcpp.so.3 Could not find library libcpp.so.4 Error occurred during initialization of VM - Java/Lang/ No Class Def found error: Java/Lang/object Product Line TAC I/A Series Environment I/A Series G3 ENC and JACE (all revisions), ENC-410, ENC-520, TRD-T-645, TRD-T-603, TRD-RB-645, TRD-RB-603, TRD-J-600E, TRD-T-700 Cause The issue is caused by downgrading the ENC / JACE without following the procedure to first install the clean distribution file. In addition, the ENC/JACE will fail if a station is copied into the ENC/JACE without first installing the OS and NRE software using the Workbench Commissioning Wizard. Note: With G3 release 3.3 and newer, the procedure for downgrading an ENC/JACE is included in the Niagara AX Platform Guide - Downgrading a JACE (Clean Dist). Resolution Tools needed: Null Modem Cable Serial Terminal (e.g. HyperTerminal or TeraTerm) Jumper Obtaining the files required to recover the ENC NOTE: If recovery of a Jace-700 is required, please contact Product Support for the recovery file. Download the appropriate OS image and gz file zip file for the ENC/JACE from the Exchange website - https://ecobuilding.schneider-electric.com ENC-410.zip ENC-410-1 standard memory - etfs512 ENC-410-EM.zip ENC-410-1 extended memory - etfs2048 ENC-520.zip ENC-520-2 standard memory - etfs512 ENC-520-EM.zip ENC-520-2 extended memory - etfs2048 NPM6E.zip JACE603/645, TRD-RB-603/645, JACE600E Note: The files used in the following procedure MUST correctly match the ENC/JACE hardware platform, otherwise permanent damage to the unit may occur. The serial shell can be used to determine the file system requirements (standard or extended memory). To find the exact image needed for an ENC (JACE 2/4/5) execute the following while connected to the unit with serial shell: Log into the unit's menu system using the platform username and password. Type sh to exit the menu system and enter the shell mode. At the # prompt, (type: cat sys/info/fs) and enter This will return the file system type of etfs512 or etfs2048. Extract the OS image and gz files from the downloaded zip to a suitable directory on the local computer (e.g. local hard drive such as: c:\temp). Enable ftp: By default, the ftp port is disabled on every ENC/JACE as shipped from the factory.  Enable the ftp as follows. Set the jumper on the ENC to serial shell mode and connect the null modem cable between the PC and the ENC/JACE. Connect to the ENC using the Serial Terminal program and the following port settings: Baud rate 57600 bps (Note: JACE-603/645 baud rate is 115200) 8 data bits, 1 stop bit, no parity After logging in to the menu system from the serial shell, do the following to enable ftp: Select option 4 from the menu Enter the port number (Normally 21). (type: 21) Press the Enter key to confirm the change Note: Leave the serial shell connection open while performing the next steps. FTP the OS image and gz files On the local system, open a command prompt window and change the directory to the location where the OS image and gz files were extracted (c:\temp). Connect to the ENC via ftp and put the OS image in the /tmp directory entering the following from the command line: Create a ftp connection to the ENC by typing: ftp and enter Type the username and password for the platform when prompted Change directory to /tmp (type: cd tmp) and enter Change to binary mode (type: bin) and enter Download the image to the ENC by using the put command. The image name must exactly match the image extracted from the downloaded zip file. ENC-410-1 standard memory (type: put york-etfs512.image) and enter ENC-410-1 extended memory (type: put york-etfs2048.image) and enter ENC-520-1 standard memory (type: put james-etfs512.image) and enter ENC-520-1 extended memory (type: put james-etfs2048.image) and enter JACE-600E, 603, 645 extended memory (type: put npm6xx-etfs2048.image) and enter Download the gz file to the ENC by using the put command. The name must exactly match the image extracted from the downloaded zip file. Change directory to the root (type: cd ../..) and enter Change directory to /ffs0/zip (type: cd ffs0/zip) and enter Download the gz file (type: put clean.tar.gz) and enter Exit ftp (type: quit) and enter Execute OS image update Return to the serial shell connection Type sh to exit the menu system and enter the shell mode At the # prompt, type: osupdate and enter After a short delay the # prompt will return. Shutdown to reboot the ENC (type: shutdown) and press enter. The ENC/JACE will reboot, install the clean distribution image and perform one additional reboot automatically. The ENC/JACE should now be recovered and allow connection to the platform. Connect and use the Workbench Commissioning Wizard to install the version of G3 required.

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 TAC Vista stopped trending or cannot read trend value. SQL reaches 4GB or 10GB limitation (depending on version, Vista 5.0.1 - Vista 5.1.6 supports up to 4 GB and Vista 5.1.7 and newer support up to 10 GB) $queues folder keep growing Product Line TAC Vista Environment TAC Vista 5 Logging errors SQL data Log full, shrink Cause The SQL 2005 Express version that come with Vista 5.0.1-5.1.6 has a 4GB limitation and the SQL 2008 Express version that comes with Vista 5.1.7 and newer has a 10GB limit. Once the SQL database reaches this limitation, Vista will not be able to read/write data from/into the SQL database. To fix this issue, the SQL database needs to be purged and a new SQL database needs to be created, or the SQL server needs to be upgraded. Once the SQL database is full, log data will be stored in the $queues folder wanting to be written into the SQL database. If the $queues folder gets too big that even creating a new SQL database with the same size limitations will not allow the Vista Server to run then data in the $queues folder will need to be removed or an upgrade to a version of SQL with larger size limits will need to be performed. Resolution Note: In deciding which resolution below will be most appropriate, consideration should be given to how quickly the SQL database is growing and how long it took to fill up initially. When the SQL database fills up it is a perfect time to carefully look at the various trends and alarms that consume space in the database and consider what if anything might reasonably be removed. Also, note Vista 5.1.7 and newer include SQL Express 2008 which has a 10 GB storage limit. This is 2.5 times greater than the SQL Express 2005 version that was included with earlier versions of Vista 5 and is a free upgrade from any Vista 5.1.X versions.   Please find the scenario that matches your issue and read the resolution section accordingly.   Scenario A Scenario B Scenario C Scenario D Data in "$queues" folder Not needed Needed Not needed Needed Data in SQL Db Not needed Not needed Needed Needed NOTE:  Administrator rights on the computer and to the SQL database is required in all scenarios in order to resolve this issue. In order to prevent the same issue occurring again, a log backup should be performed regularly.  Refer to Performing database maintenance with Vista 4.5.0 for additional information. Additionally, consideration should be given to whether an upgrade to full version of SQL should be installed to best suit the needs of the system.   Scenario A: Data in the $queues folder and SQL database are not needed. In this scenario, empty the $queues folder and create a new SQL database is the resolution. Please follow the steps below: Empty $queues folder Go to database folder. Its path can also be found in TAC Vista Server Setup (start->all programs/Schneider Electric/TAC Vista Server5.X.X. For TAC Vista 5.1.3 and prior, go to start->all programs/TAC/TAC Vista Server5.X.X instead).  Under “Vista Database” tab, the path is listed in the “Database folder path” textbox.   Delete everything in the $queues/insertevents folder (NOTE: don’t delete the folder). Delete everything in the $queues/insertlogvalues folder (NOTE: don’t delete the folder).   Delete taclogdata. Go to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data (default path). Delete “taclogdata.mdf” (default name, or go to Vista Server Setup and find the SQL name under SQL Server tab, Log database name). Delete “taclogdata_log.LDF “ (default name,  or go to Vista Server Setup and find the SQL name under SQL Server tab, Log database name).   Open “Server Setup” (start->all programs/Schneider Electric/TAC Vista Server5.1.X. For TAC Vista 5.1.3 and prior, go to start->all programs/TAC/TAC Vista Server5.X.X instead) and select “SQL Server” tab. Under “SQL configuration”, choose “Custom”.   Under “Custom connect using”, make a new name to “Log database name” (example:  change “taclogdata” to “taclogdata2”). NOTE: DO NOT change the user name and password.   Click Apply Click “OK” for “TAC Vista integrated SQL backup/restore function will not be available in custom configuration”.   Click yes at the prompt that says “No log database was found on SQL Server. Create and configure a log database?"   Click OK. Issue should be resolved at this point.   Scenario B: Data in the $queues folder is needed, but SQL database is not needed. If $queues folder is too big, need to upgrade to a full version of SQL database in this scenario.  $queues folder can be found inside the Vista database folder (refer to Scenario A step 1 for how to find the $queue folder). If $queues folder’s size is not too big do the following: Leave everything in the $queues folder. Data will be written into SQL database automatically after a new SQL database is established. NOTE: depends on the size of the $queues folder, it may take hours to transfer all data from the $queues folder into the SQL database.   Follow Scenario A steps 2-3 to purge the SQL database and create a new one. Issue should be resolved at this point.   Scenario C: Data in the $queues folder is not needed, but SQL database is needed. If the SQL database is needed, it can be removed from the Microsoft SQL Express folder and stored somewhere else. However, an upgraded version of SQL server is needed in order to view the old SQL database.  If the Vista version is <5.1.7Please follow the steps below: Follow Scenario A step 1 to empty the $queues folder.   Move taclogdata Go to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data (default path). Move “taclogdata.mdf” out of the folder to somewhere else (for example: Desktop). NOTE: taclogdata is the default name, or go to Vista Server Setup and find the SQL name under SQL Server tab, Log database name. Move “taclogdata_log.LDF “out of the folder to somewhere else (for example: Desktop). NOTE: taclogdata is the default name, or go to Vista Server Setup and find the SQL name under SQL Server tab, Log database name.   Follow Scenario A step 3 to create a new SQL database. Issue should be solved at this point.   Scenario 😧 Data in the $queues folder and SQL database are both needed. If the SQL database is needed, it can be removed from the Microsoft SQL Express folder and stored somewhere else. However, an upgraded version of SQL server is needed in order to view the old SQL database. Versions of Vista between 5.0.1 and 5.1.6 (which include SQL Express 2005) can be upgraded to Vista 5.1.7 or newer (which use SQL Express 2008).  This will upgrade from a 4 GB database size limit to a 10 GB limit and is a free upgrade for and version of Vista 5.1. (Note that it is a paid upgrade from Vista 5.0.X.) In scenarios where SQL Express 2008 is already being used and is full or where 10 GB will not be an adequate upgrade for SQL Express 2005 then a full version of SQL Server will need to be purchased and installed. If $queues folder is too large, it will be necessary to upgrade to a full version of SQL server in this scenario.  $queues folder can be found inside the Vista database folder (refer to Scenario A step 1 for how to find the $queue folder). If $queues folder’s size is not too big do the following: Leave everything in the $queues folder. Data will be written into SQL database automatically after a new SQL database is established. NOTE: Depending on the size of the $queues folder, it may take hours to transfer all data from the $queues folder into the SQL database.   Follow Scenario A steps 2-3 to purge the SQL database and create a new one. Issue should be resolved at this point.

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 Software installation problems with Windows 7 OS and above Configuration problems also known as UAC / User Account Control These problems occur when you receive an error message stating that you do not have the correct administrative rights to continue. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC INET, TAC Vista Environment Windows 7 Windows 8 8.1 Windows 10 Server 2012 Cause Windows 7 and above user administrator privilege settings (UAC) Resolution The solution to this issue is to turn off the user admin settings before the software is installed by following these instructions: Go to Start > Control Panel. Set the view to "small icons" to show all Control Panel icons Click on "User Accounts." Make sure that the account used for installing the software is a full admin user. On this page, click on "Change User Account Control settings", a slider bar that starts with "Never notify" up to "Always notify" by default will be set to "Notify me only when programs try to make changes to my computer" Set it to "Never notify." This will disable all the admin blocks that pop up in installing and configuring software Once set, restart the PC and then continue with your software installation and configuration Once all is installed and working, the feature may be turned back on if required. Additional requirements for Windows server 2012 and Windows 10. Please note: this process may open the "Windows 10 Firewall up" For Windows Server 2012 and Windows 10, additional steps are required to disable User Account Control. Although the slider bar can be set to “Never Notify”, the User Account Control does not disable completely. The User Account Control can be disabled for any user by setting the system registry value “EnableLUA” to zero in the system registry under the registry key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system”. A Windows registration file has been included in the Continuum 2.01 release in order to expedite these additional steps. Or the attached file EnableLUA.zip can be used, unzip and execute.  Supplement: Using the right click "run as administrator" instead of this is not the same. The right click will only run that .exe as an administrator and not the whole install/configuration package, i.e. SQL2005 manager will fail to run if you do not do as instructed above. You will always get an error stating that you do not have permission to run this program.  Alternate Windows 10 Admin. to User privilege for I/Net Seven:   Go to this path: C:\Program Files (x86)\ Inet Seven 1) Rename and move to a new folder these files.       A) INetIoSrv.exe.manifest       B) INetW.exe.manifest       C) If there is a file equalization client, then there is INetEqzMerge.exe.manifest to do this change on as well.  2) Change the DbCreate by doing this:       Another problem for non-admin users will be logging into and using DbCreate. A work-around for that would be to create a new login into the SQL database that could be shared among all DbCreate users and would provide the necessary rights.       Alternate Windows 7 Admin to User privilege for I/Net Seven:  See the attached Document and Manifest Files  

Issue Replacing a DC3000 controller. Environment Drayton DC3000 Cause The DC3000 is now obsolete. Resolution The DC3000 controller is obsolete, and there is no direct replacement available. Our current range of discrete controllers cannot provide the same functionality as the DC3000, assuming that functionality has been used. To provide the same controller functionality a programmable controller such as the Micronet or Xenta ranges will be required To upload an overview of the Micronet range, please click HERE. The Xenta controller range is listed as part of the TAC Vista Product Catalogue which can be downloaded from Schneider Electric but a table of the controllers and their I/O are shown below.

Issue How to configure the EcoStruxure BMS External Log Storage feature using PI System. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server Cause Need EBO to send selected trend logs and the event log to AVEVA PI System directly without the need for intermediate storage or specialized PI System connectors. Resolution The following video will illustrate how to: Install and configure AVEVA PI system (PI Server and PI Web API) for testing. Configure PI system settings in EBO. Configure trend logs to be written to PI system. View and organized the data in PI system Explorer. Things you need: EBO 2023 (V5.0.3) or higher with valid AVEVA PI System connection license or demo license (Enterprise Server, AS-P, AS-B or Edge Server). AVEVA PI server and PI web API with valid license (Check EBO Information Technology System Planning Guide for tested versions). For more information about PI system recommended architectures, system requirements and installation instructions, please check AVEVA documentation, PI System™ | AVEVA, OSIsoft - PI System and YouTube video published by AVEVA for detailed instructions about installing and setting up PI system Setting up a PI System Development Environment From Scratch - YouTube Note: In EBO V7.0.1 or higher, values can also be read and hosted from an AVEVA PI System, refer to: Hosting Points from AVEVA PI System

Issue Which models of the SE7300 series room controllers can be used with the SC3000 series relay packs? Product Line EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices Environment SE7300 series Room Controllers Cause The SC3000 series relay packs allows existing line voltage wiring between the fan coil unit and temperature controller to be re-used. Only certain models of the SE7000 series room controllers can be used with the relay packs.  Resolution The SER7300 is used with the SC3000. Refer to F-27797 SER7300 and SC3000 Series datasheet. Refer to the F-27777 SC3000 Series datasheet to select the appropriate relay pack for your application.  SE7000 series Room Controllers documentation can be found on The Exchange Download Center.   

Issue When trying to use WriteProperty to a 3rd Party BACnet device the following error is generated : "An attempt has been made to write to a property defined as inaccessible through the BACnet protocol write service" Product Line Andover Continuum Environment BACnet  Cause The error can be seen when using WriteProperty OR when attempting to Manually Command a BACnet Point on a 3rd Party Device Resolution The property that is being commanded, is not available to be written to in the 3rd party device. Many properties and object classes cannot be written to on BACnet devices, this is often defined in the devices PIC Statement which has hopefully also been BTL Tested. Some BACnet devices allow writing to be enabled/ disabled, but this must be set up on the 3rd Party device itself depending on the site requirements.  An example of this is in the Jace unit where there is a regular BACnet user that has no write capabilities from 3rd party devices, so to allow this requires a tick a box for "Super user".

Issue DUI-5N Digital Input Expander Module availability Product Line TAC IA Series Environment I/A Series Micronet LON and BACnet controllers Cause Third party product which Schneider Electric Asia Pacific (Invensys Building Systems) used to carry.  Resolution Schneider Electric no longer supplies this third party product. This product is manufactured by Barcol Industries in Taiwan. Anyone requiring this part should contact Barcol Industries directly. Contact Mr. Alex Lung at alex_lung@barcol.com.tw.    * Schneider Electric does not provide support or warranty for this product, all support requests should be directed to the manufacturer. An equivalent product which expands an universal input on an I/A Series MNL or MNB controller to 5 digital inputs is the BCS-DUIC-5P. This is also a third party product and is available from Schneider Electric Rockford. 

Issue How to add a third party LonWorks device? How to create a LonWorks device template? Why is a device template not available after import? Product Line EcoStruxure Building Operation Environment Building Operation version 1.8 and above Building Operation WorkStation Cause In order to add a third party device, need to create a device template (XIF file) for it. Device templates must be created in the server that the controller will created under. If a third party controller is going to be added to an AS-P that is associated to an ES, then the template must be created when logged into the AS-P directly. Resolution To import a device template   Log in to the SmartStruxure Server in which the device will be added underneath. In Workstation, Right mouse click on the Server and select LonWorks then import device Template. In the XIF file box, select the XIF file to import. Click Import. In the Template Name field, type a name for the template. Click OK. In the Import Device Template box, click Close. Now, this third party device template will be listed when adding a device into the LonWorks network. Note: If the device template refers to NVT or CPTs not on your system, you will be prompted to import necessary resource files. When the resource files have been imported, the device template import restarts. When finished, the device template is imported and available when creating a new device.