Building Automation Knowledge Base

Issue String Bindings between Infinet Controllers fail Product Line EcoStruxure Building Operation Environment Infinet Controllers I2 Controller String Transfer Cause Direct string transfers between Infinet Controllers were possible in Continuum (via an import PE Program), but not in EBO via Script Program Resolution Following a Continuum Conversion, direct string transfers (via an import PE Program) downloads correctly but the Strings do not update. This type of transfer is not seen often, but was possible in Continuum. See the Knowledge Base article Passing InfinityString object between Continuum controllers Details in "Infinet Troubleshooting" in "Technical Reference Guide" from version 4.0.2 Also see WebHelp The workarounds are Bind string values direct (object to object), but this will force an EBO transfer via the ASP, so if the AS is not available the transfer will fail. Also more bandwidth is used. Rewrite the script to avoid using string transfers, by using numerical Objects

Issue Upgrading Visio. Should WorkPlace Tech be uninstalled first? Product Line TAC IA Series Environment I/A Series WorkPlace Tech Cause Software upgrade Resolution Un-install both WorkPlace Tech and Visio.  Then install Visio following the instructionsWorkPlace Tech Installationand Workplace Tech 5.10.4 Release Notes 

Issue When attempting to run standalone WorkPlace Tech the following message is displayed. After attempting to launch Microsoft Office Visio, WorkPlace Tech was unable to access Visio functionality. Product Line TAC IA Series Environment Workplace Tech version 5.8.X and 5.9.X Microsoft Windows 7 and Windows 10 Microsoft Office 2013 and Office 2016 Microsoft Visio 2010 and 2013 Other versions of Office and Visio may apply.  These have known issues corrected by this procedure Cause A non-approved version of Microsoft Visio (Visio 2013/2016) was installed. Microsoft Visio 2013/2016 was uninstalled and replaced with Microsoft Visio 2010 SP2. It is suspected that the uninstall of Microsoft Visio 2013/2016 left behind files causing this issue. Resolution Uninstall Workplace Tech, Visio 2010 SP2, and Office 2013 and reinstall the software in the following order: Microsoft Office 2013 or Office 2016 Microsoft Visio 2010 SP2  Workplace Tech 5.8.X or WPT 5.9.X Run Visio standalone, shut it down, and then run WorkPlace Tech.

Issue When importing an application file created or previously edited with release 3.2sp1 of WorkPlace Tech, a "Workplace Tech Tool - Visio" error window is displayed:  "Cannot find the WorkPlace Tech add-ons for Visio.  WorkPlace Tech functions will be unavailable" Product Line TAC IA Series Environment WorkPlace Tech Tool software release 5.7.4 WorkPlace Tech application file created or edited with WorkPlace Tech Tool software release 3.2sp1. Cause The Visio stencil pages referenced in the application file cannot be found in the location specified in the application file. Resolution This is not a fatal error.  It occurs because WorkPlace Tech cannot locate the Visio object stencil files referenced in the existing application drawing file.   Click the [OK] button to ignore the error message and continue with the application file upgrade.  The error message is displayed because the default location for the stencils has been moved starting with WorkPlace Tech version 5.7.4.  During the application file upgrade, the proper stencils, as specified in the original application file, will be located and attached to the application. After clicking the [OK] button, WorkPlace Tech will display a Windows message box indicating that the application must be converted to WorkPlace Tech (WPT) 5.0 format before it can be modified or downloaded.  The message ends with a prompt asking the user if they would like the application converted.  Clicking [Yes] will allow WorkPlace Tech to process the application file and convert it to the current file format.  This is the required choice if the user intends to use the imported application in the current version of the WorkPlace Tech Tool software. Clicking [No] will bypass the conversion leaving the incompatible application open in WorkPlace Tech. Clicking [Cancel] will abort the import process.

Issue The BACnet object goes into fault when writing a NaN to an MNB controller. Product Line TAC IA Series Environment I/A Series MNB VAV I/A Series MNB 70 I/A Series MNB 300 Cause Firmware 1.424 and higher responds to receiving a NaN with an Error: "value out of range".  In firmware 1.420 it would accept the NaN and respond with a normal acknowledge message.  This is a result of a change required for BTL compliance. Resolution A slight setup change can accomplish the same result without causing the object to go into fault.  In the ENC edit the properties of the AVSPP object and set the fallback to "null".  Go to the slot sheet of the object being overridden to hide the "Set" option.  This will prevent the operator from attempting to send a NaN that causes the fault.  When a right-click override is performed only the emergency (priority1) and Override (priority8) choices are displayed.  When the override expires or the object is manually put back into “auto” the “fallback” value is output which is “null” and that is accepted at the controller and serves the same function as sending a NaN.

Issue Cannot access SP-C web interface due to TLS error. Chrome error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH Edge error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH Firefox error: SSL_ERROR_UNSUPPORTED_VERSION Product Line EcoStruxure Security Expert Environment Security Expert Controller (SP-C) Cause As per the table below, SP-C with OS  2.0.24 or lower does not support TLS 1.2.  A modern web browser will block access to sites that use TLS 1.0 or 1.1.     Resolution  If TLS 1.2 support is required, an OS upgrade to 2.0.25 or higher is required: Upgrade the controller's firmware to a version that supports HTTPS, as explained in:  AN 314 Security Expert - HTTPS Connection to the Security Expert Controller - Integration Guide If the current SP-C OS version is 2.0.24 or lower, contact Schneider Electric support to acquire the upgrade package and further documentation.

Issue Details on how Modbus IP Multiple Queries and Multiple Query Packets work Product Line EcoStruxure Building Operation Environment Building Operation SmartX Servers Modbus IP Cause Understanding of how the Modbus synchronous and asynchronous transport layers differ. Resolution By default, the Multiple queries is Disabled, this is the synchronous transport layer. To enable the asynchronous transport layer the Multiple queries must be Enabled within the Modbus TCP Network properties as shown below. Setting to "Enabled" allows multiple queries (packets) to be sent to multiple Modbus devices, thus reducing wait times.  It also enables further settings in the Modbus Device properties "Maximum concurrent queries" and "Multi-query packets".   The maximum concurrent queries and multiple-query packets as shown below are configurations for the Modbus asynchronous transport layer. The Maximum concurrent queries setting is only enabled if the "Multiple queries" is enabled in the Network Properties. When enabled, this allows the "concurrent queries" to be sent as a single packet.     Modbus Synchronous Transport Layer Each Modbus query is sent out one after the other. Before sending out the next query the transport layer waits for a specified period for the previous query. Example Poll Sequence Device No. Objects 1 2 2 1 D=Device, Q=Query, R=Reply D1 Q1 Send D1 R1 Receive  D2 Q1 Send D2 R1 Receive  D1 Q2 Send D1 R2 Receive  If it takes 1 second for the device to reply, then this sequence would take 3 seconds. Modbus Asynchronous Transport Layer With the asynchronous transport layer enabled, the queries are transmitted to multiple devices at the same time. The maximum number of queries that are transmitted to that one device is controlled by the “Maximum concurrent queries” setting. The “Multiple-query packet” specifies whether the queries are transmitted in one TCP frame or not. Simple Example Poll Sequence Device No. Objects Multiple-query packet Maximum concurrent queries 1 2 False 1 2 1 False 1 D=Device, Q=Query, R=Reply D1 Q1 Send D2 Q1 Send D1 Q2 Send D1 R1 Receive  D2 R1 Receive  D1 R2 Receive  If it takes 1 second for the device to reply, then this sequence would take 1 second Complex Example Poll Sequence Device No. Objects Multiple-query packet Maximum concurrent queries 1 10 True 5 2 4 False 2 D=Device, Q=Query, R=Reply D1 Q1, Q2, Q3, Q4, Q5 Send D2 Q1 Send D2 Q2 Send D1 R1, R2, R3, R4, R5 Receive  D2 R1 Receive  D2 R2 Receive  D1 Q6, Q7, Q8, Q9, Q10 Send D2 Q3 Send D2 Q4 Send D1 R6, R7, R8, R9, R10 Receive  D2 R1 Receive  D2 R2 Receive  If it takes 1 second for the device to reply, then this sequence would take 2 seconds   NOTES The use of this feature should be avoided before EBO v3.1, there is also a defect in EBO v3.2 that means v3.2.3.5000 should be used (minimum) Some Modbus devices do not support multiple queries or multiple query packets, so the feature should be tested on an individual basis. (Some devices may even go offline until manually reset) This feature will increase the CPU usage on the EBO server. It should be avoided on EBO Servers that are already heavily loaded This feature also has the ability to reduce the system stability, it is usually better to optimize the use of Modbus Register Groups to increase performance

Issue How to discover MNL Lon devices or other Lon devices in an SmartStruxure Automation Server. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Cause Use the below instructions when you need to find all Lon devices on a Lon network. Resolution To discover a LonWorks device In WorkStation, in the System Tree pane, select the server that is connected to the device you want to discover. Click the Device Discovery view. In the Select device type box, select LonWorks. Select the Devices folder. Right click on the Devices folder and take "Scan network for devices" In the Device Discovery view, ensure that the LonWorks device is displayed in the Devices folder. This may take up to 5 seconds. Drag the discovered device to the System Tree pane: Drag to an existing device to associate it with the discovered physical device. Drag to the LonWorks network to create the device.   NOTE: You cannot drag a standard MNL LonWorks device to the System Tree pane if the discovered device is in an unconfigured state For more information, refer to the Creating and Configuring a LonWorks Network with MNL LonWorks Devices [102423].pdf document 

Issue SmartConnector 2.5 uses the Flexera licensing model. Version 2.4 and below used native licensing. How can the existing license be upgraded for SmartConnector 2.5? Product Line EcoStruxure Building Operation, Flexera Environment Building Operation Enterprise Server Flexera FlexNet Operations Cause SmartConnector 2.5 uses the Flexera licensing model. That means you will license SmartConnector using the License Administrator interface. Prior to version 2.5, SmartConnector licensing used a native licensing model.   Resolution SmartConnector 2.5 will still support the native licensing structure that we have for SmartConnector today for its core license. The way this works is as follows...   There are two parts to SmartConnector licensing.  There is the core, or runtime license which is used to license the web portal and the windows service. There is a second part that licenses the integrations and SmartConnector extensions.  These are licensed separately. When installing SmartConnector for the first time at version 2.5 a single comprehensive license (incorporating the core and integrations licenses) is purchased.  This license is applied using the License Administrator application.   In cases where SmartConnector is being upgraded from a pre-2.5 version, the core license will remain installed as a native license. Your integrations license upgrade would be installed using License Administrator.   Obviously, with SmartConnector you could run lots of different extensions on the same machine. You would still only have one SmartConnector core license but you would license your extensions individually. So you could have many integration licenses running on the Flexera server, while your core license remains in place.

Issue How to find out if a user has created a personal and/or a public dashboard Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation Cause Customers may want to know if there is a personal or public dashboard (or both) under a user Resolution We can search in Workstation to know if a user has created a personal or public dashboard (or both). Enter “Dashboard” on the “Include type” and search over the whole server.   Public dashboards can be created by any user anywhere under the server except under the system tree. In the following example, any results that appear under the “/Server 1/System/Domains” is a personal dashboard since it is tied to the users, and the rest are public dashboards.     Please note that creating a personal dashboard requires a Personal Dashboard License.    How Dashboards Work  Public vs Personal Dashboards  

  Issue When adding an Enterprise Server (ES) to Enterprise Central (EC), the process fails with Error - Object Does not exist Domain: Data Access. Details: Modules: Connect Plugin Module Code 73 Trace log shows the following text: nsp.csc.csm.ChangeSetTransaction Rollback due to Data Access Error: Object_Does_Not_Exist (0x40004) in module Connect_Plugin(73), moduleCode=73. "" nsp.csc.cspclient.AddServerCommandPassThrough Execute: Data Access Error: Object_Does_Not_Exist (0x40004) in module Connect_Plugin(73), moduleCode=73. "" nsp.csc.cspclient.ConnectionPool Terminating. GetConnection aborted [IP Address: port#] Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central  Building Operation Enterprise Server  Registered System Cause In this instance, the ES added to the EC is currently registered.  Registered Servers can only be the parent server and therefore cannot be added to a non-registered system or a different system.  Parent servers can only be registered, and any sub-servers inherit this registration from the Parent sever.    Resolution The registration should always be on the parent server. To remove the registration from the ES, the SystemID needs resetting as per the following procedure:  Resetting the System ID Once reset, the system is no longer registered, and adding the ES to the EC will be successful. 

Issue SP-RDM2 Reader Expanders running firmware 1.12.544 appear to fail whenever an attempt is made to update their firmware revision. Product Line Security Expert Environment SP-RDM2 SP-MRDM2 Cause There is a known defect in 1.12.544 (Build .544) which prevents the SP-RDM from being upgraded or even downgraded. However, a number of SP-RDM units have been shipped from the factory with this build pre-installed. Any attempt to select an SP-RDM running this firmware and upgrade or downgrade it to a different revision will consistently fail with an error: 'Module not responding'. There is also a possibility that the SP-RDM can be permanently disabled in the process Resolution Since the .544 Build defect cannot be resolved the only recourse at this time is to swap out the unit via the Returns Material Advice (RMA) process for a new unit.      List of SP-RDM2 Serial #s affected thus far: Note: All other SP-RDMs running firmware both above and below .544 Build are unaffected

Issue A method is require to provide an Executive Privilege function to a Door to allow tailored credential requirements for specific Users. Product Line Security Expert Environment Security Expert Cause Doors are currently set up for two credentials (Card + Biometric) but there is a need to allow certain Users access through those Doors without having to present the second credential. Resolution The Access Level Door Type feature allows for this functionality. The option overrides the Door's Door Type with the one set in the Access Level (e.g. to allow a VIP to override 'Card + Biometric' to just 'Card' at a door). Required Objects Door Type Access Level User Configuration In the Door Type set the Access Level Door Type to the door type you wish to use whenever Access Level Door Type is enabled - in this example it would be "Card". Fig.1 - Door Type In the Access Level enable the Use Access Level Door Type option. Fig. 2 - Access Level Assign the Access Level in step 2 to your User. Fig. 3 - UserFor a Video KB article showing a similar configuration process see:  Security Expert user specific access vs standard door access 

Issue What actuator can be used as a replacement for the MF-63123? MF-631x3 Series_F_24732_8.pdf (209 KB) MFC 8000_F_25124_4.pdf (260 KB) Product Line Field Devices Environment MF-63123 Cause Original actuator has failed, or requirement for a non US actuator. Resolution Using the installed valve details, the actuator can be selected from the Schneider Electric Valve and Actuator selection Tool.

Issue There isn't enough documentation on how to disable the different connection protocols. I.e. TLS or SSH. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server Cause Increase the security of the system. Resolution SSL Communication Security Settings: You can edit SSL configuration in WorkStation Control Panel's Security Settings or in the Device Administrator SSL Security Settings tab. SSLv1,v2,v3 are all implicitly disabled. In EBO 2022 (4.0) or higher, TLS 1.3 is available and used as default when logging on with WebStation and for server-server communication with HTTPS. TLS 1.0 and TLS 1.1 are by default disabled but can be enabled in Control Panel. WorkStation is using TLS 1.2, disabling it would prevent logging on to WorkStation. In WorkStation, the only valid protocols are shown when you hover the mouse over disabled protocols. See below.   SSH Port: Port used for communication with Device Administrator can be disabled or changed so that the automation server communicates on another port using SSH. It is also possible to disable all SSH communication. SSH communication settings are available in Automation Server Properties – Network Tab, as shown below. Refer to Disabling Port 22 on SmartX Server and Adding an Additional SSH Port for a SmartX Server .  For more Security guidelines,  refer to EcoStruxure Building Management - System Hardening Guide, Security Overview, and Information Technology System Planning Guide 

Issue What SQL collation is supported by CyberStation Product Line Andover Continuum Environment CyberStation SQL Server Cause Which SQL collations are supported by CyberStation. Resolution Only the SQL_1xCompat_CP850_CI_AS collation has been tested with CyberStation. Note: In more recent versions of SQL server (i.e 2005), you can have the Collation on a per-database basis so ContinuumDB will have its collation set to SQL_1xCompat_CP850_CI_AS and another database can use a different collation setting. Also when the continuum database is restored it will retain the original collation that it was created with.

Issue CyberStation is unable to connect to the database. ODBC test also fails when testing the connection to the database. Product Line Andover Continuum Environment CyberStation SQL server SQL management studio Cause SQL server not on UPS. Server shut down due to a power failure. Looking at the ContinuumDB using the SQL Management Studio shows the database has been marked as suspect.  ContinuumDB (SUSPECT) The database may be marked suspect for the following reasons System Issues Transaction Log File is Missing SQL Server Crash Database Files are inaccessible SQL Server Database Operation Failures Due to Improper shut down of SQL Server System (as mentioned above) Due to Sudden Power Outage Low Disk Space Issues Hardware Failure Resolution The database may have been damaged by the ungracious shutdown. The restore option is grayed out and must first be re-enabled before a restore operation can be allowed. How to recover a database in suspect mode Clear the suspect mode of the database using sp_resetstatus DatabaseName. This will clear the suspect flag and make the database available online. The SQL Server must be stopped and re-started. Change the database status to Emergency using the following command. ALTER DATABASE DatabaseName SET EMERGENCY; Restrict database to single user by changing the access mode as mentioned below ALTER DATABASE DatabaseName SET SINGLE_USER; If the restore option is now enabled skip step 4 Run the CHECKDB command with “REPAIR_ALLOW_DATA_LOSS” option. This option should be tried as the last option as it always behaves the way it is named. We are not sure of what data it removes. DBCC CHECKDB (DatabaseName, REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS, ALL_ERRORMSGS If the repair operation is successful the database is now usable but if a recent backup is available it is strongly recommended to restore the database. Restore the most recent backup of the Continuum database. Set the ContinuumDB owner using the query SP_ChangeDBOwner 'Andover97'  

Issue A b3 controller that is shown as offline in CyberStation can incorrectly change to online when RoamIO2 is connected to the bus.   Product Line Andover Continuum Environment RoamIO2 bCX CyberStation b3 Cause When a RoamIO2 is connected to the MSTP bus and the BACnet Service Tool software is started, it assigns itself a BACnet MAC Address. It may assign itself the BACnet MAC Address of an offline b3. If at the same time you are running a listview of b3 controllers on that bus in CyberStation, and displaying commstatus, the offline b3 with that BACnet MAC address will appear online. However, attributes such as VersionNum, BACnet DeviceID, Port, and InstanceID will be blank in the listview - tipping you off that this is bogus.   Resolution Be aware of this situation and add the attributes described in the cause section above to confirm what you are seeing.  

Issue Receive an Error message "Outlook not installed"  when starting  Continuum Product Line Andover Continuum Environment Windows 7,  64Bit Continuum  1.9X Microsoft Outlook  64 Bit. Cause Outlook 64 Bit is not supported at this time. Resolution Uninstall 64-bit Outlook.  Then install 32-bit Outlook.

Issue The SQL Server 2008 is running the 64-bit version as well as the Continuum Workstations are using 64-bit Operating Systems. In the interest of increasing the SQL access speeds can the ODBC connection between them also utilize the 64-bit ODBC driver? Product Line Andover Continuum Environment Continuum v1.94 (or greater) Microsoft SQL Server 2008 64-bit Microsoft SQL Server 2012 64-bit Microsoft SQL Server 2014 64-bit Microsoft SQL Server 2016 64-bit Cause Want to know if the SQL access speeds can be increased by taking advantage of using the 64-bit ODBC drivers. Resolution The Continuum application itself is a 32-bit application, this will require the 32-bit ODBC drivers to make a connection to the SQL Server. Even though we support Continuum in a 64-bit environment, it is still only a 32-bit application so the 32-bit ODBC drivers are used for the SQL connection. Be aware that this is just the communications on the SQL side, the SQL application itself will still process data at 64-bit speeds if the 64-bit version is used.