krs.Handling

A technology package for KUKA robots handling tasks

What is krs.Handling ?

krs.Handling is a technology package for handling applications. This package includes a collection of all essential programmes, subprogrammes, functions and components for a reliable and user-friendly structure of a handling application.

Why krs.Handling ?

Despite its clear basic scheme, krs.Handling provides an application structure with countless variation possibilities. More than 200 robot projects in various branches have not only been role models, but also a proof for the flexibility of this package for 20 years.

Advantages of krs.Handling:

• Clear programme structure
• Multi-project overlapping with uniform structure of all robot programmes
• The operator/fitter only sees the essential step-by-step process/structure of the robot task (without expert code)
• Modular management for reuse with similar tasks
• Nearly no programming effort, except partly for startup processes
• Programme code can be generated by RoboVision.Designer automatically
• Dialogue-led set-up mode for startup process without sequence control
• Enormously minimized efforts for project planning

How does krs.Handling work?

….with just a few simple steps your professional application will be created…

Procedure of creating your application:

1. Defining the processing station/work station
2. Set up of handling modules each station and adding of handling sequences for procedure options
3. Definition of signals for interlocking the working area and for robot safety
4. Adjusting of grab control and monitoring
5. Select type of sequence control (internal or external)
6. Description of sequence control (with internal section control)
7. Startup process of robot (tool and base surveying, and/or teach the  process sequence)

Essential functions of krs.Handling:

• Standardized master application with …
  • Initializing
  • Activation of home position run
  • Reset of signals and modes
  • Order processing cycle
• Handling module per processing station with travel paths-subroutines like …
  • To processing station
  • Pick up an element
  • Process the element
  • Deposit component
  • From processing station
  • Return/automatic run in release mode after termination
  • …
• Optionally order control locally (logic in the robot control) …
• … or an order data-import-port to PLC or master computer
• Work area interlock
• Mechanical safety (cyclic monitoring)
• Collison monitoring e.g. for joining components
• Component-specific speed reduction
• Grab control and grab monitoring
• Tool change control
• Travel path optimization
• Return after programme termination/automatic run in release mode
• Dialogue-led set-up mode for startup process without sequence control
• and much more