2 features of the "cross cutter" prepared solution, Cross cutter, 2features of the "cross cutter" prepared solution – Lenze EVS93xx CrossCutter User Manual
Page 15

Cross Cutter
Features of the "Cross Cutter" prepared solution
Prepared Solution Servo PLC / ECSxA 1.1 EN
2-1
2
Features of the "Cross Cutter" prepared solution
2.1
General features of the "Cross Cutter" prepared solution
A brief list of the features of the "Cross Cutter" prepared solution appears below:
Basic program for a cross-cutter application requiring high cutting length tolerance. The
following individual functions are supported:
Synchronous or asynchronous operation of the cross cutter
Automatic calculation of motion profiles based on basic profile data
Selection of three interpolation modes to calculate motion profiles
Length-controlled or mark-controlled operation
Adjustable compensation speed for mark correction
Mark
window
Mark
register
Manual x trimming
Continuous
cutting
Test
cut
Reject operation with activation of a reject gate
Oversynchronous/undersynchronous cutting
Torque
precontrol
Evaluation of absolute value encoders at load and drive end
Manual
jog
Simple
positioning
Homing with 8 different homing modes
A detailed description of basic cam generation: The application is based on the "Electronic
cam" technology function and uses motion profiles (cams) created with Lenze's
CamDesigner Basic software for positioning. A detailed description of cam generation with
CamDesigner Basic enables the user to create these motion profiles adapted to meet the
needs of the given application.
Sample project for Lenze's CamDesigner Professional software tool to illustrate the cam
generation process: Contents include a sample project file (CMM file), the associated
motion profiles as source files (CAM files) and the compiled cam file (LC9 files) for this
sample.
Caution!
Application-specific profile data is required for the actual application; a description of how to
create this data appears in Chapter 3.4.2. The sample project (CMM, CAM and LC9 files)
must not be used in the context of actual systems.