Rockwell Automation Publication 2080-UM002K-EN-E - March 2019
109
Motion Control
Chapter
7
When a motion control function block ends with an error, and the axis is in
ErrorStop state, in most cases, MC_Reset function block (or, MC_Power
Off/On and MC_Reset) can be used to have the axis to be recovered. With this,
the axis can get back to normal motion operation without stopping the controller
operation.
Major Fault Handling
In case the controller encounters issues where recovery is not possible through the
Stop, Reset, or Power function blocks, controller operation will be stopped and a
major fault will be reported.
The following motion-related major fault codes are defined for Micro830,
Micro850, and Micro870 controllers.
Motion Axis Configuration
in Connected Components
Workbench
A maximum of three motion axes can be configured through the Connected
Components Workbench software. To add, configure, update, delete, and
monitor an axis in Connected Components Workbench, refer to the next
sections.
Major Fault Error Codes and Description
Major Fault
Value
Fault ID MACRO
Major Fault description
0xF100
EP_MC_CONFIG_GEN_ERR
There is general configuration error detected in
the motion configuration downloaded from
Connected Components Workbench, such as Num
of Axis, or Motion execution interval being
configured out of range.
When this major fault is reported, there could be
no axis in ErrorStop state.
0xF110
EP_MC_RESOURCE_MISSING
Motion configuration has mismatch issues with
motion resource downloaded to the controller.
There are some motion resources missing.
When this major fault is reported, there could be
no axis in ErrorStop state.
0xF12x
EP_MC_CONFIG_AXS_ERR
Motion configuration for axis cannot be
supported by this catalog, or the configuration
has some resource conflict with some other
motion axis, which has been configured earlier.
The possible reason could be maximum velocity,
max acceleration is configured out of supported
range.
x = the logic Axis ID (0…3).
0xF15x
EP_MC_ENGINE_ERR
There is a motion engine logic error (firmware
logic issue or memory crash) for one axis
detected during motion engine cyclic operation.
One possible reason can be motion engine
data/memory crash.
(This is motion engine operation error, and should
not happen in normal condition.)
x = the logic Axis ID (0…3).
TIP
Configuration changes must be compiled and downloaded to the
controller to take effect.
Содержание Micro830
Страница 6: ...vi Rockwell Automation Publication 2080 UM002K EN E March 2019 Preface Notes ...
Страница 24: ...10 Rockwell Automation Publication 2080 UM002K EN E March 2019 Chapter 1 Hardware Overview Notes ...
Страница 70: ...56 Rockwell Automation Publication 2080 UM002K EN E March 2019 Chapter 4 Wire Your Controller Notes ...
Страница 88: ...74 Rockwell Automation Publication 2080 UM002K EN E March 2019 Chapter 5 Communication Connections Notes ...
Страница 190: ...176 Rockwell Automation Publication 2080 UM002K EN E March 2019 Chapter 9 Controller Security Notes ...
Страница 254: ...240 Rockwell Automation Publication 2080 UM002K EN E March 2019 Appendix A Specifications Notes ...
Страница 273: ...Rockwell Automation Publication 2080 UM002K EN E March 2019 259 Quickstarts Appendix C ...
Страница 300: ...286 Rockwell Automation Publication 2080 UM002K EN E March 2019 Appendix C Quickstarts Notes ...
Страница 330: ...316 Rockwell Automation Publication 2080 UM002K EN E March 2019 Appendix E Troubleshooting Notes ...
Страница 344: ...330 Rockwell Automation Publication 2080 UM002K EN E March 2019 Appendix F PID Function Blocks Notes ...
Страница 352: ...Rockwell Automation Publication 2080 UM002K EN E March 2019 338 Index Notes ...
Страница 353: ...Rockwell Automation Publication 2080 UM002K EN E March 2019 339 ...