Building Automation Knowledge Base

Issue bCX9640, CX9680, ACX5720 and ACX5740 do not have ACCRestartMode system variable. Product Line Andover Continuum Environment CyberStation bCX9640 CX9680 ACX5720 ACX5740 Cause The restart mode of the second generation Infinity CX controllers (9640, 9680, 5720/40) is not user selectable. Resolution The second generation Infinity CX controllers (9640, 9680, 5720/40) have a fixed startup sequence as follows: Warm to Cool to Cold, meaning the controller will ALWAYS first attempt to WARM start, if warm start is not possible the controller will attempt a COOL start, if cool start if not possible the controller will attempt a COLD start. Warm start: Controller is re-starting with its RAM memory intact because the controller has remained powered or the memory has been kept by the battery. In this case all the configuration data (points, programs) and run time data (logs, points current values) is restored. Cool start: Controller is re-starting with its RAM memory erased or is unable to restore data from RAM for whatever reason. In this case the configuration data only (points, programs) is restored provided it has been previously backed up to flash memory. NOTE: Personnel objects are NOT kept in flash, upon cool start the controller will automatically request a personnel distribution from its access server CyberStation. Cold start: Controller unable to warm start or cool start, all configuration and runtime data will be lost. It must be reloaded from CyberStation.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Alarms cannot be sent to recipient CyberStation (Workstation) when controller has lost the link to the CyberStation in regard to the alarmed point in Import/Export table. The new alarm shows up in Active Alarm View only after the CyberStation is rebooted Product Line Andover Continuum Environment Workstation, CyberStation NetController (CX99xx, CX96xx) Cause Import/Export table in the NetController does not have the link to the workstation for the alarmed point. Resolution Backup current DB. Shutdown Continuum from all the CyberStations. Execute ImpExpFixupUtil.exe from Continuum install folder (C:\Program Files\Continuum). Reload all the NetController with the "Do not reload attached objects" option.

Issue IO Module properties show Firmware version 0.000. The module is online but no values can be read/written to/from the IO module. Product Line EcoStruxure Building Operation Environment IO Modules Automation Server Premium Building Operation Workstation Cause This can be caused by a module mismatch where the module configured in Workstation is not the same type as the physical module.  The module is shown as configured and online, but upon closer inspection of the I/O modules properties the "Module Type Mismatch" property is set to true. Resolution Double-check the module type shown under "Model Name" and correct it to match the module type printed on the IO module.  If there are not any points configured on the module then simply delete and recreate the module with the correct type.  However, if points are configured and bound and need to be retained follow the process below:- Change the module ID of the affected module configured in workstation to NULL to release the module id Create a new module with the correct type and assign the module id released in step 1 Drag the points over from the incorrect module to the new module Check the points are working as expected (the new module must support the point type) Delete the old module as it is not required Additionally, modules with a 'V' variant, such as the AO-8/AO-V-8 and UI-8.AO4/UI8.AO-V-4,  are different module types and one cannot directly replace the other.  Doing so will generate a module type mismatch.

Issue When installing PCT 2 the following error is seen: Error: System.Management.Automation.CommandNotFoundException: The term 'Get-VM' is not recognized as a name of a cmdlet, function,script file, or executable program. Product Line EcoStruxure Building Operation Environment Project Configuration Tool 2.0 Cause The Hyper-V Module for Windows PowerShell is not installed. Resolution Follow these steps in Windows 10 to install the Hyper-V Module for Windows PowerShell: Right-click on the Start button and click Programs and Features. In the Programs and Features dialog, click Turn Windows features on or off In the Windows Features dialog, check the box for Hyper-V Module for Windows PowerShell and click OK. The dialog will signal completion and the module will be installed.

Issue Alarms cannot be created in a BACnet b3 controller because the fields are grayed out. Product Line Andover Continuum Environment Continuum Cyberstation b3 BACnet MS/TP controllers Cause Alarms are created differently in a BACnet controller than with an Infinet controller.  These fields are grayed out since they are not used for alarm creation in a BACnet controller. Resolution There are instructions in the BACnet section in the Continuum help for creating an event notification and then mapping the point and the event notification within an alarm enrolment. For an example see AlarmCreatingAndConfiguring BACnet.doc

  Issue How can system alarms be configured so that electronic signatures are required? Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause Alarm Decoration rules are required to configure change control/electronic signatures for system alarms. Resolution Use the Alarm Decoration filters to apply/override settings for alarms. Create an Alarm Decoration Rule under ~/System/Alarm Control Panel/Alarm Decoration   Select the Alarm Decoration rule that filters on all System Alarms or the specific ones, select to override electric signature, and set it to True.    

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue In some cases, the event and trend databases can grow really big, although not all the space in the files is used. Therefore, one needs a way to verify that vacuuming the database will help. Product Line EcoStruxure Building Operation Environment SQLite Building Operation Enterprise Server Building Operation Enterprise Central Cause Frequent inserts, updates, and deletes can cause the database file to become fragmented - where data for a single table or index is scattered around the database file. Running VACUUM ensures that each table and index is largely stored contiguously within the database file. In some cases, VACUUM may also reduce the number of partially filled pages in the database, reducing the size of the database file further. Read further information here: https://www.sqlite.org/lang_vacuum.html Definitions are documented here: https://www.sqlite.org/pragma.html  PRAGMA schema.freelist_count; Returns the number of unused pages in the database file. PRAGMA schema.page_count; Returns the total number of pages in the database file. PRAGMA schema.page_size; Returns the page size in bytes (B), which must be a power of two between 512 and 65536. Resolution Stop the Enterprise Server or Enterprise Central. Open SQLiteStudio (link to download) Select "Databases" --> "Add database" Find the event.db or trend.db file from the "historical" folder of the EBO database folder. Use this article to locate for your installation - Clean db for Enterprise Server or Enterprise Central On the added database, right-click and select Connect to the database In the query tab, paste the following command: SELECT (SELECT freelist_count FROM pragma_freelist_count()) AS FreeList_Count, (SELECT page_count FROM pragma_page_count()) AS Page_Count, ((SELECT page_count FROM pragma_page_count()) - (SELECT freelist_count FROM pragma_freelist_count())) AS Used_Page_Count, ROUND(CAST((CAST((SELECT freelist_count FROM pragma_freelist_count()) AS REAL) / CAST((SELECT page_count FROM pragma_page_count()) AS REAL)) * 100 AS NUMERIC),2) AS Percent_Free, (SELECT page_size FROM pragma_page_size()) AS Page_Size_B, ROUND(CAST(((SELECT freelist_count FROM pragma_freelist_count()) * (SELECT page_size FROM pragma_page_size())) / (1024.0 * 1024.0) AS NUMERIC),3) AS Estimated_Space_MB; Click the blue play button above the Query tab.  Review the Percent_Free and Estimated_Space_MB, which will be returned at a minimum, to decide if you want to perform the 'vacuum' command. The vacuum process is slow, as it was designed to operate in the background. Shrink the SQLite event and trend databases. If the Percent_Free is above 80, this is the better option: Shrink the SQLite event and trends databases (Option 2) by creating a new file.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue In some cases, the event and trend database can grow really big, although not all the space in the files is used. In extreme cases, there is more free space than used space and it is quicker to create a separate file. Product Line EcoStruxure Building Operation Environment SQlite Building Operation Enterprise Server Building Operation Enterprise Central Cause Frequent inserts, updates, and deletes can cause the database file to become fragmented - where data for a single table or index is scattered around the database file. Running VACUUM ensures that each table and index is largely stored contiguously within the database file. In some cases, VACUUM may also reduce the number of partially filled pages in the database, reducing the size of the database file further. Read further information here: https://www.sqlite.org/lang_vacuum.html Resolution Stop the Enterprise Server or Enterprise Central. Open SQLiteStudio (link to download) Select "Databases" --> "Add database" Find the event.db or trend.db file from the "historical" folder of the EBO database folder. Use this article to locate for your installation - Clean db for Enterprise Server or Enterprise Central On the added database, right-click and select Connect to the database In the query tab, paste the following command: VACUUM main INTO 'C:\ProgramData\Schneider Electric EcoStruxure\Building Operation 6.0\Enterprise Server\db\Historical\event2.db'; Update the path to match your installation. One can SHIFT-RIGHT-CLICK the event.db or trend.db and select Copy as Path, then select everything inside the single quotes and paste. The paste will include double quotes, so delete those and leave the single quotes Update the database name to ensure it is unique. Click the blue play button above the Query tab. Depending on the size and amount of free space, this can take seconds to days to complete. One can monitor the progress in Windows Explorer by seeing the Size and Date Modified field update. Append .old to the end of the original file and rename the new file, event.db or trend.db, so it replaces the original. Start the Enterprise Server or Enterprise Central.

Issue SLP BACnet Setpoint limits Product Line EcoStruxure Building Operation, Andover Continuum, Field Devices Environment SpaceLogic SLP Series Cause The BACnet Object "Temperature Setpoint" includes properties Minimum and Maximum values These can be used to limit the setpoint, however the values are not saved in non volatile memory, thus the value revert to default after a power cycle (0 and 50 degC). The Setpoint object needs to be manually downloaded from EBO following a power cycle to set these properties. These properties cannot be written to individually. Thus changing these properties is unlikely to be good practice. Resolution A script program can be used to set limits to the Temperature Setpoint. Example below Note the "Value transfer settings" need changing to "Transfer value each time..." as below

Issue Modicon Switch Ordering options and how to configure the Ethernet Switch for RSTP for EBO Product Line EcoStruxure Building Operation Environment Modicon RSTP Switch (Not Connexium) Building Operation Automation Server Premium MPX and/or RPX Controllers Ethernet Switch Configurator Cause Schneider Electric Industry Offers an RSTP enabled Ethernet Switch that can be used with EBO instead of 3rd party Switches Resolution The following video will illustrate the following steps for Ordering and installing the Modicon Ethernet Switch with EBO The Modicon Connexium Ethernet Switch has been replaced by the updated Modicon Switch Modicon Switch Part Numbers and Email address for ordering Connect and use the SE Ethernet Switch Configurator executable for Switch configuration Set the Time and use the Syslog for troubleshooting Configure EBO and the controllers (MPX/RPX) for RSTP Test the Modicon Switch, EBO, and the MPX/RPX controllers for RSTP     Related Links: Modicon Switch Part Numbers and Ordering Information - (see attached Part Number slide) MCSESM Switch Installation Manual MCSESM Switch Configuration Manual Ethernet Switch Configurator Software - look for  SchneiderElectricEthernetSwitchConfigurator2303_Windows_x86.zip Other Modicon Switch documents RSTP Troubleshooting Community Thread TGML Graphic Setup Video (Training Department)

  Issue Unable to convert DMP file to SmartX servers with EBO 3.x, 4.x and 5.x using Continuum Conversion Tool(CCT) with PCT 2.0 Example: CCT3.2 is unable to connect to an AS-P in v3.2 created in PCT 2.0 It shows the "The user session is lost, no specific reason has been set" error when trying to connect. Product Line EcoStruxure Building Operation Environment Continuum Conversion Tool Project Configuration Tool Cause PCT 2.0 is not compatible with earlier versions of CCT Resolution In PCT 2.0, create a version 6.0 ES. In PCT 2.0, create an older version of AS-P. In PCT 2.0, make the older version AS-P a child of version 6.0 ES. In WorkStation 6.0, log on to the ES, navigate to the AS-P, and create the desired MS/TP or Infinet networks. In CCT 6.0, log on to the ES and import and analyze the desired Continuum dump file. In CCT 6.0, click to select the target MS/TP or Infinet networks. When doing so, navigate into the older version of AS-P to select the desired networks. Convert the dump file.

Issue The toolbar icons in PCT 2.0 are jumbled. They seems to be stacked on top of each other, making it hard to use the toolbar. Product Line EcoStruxure Building Operation Environment Project Configuration Tool 2.0 Cause Issue with the font used by PCT Resolution Follow these steps to resolve the problem: In Windows, navigate to Settings, then Font Settings, and search for "Material Icons". Select Material Icons, then choose Uninstall. Confirm by clicking Uninstall. Close all browser windows used to access PCT, then reopen and browse to PCT again. The toolbar icons should now display correctly.

Issue When attempting a login from a Security Expert client PC, it generates a "Network SSPI error" when using Windows Authentication and the machine name. Product Line EcoStruxure Security Expert Environment Security Expert 4.3.285.21 Multiple PC Security Expert Installation using Windows Authentication Cause The Network SSPI error is generated at the Client PC Login because of how Security Expert implements RFC1034 which stipulates how machine names are used for DNS. Resolution 1. Place a period at the end of the Security Expert Server machine while logging into the client only Security Expert PC Example: Using "WIN-B0DOGEHESMN" as the server name will not work Using "WIN-B0DOGEHESMN." will work Notice this works because of the "." at the end Here is a graphical example of logging in with the correct server name by adding the "." 2. The other workaround would be to use the IP address of the server instead of the fully qualified domain name (FQDN). *Note* IT departments typically prefer the use of the FQDN name

Issue An error pop-up is encountered when trying to use WorkPlace Tech Editor (WPTE) ERROR: WorkPlace Tech Editor does not function using Visio 2000. A supported a supported version of Visio must be installed for WorkPlace Tech Editor or Monitor to function properly. Product Line EcoStruxure Building Operation Environment Building Operation Workstation (WorkPlace Tech Editor) Microsoft Visio 2013, 2016, 2019 Cause The Visio installed is corrupted or not updated to the required version. Resolution Procedure for doing the repair required for the WPTE to function Ensure that the Visio installed is approved for the version of WPTE you are using by reading the EBO release notes. Confirm that Visio if licensed and activated, and not using a temporary license Install any required Security Upgrades  Perform an Online Repair, not the Quick Repair, as illustrated  The picture above shows doing this repair to the installed Office.  Perform this on the installed Visio as well. It is important to search the installed applications to make sure no 64-bit Office products are installed.  Smartware Studio 360/Design 360 installs a 64-bit Microsoft Access DB application by ignoring the 32-bit/64-bit version check.  This can cause the fluent ribbon for WorkPlace Tech to fail and if the Online Repair is done, it can force all Office applications to be removed from the PC. 

Issue Firmware version and bootloader version do not match Product Line Andover Continuum Environment BCX b3 Cause Verification required on why the two do not always match Resolution When firmware versions (application firmware files) are posted to the web, they do not always included the associated bootloader version. The reason for this is that rarely is a bootloader version changed. When bootloader versions do change it will be announced in the release notes for the particular firmware version.

Issue The network card is not working on the PC.  Product Line Andover Continuum, EcoStruxure Access Expert, EcoStruxure Building Expert, EcoStruxure Building Operation, EcoStruxure Security Expert, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series TAC I/NET, TAC Vista Environment PC Network Interface Card Cause Require a method to test the network card. Resolution Assuming you have the correct protocols loaded:- Open up a command prompt and type ‘ipconfig’(1) then press enter to get a list of the available network cards. Find the specific network card by name (2) Record the IP Address (3) assigned to the card, e.g. 192.168.5.90 If the card is unplugged (4) connect a network cable and start back at step 1 If the network card does not appear in Device Manager check the drivers are correctly installed for the card and when installed correctly start back at step 1. If the network card still does not appear it could be disabled.  In Network Connections right click the adaptor and select Enable (5) and start back at step 1. After these steps if the network card still does not appear when running ipconfig it is most likely damaged. If/when an IP Address is successfully obtained open a Command Prompt and type ping followed by the IP Address of the card, for example ping 192.168.5.90 (1). A functioning card will respond with 4 successfully replies (2) and the associated statistics (3) As additional information a good first step would be to "ping 127.0.0.1". This will not test a network card but indicates that the TCP/IP protocol is installed and functioning on the host PC.

Issue Script advise for xPDisplay on a b3/i2 controller Product Line EcoStruxure Building Operation Environment i2 and b3 Controller xP Display Cause The xP Display was designed when only Continuum was available (before EBO) and there was no documentation for EBO. Scripts need to be used to control the xP Display Binding to Object LCDAnswerString directly via "String Input" or "String Output" in a script program Then doing a check  If LCDAnswerString <> ""  then causes the script to disable with errors. "" = Null Resolution A simple way around this is to do the script check on another (manually created) string that is bound to the object LCDAnswerString Thus the following will work:  Numeric Input LCDKeyStroke       'bind to LCDKeyStroke    - this can also be used to set to zero. eg. LCDKeyStroke = 0 String Input LCDAnswerStrCopy   'bind eg LCDAnswerStrCopy  - use this to read the LCDAnswerString value String Output LCDAnswerString    'LCDAnswerString  - use this to set to Null eg. LCDAnswerString = "" Numeric Output AAA Line Wait4Value If LCDAnswerStrCopy <> "" then  'check if a value has been input    AAA = minimum(maximum(0, StrToNum(LCDAnswerStrCopy)), 100) 'Make AAA equal the input (min0, max100)    LCDAnswerString = ""     'reset LCDAnswerString back to Null Endif Outside this script, the manually created string object LCDAnswerStrCopy needs to be bound to LCDAnswerString, this can be achieved directly (change the binding type to COV) or via another script (use Print LCDAnswerString to LCDAnswerStringCopy) Note v4.0 export, script text attached and install guide attached

Issue An error message is displayed when trying to download all objects to a SpaceLogic controller. The error message says:   Offline '/SiteServer' Communication   Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Premium (AS-P) Automation Server Bundled (AS-B) Multi-purpose or Room-purpose (MP/RP) controller Cause This error can occur when the controller is an instance of a Custom Type (CT), but the CT only exists in the type library of the Enterprise Server, and not in the Automation Server hosting the controller. A BMS Server can only access it's own type library. See WebHelp article Custom Types for more information. Resolution Log in to the Automation Server where the MP/RP controller is hosted, and import the custom type to type library.

   

Issue The error "Failed to Invoke the Security Expert Suprema Component" is seen when attempting to register/enroll a user's biometric credential at a Security Expert Client Only machine.   Figure 1 - Suprema scan error   When doing a registration/enrollment from the Security Expert Server this error is not seen and the registration is successful. Product Line EcoStruxure Security Expert Environment Security Expert Suprema Biometric Reader Cause The Suprema.dll has not been properly registered on the local machine. Resolution First check in C:\Program Files (x86)\Schneider Electric\Security Expert folder and confirm that the three files Suprema.dll, BS_SDK.dll, and BS_SDK_V2.dll are all present. If they are not you will need to copy them over from a working installation of Security Expert Server Installation.   Now run the below commands via an Administrator authenticated command prompt session: For 64-bit machines cd C:\Windows\SysWOW64 regsvr32.exe “C:\Program Files (x86)\Schneider Electric\Security Expert\Suprema.dll” For 32-bit machines regsvr32.exe “C:\Program Files\Schneider Electric\Security Expert\Suprema.dll” You should get a pop-up saying the .dll was registered successfully. Close and re-open the Security Expert client and re-test enrolling a user's fingerprint.