> On 6 Sep 2018, at 12:32, Daren Schwenke <[email protected]> wrote: > > No, just respond to G0 A<angle>. It would be better if it wasn't coordinated > actually. > I will not be moving both X Y Z and A in the same command right now. > For now it will be just G1 X Y Z > <finish> > then G1 A > <finish> > Eventually I would like to be able to G1 X Y Z, and then now wait for it to > finish and do G1 A during that move, but I don't need that now. > Worst case, I can could also just reassign this to some M code, but out of > the box it expects A. > (Openpnp)
In your original question you said: >> > But It doesn't work though for G0 A0, G1 A180, etc... What exactly does not work? If you don’t mind an extra step you could set an “analog output” (its a Hal pin being set by the g-code command. That hal pin you can wire up to other components) in hal with M67 for example. So a script to change (sed) “G1 A” to “M67 E0 Q”. As long as the original G-code file is consistent then that might be the fastest result. Specify the number of analog I/O (end of the line “aio”) https://github.com/luminize/machinekit/blob/experimental-wire/configs/ARM/BeagleBone/BeBoPr-Bridge/wire-extruding/lineardelta-wire-extr.hal#L29 https://github.com/luminize/machinekit/blob/experimental-wire/configs/ARM/BeagleBone/BeBoPr-Bridge/wire-extruding/lineardelta-wire-extr.hal#L265 > >> On Thursday, September 6, 2018 at 6:23:14 AM UTC-4, Bas de Bruijn wrote: >> >> >> > On 6 Sep 2018, at 11:31, Daren Schwenke <[email protected]> wrote: >> > >> > So I have tripod kinematics working well. >> > Now I added an A axis for part rotation via an rc servo now, plumbed it up >> > with scale and limits and such, and it works in joint mode. >> > I added my rotation as an axis so the planner can have a relatively good >> > guess as to when it will reach the actual position via setting >> > feedrate/max angular velocity. >> > >> > After homing, world mode works fine for X, Y, Z >> > But It doesn't work though for G0 A0, G1 A180, etc... >> > My ini has: >> > >> > AXES = 4 >> > COORDINATES = X Y Z A >> > >> > I'm obviously missing something important here. >> >> Does your 4th Axis need to be coordinated (motion) with the other 3? > > -- > website: http://www.machinekit.io blog: http://blog.machinekit.io github: > https://github.com/machinekit > --- > You received this message because you are subscribed to the Google Groups > "Machinekit" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > Visit this group at https://groups.google.com/group/machinekit. > For more options, visit https://groups.google.com/d/optout. -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
