|
<< Click to Display Table of Contents > MOTF Offset |
  
|
|
<< Click to Display Table of Contents > MOTF Offset |
|
ScMotfOffset (option MOTF required) defines a distance in the entities property page Control.
Figure 285: Wait For Trigger |
MOTF Offset: Enable: If the check box is enabled, a distance in mm can be defined. This distance will be measured in MOTF encoder counts like it is defined in the card-specific MOTF settings. After the distance has been reached, this entity will generate an internal trigger pulse. This internal pulse can be recognized by a ScWaitForTrigger entity. React to external trigger: By default a ScWaitForTrigger entity will wait for an external or an internal trigger. That means, the pausing of an ScWaitForTrigger entity can be interrupted by an external trigger which will lead to a shorter distance than defined. This can be avoided by deactivating this check box. In this case, the first external trigger will start the pausing defined in the ScWatiForTrigger entity and every other external trigger will be ignored until the internal trigger of the ScMotfOffset entity has been sent.
|
|---|
|
•React to external trigger only available for USC-2/USC-3. The USC-1 card always reacts to each external trigger, RTC cards ignore external trigger signals while another marking is in progress. •MOTF Offset works on the first activated MOTF channel (USC: first enabled channel (0 or 1), RTC: first channel (X or Y) with multiplier unequal 0). |
|---|
When the MOTF distance (calculated by encoder counts) has increased by the ScMotfOffset distance, an internal trigger signal is generated. The internal trigger signal behaves like an external trigger, so the external trigger signal must be low. The ScMotfOffset control object itself does not cause any delay or waiting operation.ScMotfOffset and ScWaitForTrigger together can be used in MOTF applications to separate two marking objects with the distance of ScMotfOffset. This allows you to set up a job where the marking result is bigger than the working area. The order of the entities in the MOTF job should look like this:
Figure 286: Entity list with |
Assume we use the Trigger Mode. Job process would be: •One external trigger signal starts the job process •Counting for distance A starts •Target 1 is marked (marking must be done before distance A is traversed) •Waiting until distance A has passed by (external trigger must be low) •Counting for distance B starts •Target 2 is marked (marking must be done before distance B is traversed) •Waits until distance B is passed by •Target 3 is marked •Job done |
|---|
ScMotfOffset and ScWaitForTrigger together can also be used to define an initial distance offset after that the first marking part has to be started.
