Bumping this up a bit...

M25 (pause) doesn't even attempt to run pause.g but leaves the printer in "Pausing" state.
Running M0 H1 (cancel) in this state, runs stop.g and leaves the printer in "Busy" state.
cancel.g never seems to be run (maybe because the printer is still in "Pausing" state and not "Paused"?)

M24 (resume) after a pause doesn't even attempt to run resume.g, restarts the print from the beginning (which causes much carnage!), and leaves the printer still in the "pausing" state (which leaves the DWC showing the resume and cancel buttons with no way to pause again).

@gtj0 said in M400 ignored in bed.g:

At the beginning of the macro, I want to disable the heightmap before levelling, then when the levelling is complete, reload the heightmap. Unfortunately, both G29 commands are being run before the levelling even starts, even with the M400 after all the move commands are complete.

Sounds like there is more fundamental problem. I don't see why the G29 commands are executed in the existing order.

Be interested to see what dc42 finds.

I'm not using v3 so I cannot test this myself, but perhaps you could try putting the two G29 commands and the G32 command in a macro as a work around.

Thanks.

Frederick

Thanks, I'll mark this as solved.

I tried to add M400, but it didn't help...

Thanks @dc42 all is looking good with the new update.

Just tried the firmware from dropbox, and it works like a charm. Thanks for taking the time to put this out on a weekend! 👍

Also -- and I'm sure you get this a lot -- but I can't get over how easy the firmware update was. Kudos.

Please try 3.0beta11, along with the corresponding update to DSF unless you are running in standalone mode. Take note of the known issue with some types of Z probe that is described on the release page for 3.0beta11.

@dc42 haha okay, standing by eagerly 🙇

I have updated the instructions on connecting Z probes to include how to connect a BLTouch to Duet 3.

@triumphantduke All of the changes required to make this work have been merged into the codebases and I believe that @dc42 and @chrishamm are close to doing the next release. I hesitate to post binaries because of this. If you want to build it yourself, you'd need to build the v3-dev branch of RepRapFirmware and the master branch of DuetSoftwareFramework.

@mihaitintea For Duet2 board : Duet2CombinedFirmware.bin
For maestro :DuetMaestroFirmware.bin

@chrishamm I updated pull request https://github.com/chrishamm/DuetSoftwareFramework/pull/68 to catch IOException and print an error message instead of letting the exception bubble up. Done for G29 S1, G29 S3, M374 and M375.

G29 S1 Error: Could not find file '/opt/dsf/sd/sys/heightmap.csv'. gtjoseph opened this pull request in chrishamm/DuetSoftwareFramework closed Fix M500 return code, update DWC branch #68

A better place would be GitHub TBH.

The issue right now with the object model is that it is not fully populated yet and that DCS/DWC try to restore the model from the status/config responses, which is only partially feasible. We will replace the current temporary approach with the "real" object model RRF is supposed to provide at some point in the future.

thansk for reporting this. @dc42 has noted it as something to investigate:
https://forum.duet3d.com/topic/12426/duet-2-on-rrf3-servos-not-working

Awesome. I’m running a bit older version on my main machine that doesn’t have it, but it’ll be nice to have when I finish the Duet 3 upgrades.

@gtj0 nope, just adding to your karma

@T3P3Tony thank you!

Not really, but this is a minor point anyway, doesn't prohibit me from anything.