PLCopen Function Block ErrorID Output

These are the possible errors that could be returned at the ErrorID output of the function blocks.

ErrorID Description
0 no error
1 queue full
2 abort mode required
3 invalid axis
4 One of four possible scenarios:
  • invalid master axis
  • master axis and slave axis are the same
  • master axis is currently slaved to the specified slave axis
  • master axis and slave axis do not have the same update rate.
5 invalid parameter number
6 invalid move
7 invalid override
8 buffer mode required
9 invalid parameter data
10 move cannot be executed because an axis error exists, the axis is in the stopping state or the axis is disabled.
11 invalid buffer mode
12 move was aborted due to an E-stop
13 move was aborted due to a controlled stop
14 invalid start mode or sync mode
15 invalid cam profile
16 invalid slave count
17 input value is out of range
18 cannot access time stamp or latched position data
19 data not available
For example, if a MC_ReadParm of FollowingError (1006) is programmed on a simulator axis for which no following error is available, an error 19 (data not available) is returned.
20 Motion engine is not running
21 Invalid ratio of velocity to acceleration, or acceleration to jerkClosedIn physics, jerk is the rate of change of acceleration; more precisely, the derivative of acceleration with respect to time. See Limitations on Acceleration and Jerk for more details.
22 Too many profiles – the number of selected profiles is limited to 256.
23 Internal Error
24 Object already exists
25 Block needs to be called between MLMotionInit and MLMotionStart
26 The axis is owned by another group
27 The axis is already present in the group
28 No axes are mapped to the group
29 Invalid name. A name cannot be an empty string
30 Name is already used
31 The number of axes is too small
32 The number of axes is too large
33 Invalid update rate
34 Invalid axis group
35 Invalid kinematic parameter (position, speed, velocity, acceleration, deceleration, or jerk)
36 Invalid floating point number
37 Invalid object index
38 Invalid number of positions in array
39 Position is not a valid number
40 Invalid coordinate system
41 Axis is not initialized
42 Array is not the correct size
43 A move cannot be made while the group is in a stopping state.
44 The axes group is not in the Disabled or Standby state
45 The axes group is in the Disabled state
46 The axis is not in this axes group
47 Duplicate points specified
48 Invalid radius specified
49 Colinear points were specified for the border points of a circle
50 Cannot construct a circle with specified parameters
51 Invalid circle mode
52 Invalid path choice for circular move
53 Invalid transition mode
54 The axis group does not have exactly two axes. As an example, transitions are only allowed on groups with two axes.
55 Invalid engine type for axis
56 An axis or its associated drive is in an error state.
57 Cannot execute function because both queues are not empty.
58 Lines are parallel
59 Not enough room for transitions
60 Abort mode not allowed for Circular Absolute moves
61 Invalid transition parameters
62 Transition not allowed with Abort Move.
63 The axes group is not in the Standby state.
64 The maximum number of axes has been created.
65 The axis is not powered on.
66 Error in data reported from drive.
67 The axes group is not in the ErrorStop state.
68 The axes group is still in Error State.
69 The axes group is not in Standby or ErrorStop state.
70 The fast inputClosedThe inputs are taken into account at each cycle depending on the system periodicity (for example each millisecond). Under certain circumstances this can be insufficient when more accuracy is needed, or if a quick response is required from the system. To fill the gap, a drive may have some Fast Input connections (generally one or two). When an event happens that triggers a Fast Input (e.g. when a sensor sends a rising edge), the detection of a signal occurs faster (which can be 1000 times more accurate than the system periodicity). Then the timestamp associated with this input can be provided to the IPC to take corrective action is in use.
71 Set position is in progress.
72 Invalid data point count.
73 Position Axis and Trigger Axis cannot be different for position mode trigger
74 Invalid Fast InputClosedThe inputs are taken into account at each cycle depending on the system periodicity (for example each millisecond). Under certain circumstances this can be insufficient when more accuracy is needed, or if a quick response is required from the system. To fill the gap, a drive may have some Fast Input connections (generally one or two). When an event happens that triggers a Fast Input (e.g. when a sensor sends a rising edge), the detection of a signal occurs faster (which can be 1000 times more accurate than the system periodicity). Then the timestamp associated with this input can be provided to the IPC to take corrective action trigger mode
75 Cannot simultaneously perform motion from different motion engines.
76 Cannot call this function block twice in the same cycle with the same value for execute input. This error may arise from two scenarios:
77 An axis is in a controlled stop error state.

 

Stay Connected with Kollmorgen

Copyright © 2018 Kollmorgen