14.01.2015 Views

Gemini GV6K and Gemini GT6K Programmer's Guide

Gemini GV6K and Gemini GT6K Programmer's Guide

Gemini GV6K and Gemini GT6K Programmer's Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

product of master travel <strong>and</strong> average ratio. Because the slave travel is not specified explicitly,<br />

it is possible for arithmetic round-off errors to cause actual slave travel during a ramp to differ<br />

from theoretical calculations. For applications in which slave distance is important, preset<br />

segments should be used.<br />

A preset (MCØ) Following segment will also start with the final ratio of the previous segment,<br />

but may end in one of two ways. FOLRNF specifies the final ratio of a preset Following<br />

segment. The only valid value for FOLRNF is zero (0). If FOLRNFØ is given before the<br />

GOBUF, the resulting motion segment will be constructed exactly as preset Following moves<br />

are outside of compiled profiles. In this case, the starting ratio must be zero, the final ratio<br />

will be zero, <strong>and</strong> the maximum intermediate ratio will be given by FOLRN <strong>and</strong> FOLRD. The<br />

relationships between ratio, master distance, <strong>and</strong> slave distance for this case are given on page<br />

192 under the heading Master <strong>and</strong> Follower Distance Calculations. The FOLRNF comm<strong>and</strong><br />

affects only the immediately subsequent preset Following segment, <strong>and</strong> must be given<br />

explicitly for each preset segment which is to end in zero ratio.<br />

If FOLRNFØ is not given before the GOBUF, the segment will end with the ratio given by<br />

FOLRN <strong>and</strong> FOLRD, <strong>and</strong> need not start with zero ratio. This type of motion segment is<br />

constrained, however, to intermediate ratios which fall between the starting <strong>and</strong> final ratios.<br />

Compiled profiles are built from motion segments created with the GOBUF comm<strong>and</strong>. That<br />

is, the motion segments may be all Following or all non-Following, but not a mixture of<br />

Following <strong>and</strong> non-Following.<br />

The GOBUF comm<strong>and</strong> builds the appropriate type of motion segment based on the values of<br />

FOLMAS <strong>and</strong> FOLEN during compilation. These parameters may not be changed inside a<br />

compiled program after a GOBUF. The choice of zero or non-zero FOLMAS must be the same<br />

during PRUN as during PCOMP (if non-zero, the value can be changed, but still must be nonzero).<br />

If a non-zero FOLMAS is given, the value of FOLEN must be the same during PRUN as<br />

during PCOMP.<br />

Distance<br />

Calculations For<br />

Compiled<br />

Following Moves<br />

The graph below shows 6 possibilities of ratio change profiles for preset segments, with legal<br />

FOLMD <strong>and</strong> “D” values constrained by the requirement that the average ratio (given by<br />

“D”/FOLMD) is between R1 <strong>and</strong> R2. If the distance is outside these ranges, in the profile used<br />

to get from R1 to R2 over FOLMD (covering “D” slave distance), an error message will be<br />

generated during the PCOMP comm<strong>and</strong>. For the graphs shown, the constraints are expressed by:<br />

(R1 * FOLMD) = “D” >= (R2 * FOLMD) if R2 < R1<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

The two graphs above show the cases of R1R2, but the distance calculations of the<br />

ramp <strong>and</strong> constant ratio portions are the same for the two cases. For each graph, the heavy<br />

lined profile (first case) of these mimics the shape of the corresponding preset velocity change<br />

Chapter 6. Following 143

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!