Magnet Filament Monitor V4 - Calibration Issue
-
Can anyone help? I'd really like to calibrate the sensor over a longer distance than just a few millimeters...
-
@Diamondback the distance that the calibration is displayed for should be how much filament has been through the sensor during the current print since the last time you checked with M591. What happens if you run M591after printing for a longer time?
-
@T3P3Tony That's what I assumed it should be, but it always stays constant at the very low mm count.
-
@Diamondback I just saw you have it checking every 100mm. Try setting that to the default of 3mm
-
@T3P3Tony I did that already, the first two logs in the first post use the default 3mm (ie not specified in the M591 call)
-
@Diamondback ahh yes I see I have not tested the monitors as much with 3.5b1 as I have with 3.4.x are you seeing the same behaviour with both firmwares?
-
@Diamondback use the default 3mm unless you get a very large measured sensitivity range, in which case you could use 6mm. As you have the filament monitor a long way from the extruder drive, you are likely to need an even larger range than that.
When running a print, the measured sensitivity should be displayed after about 10mm of filament should be extruded. The length over which calibration has been done should gradually increase and the measured sensitivity range will widen at first and then settle down.
If you pause the print, calibration will restart from the beginning when you resume.
-
-
@dc42 Ok, that's the behavior I expected from the documentation, but unfortunately it's not what I see.
After it first displays some form of calibration data, it just stops there and won't calibrate any further. The reported values then stay constant for the entire duration of the print.If I use the reported values in my M591 call, the sensor appears to "work", as in, it does spawn filament error events when the runout switch triggers etc. However, the calibration distance of just a few mm of course leads to incredibly inaccurate results...
-
@Diamondback thanks. It may be that there is a bug in the support for filament monitors on main boards used as expansion boards. I will add this to my investigations list.
-
@dc42 Thank you
-
@dc42 Some further info, yesterday my filament didn't detach from the empty spool correctly and got caught during a testprint. The active filament monitor did not catch this, it did not generate any filament error at all even after a few minutes of continuing to print.
Its config:
M591 D2 P4 C"100.io2.in" S1 L23.2 R70:150 E5
I guess something is indeed not working?
(The switch part of the monitor works fine btw) -
Did you send M591 to see what it reported after the fail?
-
@Phaedrux Nope, unfortunately not, but I guess I can easily replicate this. I'll do that when I find some free time
-
@dc42 said in Magnet Filament Monitor V3 - Calibration Issue:
@Diamondback thanks. It may be that there is a bug in the support for filament monitors on main boards used as expansion boards. I will add this to my investigations list.
Any news on this?
-
@Diamondback said in Magnet Filament Monitor V3 - Calibration Issue:
@dc42 said in Magnet Filament Monitor V3 - Calibration Issue:
@Diamondback thanks. It may be that there is a bug in the support for filament monitors on main boards used as expansion boards. I will add this to my investigations list.
Any news on this?
@dc42 ?
-
@Diamondback please can you update your firmware to 3.5beta4 on both boards and check whether the issue still occurs. There have been some fixes in this area.
-
@dc42 Updated everything to 3.5b4 and it seems like I can still not get anything out of my sensors other than the presence switch signal.
Configuration:
;Filament sensors M591 D0 P4 C"100.io0.in" S1 M591 D1 P4 C"100.io1.in" S1 M591 D2 P4 C"100.io2.in" S1 M591 D3 P4 C"100.io3.in" S1
M591 D3 after a print using that extruder:
Duet3D rotating magnet filament monitor v4 with switch on pin 100.io3.in, enabled, sensitivity 28.80mm/rev, allow 60% to 160%, check every 3.0mm, version 4, filament present, mag 132 agc 34, no calibration data
(the other 3 also don't show any calibration data, but I guess that's expected since they weren't actually used during the print)
Previously it was sometimes showing some data, but now it's just constantly "no calibration data".
-
@dc42 anything more I can test or help you with to debug this? I'd really like to get my 4 sensors working beyond the switch signal
-
@Diamondback thanks for the reminder. I'll try to reproduce this next week before we freeze 3.5.0 rc1.