Concept
RP Controller Reset Modes
You can reset and restart the RP 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.
You can use a straightened segment of a paper clip or a similar tool to press the reset button.
|
Mode |
Description |
|
Warm start |
Press and release the reset button in less than 5 seconds. Performing a power cycle in an RP 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. |
Network Reset
Executing a network reset on an RP controller 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 RP-V are lost. As a result, you need to visit the controller location (in the ceiling) with an Ethernet cable to reconnect the RP-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.
Perform a network reset for RP controller models with “-M” in the product name to reactivate the one-time automatic baud rate detection. For more information, see 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
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).
Executing a factory reset on an RP controller 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 RP-V are lost. As a result, you need to visit the controller location (in the ceiling) with an Ethernet cable to reconnect the RP-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.
In WorkStation, if your RP controller 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.
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. For more information, see BACnet/IP Device Firmware Management .
After a physical or logical factory reset in an RP 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.
For more information, see 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 RP 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.
|
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.
For more information, see Retain Level .
Although variable values in RP 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. For more information, see 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
for that property in the Basic tab of the object.action_zoom_plus_stroke 
The command priorities configured by the Configure button
for the appropriate command priority levels in the Command tab of the object.action_zoom_plus_stroke
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.
For more information, see Binding Value and Priority Properties in a BACnet/IP Controller .
BACnet/IP Controller - RP Models
RP Controller Models
Memory in RP and MP Controllers and I/O Modules
Free Object System Memory Utilization in BACnet Controllers and IO Modules
Retain Level
Application Images
Association Selection Workflow
Configure an Online BACnet/IP Controller Workflow
Binding Value and Priority Properties in a BACnet/IP Controller
BACnet/IP Device Firmware Management
Automatic Association after a Factory Reset in a BACnet Controller or IO Module
MS/TP Communications Baud Rate