Gemini GV6K and Gemini GT6K Programmer's Guide
Gemini GV6K and Gemini GT6K Programmer's Guide
Gemini GV6K and Gemini GT6K Programmer's Guide
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Encoder-Based Stepper Operation (stepper only)<br />
Encoder Resolution<br />
When using an encoder in a stepper application, you may configure the following:<br />
• Encoder resolution<br />
• Stall Detection & Kill-on-Stall, Stall Deadb<strong>and</strong><br />
• Encoder-based position reference <strong>and</strong> position capture<br />
You must specify the encoder resolution with the ERES comm<strong>and</strong>.<br />
Stall Detection & Kill-on-Stall<br />
To detect stalls without<br />
an encoder, refer to<br />
Drive Stall Detection on<br />
page 66.<br />
The ESTALL1 comm<strong>and</strong> enables the drive to detect encoder-based stall conditions.<br />
NOTE: Encoder count reference must be enabled (ENCCNT1) before stall detect (ESTALL)<br />
can be used.<br />
If used with Kill-on-Stall enabled (ESK1 comm<strong>and</strong>), the move in progress will be aborted upon<br />
detecting a stall. If queried with the ER or the AS comm<strong>and</strong>s, the user may branch to any other<br />
section of program when a stall is detected. Refer to the ER, <strong>and</strong> AS comm<strong>and</strong> descriptions in<br />
the Gem6K Series Comm<strong>and</strong> Reference for more information.<br />
Kill-on-Stall functions only if the stall detection is enabled (ESTALL1).<br />
WARNING<br />
Disabling the Kill-on-Stall function with the ESKØ comm<strong>and</strong> will allow the controller to finish<br />
the move regardless of a stall detection, even if the load is jammed. This can potentially<br />
damage user equipment <strong>and</strong> injure personnel.<br />
Stall Deadb<strong>and</strong><br />
Another encoder set-up parameter is the Stall Backlash Deadb<strong>and</strong> (ESDB) comm<strong>and</strong>. This<br />
comm<strong>and</strong> sets the number of comm<strong>and</strong>ed counts of error allowed, after a change in direction,<br />
before a stall will be detected. This is useful for situations in which backlash in a system can<br />
cause false stall situations.<br />
Encoder Set Up Example<br />
Examples for 4 Axes<br />
(comm<strong>and</strong> line samples)<br />
The example below illustrates the features discussed in the previous paragraphs. The DRES<br />
statement defines the motor resolutions. The ERES statement defines the number of encoder<br />
steps per encoder revolution. A st<strong>and</strong>ard 1000-line encoder is used that produces 4000<br />
quadrature steps/rev. Encoder counting (ENCCNT), stall detect (ESTALL) <strong>and</strong> kill-on-stall<br />
(ESK1) are enabled. If a stall is detected (more than 10 steps out without an encoder step<br />
back), the motor's movement is killed. The ESDB statement defines the stall deadb<strong>and</strong>.<br />
DRES25000<br />
ERES4000<br />
ESK1<br />
ENCCNT1<br />
ESTALL1<br />
ESDB0<br />
; Set drive resolution<br />
; Set encoder resolution<br />
; Enable kill motion on stall<br />
; Enable encoder counting (this is<br />
; required for ESTALL to work)<br />
; Enable stall detection<br />
; Set stall deadb<strong>and</strong><br />
84 Gem6K Series Programmer’s <strong>Guide</strong>