earth_america
user_standard Iniciar sesión
action_search_stroke
earth_america
Log on to rate and give feedback 1 2 3 4 5 Log on to rate
0
Concepto

Concepto


Productos MP-C, MP-V
Funcionalidades: Ingeniería, Hardware, Dispositivos SmartX IP Controller
Versión del producto: 2023, 2024
20/06/2023

MP Controller Reset Modes

arrow1_rotationNetwork Reset arrow1_rotationFactory Reset arrow1_rotationRetain Levels for Variables arrow1_rotationValue Retention on Restarts Using Command Priority Levels

You can reset and restart the MP controllers in different ways depending on how long you press the reset button. The resets and restarts can affect the retention of values after restart based on the retain levels configured for the variables.

 
action_zoom_plus_stroke Location of the reset button on different MP controller models
Figura: Location of the reset button on different MP controller models

You can use a straightened segment of a paper clip or a similar tool to press the reset button.

Tabla: Reset Modes

Property

Description

Warm start

Press and release the reset button in less than 5 seconds. Performing a power cycle in an MP controller is analogous to a hardware warm start.

Cold start

Press and hold the reset button for more than 5 seconds but less than 9 seconds.

Network reset

Press and hold the reset button for 10 to 19 seconds.

Consult the following Network Reset subsection for more details.

Factory reset

Press and hold the reset button for 20 to 29 seconds.

Consult the following Factory Reset subsection for more details.

Erase database

Press and hold the reset button for 30 to 39 seconds.

Cancel reset action

Press and hold the reset button for more than 40 seconds and then release the button.

Performing this action cancels the reset request that would be initiated by any of the shorter button press durations.

Aviso

If the MP-C is equipped with the MP-C Display add-on module, a count-up timer and progress bar are displayed to assist in reset selection. There is also a reset mode indicator that lets you know which reset occurs if you release at that time.

Network Reset

Aviso

Executing a network reset on an MP-V that supports BACnet MS/TP communications clears all MS/TP settings. If you are operating in MS/TP mode at the time, communications with the MP-V are lost. As a result, you need to visit the controller location (in the ceiling) with an Ethernet cable to reconnect the MP-V controller to the EcoStruxure BMS IP network and reconfigure the MS/TP communications properties. Be sure to attempt all other reset modes and power cycles before applying a network reset as a last resort.

Para obtener más información, consulte Identifying MP-V Controllers That Support Both IP and MSTP Communications .

Perform a network reset for MP controller models with “-M” in the product name to reactivate the one-time automatic baud rate detection. Para obtener más información, consulte MS/TP Communications Baud Rate .

Perform a network reset in WorkStation in order to reset the IP address settings to DHCP with a failover to Auto-IP.

Factory Reset

Aviso

Due to the following considerations, when executing a factory reset of the MP and RP controllers, you should also plan to take any necessary recovery actions. A factory reset causes the following to occur:

  • A static IP address reverts to DHCP causing loss of communications at the previous IP address until corrected.

  • The BACnet Foreign Device configuration is removed which may cause the controller to become unreachable when installed on a different subnet than the hosting server.

  • The MP and RP controller RSTP configuration reverts back to Disabled which will disrupt the daisy chain ring operation that depends on RSTP.

    This may result in a major disruption causing the loss of all controllers on the ring network until you can restore RSTP configuration. (Typically, you do this by using local access).

Aviso

Executing a factory reset on an MP-V that supports BACnet MS/TP communications clears all MS/TP settings. If you are operating in MS/TP mode at the time, communications with the MP-V are lost. As a result, you need to visit the controller location (in the ceiling) with an Ethernet cable to reconnect the MP-V controller to the EcoStruxure BMS IP network and reconfigure the MS/TP communications properties. Be sure to attempt all other reset modes and power cycles before applying a factory reset as a last resort.

Para obtener más información, consulte Identifying MP-V Controllers That Support Both IP and MSTP Communications .

This factory reset issue does not affect MP-C controllers that include a DIP switch to configure the BACnet MS/TP MAC address. Para obtener más información, consulte MS/TP DIP Switches .

In WorkStation, if your MP controller seems completely unresponsive, perform a factory reset to restore the device to a state where it can be successfully commissioned. After you release the reset button, a factory reset may take up to 30 seconds to process. All diagnostic logs and the database are erased during a factory reset. By contrast, controller firmware does not revert and remains at the same active level.

Aviso

A factory reset of an MP or RP controller affects the controller's ability to support upgrading connected devices, such as SpaceLogic Sensor devices, RP controller expansion modules, and Wireless Adapter - Advanced. This is because the necessary firmware files are deleted. After a factory reset, ensure that the controller is upgraded to restore the files needed to support upgrading the connected devices. Para obtener más información, consulte BACnet/IP Device Firmware Management .

Aviso

 After a physical reset in an MP controller, any controller proxy object in the EcoStruxure BMS database that carries the serial number of that controller may trigger an automatic association. This association occurs between the reset physical controller and the controller proxy object in the EcoStruxure BMS database.

Para obtener más información, consulte Automatic Association after a Factory Reset in a BACnet Controller or IO Module .

Retain Levels for Variables

Variables have a configurable retain level, which controls if the value of the variable is retained after a restart of the MP controller. There are three retain levels:

  • No

  • Warm start

  • Cold start

The following table lists what is retained after a warm start or cold start based on the configured retain level.

Tabla: Retained Variable Values Depending on Restart Mode and Retain Level

Restart mode

Retain level:

No

Retain level:

Warm start

Retain level:

Cold start

Warm start

Default value a  

Values configured by a user or application are lost.

Variable retains last value configured by a user.

Values configured by an application are retained. 

Variable retains last value configured by a user.

Values configured by an application are retained. 

Cold start

Default value a

Values configured by a user or application are lost.

Variable loses last value configured by a user.

Values configured by an application are lost.

Variable retains last value configured by a user.

Values configured by an application are retained. 

a Default value is the value the variable gets when it is created.

Para obtener más información, consulte Retain Level .

Aviso

Although variable values in MP controllers are retained in accordance with this matrix, automation server retention behaves differently. As a result, variable values retained in the server that are not retained in the controller may be restored to the controller during a download command. Para obtener más información, consulte Retain Level .

Value Retention on Restarts Using Command Priority Levels

When you configure the restart retain level for an object with command priority levels, it is recommended that you base retention exclusively on either of the following:

  • The value property configured by using the Configure button

     
    action_zoom_plus_stroke
    for that property in the Basic tab of the object.

  • The command priorities configured by the Configure button

     
    action_zoom_plus_stroke
    for the appropriate command priority levels in the Command tab of the object.

Do not configure retention for both the value property on the Basic tab and the command priorities of the object because doing so may result in unexpected behavior following a controller restart. For example, if the value property is configured to retain during a restart, then that value is written to priority 16 following the restart, regardless of the retain level of priority 16.

Para obtener más información, consulte Binding Value and Priority Properties in a BACnet/IP Controller .

Consulte también

  • MP Controller Models
  • BACnet/IP Device Firmware Management
  • Application Images
  • MP Controller Onboard I/O Module
  • BACnet Controller and IO Module Communication
  • Association Selection Workflow
  • Configure an Online BACnet/IP Controller Workflow
  • MP Controller Models
  • Memory in RP and MP Controllers and I/O Modules
  • BACnet/IP Controller Diagnostics
  • Device Discovery for BACnet Controllers and IO Modules
  • BACnet Controller and IO Module Device Management
  • BACnet/IP Device Firmware Management
  • Automatic Association after a Factory Reset in a BACnet Controller or IO Module
  • Automatic Time Sync for BACnet Controllers and IO Modules
  • BACnet/IP Controller Standard Objects
  • Retain Level
  • Binding Value and Priority Properties in a BACnet/IP Controller
  • Identifying MP-V Controllers That Support Both IP and MSTP Communications
  • MS/TP DIP Switches
  • MS/TP Communications Baud Rate