Glad you were able to figure it out.

@JBisc Thanks for confirming, I'll work out a fix for the next DWS version.

PS: I've got a fix ready, it will be part of the next software release.

@chrishamm

Sure:

https://drive.google.com/file/d/12BHjItNynpZUoFNisMo6L-Hr6kTsQpC1/view?usp=sharing

@PCR @stuartofmt I can confirm this bug and I've got a fix ready. Nevertheless I agree it's cleaner to quote strings everywhere.

@Phaedrux Thanks for the redirect to https://forum.duet3d.com/topic/10880/rfm-reprapfirmware-filemanager-duetbackup-successor - It's really good. I added a post with some more explanation than the readme gives to help others get started a little quicker.

@chrishamm Thanks I will try that!

@NeueKlasse said in during Print Starts M32 showing Errors:

but in my case the Nozzle
crashes into the Bed on the Border after the Purgeline when the Start Z Height is setted
in the Slicer...

Is this area within the probed area, or is it outside the area the probe can reach physically? If it's outside, the firmware will use extrapolation to guess what the height adjustment would be, but it's not always going to be accurate.

Starting from software version 3.2 you must add M586 C"*" or similar to your config.g if you are using a local dev setup and want to connect to the Duet from there. Btw good luck with Axios, I replaced that dependency in DWC2 a while back because it had too many glitches.

Thanks for pointing this out. I've got a change for DSF ready so it will treat tabs just like RRF (i.e. to add up to 4 spaces to the current indentation level). I'll try to change the new editor to auto-insert tabs if the last line contains tabs, too.

The last G0/G1 ... Z code is too far from the end of the G-code file (-418284 chars). DSF scans only the last 256KiB (~262144 chars) and RRF scans even less. But you can increase this limit in /opt/dsf/conf/config.json via key FileInfoReadLimitFooter. If you double that value, it will scan the last 512KiB which would suffice for your particular file. Note that file info parsing may take longer though.

@rebel_yell_101 Please start a new thread and include the details of your setup. Include your config.g. What duet board? Include the results of M122 and M98 P"config.g".

@o_lampe said in Pause and resurrect doesn't make sense:

Isn't there a way to pause the print, exactly when the steps are 100% predictable?
In my case, drive to the next best parking position with no step-error and keep a record of it.

Currently there isn't a way to do this. It would theoretically be possible to do provided that there is only one motor per axis, or if there are multiple motors then just one endstop per axis. Also for the Z motor you would have to not be using true bed levelling. In other situations with multiple motors per axis, in general if you set one motor to a good parking position then the other motors would not be at good parking positions.

The easiest way for me to implement this would be for me to make the current microstep position available in the object model, then you would be able to use conditional GCode to move to a good parking position.

@Phaedrux i will try to recreate the situation after the print is done, , if it spikes i can verify with a thermal probe too.... post my findings later 🙂

@dc42 @Stephen6309
Ok, thanks.

G10 command for the other tool missed R0 and S0 and now it shows better values (0).

Leaving heater 1 active seems easier so I think I will leave it as it is.

Yes apologies I forgot to answer that. I am using PrusaSlicer v2.3 on Linux. But I also experienced the same issue with Windows when I was on RRF2.05.

config.g?
Did you confirm the update to 3.2 was successful with M115?
Did it also update the DWC version?
Can you show the dwv console output again with the updated versions?

Guess I spoke too soon. Problem still persist. I have updated to PrusaSlicer 2.3 as suggested by @Veti. No difference I cannot understand why it worked in firmware version 2 and not in 3.

Oh well, have to live with it.

It may be worth trying a fresh SD card. The web files are loaded from the SD card, so if they can't load, the page can't load.

I just checked again it's an image every 5 sec