Topics created by dwuk3d

@dc42 Sounds great thanks.

I don't think the number of overridden GCODEs is likely ever to be a very long list - so maybe a lookup list could work too - perhaps with some sort of extra M command in the config.g or start gcode in the slicer to register the overrides.

In the meantime I think I will alter my post processor to be more generic and do more or less the same thing.
i.e. Look for some sort of override registration M command (M802 for example) in the gcode stream, and then use that info to then override any relevant G/M/T commands later in the stream into .x equivalents.

@dc42 Thanks - that seems to work ok in single motion system mode - I have been able to set the V axis to not come within 100mm of the Y axis which is exactly what I need.

I can't test it in multi motion system mode due M400 and M598 not releasing drives - which still seems to still occur in the new rc1+1 version you sent. - see https://forum.duet3d.com/topic/36866/multiple-motion-system/64?_=1741362599789

@dc42 thanks for the confirmation - will go ahead without the motor driver boards then.

Ordered one of these
FE5591D3-1B6F-4A17-AB05-21AF7F8E59D4.png

E7CA8A6D-FA3F-4318-B63D-051CD4A41FFB_4_5005_c.jpeg

Doesn't look like it needs much power

@dc42 good news - Wired up my 2nd extruder - and this time I connected the Inductive Z probe ( 24V, 2.27V output) to the Filament Monitor 3.3v compliant connection IO1.in - and it seems to trigger ok.

So I think that is the solution unless I decide to add filament monitors. So thanks for your help.

Next issue is work out is how to handle 4 different Inductive Probes, a Switch Type Touch probe plus a positioning probe.

8B030F4C-EB06-4D69-8ACE-4E9AE33E28D6.jpeg

Sub second tool change demo. https://youtu.be/UXMu2qXNEhc
9B2A37E2-08C3-420C-AA5B-EA6AF182917D.png