Building Automation Knowledge Base

Issue Unable to add an Automation Server into the Device Administrator via IP. Error seen - Could not logon to server x.x.x.x This can be caused by providing the wrong password or the password has expired on the server.  If the password has expired, log on to the server using WorkStation and change the password. Product Line EcoStruxure Building Operation Environment Building Operation Device Administrator Building Operation Workstation Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Automation Server Cause Failed attempts of connecting to an AS-P, AS-B, or any IP controller with device admin will trigger the EBO security feature of SSH console lockout. This security feature defaults to 15 minutes and since the device admin uses SSH for communication, it will not allow the connection to an automation server while in this lockout state.  Resolution If a site is experiencing communication issues, then the SSH console lockout could be going into effect before a good connection is established. Reducing the SSH console lockout time period will allow for a connection to be made sooner without waiting out the default setting of 15 minutes. Use Workstation to log in to the server experiencing the issue. Go to Control Panel. Click on "Security settings" under the Security and Communication title. Locate the "SSH Console Lockout" configuration setting and adjust the lockout time to a shorter duration such as 1 second. Click Save. Open Device Administrator and add the Automation Server using IP.

Issue When troubleshooting server issues, it can be helpful to look at the logs that are recorded within the Automation Server. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server  Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Within the Automation Server logs are many records that are logged as a part of normal operations and unexpected events. Resolution Automation Server: Automation Server error logs can be retrieved using Workstation, Device Administrator, or WebStation. Device Administrator can be used in case of crash information is required, ex. dump files, or if the Automation Server is not accessible via WebStation or WorkStation. Workstation: Connect to EBO system with EBO WorkStation. Select the target Server  Expand the System folder Expand the Modules folder Expand the Trace folder and see Trace Settings For EBO 3.1 or higher, Double-click both Trace Log and System Log to open separately  For EBO 3.0 and lower, including SBO 1.x Right-click in Trace Settings Select Trace Settings in the menu Select Get System Log Repeat to select Get Trace Log  Device Administrator: Follow this WebHelp article: Getting Automation Server Debug Information If requested to retrieve a core dump, use this method to retrieve the Device Administrator Debug Information zip file. Then perform the following to make sure the zip file contains a core dump with a relevant timestamp for the event being investigated. Open Zip Open the folder containing the server name and IP address Open Server folder One should see file(s) with filename in this format core_dump_<Serial Number>_nsp_servers_<Timestamp>.tgz WebStation: EBO 4.0 (2022) and higher NOTE: You may have to enter Private Browsing mode to disable extensions, as you may see a blank page when viewing logs. Ensure credentials used are for a local 'admin' user or have access to the ~/System folder of the EBO Server you are connected. Click the 3-bar menu to navigate Select System, then Modules, then Trace One will see System Log and Trace Log in the menu, and clicking on System Log or Trace Log will open them in a new tab. NOTE: Please be patient as it may take some time to transfer the file. Once you see text in the tab, right-click on a blank area and select Save Page As... (Firefox) or Save As... (Chromium-based browser). It should recommend saving as SystemLog.txt or TraceLog.txt automatically; however, to be helpful, please add the EBO Server Name and Date to the filename. EBO 3.2 and earlier See the Webhelp Topic on collecting these logs from Automation Servers: Viewing and Downloading Automation Server Log Files. This process is now similar to that described above for WorkStation.   Credentials used to log in must be a member of a group that allows the policy of Web Configuration: Allow members to access Automation Server Web Configuration. Launch a web browser that is compatible with the installed EBO version as mentioned Webstation Specification Sheet. Type the IP address of the automation server to open the Webstation. Log into the Automation Server.                   Once logged into the Automation server, go to the Settings menu in the top right corner and click on Device Configuration. Click on the Server Log tab to view the automation server's log files. To save a copy of the log to your PC, click on the Get all log files link. The log files are compressed into a zip file and exported to downloads folder. Enterprise Server and Enterprise Central: For more information, check this article: Error logs from the Enterprise Server and Enterprise Central - Communities  

Issue There may be a situation where the External Interface File (XIF) needs to be extracted out of the controller in order to properly set up the controller in a building automation system.  Product Line EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment External Interface File (XIF) NodeUtil Loytec XIF Builder Cause These tools will help with the extraction of an XIF file. An XIF file is used to create a Niagara R2 shadow object, a Niagara G3 LMNL file, LonWorks device template, and a SmartStruxure device template.  Resolution The device manufacturer should provide an XIF, and in most cases, a DRF kit as well. The XIF provided by the manufacturer of the controller should be used first but if issues arise it may be required to extract the file from the controller. There are a number of tools available that will create an XIF, but the DRF kit cannot be created by any tool and must be supplied by the manufacturer. This MUST be provided along with the device. The list below covers some of the tools which are available. NodeUtil                          (header: bad,           NVs: ok,                      DMA/File-SCPTs are omitted) Vista's XIF-builder           (header: bad,           NVs: almost ok..,       DMA/File-SCPTs are omitted)  Loytec plugIn                  (does a perfect XIF from a device using Loytec's stack)   NodeUtil is available from the Echelon website (free registration is required) - The NodeUtilLauncher package attached makes it easy to use NodeUtil with Loytec interfaces. Loytec XIF Builder is available from the Loytec website (free registration is required) Using Lonmaker and the XIF Builder. Using NL220 and the XIF Builder. If the uploaded XIF still contains some detailed prompted error, refer to Error displayed when importing a device XIF into SmartStruxure.

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 Default IP Address for AS,TCP/IP IPv6, and StruxureWare Building Operation Product Line EcoStruxure Building Operation Environment Building Operation site Cause Attempted to ping AS and got "Request timed out." (AS does not have a default IP address) After going through StruxureWare Building Operation Device Administrator's Open Console which is also referred to as PuTTY(outlined below #1), the configuration has the proper: Hostname DHCP enabled/disabled IP address Subnet mask Default gateway DNS server Domain name Still the ping of the AS IP address receives "Request timed out"  Is this from a Virtual environment? See Resolution 6 below. Resolution Check the following settings: Use Device Administrator to set a static IP address for an Automation Server. Connect the Automation Server to the PC's USB port In Device Administrator, select the Automation Server you want to set the IP address for. On the View menu, click Console which opens console or PuTTY.  See NOTE below if Console icon not shown. If you are prompted to type a login name, default is "admin". Press Enter. If you are prompted to type a password, default is "admin". Press Enter. Type "setip". Press Enter. If you want to change the host name, delete the current host name and type a new host name. Press Enter. Type "no" to use a static IP address. Press Enter. Type the IP address for the Automation Server. Press Enter. Type the subnet mask. Press Enter. Type the default gateway address. Press Enter. Type the DNS server address. Press Enter. Type the domain name. Press Enter. Type "yes" to write the configuration. Press Enter. After the Network settings, "successfully updated" message is displayed, Type "exit" to log off. Press Enter. Rather than connect through a router or switch, plug the Ethernet cable directly into the AS. Ethernet port is AutoSensing (No Crossover Cable required). Adjust IP settings to close proximity IP and Subnet, such as the following example: Computer IP=192.168.1.2 Computer Subnet=255.255.255.0 Automation Server IP=192.168.1.5 Automation Server Subnet=255.255.255.0 Have only one NIC or network card enabled in Network Settings on this computer In Network Settings, uncheck the Internet Protocol Version 6 (TCP/IPv6), which will disable. TCP/IP Version 6 is the latest version of the internet protocol which provides communication across diverse interconnected networks which is not necessary for this configuration. If you are using a virtual environment, exit that virtual environment and attempt the configuration from the real-world environment.  If AS hangs or comes up with the Status light in red: Start Device Administrator and establish a USB connection between the computer and AS. Press the reset button on the AS three times in a row to place it in DFU mode. The AS will disappear from the Device Administrator and re-appear in DFU mode. Perform Upgrade device operation. The AS can be configured using DHCP (Dynamic Host Configuration Protocol) using Device Manager. It is recommended to not use DHCP but rather Static IP addresses. If the IP of the AS/ES changes, then reconfiguration of other AS/ES, or BACnet/IP, Modbus/IP interface needs to be changed also. NOTE: Beginning with StruxureWare Building Operation release 1.4.0, the Device Administrator no longer displays the "Console" icon on its toolbar. You can still access the PuTTY console by holding down the shift key and right-clicking on the automation server. You will have the option to open 'Console'. NOTE: Some network configuration setting changes may be prevented by the connected network. If you have issues getting the AS to save changes, disconnect the AS from the ethernet and use the USB connection only.

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 Example graphics components required Product Line EcoStruxure Building Operation Environment TGML - Building Operation Graphics Editor Cause No standard graphics or components are supplied within the product. Resolution A Standard graphic component library can be downloaded from the Buildings Download Center. This consists of a number of Component Libraries that can be installed on a Workstation by double clicking on each one. In your TGML Editor, Right click in the Components window and select "Categories" you can then select the categories you require to see in your components section. There are also a lot of standard Snippets that have been developed by users around the world, these are available to download from the EcoStruxure Building Operation Forum - Graphics Exchange.

Issue BACnet MS/TP Bus Communication Troubleshooting Checklist Product Line TAC IA Series Environment I/A Series BACnet controllers (MNB-70, MNB-V1, MNB-V2, MNB-300, MNB-1000) on an MS/TP bus. Cause BACnet MS/TP Bus Communication Troubleshooting Checklist Resolution This checklist provides several settings/configurations to review when faced with a communication problem at the controller level. The content was compiled from different resources, summarized, and laid out in an easy-to-use manner so as to provide a quick-reference document. Power Each controller requires 24 VAC from a Class 2 transformer. See the Installation Instructions for each controller, and the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 1, “Power Supply Wiring”. Read-Only Flag Use the WorkPlace Tech Commissioning Tool (WPTCT) to check “Device Properties” of the controller. If the status is “Operational, Read-Only”, the input voltage to the controller may be too low. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 1, “Power Supply Wiring”. Due to the short duration of the low-voltage condition required to set the flag, it is unlikely that you will see it when measuring the input voltage with a digital meter, so check the “Device Properties”, and correct the problem as noted on page 28 of the guide, (reduce transformer loading, reduce wire length between transformer and controller, and /or use wire with higher current rating). Diagnostic LEDs The MNB controllers have onboard diagnostic LEDs that are useful in troubleshooting. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 3, “Communications Hardware Checkout”, Table: “LED Indications”, for a detailed description of the behavior of the LEDs and their diagnostic uses. Topology It is very helpful to draw the topology of the bus when you start troubleshooting. If there are no repeaters on the bus, the topology must be a daisy-chain, with no tees or stars. MS/TP network wiring to MN-Sx sensors must be run to the sensor, then to the next controller on the bus, in a daisy-chain; no tees or spurs are allowed. Maximum length of a wire segment is 4000 feet. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 1, “MicroNet MS/TP Network Wiring”, for details on Communications wiring. Repeaters B-LINK-AC-S, Andover Controls MS/TP Repeater B-LINK-AC-F-S, Andover Controls MS/TP Repeater Fiber See the MicroNet BACnet Smoke Control Systems Manual, F-27419, for details on the use of these wire and fiber repeaters with MNB controllers. See F-27419, Chapter 5, “Approved MS/TP Repeaters”, including the wiring example. Maximum Number of Devices The maximum number of MNB controllers depends on the cable used, and the Baud Rate. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7,Chapter 1, Table, “Approved Cable Types”. The MNB controllers are quarter-load devices, so a maximum of 128 or less are allowed on an MS/TP trunk, depending on the cable used. Addressing Avoid duplicate addresses. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 1, “Required Configuration”, CAUTION: “Duplicate addresses on an MS/TP network trunk will result in erratic behavior, lost tokens, and disrupted communication. There is no software tool that will identify duplicate addresses on an MS/TP network trunk. Typically, if two controllers are set to the same address, one of the controllers will appear to be missing from the list, and the address shared by the two controllers will intermittently come and go from the list.” Biasing As a requirement of EIA-485 (formerly RS-485) bus topology, an MS/TP network must have a minimum of one set, and a maximum of two sets, of bias resistors in place. The MNB-300, MNB-1000, UNC-520, and ENC-520 have jumpers to enable or disable the bias resistors. See bulletin TB06-09, “RS-485 Bias Resistors and the UNC-520-2 / ENC-520-2”, page 3, for a photo of the bias jumpers on a UNC-520-2. Terminators A 120-Ohm End-of -Line (EOL) resistor is required across the “MS/TP +” and “MS/TP -” terminals at each controller at the end of a wire segment. The MNB-1000 and MNB-300 are equipped with a jumper-selectable end-of-line (EOL) termination resistor. The default position for the EOL jumper is “EOL termination not present.” See the MicroNet BACnet Smoke Control Systems Manual, F-27419, Chapter 5, “Approved MS/TP Repeaters”, Figure titled “UL 864 Listed MS/TP Repeater and Isolation”, Note 4, for an important exception, requiring external EOL for the MNB-300 and MNB-1000, when used on a bus with an approved repeater. If a UNC-520-2, ENC-520, MNB-V1 or MNB-V2 is installed at the end of the trunk, install a discrete 120 Ohm EOL resistor, part number EMSC-546, or equivalent. Cable Use of the proper cable is critical to the communications performance of the networked controllers. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7,Chapter 1, Table, “Approved Cable Types” for a list of recommended cable types. As shown in the table, cable selection affects both the maximum number of controllers allowed on the trunk, and the maximum baud rate. WorkPlace Tech Interface The MNB-ROAM-IA is the recommended communications converter for connecting WorkPlaceTech, including the WPT Commissioning and Flow Balance Tools, to an MS/TP trunk. It is supported in versions 5.7.1 and later. A converter that had been recommended earlier, the B & B Electronics model USOPTL4, was found not to operate reliably at speeds above 38.4 K baud. (See Direct MS-TP Connection with B & B Electronics Converters (Revised) - TB08-02-02 for details). The MNB-ROAM-IA supports Bluetooth wireless connection between WorkPlace Tech suite and the MS/TP network, for distances up to about 40 feet. One external Bluetooth adapter has been tested and approved - the Belkin USB adapter. (See Supported models of Bluetooth adapters with WorkPlace Tech for details). A problem we have seen with some MNB-ROAM-IAs is when trying to add Bluetooth device, the Bluetooth Wizard identifies it as "Serial Port Device, Unknown: Major(0), Minor(0)" instead of "tac-RoamIA:xxxxxxxx" where xxxxxxx is the serial number. There is no way for WPT to use the ROAM-IA if the computer can’t pair with it. Currently, there is no known solution, other than replacing the device. Divide and Conquer This is a strategy for dividing a bus into smaller sections in order to isolate a controller or section of bus that might be causing communication problems. The general idea is to divide the bus in half, and see if communications are possible from one end to the other end. If not, divide each half again, and continue until the problem(s) are found. Reference Documents F-27360 TAC I/A Series MicroNet BACnet Wiring, Networking, and Best Practices Guide F-27358 TAC I/A Series MicroNet BACnet Workplace Commissioning Tool and Flow Balance Tool User’s Guide F-27456 TAC I/A Series MicroNet BACnet MNB-70 Zone Controller Installation Instructions F-27345 TAC I/A Series MicroNet BACnet MNB-300 Unitary Controller Installation Instructions F-27346 TAC I/A Series MicroNet BACnet MNB-V1, MNB-V2 VAV Controller Installation Instructions F-27347 TAC I/A Series MicroNet BACnet MNB-1000 Controller Installation Instructions F-27419 TAC I/A Series MicroNet BACnet Smoke Control Systems Manual

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 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. To get access to the password reset mode, the server needs to be started.     For detailed information please see the video: 

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 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 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 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 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 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 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 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 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 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.