On Saturday 04 June 2016 18:17:24 John Thornton wrote:
> I've seen 10-20 to 1 for acceleration to max velocity.
>
> JT
I have that G0704 at nearly 40/1 just to see what happens. The theory
being that the huge amount of accel is from a dead stop or a reversal,
and I'll reduce it again the first
I've seen 10-20 to 1 for acceleration to max velocity.
JT
On 6/4/2016 4:37 PM, Danny Miller wrote:
> Max vel 15, max accel 50.
>
> That cuts like 1" radius arcs. But the docs are saying that's
> basically what G64 with no P-parameter does, basically totally
> disregarding accuracy to keep the
On 4 June 2016 at 22:37, Danny Miller wrote:
> Max vel 15, max accel 50.
>
> That cuts like 1" radius arcs.
accel = v^2 / r (in metric) so your numbers give a radius of 11.25mm
if those are mm / sec numbers.
Anyway, the arc radius is a super-simple calculation based on velocity
and acceleration,
Max vel 15, max accel 50.
That cuts like 1" radius arcs. But the docs are saying that's
basically what G64 with no P-parameter does, basically totally
disregarding accuracy to keep the feedrate up.
Danny
On 6/4/2016 4:16 PM, andy pugh wrote:
> On 4 June 2016 at 20:20, Danny Miller wrote:
>>
On 4 June 2016 at 20:20, Danny Miller wrote:
> G64
>
> No "P0.001" parameter. Well that's pretty damn toxic, it'll create huge
> arcs instead of what it's supposed to do.
If "best-speed" gives huge arcs I would suspect a miss-match between
the cutting speed and the machine acceleration limits.
W
I've seen this several times...
So Vectric Aspire 8.0 is a great program. Most of the time it works
ok. However, we've found Gcode generation sometimes yield just this:
G64
No "P0.001" parameter. Well that's pretty damn toxic, it'll create huge
arcs instead of what it's supposed to do. It'
