25.95mm/rev, min -33% max 162% over 9615.6mm
-
@t3p3tony Thanks for your honest feedback.
May I direct Filastruder support to your post confirming a warranty swap? -
@themelle yes
-
@t3p3tony Thank you!
-
Well I thought I was good to go with correct setup.
2 small 1 hour long prints no false positives. 11hour print - false trigger to little movement, about 5 hours in. Had to disable sensor so I didn't have to sit there having to keep resuming print. -
Are there any other troubleshooting measures I could try?
-
@nuroo I got my sensor swapped as it seemed to be faulty. Since then I have been getting much better values - but I am running 70-130% allowed movement to compensate for spike values.
Maybe you also should loosen the grip a little bit -
@themelle good to hear they swapped yours out. Figured I'd give the sensor another look.
I love that you can gather data while not actually having the printer stop.
Im current running:
M591 D0 P3 C3 S0 R85:115 L25.12 E3.0 (which worked on shorter prints)S0 - disable filament monitoring.
So with my current longer print I did:
M591 D0
Duet3D rotating magnet filament monitor v2 on input 3, disabled, sensitivity 25.12mm/rev, allow 85% to 115%, check every 3.0mm, current pos 210.9, measured sensitivity 24.33mm/rev, min 1% max 110% over 6134.2mmThe high side range seems ok. Max I got is 110% but room for error still with 115%.
That min 1% is strange?? It would have surely triggered a pause had filament monitoring been enabled. But I have moved the sensor location as suggested. It reminds me of the min -33% I got starting this thread.How do I over margin min 1% or min -33% so that these results are within good range?
For min 1% do i enter 0%? ie (M591 D0 P3 C3 S1 R0:115)??
For min -33% do i enter -40%? (M591 D0 P3 C3 S1 R-40:115)??
Can your algorithm handle such low values?
Do these low values still point to an issue with my setup? -
@nuroo Please look out for frame errors reported by
M122
.
They went away with my replaced monitor, and so did the ultra-low min-values it got before.