Open zurbaran opened 2 years ago
Hi, i see this as well, but only with the new version. It was working fine with 0.2.3, but after the Update the sensor gets triggered 3-4 in a 1 hour print altought the filament is still present..
Same problem here. Any solution??
BG kami
+1 also seeing the same issue using a basic microswitch type sensor
there must be 10 consequent reads to consider filament end as valid to prevent false positives, will try to test
Possibly fixed by #55
Hi guys, as @CMR-DEV mentioned this is possibly fixed and now available in 0.3.2 version, please try updating
It seems that the filament sensor sends microcuts, which causes the printer, octoprint, to detect that the filament has run out for a few thousandths of a second and pause printing. Could it be configured the times that it must be in a state change so that it considers it real? Marlin himself does not detect the end of the filament for me because he must be filtering those microcuts, but the raspberry, octoprint, if he thinks he has received the signal that the filament is over.