3 "standby" state, 4 "manualjog" state, 5 "homing" state – Lenze EVS93xx CrossCutter User Manual
Page 166: 6 "positioning" state, 7 "cam" state, 8 "trouble" state, Standby" state -152, Manualjog" state -152, Homing" state -152, Positioning" state -152
Cross Cutter
Functions
Prepared Solution Servo PLC / ECSxA 1.1 EN
4-152
4.3 "StandBy"
state
The system must be in this state in order to switch to one of the other states, e.g. Positioning.
Direct switching from e.g. ManualJog to Cam is not possible. State changes must always be
performed via the StandBy state. Whenever a state such as ManualJog or Cam is aborted, the
system will revert to StandBy. This is illustrated in Figure 42, where you can see that the system
always switches to StandBy.
4.4 "ManualJog"
state
In "ManualJog", you can traverse the drive and/or tool by means of manual operator inputs. In
this state, the drive moves independently of the motion profile. This type of function is used, for
example, to clean the tool or feed in new material.
4.5 "Homing"
state
In the "Homing" state, you can perform homing in order to map the position of the tool on the
PLC and declare the zero position (home position) to the system. Several homing functions are
available to the user for this purpose.
4.6 "Positioning"
state
In the "Positioning" state you can move the drive to a defined position independently of the
motion profile, e.g. for maintenance work on the tool. The link between the drive and the motion
profile can be restored once such work is complete.
4.7
"Cam" state
The "Cam" state is the state in which the axis follows the motion profile. The traversing of the
drive on the motion profile is controlled the digital frequency entry. Initially, the motion profile is
activated by sending the "Lock To Cam" command. In this state it is possible to switch between
individual motion profiles.
4.8 "Trouble"
state
The target system switches to the "Trouble" state to report a trip or in other words a FAIL-QSP.
The condition for the change to/from the "Trouble" state is not generated in the state machine
itself but via a POU working in parallel with the state machine. The user can create further error
messages in Program_Task3 in the UserErrors POU. Chapter 6.3.3 explains how to create user
errors.