Y_YA_RebootController
This function block reboots controller processes, and reinitializes the motion network. Nodes are temporarily disconnected from network and rediscovered afterward.
Parameters
| * | Parameter | Data Type | Description | Default |
|---|---|---|---|---|
| VAR_INPUT | ||||
| B | Execute | BOOL | Upon the rising edge the function block is executed and the controller is rebooted. | FALSE |
| VAR_OUTPUT | ||||
| B | Done | BOOL | Set high when the commanded action has completed successfully. The Done output will never become TRUE after execution because the reboot process stops the PLC tasks. | |
| B | Busy | BOOL | Set high when the command is Executed and Stays high until Done goes TRUE. | |
| B | Error | BOOL | Set high if an error has occurred during the execution of the function block. This output is cleared when 'Execute' or 'Enable' goes low. | |
| E | ErrorID | UINT | If Error is true, this output provides the Error ID. This output is reset when 'Execute' goes low. | |
Notes
- This function block is useful for resetting an alarm condition which requires a controller power cycle, such as an absolute encoder reset.
- Executing this function will start a complete system reboot, meaning that Ethernet communications will also be restarted.
Error Description
See the
Function Block ErrorID List.
Example
When executing this Function Block the controller will shut down several services before rebooting and therefore the reboot is not instant. This means that at least one scan is needed before the reboot is completed. The following example shows the use of this Function Block in a program with a 1ms task interval taking 6 scans before rebooting. The number of scans might vary due to other factors related to internal processes.
Note: Busy and Execute above are not shown as TRUE due to the controller rebooting faster than the UI updates.
Timing Diagram
Once Reboot occurs, the Done drops out from the block and is not retained.