Building Automation Knowledge Base

Issue There is a need to know which card formats are supported by Continuum Product Line Andover Continuum Environment Access Control Continuum Cyberstation Cause There are many different card formats available from HID, so there is a need to know which formats that Continuum allows. Resolution Here are the formats that HID offers: 26-Bit Format: H10301 HID Proprietary 37-Bit Format: H10302 **** HID Proprietary 37-Bit Format with facility code: H10304 Corporate 1000 Formats HID Long Format Card Programming OEM Proprietary Formats (i.e. Continuum 37) 35-Bit Card Format Formats 1, 4, and 6 above are supported natively We support all the other formats (as custom cards) so long as the format does not exceed 64-bits and the format can be supplied or understood. (i.e. start/end bit of the site code, card number, etc.)   ****IMPORTANT Continuum supports a maximum of 32 bits for the Card Number field, any format above, such as the H10302, that defines more than 32 bits for Card Number field will only work if the card number range used at the site is between 1 and 4,294,967,295, any card number above 4,294,967,295 will NOT be read correctly by the controller. A possible solution for this limitation is to use the Extended Custom Cards feature supported ONLY in the ACX5720 and ACX5740 controllers.   More information about Extended Custom Cards https://community.se.com/t5/Building-Automation-Knowledge/Extended-Custom-Wiegand-features-available-for-ACX57xx/ta-p/1215 

Issue The CyberStation installation guide states that the Continuum DB Server can be run on a Windows 7 PC while the Continuum Compatibility Matrix does not. Which document is correct? Product Line Andover Continuum Environment CyberStation WebClient ContinuumDB Server Cause There are a variety of documents that describe system requirements for various Continuum products, it is unfeasible to update system requirement information in each document every time a change occurs. For this reason the Continuum Compatibility Matrix should be used as the ultimate word on Continuum products and controllers and the software and firmware that support them. Resolution The Continuum Compatibility Matrix is the ultimate authority when it comes to hardware/software/firmware compatibility.

Issue Is it currently supported in EcoStruxure Building Operation to make EWS requests with users managed by Active Directory (Windows user)? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause The EcoStruxure Building Operation software provides two methods to log on to the system, as a Windows user or as an EcoStruxure Building Operation user. Windows User A Windows user account is mapped to a Windows Active Directory user account group. Log On as an EcoStruxure Building Operation User When logging on as an EcoStruxure Building Operation user, you authenticate yourself with an EcoStruxure Building Operation account user name and password Resolution EWS only supports login to SBO domains (with Challenge Response, RFC7616) and NOT Windows domains added into SBO. It is not possible for an EWS request to authenticate using a Windows user only an EcoStruxure Building Operation user.

Issue How to clear the controller flash backup from the hardware using the reset IP switch. Environment CX9640 CX9680 CX5720/40 Cause Need to remove any backup in flash but has no access to the controller's web page configuration. Resolution Pushing and holding down the controller's reset IP switch for 30 seconds clears any backup of the database in flash in addition to resetting the IP address and ACC node id.

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

Issue Is it possible when starting Internet Explorer: To log on automatically. To start in Full Screen mode. To show a TGML graphic (without system tree) and without entering a user name and password by a shortcut. Is it possible to hide the 2 toolbars as described below? Product Line EcoStruxure Building Operation Environment Building Operation WebStation Kiosk Mode Cause For some applications such as Kiosk screens, these features are needed Resolution Automatic logon This can be accomplished either by using the "Remember me" checkbox on the logon screen, or by using the guest logon feature. To make WebStation bypass the logon screen, create a user with a username of GUEST and a password of GUEST, give this user limited permissions. For 1.7 and later, the password for the GUEST account when used for WebStation automatic logon, is not compatible with the default password policies. Automatic logon will only happen if the GUEST account password is exactly "GUEST". If policies are not changed the automatic logon will stop working after 90 days. Full Screen mode To make Internet Explorer go directly to full screen mode, you can use the "kiosk mode" switch. Create a shortcut with the command  iexplore.exe -k [insert your URL here] Display TGML Graphic without toolbars Open the graphic you require, using the "Open in a new window" right-click command. Copy the URL and create a shortcut with it. When you open this URL the user is taken directly to the graphic, without toolbars or menus.

Issue Support for OPC or DDE integration with EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Cause The OPC Server is a software program that converts hardware communication protocol into the OPC protocol. The OPC client software is any program that needs to connect to the hardware. It uses the OPC Server to retrieve data from or send commands to the hardware. Resolution Supported Functionality OPC UA Client functionality is available in EBO version 6.0.1 or higher. Refer to: OPC UA Client Support Currently Not Supported OPC UA Server OPC DA Client/Server DDE Configurations Alternative Integration Options If integration with unsupported protocols is required, consider the following alternatives: Protocol Conversion Use a converter to translate between OPC and a protocol supported by EBO. Examples: OPC Server → BACnet Server EBO BACnet Points → OPC Recommended 3rd Party Tools (not supported by Schneider Electric): Kepware Matrikon SCADA engine Note: Ensure the EBO server's role is clearly defined (e.g., exchanging point values) to determine compatibility. SmartConnector Extension Use a SmartConnector Extension as middleware between EBO and an OPC client/server. Resources: Exchange shop SmartConnector Server EBO SmartDriver and Smart Connector Additional Notes These integration methods involve 3rd party software and may require additional configuration and validation. Schneider Electric does not provide support for 3rd party tools.

Issue Actuator M44 is no longer available (withdrawn in 2000) and needs a replacement. Environment M44 M9B EM9 Forta Cause Depending on application, since the M44 was used for both rotating and sliding valves, a few different replacement actuators could be used. Resolution For valves with rotating stem, (TRV, VTRA, VTRE and STMG), actuators M9/EM9 can be used. For valves with linear moving stems the TAC Forta series actuator is used.

Issue Need to change from the Small Number Format (Card Number) to the Large Number Format (Facility Code + Card Number). Requirement for Security Expert Transitions with I/NET Hardware.   Badging card on SCU1284 Reader using Security Expert, the reader event displays "Format error RD xx Port x Error Number of Bits" From Security Expert Client Events Product Line TAC INET, EcoStruxure Security Expert Environment I/NET Seven Security Expert Transitions Cause The I/NET system is limited to a maximum number of access cards, 32,000 per Tenant.  If a larger number is required, then I/NET must be configured to use large card numbers.  The Large card number format described in the Resolution MUST be completed before transitioning from I/NET to Security Expert and utilizing the I/NET SCU hardware as detailed in the Transition Guide Security Expert - INet Access Control to Security Expert - Reference Guide. Resolution To convert I/NET to use the Large Card Number support, the following steps must be performed:  Conversion of Card Numbers (small) to Large Numbers Sort the Individuals list according to the Individual Number. Look in the Individuals Editor “Options” function to set this up. Look at the tenant editor to determine the Tenant Code/ Facility code of the cards. From this, use the circled items the Tenant Code (Facility Code) and the First Individual Number as the lowest possible card number in the next step.  Verify in the door editor that the cards in this system are in a known Wiegand bit format.  In this case, we are using 26-bit. Attached are various Excel spreadsheets that can determine the Decimal number of the first card in the system (e.g., Card #970 Facility code 199) is the Decimal number 13042634, using a 26-bit Wiegand Excel spreadsheet.  This number will become the Source number in the Key/Card Translation table. These include 26-bit 32-bit ABA115 format Create a Key/Card Translation table similar to that shown below in the I/NET Seven Access Control editor.  This table will be removed after running the provided SQL Script.  The Key/Card Translation must contain: Source - Decimal number calculated in Step 3 above (13042634) Target - First Individual number shown in the Tenant (970) Count - Number of Individuals as shown in the Tenant (10000) Tenant - Tenant number this translation refers to (1) If there are multiple Tenants, then this process MUST be repeated for each Tenant Tenant Editor and Key/Card Translation Editor Shut down I/NET completely and run the attached SQL Script. Then once the script runs then, restart I/NET and look in the Individual Parameters editor, as shown below. Start I/NET and delete the Key/Card Translation table create above. Open the Individual Parameters and verify a Hex number and the decimal number matching that from the Excel spreadsheet (Step 3) is seen in the Individual Editor Card section. NOTE: There may be multiple card entries here; the Last entry shown is that entered by the SQL Script.  It will depend on whether an existing Card entry was entered for the Individuals before running the SQL Script.  To have large numbers working on a site DipSw #7 has to be turned ON for the 7910/7920 DPUs. For the SCU1284 in the door editor, at the top center of that editor, there is a check box, "Card Translation," which has to be enabled for large numbers to work in the SCUs. An SLI “SAV” should then be done because that is where the Card numbers and Door settings are stored. Then perform an SLI restore. Followed by a DPU restore to all of the door controllers. NOTE: Steps 6d. and 6e. are NOT required when performing the transition to Security Expert as this information will be performed by the SP-C.   

Issue Script programs in b3 controllers will not autostart after reboot of the controller Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation AS-B Cause The program is not configured to autostart in StruxureWare Building Operation. Resolution In the Properties of the program object, ensure that the Autostart field is set to True. For further information on these properties please refer to Webhelp

Issue Launching Continuum results in error "This workstation is currently unable to connect to the database. Click OK to exit." Also, running Continuum DB initialization results in error: SQL Server [server name] does not exist or access denied. Workstation Setup Failed! Please try again or click Cancel to exit. Environment CyberStation LAN system Cause Fire wall on the server machine is blocking TCP port 1433 Another cause for this happening is a Windows firewall or McAfee firewall being enabled and blocking the IP of the 2nd Cyberstation that is trying to connect. Resolution Disable fire wall at the server or add an exception for TCP port 1433 (or the port used by the client to get access to the server if different).

  Issue Using graphics in WebStation, “MutationEvents not defined” error messages and/or data in not shown correctly, after the web browser used is upgraded to latest versions.     Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation WebStation Google Chrome v127 and later Microsoft Edge v127 and later Firefox v140 and later Cause After upgrading to the latest web browser versions EcoStruxure Building Operation web-based user interface, WebStation, in all released and supported versions may no longer operate correctly when graphics are attempted to be displayed. The symptoms include, but may not be limited to, failure for graphics to show data correctly and error prompts such as “MutationEvents not defined” being shown. As referenced in Mutation events will be removed from Chrome  |  Blog  |  Chrome for Developers, Google has deprecated these Mutation events and replaced them with a different function. Also as referenced in Firefox 140 for developers - Mozilla | MDN The  MutationEvent  interface and its associated events have been removed from Firefox build 140 onwards. Resolution Consolidation point releases are available for supported EBO versions to resolve these compatibility problems with the latest browsers. These releases are available to authorized Schneider Electric EcoXperts and employees only from the EBO Hotfix List in the EcoExpert Community and the Software and Firmware Center of the EcoXpert Extranet. Other customers should contact their local Schneider Electric EcoXpert or Schneider Electric office and arrange a service visit.   The issue is addressed in the following releases: EcoStruxure Building Operation 3.2.4 : EBO 3.2.4.7003 (CP5) onwards EcoStruxure Building Operation 4.0.5 : EBO 4.0.5.5001 (CP4) onwards EcoStruxure Building Operation 5.0.3 : EBO 5.0.3.12005 (CP11) onwards EcoStruxure Building Operation 6.0.3 : EBO 6.0.3.2001 (CP1) onwards EcoStruxure Building Operation 7.0 Unsupported versions such as EBO 3.1 and earlier will not be addressed. Upgrading to the latest version of EcoStruxure Building Operation is strongly recommended to ensure full compatibility with current web browsers and to benefit from the latest features and security updates.

Issue Satchwell MJF 3-Port Flanged Valve Body requires replacement. Environment Satchwell 3-Port Plug and Seat Flanged Valve Body MJF3426    MJF 3426 MJF3427    MJF 3427 MJF3476    MJF 3476 MJF3526    MJF 3526 MJF3576    MJF 3576 MJF3626    MJF 3626 MJF3676    MJF 3676 Cause Obsolescence of Satchwell MJF 3-Port Flanged Valve Body Resolution Replace Satchwell MJF 3-Port Flanged Valve Body with S-E V311 3-Port Flanged Valve Body of appropriate size N.B. Existing Satchwell Actuator installed on MJF 3-Port Flanged Valve Body may be retained for installation on replacement   S-E 3-Port Flanged Valve Body.  In such instances a S-E L8TV Linkage Kit will additionally be required.  Alternatively an Actuator from the S-E range of Actuators may be installed on the V311 3-Port Flanged Valve Body, in which case no additional Linkage Kit will be required. IMPORTANT NOTE It should also be noted that the face to face dimension of the S-E V311 3-Port Flanged Valve Body differs to that of the Satchwell MJF 3-Port Flanged Valve Body  Similarly, the centre line to bottom of third port dimension of the S-E V311 3-Port Flanged Valve Body differs to that of the Satchwell MJF 3-Port Flanged Valve Body  As a result alterations to the pipework connected to the MJF 3-Port Flanged Valve Body will be required. Details of the Satchwell MJF 3-Port Flanged Valve Body may be viewed here. Details of the S-E V311 3-Port Flanged Valve Body may be viewed here. Details of the S-E L8TV Linkage Kit may be viewed here.

Issue Can Extended Log data be removed from the Database by de-selecting the extended logging option in the point being logged or by deleting the point all together? Environment Continuum Cause Need to reduce the size of the Database by removing stored Extended Log data. Resolution Any point data logged as Extended Log data will only be removed from the Database during an automatic purge or manual truncation of the tables. This extended log data does not get removed when extended logging is disabled or the point is deleted from the database, this data remains until removed. To setup automatic purging you'll need to go to your Continuum General Preferences. Right-click Continuum icon in task tray and select General Preferences, you will find an entry for "Extended Log Automatic Purge Interval (days)". This needs to have a number assigned to it to determine how many days of ExtendedLog data is retained in the ContinuumDB. If this is 0 then nothing is deleted and all data is retained (the suggested value for this is somewhere around 30 -90 days depending on your DB size restrictions and retention requirements).

Issue Starting in EcoStruxure Building Operation 2.0, a new licensing structure has been implemented to reflect the new scalable pricing model.  This new pricing model is different from previous versions. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Version 2.0 and up Cause Due to the change in our pricing model within EcoStruxure Building Operation 2.0 and later, we have new policies regarding scalable pricing which has been different in the past. Resolution In regards to questions around the new scalable pricing structure For EcoStruxure Building 2.0, please reference the sources below. EcoStruxure Building Operation Scalable Pricing Frequently Asked Questions EcoStruxure Building Operation v2.01 - Scalable Pricing Policy Scalable Pricing Overview Video - EcoStruxure Building EcoStruxure WebHelp Article about Licensing Model General Notes: An upgraded or newly purchased 2.0 license will work with sites running older versions of EcoStruxure Building Operation. Each Enterprise Central and each Enterprise Server license comes with one client license.  It will always be possible to operate the system and will always be possible to add to the system (besides attaching automation servers to the enterprise server) if you do not have enough licenses. After certain time periods, the warnings, banners, and prompts will get larger and more noticeable.  If ONLY hosting IP devices and no Automation Servers under the Enterprise Server, it is still necessary to purchase the minimum size Enterprise Server license (10 or fewer Automation Servers) as well as then the appropriate number of hosted node licenses.  The intent of this is to limit the development and support costs of having a highly resourced user interface at the Enterprise Server and to distribute this load across multiple servers.

Issue Getting error "Failed to run: import-VM" when trying to install PCTv2 Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Could install PCTv2 fine but the issue started when going back and forward between PCTv1 and PCTv2 so that might have caused the issue. Resolution Uninstall Hyper V in Windows Programs and Features and restart computer Delete everything in ProgramData\Microsoft\Windows\HyperV Install PCTv2 version 2.0.2.13 or later

Issue Upgrading a JACE-8000 or Edge-10 from 4.10U7 to 4.11 or 4.12 will prevent Niagara Daemon from starting.  You will be unable to connect via Workbench or Browser. Product Line TAC IA Series Environment I/A Series N4 Jace 8000 Tridium Edge 10 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. Cause The software in builds 4.10u7 and later LTS builds (4.10u8, 4.10u9, 4.10u10) was released after 4.11 and 4.12 reached EOL.   4.10u7 contains a newer signing key that is not recognized by 4.11 and 4.12. Resolution When upgrading JACE-8000 and/or Edge 10 running 4.10 LTS builds 4.10u7 and later, please skip over 4.11 and 4.12 and instead upgrade to 4.13u3 or newer. Alternatively, you may apply the dist that reverts JACE-8000 to clean 4.9u1 state, or for Edge-10, the dist that reverts it to clean 4.7 state. You can then install 4.11u2 or 4.12u2, if that's the version you have to use.  If you've already attempted the commissioning operation and bricked a device, and have backups, you can connect to the debug port and use the factory reset process per the documentation.  For Edge 10, consult the section titled Factory Default Recovery  in the Niagara Edge 10 Install and Startup Guide.  For JACE-8000, consult the section titled Restoring factory defaults  in the JACE-8000 Backup and Restore Guide. If you are lacking any backups for the host, then before performing the factory reset, you should enable SSH/SFTP via the debug port, and then copy out the Station files using Filezilla or WinSCP or equivalent.  Reach out to your support channel if you have difficulty finding the location of station files. Typically, the files will be in a subfolder of /home/niagara/stations. The config.bog file will be keyring encrypted, and you'll have to reset it using the Bog File Protection Tool. See Editing the .bog file passphrase offline in the Niagara Platform Guide  for details on using the Bog File Protection Tool.  For details on using the debug port on JACE-8000, see Debug port  in the JACE-8000 Install and Startup Guide.  For details on using the debug port on Edge-10, see Connecting to the debug system shell  in the Niagara Edge 10 Install and Startup Guide.

Issue The controller installation guides detail how to display the values in Water Column (WC), but how can this be displayed in metric units? Product Line Andover Continuum Environment Infinet controllers (i2865 & i2865-V, i2866 & i2866-V , i2885, i2885-V, i2850 &i2853 ) BACnet controllers (b3865 & b3865-V, b3866 & b3866-V , b3885, b3885-V, b3850 & b3853) Cause A conversion to metric units (Pascals) is needed. Resolution i28xx type of Infinet Controller has 0-2" WC (Water Column) range which corresponds to 0-2V so the input value can be read directly in WC. The 850 has a single airflow sensor on channel 8 The 853 has two airflow sensors on inputs 7 and 8 For 865, 866, and 885 the airflow sensor is on Input 7 Always use input type Voltage Set the units to Pascals The following conversion can be used on the conversion line: ElecValue * 500 The i28xx-V type of Infinet Controller has 0-1" WC (Water Column) range. For 865-V, 866-V and 885-V, the airflow sensor is on Input 7 Always use input type Voltage Set the units to Pascals The following conversion can be used on the conversion line: ElecValue * 250  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. Also see Setting up the override value to show the damper feedback on an i2/B3 866-V for details on reading the damper feedback on the i2/b3886-V.

Issue One of the following error messages are displayed. Internal server error Server already part of a system Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation Server Cause Version Mismatch: The Automation Server is either not the same version as the Enterprise Server or it is still connected to a different Enterprise Server. If the Automation Server is still connected to another Enterprise Server then it must be detached before it can be added underneath a new Enterprise Server. User Permissions: In some instances, the User Permissions "System Address" is not added to the user account that is attempting to add the server.    Resolution If you are given an error that states "Domain: Internal Server Error" then you need to download the same version of firmware to the AS that is installed on the ES. Resolution #1: Detach the Automation Server Log in to the Automation Server.   In the system tree pane, right-click on the automation server and go to Advanced > Detach server.   The Disconnect Automation Server window will open; click yes.   The Automation Server is now detached and can be added to an Enterprise Server. Resolution #2: Verify User Permissions Check a current backup using the SBO xbk Analyzer and verify the number of servers listed under Reports>Servers Log on using the default admin account and see if these servers exist. Detach the server(s), as described above. If the secondary user still requires permission to add and see ALL servers: Go to the user and select the Permissions tab Ensure the ES path is selected Click on the Add System button (identified with the arrow) Enable all options to allow read/write, create etc.  Save these changes and log off and back on with this user to see the changes. This user should now be able to add/see ALL servers.

Issue Sites using Report Server need to upgrade to EcoStruxure Building Operation (EBO) 2022 or higher, where WebReports/Report Server is no longer supported. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Report Server Building Operation Timescale Database Cause WebReports/Report Server is not supported in EBO 2022 (version 4.0) or higher. Resolution To address this, Schneider Electric provides a Data Migration Assistant (DMA) tool that: Reads data from WebReports 3.x Writes data to External Log Storage Download the DMA Tool External Log Storage Overview Stores historical data from EcoStruxure BMS Storage capacity is limited only by your hardware Historical data is displayed in WorkStation and WebStation (event and trend views) Any server can be configured to write data to TimescaleDB   Any server in the system can be configured to write historical data to the TimescaleDB database. Licensing Requirements External Log Storage requires a license Refer to: Software and Features that Require Licenses Part Number Summary and Hardware Software Matrix Hardware & Software Requirements Ensure compatibility with: TimescaleDB PostgreSQL Recommended specs for large systems (e.g., 100 BMS servers): High-performance SSD Minimum 64 GB RAM Additional CPU capacity Refer to: IT System Planning Guide Merging Log Data External Log Storage reduces extended trend logs on BMS servers You can merge extended trend logs into source logs in External Log Storage See: Merging of Trend Log Data Enhanced Reporting (XLSX Templates) EBO servers (v3.2 or higher) support native reporting with: Text and XLSX formats Advanced XLSX features: formulas, conditional formatting, charts, sparklines Historical data pulled from External Log Storage (PostgreSQL/TimescaleDB) Refer to: Examples for Native EBO Notification Reports