Parameterisable boundary conditions, specifying the mode of operation

It is possible to specify a wide variety of boundary conditions for the slave movement in the synchronization phase of the Universal Flying Saw. These boundary conditions make it possible to specify limit values for the slave magnitudes listed in the table below. The SyncMode bit mask can be used to check whether the individual limit values are being observed. The boundary conditions specified for the synchronization phase also affect the set value profile for the synchronization. Whether, and in what way, the conditions affect the profile can be seen in the diagram in the chapter below.

Synchronization mode

Description

Define:

GeaInSyncMode

GEARINSYNCMODE_POSITIONBASED

In this mode of the universal flying saw, a profile dependent on the master position is generated to synchronize the slave axis to the master axis.

GEARINSYNCMODE_TIMEBASED

In this mode of the universal flying saw, a time-dependent motion profile is generated for synchronizing the slave axis to the master axis, which ensures compliance with all dynamic limit values of the slave axis. This mode is currently only available with coupling on velocity.

Bit masks for the "SyncMode"

Description

Boundary condition

Define:
GEARINSYNC_CHECKMASK_

Value

Decimal

Value

Hexadecimal

MINPOS

1

0x0000 0001

Checks whether the slave axis has passed below its software minimum end position (machine data).

posSlave ≥ posSlaveMin

MAXPOS

2

0x0000 0002

Checks whether the software maximum end position (machine data) of the slave axis has been exceeded.

posSlave ≤ posSlaveMax

MAXVELO

4

0x0000 0004

Checks whether the maximum permitted slave velocity (machine data) has been exceeded.

| vSlave | ≤ vSlaveMax

MAXACC

8

0x0000 0008

Checks whether the maximum slave acceleration (machine data) has been exceeded

accSlave ≤ accSlaveMax

MAXDEC

16

0x0000 0010

Checks whether the maximum slave deceleration (machine data) has been exceeded

decSlave ≤ decSlaveMax

MAXJERK

32

0x0000 0020

Checks whether the maximum slave jerk (machine data) has been exceeded.

jSlave ≤ jSlaveMax

OVERSHOOTPOS

256

0x0000 0100

Checks for overshooting of slave position.

 

UNDERSHOOTPOS

512

0x0000 0200

Checks for undershooting of slave position.´

 

OVERSHOOTVELO

1024

0x0000 0400

Checks for overshooting of slave acceleration.

 

UNDERSHOOTVELO

2048

0x0000 0800

Checks for undershooting of slave acceleration.

 

OVERSHOOTVELOZERO

4096

0x0000 1000

Checks whether the slave velocity has exceeded 0.0.

 

UNDERSHOOTVELOZERO

8192

0x0000 2000

Checks whether the slave velocity is below 0.0

 

Bit masks for operation modes


GEARINSYNC_OPMASK_

Description

ROLLBACKLOCK

65536

0x0001 0000

Bit = 0: (default)

When the slave has achieved the synchronous phase, synchronous coupling of all the following master movements is maintained until the coupling is removed. This also applies if the master changes direction and moves backwards over the coupling position. (Further explanations)

Bit = 1:

Setting this bit activates the backstop, which causes the slave to stop when the master moves backwards beyond the coupling position after a motion reversal.   (Further explanations)

INSTANTSTOPONROLLBACK

131072

0x0002 0000

Bit = 0: (default)

On reaching the coupling position, the slave velocity is reduced smoothly following a 5th order polynomial. The polynomial is optimized to halt the slave as quickly as possible. (Further explanations)

Bit = 1:

In terms of the set value, the slave is halted within one NC tick of reaching the coupling position. The slave velocity is set to 0.0 and the position is maintained.
This abrupt stop can trigger the following error monitoring system! (Further explanations)

PREFERCONSTVELO

1048576

0x0010 0000

Bit = 0: (default)

Default setting

Bit = 1:

The system will try to use a phase with constant velocity, instead of just one 5th order polynomial. This can result in a combination of a 5th-order polynomial, a synchronous phase and another 5th-order polynomial (P5-P1-P5), (see further explanation). The maximum given acceleration and deceleration is used. To control and limit the jerk it is recommended to set MAXJERK in the bit mask.

IGNOREMASTERACC

2097152

0x0020 0000

Bit = 0: (default)

Default setting

Bit = 1:

When calculating the coupling, the acceleration of the master is ignored, i.e. set to zero. This causes the use of internal optimizations. At moderate acceleration, this specification leads to tolerable following errors. After the following error has been reduced, the relative position accuracy is independent of this setting.

 

Note

The checks listed above apply only to the synchronization phase (GEARINSYNCSTATE_SYNCHRONIZING), not to the phase of synchronized movement.  These calculations and checks are also only possible when the assumption is made that the master continues to move with constant velocity after the coupling time, i.e. that it is not subject to acceleration. Making other assumptions for the master makes no sense, since at the time of coupling it is generally not known how the master will move in the future.