@droftarts

Hi Ian,

thanks a lot for your advice.

Regarding the firmware.
As I said: this machine is used in an experimental phase and we want to keep everything as stable as possible. And since we did not recognise any advantage with a newer version we kept it as it was.

About the filament sensor:
We just used

M591 D0 P3 C"io6.in" S1

in our config.g.

Then we started a small manual programm:

homing move z to 50 mm extrude 200 mm filament end

Here are the results from the console in timed order:

18.7.2023, 09:56:29
M32 "0:/gcodes/Test extrusion filament sensor.gcode" File 0:/gcodes/Test extrusion filament sensor.gcode selected for printing

18.7.2023, 09:56:46
Duet3D rotating magnet filament monitor v4 on pin io6.in, enabled, sensitivity 28.80mm/rev, allow 60% to 160%, check every 3.0mm, version 4, mag 129 agc 82, no calibration data

18.7.2023, 09:57:51
Finished printing file 0:/gcodes/Test extrusion filament sensor.gcode, print time was 0h 1m

After typing M591 D0 into the console we got this message:
18.7.2023, 09:58:11
Duet3D rotating magnet filament monitor v4 on pin io6.in, enabled, sensitivity 28.80mm/rev, allow 60% to 160%, check every 3.0mm, version 4, mag 130 agc 82, no calibration data

Are there any further advices?
Anything that we can change and try.
The communication seems to work. But there must be any other mistake we did.
Or another possibility could be a faulty device/part.

greetings
Andreas

Thank you very much, I really appreciate this! @T3P3Tony I sent you the email

@dc42 Thanks for pointing that bit out. I had missed that on the docs site. I filed it down some and it seems to be at a more acceptable range.

thanks for your reply @T3P3Tony

I will use that and see how I go. It makes sense to use the longer one. I did a print last night that had a fair bit of retraction and it only got down to a min 94% and a max of 107% over 9m of filament using the newer mm/rev.

Sam