On Sun, Nov 6, 2016 at 2:46 PM Danny Miller <dan...@austin.rr.com> wrote:

> I did some rotary stuff on Mach3 and was baffled by similar issues.
>
> Seems like it'd be CAM's job to manage the feedrate, and calculate for
> the work radius.  That would make sense if you were cutting a cylinder
> and the G-code move was "X moves 3 inches, A rotates 100 times, feed X
> at 1.5 inches/min"
>
> But if the cartesians aren't moving- which is common- the F value has no
> meaning at all if it's cartesian.  There is no way for G-code language
> to communicate "polar Feed =  200 deg/sec" and it's nonsense to combine
> polar and cartesian vectors into a single scalar for a feedrate.
>

The F word is overloaded. If there's no cartesian motion, then it treats
the number as degrees per min instead of in per min.

Seems like the logical answer is amending G-code Feedrate with syntax
> for an angular vector in addition to cartesian, but no CAM pkg would
> support it.


The "proper" way as I understand it is to use inverse time when doing both
linear and angular moves. It's perfectly sensible to say "move X inches and
A degress within T seconds".
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to