Dynomotion

Group: DynoMotion Message: 13056 From: Colin Fera Date: 4/3/2016
Subject: issues with g83 v4.33
G83 usually results in a gcode error when attempting to actually run a file due to following error.  Max following error is set at 127.  When id does actually abort there is ~6000 counts of error.

No other sequences of GCODE result in this.

here is example code that causes the error:
G98 G80 G17 G90 G54 G64

G20 G90
(***New Tool Selected***)
(ToolNum: 110  Diameter: 0.2450  )
(Feed: 2.4900  SFM: 100.0000  Plunge: 1.2500  ChipLoad: 0.0008  )
M9
M5
M06 T110 (drill)

M03 S1559
(***Line of Holes***)
(Xstart:  -1.1500  Ystart: 0.0000  Num: 07  Inc: 0.3500  )
(Angle:  0.0000  Ztop: 0.0000  Depth: -1.5000  Peck: 0.1000  )
G00 Z0.2000
G83 X -1.1500  Y 0.0000  Z -1.5000  R 0.1000  Q 0.1000  F 2.4900
X -0.8000  Y 0.0000
X -0.4500  Y 0.0000
X -0.1000  Y 0.0000
X 0.2500  Y 0.0000
X 0.6000  Y 0.0000
X 0.9500  Y 0.0000
G80
M09
M05
M30 (end of file
Group: DynoMotion Message: 13102 From: Tom Kerekes Date: 4/6/2016
Subject: Re: issues with g83 v4.33
Hi Colin,

Sorry just noticed no one responded.

Did you ever resolve this?  Could it be that your system simply can't handle a full Rapid direction reversal in Z without a following error greater than 127?  Most GCode would never do this.  The Step Response Move command wouldn't either.  It moves, Stops, then reverses.

Attached I plotted the Trajectory sampled every 10ms when running the first one and a half G83 peck drill in your example (resolution 3225 counts/inch used).  It looks correct to me.

You might slow down your Z Rapid Speed to see if it then runs ok.

The CaptureZMotion.c example can be used to capture Z Command and Position while running GCode so you can analyze if that is what is happening.

Regards
TK


On 4/3/2016 12:13 PM, Colin Fera colin.fera@... [DynoMotion] wrote:
 
G83 usually results in a gcode error when attempting to actually run a file due to following error.  Max following error is set at 127.  When id does actually abort there is ~6000 counts of error.

No other sequences of GCODE result in this.

here is example code that causes the error:
G98 G80 G17 G90 G54 G64

G20 G90
(***New Tool Selected***)
(ToolNum: 110  Diameter: 0.2450  )
(Feed: 2.4900  SFM: 100.0000  Plunge: 1.2500  ChipLoad: 0.0008  )
M9
M5
M06 T110 (drill)

M03 S1559
(***Line of Holes***)
(Xstart:  -1.1500  Ystart: 0.0000  Num: 07  Inc: 0.3500  )
(Angle:  0.0000  Ztop: 0.0000  Depth: -1.5000  Peck: 0.1000  )
G00 Z0.2000
G83 X -1.1500  Y 0.0000  Z -1.5000  R 0.1000  Q 0.1000  F 2.4900
X -0.8000  Y 0.0000
X -0.4500  Y 0.0000
X -0.1000  Y 0.0000
X 0.2500  Y 0.0000
X 0.6000  Y 0.0000
X 0.9500  Y 0.0000
G80
M09
M05
M30 (end of file

Group: DynoMotion Message: 13105 From: Colin Fera Date: 4/6/2016
Subject: Re: issues with g83 v4.33 [1 Attachment]
Attachments :
    Thanks Tom, I will try the CaptureZMotion.c.

    I don't think its the system.  I can do this:

    G00 Z0
    G00 Z-1
    G00 Z0
    G00 Z-1
    G00 Z0
    G00 Z0.2
    ....

    Without a problem.

    -Colin



    On Wed, Apr 6, 2016 at 5:02 PM, Tom Kerekes tk@... [DynoMotion] <DynoMotion@yahoogroups.com> wrote:
     
    [Attachment(s) from Tom Kerekes included below]

    Hi Colin,

    Sorry just noticed no one responded.

    Did you ever resolve this?  Could it be that your system simply can't handle a full Rapid direction reversal in Z without a following error greater than 127?  Most GCode would never do this.  The Step Response Move command wouldn't either.  It moves, Stops, then reverses.

    Attached I plotted the Trajectory sampled every 10ms when running the first one and a half G83 peck drill in your example (resolution 3225 counts/inch used).  It looks correct to me.

    You might slow down your Z Rapid Speed to see if it then runs ok.

    The CaptureZMotion.c example can be used to capture Z Command and Position while running GCode so you can analyze if that is what is happening.

    Regards
    TK


    On 4/3/2016 12:13 PM, Colin Fera colin.fera@... [DynoMotion] wrote:
     
    G83 usually results in a gcode error when attempting to actually run a file due to following error.  Max following error is set at 127.  When id does actually abort there is ~6000 counts of error.

    No other sequences of GCODE result in this.

    here is example code that causes the error:
    G98 G80 G17 G90 G54 G64

    G20 G90
    (***New Tool Selected***)
    (ToolNum: 110  Diameter: 0.2450  )
    (Feed: 2.4900  SFM: 100.0000  Plunge: 1.2500  ChipLoad: 0.0008  )
    M9
    M5
    M06 T110 (drill)

    M03 S1559
    (***Line of Holes***)
    (Xstart:  -1.1500  Ystart: 0.0000  Num: 07  Inc: 0.3500  )
    (Angle:  0.0000  Ztop: 0.0000  Depth: -1.5000  Peck: 0.1000  )
    G00 Z0.2000
    G83 X -1.1500  Y 0.0000  Z -1.5000  R 0.1000  Q 0.1000  F 2.4900
    X -0.8000  Y 0.0000
    X -0.4500  Y 0.0000
    X -0.1000  Y 0.0000
    X 0.2500  Y 0.0000
    X 0.6000  Y 0.0000
    X 0.9500  Y 0.0000
    G80
    M09
    M05
    M30 (end of file


    Group: DynoMotion Message: 13119 From: Tom Kerekes Date: 4/8/2016
    Subject: Re: issues with g83 v4.33
    Hi Colin,

    That is a good point. You might run a similar test with combinations of Rapids to Feeds and Feed to rapids Reversals (feeds are not Jerk Limited and can cause more shock to the system).

    Regards
    TK

    On 4/6/2016 6:22 PM, Colin Fera colin.fera@... [DynoMotion] wrote:
     
    Thanks Tom, I will try the CaptureZMotion.c.

    I don't think its the system.  I can do this:

    G00 Z0
    G00 Z-1
    G00 Z0
    G00 Z-1
    G00 Z0
    G00 Z0.2
    ....

    Without a problem.

    -Colin



    On Wed, Apr 6, 2016 at 5:02 PM, Tom Kerekes tk@... [DynoMotion] <DynoMotion@yahoogroups.com> wrote:
     
    [Attachment(s) from Tom Kerekes included below]

    Hi Colin,

    Sorry just noticed no one responded.

    Did you ever resolve this?  Could it be that your system simply can't handle a full Rapid direction reversal in Z without a following error greater than 127?  Most GCode would never do this.  The Step Response Move command wouldn't either.  It moves, Stops, then reverses.

    Attached I plotted the Trajectory sampled every 10ms when running the first one and a half G83 peck drill in your example (resolution 3225 counts/inch used).  It looks correct to me.

    You might slow down your Z Rapid Speed to see if it then runs ok.

    The CaptureZMotion.c example can be used to capture Z Command and Position while running GCode so you can analyze if that is what is happening.

    Regards
    TK


    On 4/3/2016 12:13 PM, Colin Fera colin.fera@... [DynoMotion] wrote:
     
    G83 usually results in a gcode error when attempting to actually run a file due to following error.  Max following error is set at 127.  When id does actually abort there is ~6000 counts of error.

    No other sequences of GCODE result in this.

    here is example code that causes the error:
    G98 G80 G17 G90 G54 G64

    G20 G90
    (***New Tool Selected***)
    (ToolNum: 110  Diameter: 0.2450  )
    (Feed: 2.4900  SFM: 100.0000  Plunge: 1.2500  ChipLoad: 0.0008  )
    M9
    M5
    M06 T110 (drill)

    M03 S1559
    (***Line of Holes***)
    (Xstart:  -1.1500  Ystart: 0.0000  Num: 07  Inc: 0.3500  )
    (Angle:  0.0000  Ztop: 0.0000  Depth: -1.5000  Peck: 0.1000  )
    G00 Z0.2000
    G83 X -1.1500  Y 0.0000  Z -1.5000  R 0.1000  Q 0.1000  F 2.4900
    X -0.8000  Y 0.0000
    X -0.4500  Y 0.0000
    X -0.1000  Y 0.0000
    X 0.2500  Y 0.0000
    X 0.6000  Y 0.0000
    X 0.9500  Y 0.0000
    G80
    M09
    M05
    M30 (end of file