Building Automation Knowledge Base

Issue What are the proper configurations in the network Poll Service to balance the BACnet packet traffic for better data handling? Product Line TAC IA Series Environment I/A Series Enterprise Server I/A Series ENC and Jace 8000 Cause Improperly defined poll rates, and poll groups in the Poll Service. Resolution This video demonstrates the Poll Service configurations in a Jace (MS/TP and IP) and an Enterprise Server (IP)   About Polling  Polling Statistics  Polling Rate Tuning  About Polling Components   

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 Services for assistance. Issue Backup and Restore assures that Building Operation server data can be restored after a hardware failure or data loss. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Enterprise Server Automation Server Workstation Cause Restore is the process of restoring data to an original or former state. Using restore, you can revert back to a previous snapshot of the server data despite any configuration changes made since the last backup. In Building Operation, restore is designed to be a manual rather than an automatic process to avoid the accidental overwriting of current server data. For convenience, Building Operation displays only the backup files that apply to the selected server.  For more information on making a backup, see Backup of StruxureWare/EcoStruxure Building Operation AS and ES. Resolution Restore an Enterprise Server Backup Set If restoring to a previous snapshot of the database that is currently running, start with step 6. If restoring a database that is different from the one currently running, start with step 1. Launch StruxureWare Software Administrator; Start > All Programs > Schneider Electric > StruxureWare X.X > StruxureWare Software Administrator. Click the Stop Service button and then click OK. Go to the Enterprise server database folders; C:\ProgramData\Schneider Electric\StruxureWare X.X\Enterprise Server Change the name of the current database folder to something that identifies it with the project's name (Example outlined in red: db changed to Old_db). Make a duplicate of the "db - Copy" folder (Example outlined in orange). It is important to always maintain a clean database folder by making copies. After first installing StruxureWare, a copy should be made of the original "db" folder. Copies of this folder should be made before restoring databases or creating new ones from then on. Change the name of the "db - Copy" folder to "db" (Example outlined in blue: db - Copy changed to db). Launch StruxureWare Software Administrator again, click Start Service, and then OK. Launch StruxureWare WorkStation and log into the enterprise server;  Start > All Programs > Schneider Electric > StruxureWare X.X > StruxureWare WorkStation. Select the enterprise server and go to the Main Menu > Actions > Restore. In the Restore Options window, there are a few different options that can be selected. If the desired .xbk file to be restored has already been imported into the current database, it will be visible in the "Available restore points" window. To import the file into the database, select the "Import Backup Set" button and browse to the .xbk file. After selecting the backup set, choose to perform a Configuration only or All data restore. Click Restore. Note: If a backup set is seen in red it means that the backup is not compatible with the current version of the server. The backup has to be the exact same version as the server including any hotfixes or service packs.   Select Yes to restore. Click Close, the restore is now complete. The server will restart, causing the current user to be logged off. After a couple of minutes the server will restart, log into WorkStation and the backed up data will be available. Note: The server name is part of the restore data. Therefore, if you rename a server after a backup, a restore process will revert back to the previous server name.       Replace an Automation Server with a Restore Note: The automation server restore should be done by logging directly into the automation server. Launch StruxureWare WorkStation and log into the enterprise server or the automation server;  Start > All Programs > Schneider Electric > StruxureWare X.X > StruxureWare WorkStation. Select the automation server and go to the Main Menu > Actions > Restore. In the Restore Options window, there are a few different options that can be selected. If the desired .xbk file to be restored has already been imported into the current database, it will be visible in the "Available restore points" window. To import the file into the database, select the "Import Backup Set" button and browse to the .xbk file. After selecting the backup set, choose to perform a Configuration only or All data restore. Click Restore. Select Yes to restore. Click Close, the restore is now complete. The server will restart, causing the current user to be logged off. After a couple of minutes the server will restart, log into WorkStation and the backed up data will be available.

Issue What process do the bCX and b3 controllers use to automatically establish their communication bus speed. Product Line Andover Continuum Environment bCX b3 Auto Baud MSTP Cause Having issues with b3 controllers selecting the wrong bus speed. Resolution The process by which the b3 controllers establish their communication speed is as follows. When the b3 controllers power up, they listen to the network for 2.5 seconds If they hear communication at their last known Baud rate, they start talking when they hear the poll for master. If they hear no communication after 2.5 seconds, they start their own poll for master at their last known Baud Rate. If they hear garbled communication during the 2.5 second listen mode, they begin hunting different Baud Rates while listening until they have synced to the Baud Rate they are listening to. Then they join the token passing when they receive the Poll for Master. Note:  There was a issue with the autobaud process in earlier versions of the b3 and BCX40xx controllers which would cause them to set the communication speed incorrectly.  This issue was corrected in the following firmware versions. BCX40xx ==> 4.500053 b3xxx      ==> 4.500064 b-3xxx-V ==> 4.501064

Issue When starting Continuum version 1.94 (64-bit OS), the main screen is blank.   Product Line Andover Continuum   Environment CyberStation 1.94 (64-bit OS) WebClient 1.94 (64-bit OS) Cause When Continuum is installed on a 64-bit OS, the Main.bmp file is stored in: C:\Program Files (x86)\Continuum\UserProfile  However the application is looking for the file in C:\Program Files\Continuum\UserProfile.   Resolution Configure the Main Menu to search for the Main.bmp file in the correct directory: In the "blank" Main menu, right-click in the white space, and select Edit Right click in the white space again, and select Page Properties In the Background File field, press the "..." button.  In the "Open" window, navigate to the  C:\Program Files (x86)\Continuum\UserProfile directory Select the Main.bmp file.  Press Open Click OK on the Page Edit window In the Edit window, press the Run Page button (looks like a Lightning Bolt) to close the Edit window Re-start Continuum (if necessary)

Issue Automation Server -Trend does not record at time interval when it is stopped and restarted by AS power cycle or reboot. Trend log cycle is thrown off when the trend is stopped and started again due to an AS power cycle or reboot. For example, an Interval Trend Log set up to log ever 15 minutes with an activation time right on the hour (1:00, 1:15, 1:30 etc.) that lost power for a while would start logging as soon as the power was restored (this might be 2:07, 2:22, 2:37 etc. for example). UPDATE: This issue has been corrected in SBO version 1.5, any SBO version 1.5 or grater will synchronize the interval log to the clock. Product Line EcoStruxure Building Operation Environment Automation Server Struxureware Workstation Cause This is how Interval Trends behave. For interval trending based on the time a different approach must be taken. UPDATE: This issue has been corrected in SBO version 1.5, any SBO version 1.5 or grater will synchronize the interval log to the clock. Resolution Rather than using Interval Trend Logs use Variable Triggered Trend Logs and trigger them using the following method: Create a new binary value and a new function block program. The value will serve to trigger the Variable Triggered Trend Logs. The program will set the trigger variable based on a certain time interval (for example on the hour, 15 minutes, 30 minutes and 45 minutes). Edit the program and configure it as seen in the image below. This include an integer input, an expression that will evaluate the minutes attribute of the AS and a binary output. You can also download an export of the program and value here. Bind the input of the program to the minutes attribute of the Automation Server and the output to the trigger value that you created. Note that you should also bind the Task to Task 1 (100 ms) for best performance. Create your Variable Triggered Trend Logs on the points that you want to trend. Do this by right-clicking the point to trend and selecting New > Trend and then in the dialog select Variable Triggered Trend Log. Click Next and then set the Trigger Variable to the value that you created. Make sure Trigger when is set to Change to true. Note that this example will create a log at 0, 15, 30 and 45 minutes past the hour. You can modify the program to trigger only every hour, every half hour or however you want.

Issue What are the locations where Controller configuration data is saved? Environment Continuum Cyberstation Continuum Controllers Cause Unsure as to where controller configuration information is stored and how to clear/reset this information if required. Resolution There are a number of different locations that a controllers database (configuration information) is stored - there are four locations for a BACnet controllers database and three for an Infinity controller. 1. Continuum SQL Database - Infinet tree In Continuum Explorer, this is where the controller is originally created as a Device object under a Network Folder and commissioned into the Database. This is the location where objects (inputs, outputs, programs, etc...) are created. When creating a new object, it is created in both the SQL Database and also sent out to the controllers database at the same time. The controllers information stored in the SQL Database can be sent out to the controller at any time by performing a reload of that controller (right-click Device object, Send to controller). This information can be removed from the database and the controller by deleting individual objects or by deleting the entire Device object. If the Workstation where this delete was performed is online to the field devices then the same object(s) will be removed from the live controller in the field as well as from the SQL Database. If the Workstation is offline to the field controllers  (Workstations can be taken offline for offline editing) then this delete is only applied to the objects in the SQL Database – the objects will still be located in the controllers though, creating a mismatch between the two until the controller is reloaded. 2. Controller RAM This is the active location of memory on the controller where the running database resides. On most controllers there is a backup battery that keeps this RAM alive with a trickle current when there is no power to the controller. When the controller is powered up it first tries to load its active database from RAM - this is the most current backup. The database in controller RAM can be cleared by pressing the Reset button on the Runtime tab of the controllers Device object in Continuum Explorer. 3. Controller FLASH This is the backup location of where the controllers configuration database resides. At any time the active RAM database can be saved to backup Flash by selecting "save to flash" from the controllers Device object in Continuum Explorer. This then makes an exact copy of the database in RAM (excluding point values) that can be restored at a later date either manually or automatically if the controller reboots and their is no valid database in RAM. For Netcontrollers and bCX's, this database saved to Flash can be deleted from the controllers configuration page (configuration webpage) select Clear Database Backup and then commit changes to controller. If the controllers webpage cannot be accessed, pushing and holding down the controller's reset IP switch for 30 seconds clears any backup in flash in addition to resetting the IP address and ACC node id to default. Another way to clear a controllers flash is to save a blank controller database to flash. Create a new controller Device object and then save that to flash. 4. Continuum SQL Database - BACnet tree The information stored in the BACnet tree is the BACnet side of our configured Infinet objects. This is the BACnet objects as seen in the controller and as third-party BACnet Devices will see them. When performing a "send to database" on the BACnet side, the Workstation goes out to the controller in the field, grabs all the BACnet objects and exposes them in the BACnet tree so that they can be used within Continuum. These can be deleted from the BACnet tree without harming those objects configuration in the controller or the Infinet tree. To recap:   To Create and save objects to the controller requires a two step process. Step 1: Create Database objects using Continuum Cyberstation. Objects are added to both the active RAM of the Controller and the SQL Database. Step 2: Save to Flash on the Controller. The objects in active RAM are backed up to the Flash RAM. If unsure, the only way to know that the Database in the RAM and Flash is the same as that in the SQL Database is to perform a reload of the Controller and then backup to Flash. Step 3: Send to Controller to reload configuration information from SQL Database to Controller RAM. After reload, redo Step 2 to backup to Flash. To completely wipe configuration information from a controller in the field you will need to clear its active RAM and its backed up Flash. If you want to clear all information of the controller from the field and the SQL Database then you will need to clear the RAM and Flash and delete the Device object from both the BACnet and Infinet sides of the tree. If you want to remove specific configured points from the controller but retain it in the tree, you will need to first delete the BACnet side of the controller from the BACnet tree, then you can delete individual objects (or make changes) from the Infinet tree.  

Issue EM42 is obsolete and is no longer available when replacement is needed Environment VTRA linkage kit 8600990000 EM9 180° 8601110000 VTRA valve EM42 Cause Replacement of obsolete actuator on old style valve Resolution The replacement actuator for EM42 on a VTRA valve is  EM9 180°, 8601110000, together with linkage kit 8600990000. The linkage kit originally included with the EM9 package should NOT be used.

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 Some actuators manufactured by Belimo are also available from Schneider Electric Environment Various Belimo Actuators: AF 230 AF 230-S AF 24 AF 24-S AF 24-SR LF 230 LF 24 LM 230 A LM 230 A-S LM 24 A LM 24 A-S LM 24 A-SR NM 230A NM 24A NM 24A-SR SM 230A SM 24A SM 24A-SR Various Schneider electric actuators, part no: 875-0000-010 875-0010-010 874-0000-010 874-0010-010 877-0000-010 875-0003-000 874-0003-000 875-1001-000 875-1003-000 875-1005-000 875-1007-000 875-1009-000 875-1011-000 875-1015-000 875-1019-000 875-1021-000 875-1025-000 875-1029-000   Cause Cross reference between various actuators of Belimo and Schneider Electric Resolution A cross reference table for these actuators can be found here (.xls).

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 If the passphrase is incorrect when trying to install a station .bog, the following error message can appear; Transfer failed. com.tridium.platform.daemon.DaemonResponseException: Request to platform daemon at (stationName) failed: bad return code to commit file instance at com.tridium.platform.daemon.DaemonFileUtil.transfer(DaemonFileUtil.java:661) at com.tridium.install.InstallScenario.commit(InstallScenario.java:1444) at com.tridium.platDaemon.ui.stationtransfer.FinalStep.run(FinalStep.java:341) at java.lang.Thread.run(Thread.java:750) Product Line TAC IA Series Environment I/A Series N4 Enterprise Server I/A Series N4 Jace Cause The .bog has not been properly placed in the User Home / Stations for copying into the device or the passphrase is not known. Resolution Always use the Station Copier to install the .bog from the User Home / Stations path If the error message appears, open Workbench and navigate to the "Stations" folder under the "User Home" Expand the station you are attempting to install Double-click the .bog (1) and locate the "Bog File Protection" icon at the top of the page (2) Select the (1) "Force the File to start..." radio button and (2) Update.  Note the information regarding existing passwords. If the message "Cannot display page" occurs when you double click the .bog, open the "Details" and look for missing modules "Cannot load module '......=.....'. Any missing modules will need to be available on the Jace or ES before attempting the force start operation.  

Issue What diagnostic information is available within Niagara that can be sent to Product Support or acted on locally? Product Line TAC IA Series Environment I/A Series Enterprise Server I/A Series Jace Cause Jace or Enterprise Server operating slow or specific problems are causing the need for debugging a station or platform Resolution There are several diagnostic tools available: Check the station Resource Manager Right-click on the station and select "Views - Station Summary" This will open up a resource monitor page where you can check CPU and memory usage.  The CPU should not be consistently above 80%.  Spiking is common as the process is executing and completing tasks.  There are other things easily referenced here also. Heap memory will vary as well.  It can slowly increase until a garbage collection cycle releases unused heap back to the pool.  You should never use more than 75% of the total available heap memory. Heap Memory is primarily used by station modules and java program objects, so if the memory usage is high, these 2 might be the main reasons Engine Hogs   Right-click on the station, and select "Spy". From the main view, click on "sysManagers". Click "engineManager" and then scroll down to find "Engine Hogs". Clicking Engine Hogs will open a list of the main components of the station and a column on the right-hand side will display the average execution time of the component. Review the top 10 or so and see if any are taking an extraordinary amount of time.  This can help to locate improperly executing objects. Driver Poll Rates Drivers that are based on polling data, like BACnet when COV is not enabled, or Modbus constantly run commands to read data based on the fast, normal, and slow configured rates.  Open the Poll Service under the network the points are being polled on. Looking at the property sheet of the driver, it is important to verify that the cycle time (1) for each rate (fast/normal/slow) is always equal to, or below the actual time configured (2) for that rate. The defaults are 1 second for Fast Cycle Time, 5 seconds for the Normal Cycle Time and 30 seconds for the Slow Cycle Time. Seeing a longer cycle time is usually an indication that the network is saturated with commands and may cause the Jace/Niagara controller to be slow with heavy use of controller resources.  There are several ways to correct this: changing the polling rate spreading the number of objects being polled at each rate, etc. In this example, all points (3) are in the "normal" bucket. Application Director console The "Application Director" (under "Platform") shows a live console output.  Open it by clicking the option under the platform Copy the content of the Application Director, or "stream to file" to send the content to support. It will be essential to help the support engineer to understand the problems in the station.  Add more debug information to the Application Director console You can add more granularity to the messages in the Application Director for a deeper look into possible issues. This can be accomplished in 2 different ways: Right-click on the station, and select "Spy". Then, select "logSetup" on the main view From the list that appears, you can scroll and find appropriate topics to log and you can select at what level you want the information to appear.  This will add traffic to the application Director window so be careful how "fine" and how many logs you enable.  It might be good to consult with support before enabling these logs. example; bacnet.debug/finest if you select this box. Debug Service   Select the "DebugService" from the station "Services" In the Log Category, type a few letters of the topic and scroll to find what you are interested in logging From the pulldown menu, determine the granularity of the log Click the plus Click "Save" Setting this logging and streaming the output to a file will allow information to be sent to support for better diagnostics if required.  Remember to set this logging back to "Default" when done so the Application Director is not overwhelmed with information when you are only trying to view normal station activity.

Issue Belkin Bluetooth adapter (F8T01n) on WIN 7 32-bit computer won't connect to MNB-ROAM-IA. Environment PC with Windows 7, 32-bit operating system Belkin Bluetooth adapter, model # F8T016 - F8T017 MNB-ROAM-IA WorkPlace Tech 5.x, configured for BACnet/ MSTP communications with MNB-ROAM-IA Cause The instructions for installing the Belkin Bluetooth adapter as documented in F-27578, TAC I/A Series ROAM-IA Quick Start Guide, "Windows XP-Specific Instructions for Bluetooth Installation", do not apply to installing the adapter on a computer with the Windows 7 operating system.  The procedure is substantially  different in "look and feel" on a Windows 7 computer than on a Windows XP machine - the instructions for Windows XP are not much help on a Windows 7 installation. Resolution The following series of screen captures will illustrate the procedure for installing a Belkin Bluetooth adapter on a Windows 7, 32-bit machine. 1. According to the Belkin FAQ shown, "Most Belkin Bluetooth USB adaptors install automatically without any extra software on Windows 7. Simply plug the device into a spare USB Slot. Windows 7 should automatically recognize the device and install the necessary drivers and software."  This was the case on the laptop PC tested, a Dell Latitude E5500. Screen prompts indicated that the drivers were loaded successfully, and the device was ready to use. 2. Open the Device manager, and there will be a folder for Bluetooth Radios. Expand the node, see the Generic Bluetooth Adapter. 3. Switch on the MNB-ROAM-IA. A Bluetooth icon will be added to the Windows Toolbar. 4. Click on the icon to bring up a menu. From the menu, select "Add a Device". The wizard will search for Bluetooth devices within range, should find the tac-RoamIA:nnnnnnn, where nnnnnnn is the serial number of the MNB-ROAM-IA. This should match the label on the back of the MNB-ROAM-IA 5. Pressing the "Next " button will bring up the "Select Pairing Option" screen. 6. Select the middle option, "Enter the device's pairing code", and press "Next". This brings up the following screen.  Type the pairing code "tac" in the box. The code is case-sensitive, must use lower-case as shown. 7. When the MNB-ROAM-IA has been successfully added and paired, the wizard will display the status. 8. Click on the hyperlink for Devices and Printers to verify that the device has finished installing properly, as follows. 9. In the Windows Device Manager, a Bluetooth Radios folder should be displayed. Expand the folder to see the Generic Bluetooth Adapter. 10. Right-click on the Generic Bluetooth Adapter, go to its Properties, Driver tab. The driver shown (6.1.7600.16385) was installed when the adapter was first plugged into the USB port   11. In the Device Manager, expand the ports folder, and two "Standard Serial over Bluetooth link" ports are shown, COM15 and COM5 12. Use the port with the lower number in the WorkPlace Tech communications setup for the MNB-ROAM-IA. In the example shown, COM5 is selected. Press the "Test and Configure Connection" button. 13. When communications are successfully established, the blue LED on the MNB-ROAM-IA will be ON continuously.

Warning COMPLEX PROCEDURE REQUIRED. The resolution of this article has many complex steps that may result in unforeseen results if not performed correctly. If you are at all unfamiliar with the requirements, please contact Product Support Services for assistance. Issue In some situations, when doing a learn on the CX/BCX controller, the learn process aborts and an error prompt pops up, "Can not learn this controller, it contains an unknown model number." Product Line Andover Continuum Environment Cyberstation CX/BCX I2/B3 Cause Learn process has been executed more than once and at least one has not completed. Some controllers that reside in the CX/BCX have not been cleared and have a duplicate infinetID with some controller in the database. Reloading the CX/BCX controller will indicate which controller has the duplicate InfinetID. Resolution It is recommended to create I2/B3 controllers manually (not by learn) to avoid this problem. If this problem happens: Open the BCX/CX controller and click "reset" Reload BCX/CX controller, from the distribution properties window to find out which controller has the duplicated InfinetID Go to the Continuum Explorer, right click the i2/B3 controller which has the duplicated InfinetID and then select "send to text file" Open the text file, change the infinetID for this controller to another number that does not exist in the database. Delete the i2/B3 controller which has the duplicated ID and import the text file. Reload the CX/BCX controller, there will be no more error. Do learn again on the commport of BCX/CX controller, that should execute successfully. For any other installation issues that also result in this error, please refer to Unknown model number error when learning I2/b3 device

Issue Niagara 4.9 (or later) sometimes has a new Host ID that differs from the Host IDs of other versions of Niagara that were installed on the same host PC Product Line TAC IA Series Environment I/A Series N4 Enterprise Server Cause Niagara 4.9 and later, are only available in a 64-bit version. The older Niagara versions installed on the host PC are probably 32-bit versions, which will always have Host IDs different from 64-bit versions. Resolution If the older versions are Niagara 4.3 or lower, you may need to update the older versions, as per the following document… I/A Series G3 and N4 Eliminating multiple HostID on a single PC  Niagara 4.9 (or later) is only available in a 64-bit version.  The other Niagara versions installed on the host PC are probably 32-bit versions, which will always have Host IDs different from 64-bit versions.  In this case, the host PC will require one of the following Un-installing the 32-bit versions and re-installing 64-bit equivalents One license, to be "transferred" to a different Host ID when necessary Multiple licenses, one for each unique Host ID.

Issue N4 software installation stops because; azul-zre-compact3-qnx7-arm tridium-qnx7-n4-titan-am335x software is missing Product Line TAC IA Series Environment I/A Series N4 Jace 8000 Cause A valid license including the features that meet the dependencies is not installed. Resolution Install a valid license containing the jre8J8000Azul, jre8Qnz7Zulu and qnx7, jreQnx7Zulu features before attempting to commission the Jace 8000

Issue Require details on where to find the Pelco VideoXpert integration package and which versions are supported with Security Expert as the information cannot be found on the Scheider Electric EcoXpert Extranet. Product Line EcoStruxure Security Expert Environment Security Expert Pelco VideoXpert Cause Pelco now supports the VideoXpert integration with Security Expert directly. Resolution All information can be found on Pelco's  partners website, this includes: Security Expert VideoXpert Integration User Guide Security Expert VideoXpert Integration Download Installer Access Control OpsCenter Plugin Information on required licenses A contact form for further support

Issue When opening a BACnet AnalogInput  from (the Blue) BACnet device side, the value of the object displays as 3 decimal digits by default. The format can be changed in the format field as desired, however when clicking the "Apply" button, an error prompt box pops up with the message "An attempt has been made to write a property defined as inaccessible through the BACnet  protocol write services". if the "Apply" buttonis clicked again, the error disappears and the format is been changed successfully. Product Line Andover Continuum Environment Continuum BACnet BCX1 B3s Cyberstation V2.02 and earlier. Cause Format is not a standard BACnet property, it is a Continuum attribute and when the format is changed Cyberstation sends a command to change the "present value" of the point in the controller. The present value of AnalogInput cannot be written so the error occurs. When clicking "apply" or "OK" for the second time Cyberstation only writes the attribute of the point in the database rather than the controller. Therefore we can get a successful change of format for AnalogInput by clicking "Apply" twice. For AnalogValue, the "present value" of  AnalogValue can be written in BACnet, so there is no error when changing the format of an AnalogValue. Resolution Ignore the error when making the change, click the "Apply" button twice after updating the "Format". Or upgrade to V2.03 where this issue has been resolved.

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 Controller loses data following power failure or mains noise (from transients or spikes). Product Line Andover Continuum Environment All CX, ACX, i2, bCX, b3 controllers Cause Controllers are exposed to operating conditions outside their operating envelope and tested limits. This can cause them to reset, go offline or lose data. In extreme circumstances, poor installation can take controllers outside their operating envelope and cause damage requiring a repair. Resolution If a controller is setup on a bench with a clean power supply and the correct grounding, you will be able to turn off/ on the power and the controller will warm start every time. This test will confirm the controller is operating correctly, not faulty and that the software settings are correctly set for warm starting. Also that the RAM backup battery is connected and operating. If site resets, lockups, loss of memory or other corruption are seen on a site, then here are some of the installation issues to consider: Grounding - All controllers require a clean low impedance earth to sink all of the noise and emission energy a controller may be exposed to. The noise protection circuitry within a controller is designed to dissipate this energy down to earth, if this path is not low impedance the energy can cause a controller to reset or even be damaged permanently. Shared Ground - The earth cable to the Controller should not be shared with any other equipment that is a high inductive or capacitive load, these can generate noise spikes back into the controller. This includes motors (pumps/ fans etc) lighting circuits (capacitive loads), inverters (high frequency noise). Induced emissions - The controller should not be installed near any equipment that may induce excessive radiated emissions into the unit, the radiated emissions from Motors, inverters, radio & microwave equipment, lighting circuits, power wiring can all produce radiated emissions that could exceed the specified limits of the Controllers. By fitting the controllers into earthed metal enclosures you can minimize the external emissions by effectively creating a Faraday cage protecting the controllers circuitry. Power feed - The power requirements for every controller is defined in its datasheet with the defined tolerance, taking the power levels outside these limits can cause incorrect operation. Power spikes - Surges or spikes in power feeds or connection I/O cabling can cause controllers to reset, lose data or even become damaged. Fitting varistors to the power supplies and across any output loads can minimize the impact on the controller, See What Varistors should be used?. Shared Supply - The power feed to a controller should never be shared with other equipment that can generate electrical noise. Never use the same supply to power both controllers and field equipment like valve/ damper actuators in BMS systems or magnetic door locks in Access control, both actuators and the solenoids in Mag locks can generate large back EMF pulses into the controllers that can cause resets or even damage.. Fitting power filters or an external UPS on the controller can protect it from spikes on power up/ down, it is however always best to remove the noise spikes at source, so fit filters the generators, motors, contactors etc. It is also possible for the above issues to cause Infinet networks to Reconfig as well as other networking problems. Note: All controllers are approved and tested to the defined limits for FCC and CE induced and radiated emissions as detailed in the datasheets, for a controller to fail, restart or lose data it must be exposed to levels exceeding these specifications. They are not however power equipment and cannot be exposed to the noise levels power and industrial controls equipment is designed to withstand.

Issue When attempting to create a SOAP Web Service in StruxureWare,  WorkStation crashes after pressing the "Get operations" button for a WSDL file. Environment StruxureWare Workstation version 1.2.0.767 (released 1.2 build) Cause StruxureWare only accepts simple data types in the WSDL file.  Some WSDL files (e.g. Microsoft Exchange Server) uses complex data types (types.xsd) for input parameters and StruxureWare cannot process these data types.   Workstation crashes because of an unhandled exception. Resolution The unhandled exception error crash will be addressed in a future release so that Workstation does not crash upon receiving the error.  At this time, StruxureWare cannot process complex data types in WSDL files, and there are no plans to add this feature.