KUKA Dynamic Movementparameters

If you use spline type movements you can add the parameters behind a WITH, e.g.

SLIN XP1 WITH $VEL.CP=0.2, $ACC_AXIS[1]=100, .... C_SPL

Also using the predefined BAS.SRC functions can be handy, e.g.

BAS(#CP_PARAMS, 0.2)

LIN XP1

For geometric offsets you can use the : operator, e.g.

PTP XP1:SHIFT C_DIS

PTP SHIFT:XP2 C_PTP

with SHIFT before or after the : depending whether you want to shift in base or tool system.

At best download system integrators manual from kuka xpert portal, see pinned topic READ FIRST in this subforum.

Fubini

In KRL, unlike RAPID, motion commands are completely separate from Velocity, Tool, Base/WObj, etc settings. Setting the motion parameters is separate executable lines from the motion commands themselves. Even if you're not using ILFs, you can still make use of the system BAS functions to make this easier.

You don't have to avoid ILFs if you want to do offsets. ILFs just don't include offsets, but you can still do them. Also, your example KRL is not going to do what you want -- it will generate a tool offset, not an offset in the active WObj/Base:

PTP P1 : {X 0,Y 0,Z -100,A 0,B 0,C 0}

PTP {X 0,Y 0,Z -100,A 0,B 0,C 0} : P1

The order matters, since that's not an offset command, it's an actual mathematical equation. It works like a function call, the result of the equation goes into the PTP/LIN command. The offset after the point takes the point, and shifts along the point's Z axis. The second line applies a shift along the Z axis of the active Base/WObj to the point, before taking the point's orientation into account.

To use offsets with ILFs, the simplest method is to use Base offsets. This works just like applying offsets to a Work Object in RAPID, except KRL Bases don't have a second OFrame element, only the primary frame. So, something like:

DECL FRAME _fOffset
DECL INT _nIndex
DECL REAL _nShift

_nShift=7.5 ; mm
FOR _nIndex = 1 TO 10
  _fOffset = $NULLFRAME ; set to all 0s
  _fOffset.Z = _nShift * _nIndex
  BASE_DATA[2] = BASE_DATA[1] : _fOffset
  PTP P1 Vel100% Tool1 Base2 yada yada ILF stuff
ENDFOR

The key here is that Base2 is being written to. BASE_DATA[1] is your "reference" base, set up once, and should never be altered by the program. This can work for "raw" KRL, or for ILFs. You simply have to alter the Base values before the ILF executes.

Doing tool offsets with ILFs is harder -- either you dynamically apply adjustments to the TOOL_DATA value, or apply offsets to the actual E6POS value of the point itself, before the ILF.

you could make subprograms called MovJ, MovL and function Offs that behave like what you are familiar with.

for programming info check key manuals as mentioned in READ FIRST. your friends are

Programming Manual for System Integrators

System Variables Manual

both should be for your KSS version but most of info will apply even if you use documentation for a very different version. few variables have changed over time and newer KSS have more motions instruction at disposal (two motion planners).

Quote from EXOR

Any tips on how to lower/set speed and approximation during continuous movements else then the stuff fubini just wrote?

Not really. If you have a series of motions, and want each motion to have different speed/accel/approximation/tool/base settings, you have no choice but to add non-motion KRL commands in between the motion commands to set those values. If you unpack a motion ILF, you can see how to do this. Frankly, just making your own calls to BAS, like the ILFs do, is probably the easiest approach. Making your own subroutine that accepts values for TCP velocity, joint velocity, approximation radius, accel, Tool, Base, and then sets CPDAT_ACT, PDAT_ACT, and FDAT_ACT before calling BAS will save the most linecount in your motion program.