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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

The table below summarizes the restrictions on pre-emptive GOs.<br />

Condition<br />

Execute GO during MC1 & FOLENØ<br />

Execute GO during MC1 & FOLEN1<br />

Execute GO during MCØ & FOLENØ<br />

Execute GO during MCØ & FOLEN1<br />

Change MC setting during motion<br />

Change ENC setting during motion<br />

Change FOLENØ to FOLEN1 during motion<br />

Change FOLEN1 to FOLENØ during motion<br />

Possible<br />

Yes<br />

Yes<br />

Yes<br />

No<br />

Yes (but cannot change MC1 to MCØ during FOLEN1)<br />

No<br />

No<br />

Only while MC1, constant ratio, <strong>and</strong> not shifting<br />

OTF Error Conditions<br />

The ability to change the goal position on the fly raises the possibility of several error<br />

conditions:<br />

Further instructions<br />

about h<strong>and</strong>ling error<br />

conditions are provided<br />

on page 30.<br />

Error Conditions<br />

The new position goal of an on-the-fly<br />

GO cannot be reached with the<br />

current direction, velocity, <strong>and</strong> decel.<br />

Set axis status<br />

bit #30<br />

Gem6K Response<br />

Set error<br />

status bit #10<br />

Kill motion (decelerate<br />

at the LHAD value)<br />

YES YES NO<br />

The direction of the new goal position<br />

is opposite that of current travel YES YES YES<br />

There has not yet been an overshoot,<br />

but it is not possible to decelerate to YES YES YES<br />

the new distance from the current<br />

velocity using the specified AD value.<br />

RELATED STATUS COMMANDS<br />

Axis Status — Bit #30: (this status bit is cleared with the next GO comm<strong>and</strong>)<br />

AS.30 ....Assignment & comparison operator — use in a conditional expression (see pg. 25).<br />

TASF ......Full text description of each status bit. (see “Preset Move Overshot” line item)<br />

TAS ........Binary report of each status bit (bits 1-32 from left to right). See bit #30.<br />

Error Status — Bit #10: The error status is monitored <strong>and</strong> reported only if you enable errorchecking<br />

bit #10 with the ERROR comm<strong>and</strong> (e.g., ERROR.1Ø-1). NOTE: When the error occurs, the<br />

controller with branch to the error program (assigned with the ERRORP comm<strong>and</strong>). (this status bit is<br />

cleared with the next GO comm<strong>and</strong>)<br />

ER.10 ....Assignment & comparison operator — use in a conditional expression (see pg. 25).<br />

TERF ......Full text description of each status bit. (see “Preset Move Overshot” line item)<br />

TER ........Binary report of each status bit (bits 1-32 from left to right). See bit #10.<br />

Scenarios<br />

Scenario #1: OTF change of velocity <strong>and</strong><br />

distance, where new comm<strong>and</strong>ed distance (D 2 ) is<br />

greater than the original distance (D 1 ) that was<br />

pre-empted [D 2 >D 1 ]. The distances are the areas<br />

under the profiles, starting at t 0 for both. If the<br />

original move had continued, D 1 would have been<br />

reached at time t 1 . D 2 is reached at time t 2 .<br />

<br />

<br />

<br />

<br />

<br />

<br />

156 Gem6K Series Programmer’s <strong>Guide</strong>

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

Saved successfully!

Ooh no, something went wrong!