Topics created by Serbitar

In SBC mode, thanks for looking at it!

@Serbitar I suspect that pausing from a tool change macro is going to cause problems. I'm not even sure what the correct resumption point should be if you do that. Having said that I've also no idea what the correct way is to handle a failed tool change. I tend to treat them in effect as a fatal error on my e3d toolchanger and just abort everything, but I can see how on printers that may have "expected" fails during a change this is not really a good solution.

@fcwilt Thanks, for pointing that out. I should have read that doc more thoroughly.

I have also found a proper solution which is to specify M558 A2 (or higher) which causes all the G30 S-2 to probe slowly on the second (and third) probes.

I'm still surprised by the difference in behaviour between G30 and G30 S-2 in my previous configuration.

bltouch back on io1 with your updated build works. fantastic! thanks!

@serbitar The reason is that PrusaSlicer doesn't send the G-code request to start the print in the correct format. I've already prepared a work-around for the next DSF version.

This will be fixed in the next version.

@serbitar yes you should see +1g on Z.

@dc42 Wow fantastic! I looks forward to experimenting with it once released!

That fixed it for me as well.

Many thanks to everyone who helped resolve this issue, for your patience, persistence and providing vital testing and feedback. I hope you didn’t waste too much filament!

Ian