Hey the issue I have with controlling the axis with gcode is I think it
will interfere with the main machine that is doing the cutting.

As I need them both to be running at the same time.

Your carousel component works fine but I think any axis movements can't
happen independently to other axis in machine actually doing the cutting.

Which is why I was asking about joints?

I think possibly some of them can be independent

On Sat, 21 Dec 2024, 12:32 andy pugh, <bodge...@gmail.com> wrote:

> On Fri, 20 Dec 2024 at 20:54, andrew beck <andrewbeck0...@gmail.com>
> wrote:
>
> > and the actual toolchange arm i will control with classic ladder as its
> > just a state machine system
>
> That will work, as would a custom HAL component.
> But you can also control the sequence in G-code, which is clunky but
> has the advantage that you can include axis moves in the sequence
> easily.
>
> Take a look at sim/axis/vismach/vmc-toolchange for an example config
> (with a virtual milling machine so you can see the motions)
> (It uses carousel for the tool carousel control)
>
> The G-code routine that controls it is here:
>
> https://github.com/LinuxCNC/linuxcnc/blob/master/configs/sim/axis/vismach/VMC_toolchange/toolchange.ngc
>
> In this example the pocket number is sent from the G-code to the
> carousel by M68 (analogue output)
>  M68 E0 Q#<selected_pocket> ;set the carousel to move to the right pocket
> And the carousel is enabled/disabled by a digital output from the G-code
>  M64 P0 ; start carousel
>
> --
> atp
> "A motorcycle is a bicycle with a pandemonium attachment and is
> designed for the especial use of mechanical geniuses, daredevils and
> lunatics."
> — George Fitch, Atlanta Constitution Newspaper, 1912
>
>
> _______________________________________________
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users
>

_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to