Building Automation Knowledge Base

Issue The user installed the PCT on a machine and after running it, the following error pops up: “VM Module INITIALIZING_ Failed to refresh versions”     Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT)  Cause An installed and enabled antivirus may have corrupted the PCT installation. Resolution By verifying the PCT Virtual Box logs, we can see the folloiwng error:    ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={xxxx-xxxx-xxxxx-xxxx-xxxx} aComponent={MachineWrap} aText={The virtual machine 'Project Name' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005)}, preserve=false aResultDetail=0   This indicates that the antivirus may have corrupted the PCT installation if it remained enabled during the installation. Now the PCT cannot communicate with the Virtual Machine. To resolve this, users will need to re-install the PCT while the antivirus has been disabled temporarily.

Issue When trying to embed a website in an N4 Px view, the site renders in Workbench but not in most browsers displaying this error in the browser's developer console; Product Line TAC IA Series Environment I/A Series N4 Workbench Web Browsers, Chrome, Firefox, Edge, Internet Explorer Cause Most major browsers no longer support NPAPI/Java plugins.  Oracle has stated they would remove it in JDK 9  and from Java entirely.  The N4 WebBrowser object under the workbench pallet requires Java to work correctly.  That is why it only works in the Workbench environment, Internet Explorer, and older Oracle Java platforms. Resolution When using the WebBrowser object in Niagara N4. Viewing in the Browser Preview Mode or in an actual browser that doesn't support the Java plugin, the embedded site will not render. The only solution is to use Internet Explorer or the Web Launcher application detailed in the attached document to view the Px. For more information, refer to the Niagara Web Launcher - Niagara Java-based Web Clients Guide PDF

Issue There is no information on how to create and prepare signed certificates for import in Building Operation. PEM file format has to be used. If another format is used or the certificate files are not correct, you get a message like this when importing SAXParseException: Reference to invalid character number in line X column Y Product Line EcoStruxure Building Operation Environment Certificates Cause There is no information on how to create signed certificates in Building Operation. Resolution Make sure that when preparing the pfx file that the full chain of trust is included in the pfx file. You have various options when preparing a pfx certificate export file, and the private keys and chain of trust are options that must be selected. Otherwise, you won't extract the intermediate certificate or the private key if not included. Complete a Certificate Request and then request a certificate in PEM format in a .pfx file "container".  Extract the CA certificate, Intermediate certificate, and private key using the following OpenSSL commands. After executing each command, enter the password if prompted. Make sure you reference the right pfx file. Below filename.pfx is used as an example Make sure you enter the commands manually and do not copy/paste from this article Download OpenSSL tool here or use OpenSSL installed with EBO  openssl pkcs12 -in filename.pfx -out host.pem -nodes -clcerts -nokeys openssl pkcs12 -in filename.pfx -out inter.pem -nodes -cacerts -nokeys openssl pkcs12 -in filename.pfx -out privkey.prv -nodes -nocerts The three files produced must then be parsed of any characters that aren't in the part of the certificate/key and in PEM format (or PRV if private key) - basically all the characters before "-----Begin Certificate-----" or after "-----End Certificate-----". Ensure each file ends with a blank line and that a blank line separates each section. This can be done in any text editor; however, this example uses Notepad++ with the "Show All Characters" button selected.  Import the files into SBO using the certificate manager in the Control panel. File type conversion If the host and intermediate certificate are in crt, cer or der format, you can convert them to pem format using the following method/command: openssl x509 -outform der -in certificate.cer -out certificate.der openssl x509 -inform der -in certificate.der -out certificate.pem Replace "certificate.cer" with the name of your file Determining certificate file type To determine which filetype a given certificate file has (PEM, DER, or pkcs12/pfx), you can use the following commands (replace "cert.crt" with the name of your file). A valid output will confirm the file type. PEM openssl x509 -in cert.crt -text DER openssl x509 -in cert.crt -inform DER -text pkcs12/pfx openssl pkcs12 -in cert.crt -info

Issue How to change the IP address in the EC/ES software when it is grayed out. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central (EC) and Enterprise Server (ES) Building Operation WorkStation Cause The EC/ES IP address is grayed out in the Network Tab of the Server Properties and cannot be changed.  This setting is only used to view the IP address that the server is currently using - typically the IP of the network interface card of the PC running this.  To change this setting it must be done through the Communications TAB of the server as detailed in the resolution.  Resolution EcoStruxure Building Operation 2.0 and above EBO 2.0 and above now supports multiple NIC configurations, see 2.0.1 Release Notes for details, in particular, the following note.   Note: That from 2.0 the server will still listen for incoming requests on all network adapters so this setting is only used for choosing which communication settings that the server will use to communicate with child servers. This allows other IP protocols on different networks, e.g. BACnet, Modbus, etc. to communicate with the Server.    It is now possible to select which network adapter the Enterprise Central and the Enterprise Server use.  See the following WebHelp Topic Configuring Network Interface Card for an Enterprise Server or for an Enterprise Central StruxureWare Building Operation 1.9 and below  When the IP address of the computer changes the ES will automatically update the "IP/DNS Address" in the Properties, Network tab. If your computer has multiple network connections, ensure that the Network Interface Card (NIC) to be used for the SmartStruxure network is set to be at the top of the list in the Adapters and Bindings. Go to the computer's Control Panel > Network Connections Select "Advanced, Advanced Settings... " from the menu. In the "Connections:" section, select the Network Connection to be used and press the up arrow to move it to the top of the list. For Windows 7 / Server 2008 See the following link on how to change the order of protocol bindings: How to change the network connection priority in Windows 7 For Windows 8 and beyond, please refer to Adapter priority setting unavailable in Windows 10 In addition to the ES Network Properties, there is also the Communication tab in the ES that lists all of the Server IP addresses in the system. If these need to be changed this can be done by selecting the server and clicking on the "Show/ Hide Communication settings" button circled in red below.

Issue At times it is necessary to manually delete MSMQ messages Product Line Andover Continuum Environment Continuum Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause Under certain conditions messages build up in queues and don't clear out from msmq (i.e. Cyberstation offline that is configured to receive alarms) Resolution To open MSMQ Go to Windows Control Panel> Administrative Tools>Computer Management Expand Services and Applications Expand Message Queuing Expand Outgoing Queues and select one of the entries Right Click on queue messages and select AllTasks>Purge Are you sure you want to delete all messages? Yes Repeat this for the queues that require purging Note: The IP of the Cyberstation is listed in the Outgoing Queue Channel (an offline Cyber will keep building up messages) Here is a snapshot of the queues below.

Issue When attempting to add a new Automation Server under an Enterprise Server that already has one or more AS servers attached it results in an "Object already exists" error ERROR Object already exists Domain: Data access Info:~/System/Server Communication/Models/xxxxxxxx/Members/xxxxxxxxx in module Run Db manager xxxxxxxx = Global Unique Identifier (GUID) The GUID underlined in red in the screenshot above is the duplicated Id. Additional error message possible depending on EBO release version. ERROR: Server already part of a multi server system Domain: Invalid data  Info: Attempt_To_Add_An_Object_To_The _System_That_Already_Exists ERROR: Cannot add a server that is a clone of a server that already exists in your system Domain: Startup  Technical Info: An added server with name 'XXXXX' has the same unique id as an existing server with the name 'YYYYY' which is not allowed. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server  Building Operation Automation Server Bundled Cause The AS that is being added has been restored from a backup created from one of the servers that are already configured under the ES resulting in a duplicate GUID. Resolution Backup the Server Restore the Server and make sure to select "Restore configuration with new IDs" check box. This will ensure that a new GUID is assigned to the AS. Add the Server from ES Please note that the restore function to re-use configuration data from a backup set is supported for all Building Operation supported protocols, except for BACnet and b3 BACnet.  To read more see Web Help To read more see Web help: http://help.sbo.schneider-electric.com/topics/show.castle?id=10228&locale=en-US&productversion=1.7 To read more see Web help: http://help.sbo.schneider-electric.com/topics/show.castle?id=10228&locale=en-US&productversion=1.7

Issue In EcoStruxure Building Operation (EBO) version 3.1 and later the password reset function have changed, how does it work, and what is changed from before? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Project Configuration Tool (PCT) Cause The changes have been done due to cybersecurity issues. The basic workflow is the same as before but the generation of the reset token has changed. Resolution IMPORTANT: The session ID is unique for each session of WorkStation. You cannot close WorkStation until the password has been reset. If you close WorkStation, before the password has been reset, a new session ID is generated that cannot be used with the temporary password provided by your local Schneider Electric Buildings support team.  See online help topic: Copying the Session ID when Resetting the Password   To get a password reset token in version 3.1 and later you need to set the server in password reset mode(valid 24 hours)   For Automation Server(AS, AS-P, AS-B) this is done using the Device Administrator(DA), a USB connection is required between the computer and the server   For the Enterprise Server(ES) administrator privileges on the PC where the ES is installed are required. The ES is set in password recovery mode using the DA, the DA needs to be started as an administrator.   For the virtual server environment, Project Configuration Tool (PCT) tool is used.   For detailed information please see the video: 

Issue How are the 'Advanced Polling Configuration' settings under the BACnet interface to be used? Product Line EcoStruxure Building Operation Environment Enterprise Server (ES) Automation Server (AS) Cause These settings can be used to reduce traffic on the BACnet networks that can overload both the EBO server as well as the devices being polled. Resolution The settings are used to specify an amount of time (in milliseconds) that the server should wait after completing a polling cycle on the applicable BACnet network before starting the next cycle. A polling cycle is the set of point being polled on a particular network interface. For example, lets assume that the Minimum polling interval for MSTPA network has been set to 1000 ms, if you are polling 30 points on MSTP port A then the BACnet plug in will do synchronous ReadProperty requests to poll each of the 30 points one at a time. Once the 30 points are polled, (one polling cycle) the BACnet plug-in will delay 1000ms before polling the 30 points again. (next polling cycle) NOTE: The settings apply to polling ONLY and do not affect communications done via change of value (COV) To find a proper value to use, it is recommended that you start with 1000 ms and then adjust the value up or down based on polling performance. If the polled values update fast enough, increase the minimum polling interval to reduce CPU usage. If the polled values become too sluggish, reduce the minimum polling interval until performance returns to satisfactory levels. It may take some trial and error to find the optimum balance.

Issue Satchwell V V series Butterfly Valve Body requires replacement. Environment Satchwell V V series Butterfly Valve Body installations. Cause Obsolescence of Satchwell V V series Butterfly Valve Body. Resolution Replace Satchwell V V series Butterfly Valve Body with S-E VF208W series Butterfly Valve Body. Replace Satchwell A R series Actuator with S-E MF20 / MF40 series Actuator as appropriate. It should be noted that where a Satchwell V V series Butterfly Valve Body is to be replaced by a S-E VF208W series Butterfly Valve Body the Satchwell A R series Actuator fitted to the Satchwell V V series Butterfly Valve Body will not be suitable for reuse on the S-E VF208W.Buttterfly Valve Body. Satchwell V V series Butterfly Valves utilise Satchwell A R series Actuators. Satchwell A R series Actuators are not suitable for use on S-E VF208W series Butterfly Valve Bodies. S-E VF208W series Butterfly Valve Bodies utilise S-E MF20 / MF40 series Actuators. S-E MF20 / MF40 series Actuators are not suitable for use on Satchwell V V series Butterfly Valve Bodies. It should also be noted that Satchwell  V V series Butterfly Valve Bodies have screwed connections, whereas S-E VF208W series Butterfly Valve Bodies have Flanged connections. Further it should be noted that the width of a S-E VF208W series Butterfly Valve Body is significantly less than the corresponding length of a Satchwell V V series Butterfly Valve Body of equivalent pipe-size that it is replacing and that this will result in the need for mechanical work including installation of counter flanges to be undertaken to the pipe work at the location the S-E VF208W series Butterfly Valve Body is to be installed.  Please check the latest catalog for current equipment.

Issue MBus to Modbus TCP Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment Mbus Modbus Cause How to read MBus devices into a BMS System using Modbus TCP Resolution There are different methods, but these are generally using a Modbus RTU / Mbus gateway and then converting it to Modbus TCP. The following ADFweb solution allows Mbus to be read directly into a Modbus TCP device. Click here for the datasheet.

Issue BACnet/IP controllers are not configured in RSTP Mode by default, therefore must be configured during installation. Having RSTP Mode disabled by default allows one to connect BACnet/IP controllers to any switch, even with port security configured to detect BPDU packets and disable the port. Product Line EcoStruxure Building Operation, TAC IA Series Environment Multi-purpose Controller (MP-C) Multi-purpose VAV (MP-V) Room Controller IP-IO I/A Series N4 Jace8000 SmartX IP Driver for Niagara Cause RSTP protocol requires that controllers, switches, and network architecture are configured to ensure the protocol will operate as expected.  Resolution Setting RSTP Mode for BACnet/IP Controllers ALL devices in the RSTP loop MUST BE IN RSTP MODE to function properly. This is not a huge issue because during startup you can unplug 2nd side of the loop and it will function properly in a daisy chain. Ensure the SmartX Controllers are configured correctly Configuring BACnet/IP Controller Device Settings A factory or network reset returns the RSTP setting to Disabled. Important: Whenever you change RSTP settings, the controller MUST be WARM START. If you fail to perform this restart, the BACnet/IP controller will continue communicating using its previous RSTP settings. 'Activate IP Changes' does not affect RSTP mode. Ensure the switch is configured correctly per Configuring RSTP on a Managed Switch for SmartX IP Controllers. If asked to review this for a case, please provide PSS screenshots from the switch configuration page(s).  Bridge Priority = 4096 Hello Time = 2 sec Max Age = 40  (40 is the maximum value allowed by the protocol. Default is 20) Forward Delay = 21 sec Bridge Priority Considerations Change Bridge Priority by adding 4096 as switches get further away from AS. (8192, 12288, 16384, 20480, 24576, 28672) DO NOT set the priority as 32768 or higher because that is the built-in Bridge Priority of BACnet/IP Controllers. First, configure the Root Bridge Switch (closest to the Automation Server) settings. Then, configure the additional Switches in order of increasing Bridge Priority. Plug in 2nd side of the RSTP Loop If all devices stay online, then it is working properly. Now test line breaks or controllers that are powered off. If all devices go offline and/or the switch LED is flashing rapidly, then go to RSTP Troubleshooting. Managed Switch Troubleshooting Consult the documentation or contact the vendor or manufacturer to assist with configuration for the items below. Ensure the switch is IEEE 802.1D - 2004 capable. BACnet/IP Controller Networking Term Definitions RSTP Ring mentions the Rapid Spanning Tree Protocol is specified in IEEE 802.1D - 2004. Ensure the firmware is up-to-date by contacting the vendor or manufacturer or downloading it from its website. Ensure ports not participating in RSTP are configured as Edge Port, Admin port, or have STP disabled. Nomenclature for those settings on your specific managed switch may vary. Adding BACnet/IP controllers to site-managed switches, work with Local IT to add these devices to their network. They will need to work with their switch vendor/manufacturer/support group to ensure the configuration of those switches because it could be more complex than changing the minimum recommended four settings above. Also, since RSTP Protocol is limited to Max Age = 40 (hops including site switches and BACnet/IP controllers), each loop's size may be limited based on their site switch network configuration and architecture.  Determined the proper configuration (or disable) for the following features. DHCP snooping Dynamic ARP inspection Denial-of-service (DOS) mitigations BPDU Guard BPDU Filter RSTP Troubleshooting Check each BACnet/IP Controller -> Diagnostics -> Device Report to confirm in RSTP Mode MANUAL CHECKOUT Double-click MP - Diagnostics Files - Device Report It will open in the default text editor Review the Device Settings section near the bottom. In firmware 1.00.0x, the report should report RSTP Mode: Enable In firmware 2.00.0x or higher, RSTP: Enabled and RSTP Status: Operational If it reports disabled, then perform Setting RSTP Mode for BACnet IP Controllers Step 1 until RSTP is working properly. USE SEARCH & EVENTS EBO 2.x MP Device IP and Settings.xml for EBO 2.0 as it only includes MP controllers EBO 3.x SmartX Device IP and Settings.xml for EBO 3.x or higher Import attached search USE RSTP STATUS GRAPHIC IN WEBSTATION MUST BE EBO 3.1 or higher which includes ClientAPI support Frontline Fridays Episode 02 - Rapid Spanning Tree Protocol (RSTP) Date: 2022-11-11 Mike Botens posted the following in the thread: RSTP Status TGML dated 2022-11-09 PDF of the presentation Fusion Fridays - Session 07 ​​​​ Date: 2020-05-28 The start of the video shows the graphics page in use RSTP Status.zip is downloaded via the link below the video. Extract the TGML and drop it on the AS to import. The suggestion is to store TGML directly under the AS to help with navigation in Webstation. bind Network to the BACnet/IP network with the BACnet/IP Controllers. (You may need a second TGML page if BACnet/IP controllers are on Primary and Secondary IP) Run from web browser via WebStation because utilizes ClientAPI KNOWN ISSUES Offline controllers that are scattered are NOT an RSTP issue. Check to see if there is a possible DHCP issue by verifying controllers are still at their AUTO-IP address (IP 169.254.nnn.nnnn Subnet Mask 255.255.0.0). RSTP communications issues affect the entire RSTP loop or one contiguous group of controllers. Factory Reset or controller replacement should leave one ethernet cable unplugged until configured for RSTP per these articles: Replace a BACnet/IP Controller in an RSTP Ring Network Workflow and MP Controller Reset Modes If BACnet/IP Controller Device Report OR RSTP Graphic reports RSTP Status: Changes Pending instead of RSTP Status: Operational, disable RSTP Mode, Warm Start, re-enable RSTP Mode, Warm Start, and check again. SmartX is now SpaceLogic. KNOWN ISSUES with Firmware affecting RSTP: If Firmware 3.02.01 is installed, please upgrade to 3.02.02. RSTP not performing as expected with Static IP addressing RSTP does not work well on RPC HW RPC-16-B HW revision 6

Issue Simple Modbus Lua Script Product Line EcoStruxure Building Expert Environment Lua Programming Cause Simple script to test Modbus function Resolution In each of the samples, the following needs to be observed: The Modbus port is closed and opened with the port settings. The samples can be combined but the port is only set once. The settings for the Modbus RS485 port requires an address, in this instance 99 is used. This must be different from the slaves. The nnn.MOD1 must be left unchecked so that it is not enabled. This will allow the Lua script ModbusB to work. For added functionality the "Print" command is used. The "print" command provides added functionality indicating a successful read / write in the output window. If the result = 0 then the read / write is successful. Anything else is an error code. Contact Product Support. The value = is the value that is either read in or written dependant on the function used. The following samples provide simple read / write functions.: Coil Registers Digital Input Registers Holding Registers Input Registers 32bit Floating Point

Issue The SmartX server has a "?" under the server name field and shows the error "SSL certificate validation failed!" as the server state in Device Administrator. In some instances, this may cause a failure to upgrade of the SmartX Server displaying these symptoms.  Product Line EcoStruxure Building Operation Environment Building Operation Device Administrator Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Automation Server Cause The SmartX Server is added into Device Administrator over HTTPS 443 but does not have a valid SSL certificate installed. Resolution Change the connection from HTTPS 443 to HTTP 80 This can be done by clicking into the server settings (click on the "?") Select "Edit Connection"   Change the EBO Server Protocol from HTTPS to HTTP  Create a trusted chain between Device Administrator and the problem SmartX Server using a self-signed certificate by following this workflow

Issue There are missing serial ports (COM ports) when viewing the 'SerialPortService' under 'PlatformServices' in a station. Some or all COM ports will be missing. Local serial ports and/or serial ports of the attached modules do not function. Product Line TAC IA Series Environment I/A Series AX Jace 8000 Cause This could show up for several reasons. This was found during an upgrade to Niagara 4.2. It was also experienced when converting a Jace8000 running N4.2 (or lower N4 version) to AX. This can occur with a new out of the box J8000 to AX conversion if you do not first commission the Jace8000 to Niagara 4.4 or above before converting to AX. All of these problems are due to older version USBbinary files not being properly updated during commissioning. The LON option module (side-car) might stop communicating on the LON trunk due to the same binary file issue. Resolution This can be fixed via serial shell; either by direct connecting with a mini-USB cable or via ssh after it is enabled from the Platform Administration view. It is recommended that PuTTY.exe be downloaded and used as the terminal program to access the shell. The directions below are CASE-sensitive and must be entered exactly as shown. We recommend that you do not type these commands, but rather use copy-and-paste to avoid typographical errors. This is especially true of the usbSerialNumber itself -- it is case-SENSITIVE. By default, PuTTY.exe uses mouse-left-click-drag-and-highlight as an automatic shortcut for copy. Mouse-right-click is the automatic shortcut for paste. Once logged in type: Display the USB serial number(s) sh [hit enter] $ ls /etc/usb [this will display the USB serial number(s), if nothing displays see the note* at the bottom] 85091090FPGGS41 [this is an example serial number] Display the available binary files $ ls -Rp /sys/images/usb [this will display the available binary files] /sys/images/usb/applet-flash-sam4s16.bin* /sys/images/usb/vid03eb/pid2404/Tridium232-1_r03.bin* /sys/images/usb/vid03eb/pid2425/Tridium485-2_r04.bin* Note: You could also see '_r05' instead of '_r04'. If this is your result, make sure to update using the line below. /sys/images/usb/vid03eb/pid2425/Tridium485-2_r05.bin* The USB ports unavailable is due to the 'Tridium485-2_r04.bin' (or Tridium485-2_r05.bin) file was not written to the USB serial number file. This can be corrected by updating the USB serial number file with the correct binary file using the statement below. Make sure to replace the X in the statement with the highest number binary found in 'STEP 2' above. $ echo /sys/images/usb/vid03eb/pid2425/Tridium485-2_r0X.bin > /etc/usb/<usbSerialNumber> Update the binary file Using the example serial number and USB binary file found in STEP 2: $ echo /sys/images/usb/vid03eb/pid2425/Tridium485-2_r05.bin > /etc/usb/85091090FPGGS41 Make sure to use the serial number found when 'ls /etc/usb' was called. If there is more than one serial number found, write the command multiple times, once for each serial number found. Also, make sure to use the highest USB binary file number found. Currently r05 is the highest number. If '_r05' is returned as the available USB binary file, make sure to use '_r05' when updating the USB serial number. After a reboot, check the SerialPortService to confirm the ports are restored. *Note: if no usb serial number was found using ls /etc/usb another method would be to call for the slog by typing: $ sloginfo An error would have been logged here during the last startup and will display the serial number; example output: Oct 10 13:42:06 1 6 0 serusb_is_device_supported: Device 2 on bus 0 unrecognized. Using CDC-ACM Class Oct 10 13:42:07 4 11111 0 error opening /etc/usb/85091090FPGGS41 rc=-1 In addition to the symptoms listed above, the inability to communicate with the LON option module may cause the any of the following messages in the Serial Shell and/or the Platform Administration System Logs: error opening /etc/usb/<serial number here> rc=-1 U50Read returned unknown rc = 8!!! io_write failed ldvRC=7, length=<various numbers of bytes> The Station will most likely show that the LON network is up, but the LON devices are down. The device fault cause may show "unable to write" or something similar.

Issue When logging in to an AS or ES, WorkStation freezes or it takes a very long time (>30 minutes) before the login process finishes. Building Operation WorkStation hangs on "Reading data..." when trying to login to an AS or ES Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation WorkStation Cause The problem is related to a delay when validating the license details. It only seems to happen when running a mixed EBO/SBO 1.9.3 system and after having EBO license administrator 2.0.1 previously installed. Resolution Run the SBO License Server Reset tool and perform Reset - Simple Log in to WorkStation, and if the hang or freezing is still present, then follow the next set of instructions. Run Diagnostics in the License Administrator and take note of all the ACT (Activation) and Entitlement IDs Return all the licenses Close all WorkStations and stop all SBO/EBO processes (whichever may be running) Uninstall all License Administrator and License Server Run the SBO License Server Reset tool and perform a Reset - Complete (you will get an output of the commands and result) Install the latest released version of License Administrator and License Server (the latest released version of License Administrator has fixes for virtual servers and some cyber security vulnerabilities, note that License Administrator is backward compatible with earlier SBO versions) Activate the licenses based on the info from step 3 Note: If running the demo license, steps 3 and 4 may be skipped. If problems continue to occur, then send the above details collated (in step 3) and email this/contact support.

Issue Confusion over the thermistor type selection for an EBO Temperature Input object Product Line EcoStruxure Building Operation Environment Building Operation I/O Module Building Operation Automation Server Bundled Building Operation Multi-purpose Controller (MPC) Building Operation Room Controller (RPC) Building Operation IP-IO Cause The Thermistor type selection lists sensor "Types" I through V     This is confusing since, for example, the Continuum sensor is listed as 10k Type I but in manufacturers literature and temperature vs resistance tables is often referred to as 10k Type 3 Resolution The reference to Thermistor 10k Type in the selection list is an internal reference and not intended to refer to the types listed in manufacturers literature and temperature vs resistance tables. For reference the selections refer to the following sensor types:   Thermistor 10k Type I (Continuum) – Thermistor 10K4A1 also referred to as 10K Type 3 - SpaceLogic Sensors (as SLASXXX, SLAWXXX and SLABXXX), STx5xx Sensors (see HVAC Sensor catalog for details) Thermistor 10k Type II (I/NET) – Thermistor 10K2A1 Dale/Vishay - STx20x Sensors (see HVAC Sensor catalog for details) Thermistor 10k Type III (Satchwell) – Thermistor 10K3A1 (No Longer Applicable for Satchwell sensors) Thermistor 10k Linearized (Satchwell DxT - Type T) - STx6xx Sensors (see HVAC Sensor catalog for details) Thermistor 10k Type IV (FD) – Thermistor 10K4A1 type ‘G’ (U.S. Sensor) Thermistor 10k Type V (FD w/ 11k shunt ) – Thermistor 10K type ‘G’ (U.S. Sensor) with external 11k ohm shunt resistor installed Thermistor 1.8k (Xenta) – Thermistor type 1.8KA1 - STx1xx Sensors (see HVAC Sensor catalog for details) Thermistor 1k (Balco) – (not a thermistor) RTD, 1000 ohm Balco Thermistor 20k (Honeywell) – Thermistor 20K6A1 type H Thermistor 2.2k (Johnson Controls) – 2.2K3A1   Refer to the Temperature Sensor Resistance Charts Knowledge Base article for temperature vs resistance charts for these sensor types and others.

Issue Troubleshoot Security Expert Controllers showing offline in the client. Product Line EcoStruxure Security Expert Environment Security Expert Cause Require some common troubleshooting steps to help determine why controllers may be offline to the client. Resolution The main items to check are: Refer to the Troubleshooting Security Expert Controller Connectivity - Application Note on Exchange. If a controller has failed and the Replacement controller unable to be brought online then check if controller encryption had been enabled on the replaced controller. Restart the client software. Power restart the controller. Remove power Wait for all LED's on the controller to go completely off Apply power to the controller. In the controller web interface, on the Settings page, check that Event Server 1 has the correct IP address. Check that the Firewall is disabled. Check any Anti-Virus Firewalls/settings as well. If the Firewall cannot be disabled, ensure that all required ports are open between devices. See SX-SRVR Security Expert - Network Administrators - Installation Guide for details. Restart the Security Expert services under the PC's Services option in Control Panel. These need to be restarted when any changes are made. Confirm that the User Interface, Data Server, Event Server and Download Server module versions are all the same. Go to About  > Version and check there. If the database has not been upgraded to the same version as the client software, then this can cause communications issues. On the Security Expert Server check that MSMQ is installed as this is now a requirement   Security Expert MSMQ is required (Not showing live point status / shows "Unknown Status" error)   If MSMQ was installed after Security Expert, you'd need to reinstall Security Expert to allow it to run correctly. If MSMQ is installed and controllers are still not coming online (or the controllers are "bouncing" offline/online) then anecdotal evidence suggests enabling Windows 8 Compatibility Mode may help especially for Windows Server 2016 and Server 2019. Set the Windows 8 Compatibility Mode checkbox in the Properties page for C:\Program Files (x86)\Schneider Electric\Security Expert\SecurityExpertEvtSvr.exe   Also, note that if a database backup has been imported, then there is a need to check/change some other settings as well to ensure everything is set up for the specific server and controller.   Under Global > Download Server confirm that your computer name is the name of the PC where the download server service is running. Under Global > Event Servers ensure that the computer name is the name of the PC where the event server service is running. Under Sites > Controllers confirm the Serial number, IP Address, Download Port, Download Server and Control and Status Request Port match what is set in the controller's configuration web page (browse to the controllers IP Address to view). On that same General tab go to Diagnostic Windows and open the download and event server windows. Review the information contained and if there are any errors shown. Right click the controller and select Get Health Status. Review the status messages displayed.

Issue BACnet MSTP Wireshark capture Product Line EcoStruxure Building Operation Environment Schneider Electric StruxureWare Building Operation AS using MSTP for BACnet Cause Example of Wireshark capture and WriteProperty in MSTP    Resolution Using Wireshark, a bacapp.confirmed_service == 15 filter is applied which shows only BACnet WriteProperty packets Below is a screenshot of the Wireshark screen after applying the filter. I have Requests (REQ) and Acknowledgements (ACK) shown: Below is a Request, and clarification on what is Requested. A third party Metz (address 91) device is requested from the AS (address 0) for Analog Value 1 to be 0.00 Below is a Request, and clarification on what is Requested. A third party Metz (address 91) device is requested from the AS (address 0) for Analog Value 1 to be a value of 100.00 Filters which may be useful: Capture Filters   udp port 47808 BACnet/IP packets on UDP port 47808 udp port 47808 or udp port 47809 BACnet/IP packets on UDP port 47808 or 47809 Display Filters   bvlc || bacnet || bacapp all BACnet packets bacnet BACnet NPDU packets bacnet.mesgtyp BACnet Network Layer (router) packets bvlc BACnet/IP packets bvlc.function == 0x0b BACnet/IP Broadcast packets bacapp APDU packets bacapp.confirmed_service == 12 readProperty packets bacapp.confirmed_service==14 readPropertyMultiple bacapp.confirmed_service == 15 writeProperty packets bacapp.confirmed_service==16 writePropertyMultiple bacapp.confirmed_service==1 confirmedCOVNotification bacapp.confirmed_service==5 subscibeCOV bacapp.unconfirmed_service == 0 I-Am packets bacapp.unconfirmed_service == 8 WhoIs packets bacapp.unconfirmed_service == 2 unconfirmedCOVNotification packets bacapp.unconfirmed_service==3 unconfirmedEventNotification bacapp.unconfirmed_service==6 timeSynchronization     mstp.frame_type>2 exclude all token passing mstp.frame_type>127 view all proprietary traffic mstp.frame_type==0 only token passing mstp.frame_type==1 only poll for master mstp.frame_type==2 only poll for master responses bacapp.instance_number==[BACnet ID] all traffic from/to a specific ID mstp.dst==[MAC address] all traffic to a specific MSTP address mstp.src==[MAC address] all traffic from a specific MSTP address ip.dst==[IP address] all traffic to a specific IP address ip.src==[IP address] all traffic from a specific IP address      || (between filters) combines above filters (or)  && (between filters) combines above filters (and)   Also check out the BACnet-Capturing MS/TP Traffic Quick-Help video on the Exchange.

Issue In EBO 2022 or higher the "Semantic Engineering View" button is grayed-out in EBO WorkStation and "Semantic DB authentication failure" is shown in Alarm View. "Semantic Engineering View" button is grayed-out and "Semantic DB authentication failure" alarm   Semantic db authentication error   Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause  EBO user that connects to the Sparql database has the wrong username and/or password. Resolution Make sure that the user configured in EBO semantic settings matches the user created in the GraphDB web interface. In WorkStation, in the System Tree pane, select the EBO server. Click the Control Panel tab. Click Navigate to Sparql database, this will open the GraphDB web interface. Login with the admin user account.  In the top right corner, make sure that correct repository is selected, default name is "nsp".  Go to Setup -> Users and Access. Edit user "nspService". Set a password for the "nspService" account and make sure it has access rights to the "nsp" repository then click save. In EBO WorkStation control Panel, open Semantic Settings. Set the password for username "nspService" to match the password set in the GraphDB interface. For more information, please refer to the GraphDB help: Secure GraphDB — GraphDB SE 9.10.0 documentation (ontotext.com)

Issue Certificate for FDA regulations in the manufacturing of pharmaceuticals, 21 CFR Part 11 "Electronic Records / Electronic Signatures." Can Building Operation incorporate a comment section to capture a reason for change made by an operator/user? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause Building Operation site in need of the compliance certificate for 21 CFR Part 11 "Electronic Records / Electronic Signatures." Usually, these are pharmaceutical manufacturing sites, and the full FDA document PRT11Elect.pdf is attached to this article. Resolution EcoStruxure Building Operation 3.2 and higher Compliance Pack enables 21 CFR Part 11 compliance for regulated industries. The Compliance Pack is an add-on module to EcoStruxure Building to help regulated industries meet the compliance requirements for Electronic Signatures & Electronic Records that are in place in the region.   This feature in our EcoStruxure Building Operation software provides facility-wide accountability and traceability of the environmental conditions that can impact the quality and safety of products developed in controlled environments in line with the 21CFR Part 11 regulation.   Compliance Pack is a licensed feature and compatible with EcoStruxure Building Operation V3.2.1 and later. Part Number Description SXWSWCMPLPK001 Compliance Pack – includes TimescaleDB, Digital PDF Signing, Change Control, For one Enterprise Server or one Enterprise Central For technical documentation and sales enablement tools for the Compliance Pack, please visit The Exchange Building & Power Extranet and use the search keyword: 21cfr ebo   EcoStruxure Building Operation 3.1 and below EcoStruxure Building Operation V3.1 and below has not addressed the pharmaceutical market and there is no electronic signature feature set that meets the FDA regulations 21 CFR part 11.   For sales issues surrounding FDA regulations, please contact through your sales channel to the local Category Manager. Americas: Americas.EcoStruxureBuilding@schneider-electric.com EMEA: EMEA.EcoStruxureBuilding@schneider-electric.com Asia Pacific: AsiaPac.EcoStruxureBuilding@schneider-electric.com