Building Automation Knowledge Base

Issue When launching a program or when working with a program, you get an error from "Microsoft .NET Framework".   Product Line EcoStruxure Building Operation, Satchwell MicroNet, TAC INET, TAC Vista Environment Windows .NET Framework Cause Microsoft .NET Framework is used in almost all larger applications, and there can be various reasons why you see an error. One reason can be application specific, meaning that there is an actual issue with the software and the way the software is using .NET Framework, but another reason can be that the .NET Framework installation itself is corrupted. If it's an application specific issue, you need to contact product support, but in many cases simply repairing the .NET Framework installation has proven to solve the issue. Resolution 1: Close all applications 2: Make sure you have the correct version of .NET Framework installed for the software you use referencing the product's data sheet. You can use this tool to check what versions you have. Here is a direct download link. 3: Install versions that might be missing. You can download the various versions from the tool linked above. 4: Download Microsoft's .NET Framework repair tool and run it applying all fixes the tool suggests. Here is a direct download link.

Issue GSM modems that can be used with the Remote Alarm Manager. Product Line Satchwell BAS & Sigma,Satchwell MicroNet,TAC Vista Environment Remote Alarm Manager. BAS Sigma Micronet Vista  GSM RAM Siemens TC35i Siemens MC52i Multi-Tech MTCBA-G-F4-GB/IE Cinterion MTX-65+G-V53 Cause Not all GSM modems will allow the full functionality of message acceptance in the Remote Alarm Manager. Resolution The following GSM modems are known to provide the full message acceptance of the Remote Alarm Manager. Siemens TC35i GSM modem terminal. In the Remote Alarm Manager configuration select the C35i driver. This modem is now being replaced be the Cinterion (Siemens) MC52i GSM/GPRS Dual band modem terminal, which has not been tested, but appears to be a direct replacement with added functionality. TC35i GSM/GPRS modem terminal data sheet MC52i GSM/GPRS modem terminal data sheet Multi-Tech MultiModem MTCBA-G-F4-GB/IE modem terminal. In the Remote Alarm Manager configuration select the Brodersen UCM 91/92. This modem is still available, but seems expensive and difficult to source. MultiTech MultiModems MTCBA-G-F4 data sheet Cinterion MTX-65+G-V53 modem terminal.In the Remote Alarm Manager configuration, allow the software to locate the modem and use a generic driver. Cinterion MTX-65+G-V53 modem terminal data sheet   Remote Alarm Manger is no longer a support solution, it is recommended transitioning or upgrading to EcoStruxure Building Operation.

Issue The Drayton Theta YBM2A Valve Body / Actuator assembly is to be replaced. Product Line Field Devices Environment Replacement Drayton Actuator Valve YBM2A Cause The Drayton Theta YBM2A Valve Body / Actuator assembly is obsolete. Resolution OVERVIEW The Drayton Theta YBM2A Valve Body / Actuator assembly is obsolete, and there is no purpose built replacement. The Valve Body was available in 1.1/4", 1.1/2" and 2" B.S.P. sizes and was normally installed as a mixing valve in variable temperature, constant volume, compensated heating circuits. No Valve Body / Actuator assemblies are currently available in these sizes. Details of the YB Valve Body may be viewed here.   VALVE BODY REPLACEMENT To replace the YBM2A Valve Body the following is required:- S-E Satchwell MB Valve Body of appropriate size - MB1552 (1.1/4"), MB1602 (1.1/2"), MB1652 (2") Details of the MB Valve Body may be viewed here.   ACTUATOR REPLACEMENT The YBM2A Actuator comprised a 3-wire electrical connection enabling it to be operated by a Mains Voltage changeover contact device as follows :- Terminal M1 – Open signal Terminal M2 – Close signal Terminal M3 – Common The YBM2A Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-230 MD20B-230 (if MD10B-230 not available) Details of the MD10B-230 Actuator may be viewed here. Details of the MD20B-230 Actuator may be viewed here. N.B. The YBM2A Actuator also included an additional 3-wire electrical connection associated with an integral S.P.C.O. Auxiliary Switch wired as follows :- Terminal S1 – Normally Closed Contact Terminal S2 – Common Terminal S3 – Normally Open Contact Where external wiring is connected to the YBM2A Actuator Auxiliary Switch then an Auxiliary Switch Kit containing a S.P.C.O. Auxiliary Switch should be installed on the MD Actuator. Auxiliary Switch Kit MD-S1 (914-1060-000) Details of the MD-S1 Auxiliary Switch Kit may be viewed here. The MD-S1 Auxiliary Switch Kit should be wired as follows :-. Terminal S1 – Common Terminal S2 – Normally Closed Contact Terminal S3 – Normally Open Contact   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here In such 3-wire installations the YBM2A Valve / Actuator assembly only will need to be replaced, while any associated Controller and Sensors may be retained.

Issue What is valve authority? Product Line Field Devices Environment Any valve Cause Information on Valve Authority to obtain good control. Resolution Valve Authority = (Pressure drop across fully open control valve) / (pressure drop across the remainder of the circuit) + (pressure drop across fully open valve) In other words, valve authority within a system indicates how much of the system's total pressure drop comes from the control valve. It is common practice to consider the range between .2 to .5 as "acceptable" authority for proportional valve.

Issue The Drayton CRL 240 Actuator / Valve assembly is to be replaced. Product Line Field Devices Environment Replacement Drayton Actuator Valve CRL 240 Cause The Drayton CRL 240 Actuator / Valve is obsolete Resolution The Drayton CRL 240 Actuator / Valve assembly is obsolete and there is no purpose built replacement. The associated Drayton Valve Body was available in numerous sizes.  These sizes are not available in current combined Actuator / Valve designs. To replace one of the above Actuator / Valve Body combinations the following are required :- Valve sizes ½” – 2” Valve – MB(1/2" - 2") Actuator -  MD10B-230 (  MD20B-230 could  be used if MD10B-230 is not available) Auxiliary Switch - MD-S1 ( MD-S2 could be used if MD-S1 is not available) Linkage Kit - LMD/AR-MB or the RM3601 actuator without the need for a linkage kit Linkage Kit Select S-E LMD/AR-MB Linkage Kit. (914-1071-000) MBF Valve sizes 65mm – 100mm Could be replaced by the VTRE range To view the MB Valve Data Sheet, please click here. To view the MD10B Actuator Data Sheet, please click here. To view the MD-S1 Auxiliary Switch Data Sheet, please click here. To view the LMD/AR-MB Linkage Kit Data Sheet, please click here. To view the LMD/AR-MBF Linkage Kit Data Sheet, please click here. To view the RM 360 data sheet please click here

Issue Schneider Electric domain firewall policy Product Line Satchwell BAS & Sigma Environment Engineer's laptops Cause Schneider computer/domain updates include McAfee firewall updates. It has been seen on some laptops with a fully working Sigma system, after a  Schneider policy update, the Sigma client fails to connect to the server.   Resolution Access to the firewall setting, on most Schneider Electric engineer's  laptops is not possible. Disabling the McAfee firewall should allow Sigma to load. Locate and, with a right mouse click, select the McAfee Icon  (found on the taskbar near the clock). From the list provided select "Quick Settings" Then select "Enable Firewall Timed Groups", You will need to enter a reason. The firewall will be disabled for a one hour period. 

Issue Automation Server - Warm and Cold Start differences Product Line EcoStruxure Building Operation Environment Building Operation Automation server Cause The explanation on the differences between a warm start and a cold start in the documentation and web help may not be clear to some.  Resolution Warm Start: Restarts the controller's application Cold Start: Restarts the controller's operating system An Automation Server can be warm/cold started from Workstation or by using the reset button on the Automation Server. Refer to Reset Functions on Web Help for an explanation of the differences between warm and cold starting the AS.  Basically, you can set the Retain Levels for variables in Building Operation to 'No', 'warm start' or 'cold start'. To change the retain level of a variable and go to its properties.  - Click on the gear icon. - Set the retain level of the variable. 1. Retain level set to 'No' - The variable is reset to the value set when the object was created. When you create an Analog Value object, the value of the newly created object is '0'. A user can set this to another value. When retain level is set for this Analog Value object, after a warm or cold start, the value of this object will default back to '0'. 2. Retain level set to 'Warm start' - The value is set back to the last value set by the user. If a user change the value of an Analog Value object to another value and save, after a warm start, the object will return to the last value set by the user.  3. Retain level set to 'Cold start' - The value is set back to the last value set by either the user or the system (for instance by a program). The operation is similar to the warm start but in this case, the last value set by the system will also be retained. 

Issue AVUE 5 Series Actuator does not actuate Control Valve correctly when installed in place of AVUE 2, 3 or 4 Series Actuator. Product Line Field Devices Environment AVUE 5304, AVUE5305, AVUE5354 and AVUE5355 Actuators installed on FEU, MEU, VEU Unit Control Valves. AVUE 5304, AVUE5305, AVUE5354 and AVUE5355 Actuators installed on MZX, VZX Plant Control Valves. Cause AVUE 5 Series Actuators are available with stoke lengths of 9.5mm and 12.7mm AVUE 5304 and AVUE 5354 Actuators provide a stroke length of 12.7mm AVUE 5305 and AVUE 5355 Actuators provide a stroke length of 9.5mm   AVUE 2, 3 and 4 Series Actuators provided universal stroke compatibility. Control Valves having either 9.5mm or 12.7mm stroke could be actuated.  Resolution Select AVUE 5304 (Direct Acting) or AVUE 5354 (Reverse Acting) to actuate MZX or VZX Plant Control Valves. Select AVUE 5305 (Direct Acting) or AVUE 5355 (Reverse Acting) to actuate FEU, MEU or VEU Unit Control Valves.   For further AVUE 5 Series Actuator information please refer to Data Sheet DS 3.002  11/06   The AVUE is no longer available, check the 2022 Valves & Actuators Catalog - EMEA & APAC for a replacement. Note: The valve would need to be replaced to accommodate the replacement actuator.

Issue Communications with other Lon network devices are lost after the IC-Lon/IC3-Lon has cold-started. Product Line Satchwell Sigma Environment Sigma IC-Lon Integration controllers IC3-Lon Integration controllers Cause The controller has been cold-started either manually or through the automatic process. Resolution The final part of the engineering process of the IC-Lon/IC3-Lon, is for the file named NVConfig.bin to be uploaded from the IC-Lon/IC3-Lon to the Sigma server. If this file is not uploaded, then the IC-Lon/IC3-Lon reverts to its non-bound state. The NVConfig.bin file contains information about the Lon bindings and is modified during the binding process when using LonMaker. To upload the NVConfig.bin, carry out the following: Open "System Diagnostics"  on the Sigma server. Select the correct controller number. From the "Options" menu select "Upload Files" and NVConfig.bin This file will now be uploaded and overwrite the existing file in the controller folder, and therefore when the controller next cold-starts, the correct file will be downloaded to it. For more information on the Engineering process of an IC-Lon/IC3-Lon, please click here.   The Sigma system is now out of its support period, consideration should be given to transitioning or upgrading to SpaceLogic - EcoStruxure Building Operation.

Issue Satchwell AR Series 7 Rotary Actuator requires replacement Product Line Field Devices Environment Satchwell AR Series 7 Rotary Actuators installed on Air Dampers, Satchwell MB Series or MBF Series Rotary Shoe Valve Bodies. Actuator types :- ARE ARM ARX Cause Obsolescence of Satchwell AR Series 7 Rotary Actuators Resolution Replace Satchwell AR Series 7 Rotary Actuators with appropriate Schneider Electric MD Series Rotary Actuators and Linkage Kits selected from the following :- Satchwell AR Series 7 Rotary Actuators installed on Air Dampers. ARE Series 7 = MD20A-24 ARM Series 7 = MD20B-230 ARX Series 7 = MD20B-24 N.B. Schneider Electric MD20 Series Actuators are supplied with a Direct Damper Mounting Kit enabling the Actuator to be installed direct on to an Air Damper Spindle. Should the Actuator be required to operate an Air Damper remotely by means of a Damper Crank Arm and associated Connecting Rod and Universal Connectors, then this may be achieved through the installation of the following Linkage Kit :- ZG-MD20 Damper Linkage Kit (914-1063-000) Should the Satchwell AR Series 7 Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the Schneider Electric MD Series Actuator as appropriate :- MD – S1 One independent Mains Voltage rated changeover contact Auxiliary Switch MD – S2 Two independent Mains Voltage rated changeover contact Auxiliary Switches   Satchwell AR Series 7 Rotary Actuators installed on Satchwell MB Series Screwed Rotary Shoe Valve Bodies. ARE Series 7 = MD10A-24 + Linkage Kit 914-1071-000 ARM Series 7 = MD10B-230 + Linkage Kit 914-1071-000 ARX Series 7 = MD10B-24 + Linkage Kit 914-1071-000 N.B. Should the Satchwell AR Series 7 Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the Schneider Electric MD Series Actuator as appropriate :- MD – S1 One independent Mains Voltage rated changeover contact Auxiliary Switch MD – S2 Two independent Mains Voltage rated changeover contact Auxiliary Switches   Satchwell AR Series 7 Rotary Actuators installed on Satchwell MBF Series Flanged Rotary Shoe Valve Bodies ARE Series 7 = MD20A-24 + Linkage Kit 914-1070-000 ARM Series 7 = MD20B-230 + Linkage Kit 914-1070-000 ARX Series 7 = MD20B-24 + Linkage Kit 914-1070-000 N.B. Should the Satchwell AR Series 7 Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the Schneider Electric MD Series Actuator as appropriate :- MD – S1 One independent Mains Voltage rated changeover contact Auxiliary Switch MD – S2 Two independent Mains Voltage rated changeover contact Auxiliary Switches   Product information. For details of MD10A please see here For details of MD10B please see here For details of MD20A please see here For details of MD20B please see here For details of MD-S1 please see here For details of MD-S2 please see here For details of Linkage Kit ZG-MD20 please see here For details of Linkage Kit 914-1070-000 please see here For details of Linkage Kit 914-1071-000 please see here

Issue TAC Vista Server fails to start or "hangs" during startup. "Ensure TAC Vista Server is started" error, after having just started Vista Server and attempting to open Workstation. Product Line TAC Vista Environment Vista Server Cause Corrupt Vista database Bad installation of TAC Vista Resolution Troubleshooting technique to determine if you have corruption of the TAC Vista Database or TAC Vista Software. Determine if the TAC Vista Server is starting by observing the Tacos.exe process in Windows Task Manager. Server is crashing if Tacos.exe is not present or disappears after starting the Server. From the Start Menu, navigate to TAC Vista Server Setup and browse the Vista Server database location to a test location, i.e. :\DBTest. This will create a new "blank" database at that location. Attempt to start TAC Vista Server and observe results in Windows Task Manager. You should get one of two results: If TACOS.exe process is running and the Server seems to start correctly, you may have a corrupted Vista Database. You may further investigate by copying the site Vista Database folder structure and placing it on another computer (with the same Vista Software version) to see if the Server will start. In some cases, it may be successful, a backup can be made and restored to site machine. In most cases, it will also fail. Restoring to a known good backup is the only recourse.   If TACOS.exe process is not running and the Server seems to start incorrectly, you may have corrupted Vista Software. It is recommended to follow the uninstall/ reinstallation procedure for your version of Vista. You may further investigate by copying the site Vista Database folder structure and placing it on another computer (with the same Vista Software version) to see if the Server will start. In this case, it should be successful.

Issue Where can we find the LON xif files for SE72xx, SE73xx, SE76xx controllers? Product Line EcoStruxure Building Expert,EcoStruxure Building Operation,Field Devices Environment SE7200 / SE7300 / SE76000 Room Controllers Cause xif files are needed for LON applications. Resolution All LON related files for these controllers are available for download on The Exchange Download Center:   XIF files and plug-ins Resource files (DRF kit)

Issue BAS is obsolete how can it be upgraded to Sigma? Product Line Satchwell BAS & Sigma Environment Satchwell BAS 2800+ V2.9 Satchwell Sigma Cause BAS is obsolete but there is a defined path to upgrade the system to Sigma Resolution Upgrading must start from BAS2800+ v2.9 when upgrading to the latest version of Sigma.  Sigma not only allows for more features but also future proofs the system. Upgrade procedure can be found here Migration document (Sales support) can be found here Any BAS versions before BAS2800 + V2.9 please contact Product Support with the details.   The Sigma system is now out of its support period, consideration should be given to transitioning or upgrading to SpaceLogic - EcoStruxure Building Operation.

Issue A calibration certificate is sometimes requested by the end customer Product Line Field Devices Environment Schneider Electric sensor portfolio Cause To ensure that a sensor is keeping measurement values within specification, a certificate is sometimes requested by the end customer. Resolution If a calibration certificate is requested, this must be notified to the Orders dept when the order is placed. The ordered sensors are then tested again according to the specifications and delivered with a calibration certificate. This process may lead to additional costs and a slightly longer delivery time. Calibration certificates cannot be produced after the products are delivered. Download the Sensor Calibration Certificate Order Form

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 Some IO modules status showing as 'Blacklisted device detected" or "Address shift detected" or a system alarm is received indicating the condition. AS trace logs may show one of the following entries... 2015-08-18 17:41:02.675 [1256862784] nsp.pin.cio.IODevice Module at address 14 is reporting Internal Error Code 32 2015-08-18 17:41:02.757 [1256862784] nsp.pin.cio.IODevice Module at address 28 is reporting Internal Error Code 32 2015-08-18 17:41:02.825 [1256862784] nsp.pin.cio.IODevice Module at address 12 is reporting Internal Error Code 32 2015-08-18 17:41:02.869 [1256862784] nsp.pin.cio.IODevice Module at address 13 is reporting Internal Error Code 32 2015-08-18 17:41:02.951 [1256862784] nsp.pin.cio.IODevice Module at address 15 is reporting Internal Error Code 32   2015-06-18 10:05:13.912 [1255584832] nsp.pin.cio.CIOException Error: Bad_Address (0xb0000), module Automation_Server_Io_Bus(31), moduleCode 0, dispString "AS address is invalid", techString "nsp_servers/plugins/CentralIOPlugIn/CIO/source/IOManager.cpp line 460" 2015-06-18 10:05:20.789 [1255584832] nsp.pin.cio.IOBus IOBusServer::run: Caught CIO exception from slot 3   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause One or more terminal base may have to be replaced. Intermittent IO connection (typically in S-cable). Resolution Follow this document or Blacklisted Device Detected for steps to resolve the problem.

Issue Site looking to add some WorkStations with the ability to show Graphics but without the Graphic editor. Not sure which part number to order. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Cause Documentation Resolution V2 or higher, Enterprise Server or Enterprise Central license includes three concurrent client licenses (WebSation or WorkStation). For additional clients, order one or more of the licenses below. These licenses do not include any editors, the WorkStation will show the graphics but will not allow editing, order below part numbers:   If graphic or programming editing is required, you can order professional WorkStation license, which will add extra WorkStation with editors, or order Programming & Graphics Editor licensing, which will add editors to existing WorkStation Standard license.  

Issue How to get an MSTP capture file so it can be analyzed for comm activity on an MSTP bus How to determine if a site is using bad COV management How to determine if a controller has poor bus design or installation How to determine if a site has multiple BBMD's on the same subnet Product Line Andover Continuum, EcoStruxure Building Operation Environment bCX4000, bCX4040, ASP, ASB b3 controllers Third party BACnet MSTP devices Wireshark Cause Analyze MSTP traffic via capture. Resolution To capture MSTP communication activity to a capture file that can be analyzed using a network sniffer application such as WireShark you will need the following.   Hardware One is required to have an RS-485 Adapter to connect to the MS/TP trunk USB to RS-485 Adapter USB-RS485-WE-1800-BT FTDI, Future Technology Devices International Ltd | 768-1041-ND | DigiKey  RoamIA or RoamIO Any other RS-485 adapter compatible with BACnet MS/TP and baud rates used Software Download and install the following applications: BACnet MSTP Capture Application WireShark Configuration If using the USB to RS-485 Adapter Connect the USB adapter cable to the USB port on a laptop PC Connect the RS232/RS485 adapter to the 9-pin end of the USB adapter cable. Attach a length of MSTP bus cable to the wire terminal on the RS485 adapter. If using the FTDI Connect the TDI RS-485 adapter to the USB port on a laptop PC Connect the cables to the MSTP trunk where Orange = Data+ (A) and Yellow = Data- (B) Ensure the RS-485 adapter driver is installed in Windows by opening Device Manager and ensuring that it is listed as expected under Ports (COM and LPT). Record the COMx being reserved by the adapter.  If using Wireshark with MSTPcap.exe to capture Ensure MSTPcap.exe is installed in the Wireshark Extcap folder per MSTP Capture Application link above NOTE: Wireshark may need to be rebooted if MSTPcap.exe was added while it was open Launch Wireshark Select gear next to BACnet MS/TP on COMx Set known baud rate Click to start a capture.  If using MSTPcap.exe via Command Prompt to capture Copy the MSTP Capture application to C:\ Open a command window. Launch the application by entering C:\> Mstpcap com# ###### where com# is the PC's serial port (Com1, Com2, etc.) and ##### is the current baud rate the bCX/AS MSTP bus is configured for (19200, 38400, etc.). The command window will indicate the name of the file the activity is being captured to. Once done, close the command line window The capture data can be viewed by running Wireshark. Select File > Open and navigate to the folder the capture file was saved to and select the capture file. With the higher-end MSTP capture tools such as tools developed by PolarSoft and Cimetrix, MSTP captures at 76.8K baud are possible. Lower-end capture applications like MSTPCap typically are only able to capture MSTP packets from networks running at bus speeds at or below 38.4K baud. Also, check out the BACnet-Capturing MS/TP Traffic Quick-Help video on the Exchange. This video uses the older pipe method that was used before Extcap was available in Wireshark.

Issue Controller Download fails when downloading files into a BAS outstation. Product Line Satchwell BAS & Sigma Environment Satchwell BAS2000 Satchwell BAS2800 Satchwell BAS2800+ Cause File downloads (only outstation files, not node files) fail from a terminal connected to port 2 of an outstation e.g an engineers laptop.  Resolution Either perform a commstats (F3) of the node and a list of what devices and their number attached to each port is displayed. Or check the site node file to see what terminal number is configured to the outstation on Port 2. In either case the letter "T" with a device number will indicate a terminal has been set. In the BAS setup page, change the terminal number to match that found in item 1. Save and exit BAS. Re-open BAS, now download files to the controller.

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 Upgrading the MPMs firmware through the boot loader was unsuccessful. 10.50.80.2 is pingable, but not the default IP 10.50.80.3. The LED's keep blinking in tandem (alternating one after the other), even after having the MPM powered over 10 seconds. Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager Cause This can be triggered by multiple events: - MPM was interrupted (powered off) while the firmware was still being upgraded. - Database does not exist; MPM was formatted and does not have firmware installed. - Database is corrupt (for any reason) Resolution It is strongly recommended that a firmware upgrade be done via the "File Manager" tab in Building Expert. However, if this is not possible, an upgrade can be performed through the bootloader using the following steps: 1 - At the top left part of the screen, make sure "Status" says "Connected". 2 - Format the SD card clicking on the "Submit" button next to "File System Format". "Format Done" will be displayed next to the button once the format has been completed 3 - Click on the "Browse" button and Navigate to the Firmware_update_V2.XX.bp" on your computer then click on "Submit Query". 4 - The previous step will upload the firmware file to the MPM's SD card. Once the file has been transferred, the following message will appear: or 5 - The MPM Must be kept powered-up for at least 15 minutes in order to allow the MPM some time to unpack the firmware file. The best way to determine whether the MPM is back online is to ping its IP address using a "Command Prompt" window. 6 - Once the MPM replies to the ping, Building Expert can be accessible though 10.50.80.3   If the above solution does not work; meaning that every time a new firmware is pushed to the MPM, the MPM keeps coming back to the bootloader, contact technical support

Issue Definition of number of nodes and points allowed using Modbus TCP/IP or RTU xdriver. Product Line Andover Continuum Environment Modbus Protocol Cause Definition of number of nodes and points allowed using Modbus TCP/IP or RTU xdriver according to the modbus protocol. Resolution The maximum number of nodes is 254. The address range for points is 1 through to 65535. The number of addresses is limited by the controller memory. We have had ~6000 points but please note the Modbus is a polled protocol so the more points you have the longer the poll rate.   Specific Modbus RTU Details Our Modbus RTU XDriver supports the node range from 0-255. According to the Modbus specification, the node range is from 0 – 255, with 0 being the master, 1-247 being the slaves, and 248-255 being reserved addresses. After 32 nodes (1 master + 31 slaves), you may need RS-485 repeaters to ensure proper communications. This depends on a number of different items, including if the RS485 transceivers are full or quarter load. You can find the Modbus serial standard at the link below for further details. http://www.modbus.org/docs/Modbus_over_serial_line_V1.pdf