how to configure Pulse generating BigTreeTech filament sensor?
-
I calibrated my BTT following : https://duet3d.dozuki.com/Wiki/Duet3dFilamentMonitor_LaserVersion#Section_Calibration
I got allowed movement 60 to 160 every 5mm. But I was getting different values for sensitivity,min,max % each time. Heres yesterday's reading:L MIN % MAX % Over mm 6.362 0 33 591.7 6.647 0 48 384.5 8.156 0 20 - 9.755 0 20 107.3 7.478 0 20 231.8 9.897 0 83 - 12.226 0 19 - 8.747 0 21 - 8.376 0 21 - 11.125 0 27 -I tried 7.6 , 7, 6.25, 3.25 values for sensitivity with increased range of R(allowed movement). Still prints keep getting paused because of filament error.
My current setting:
M591 D0 L6.30 R25:195 E5 S1So today I disabled monitoring and took readings again:
L MIN % MAX % Over mm 6.034 0 196 5496.9 5.862 63 206 129.0 5.738 0 233 286.9 5.517 0 233 353.1 5.914 0 342 816.1 5.895 0 342 866.6How do I get it solved?
-
Sorry, but what is the BTT sensor?
-
@phaedrux BigTreeTech .Sorry for inconvenience ! I'll edit rn.
-
Is this the same one?
https://forum.duet3d.com/topic/17107/how-to-setup-the-bigtreetech-smart-filament-sensor
-
Add this to your config.g
M574 E2 S1 P"e0stop" ; configure active-high endstop for high end on E via pin estop M591 D0 P7 C"e0stop" L7 R50:200 E15 S1 ;configure BTT smart filament sensoradjust the "e0stop" to be whatever pin you are using.
verks just fine for me
-
@printernoodle I think its M574 that I missed. Thank you ! I'll try that.
-
@printernoodle you do not need the M574 command (which ought to result in some error anyway since M574 does not support the "E" parameter anymore since version 1.16 - which was quite some years ago).
The M591 command is enough.
The only problem that drove me crazy on my Duet Wifi running with firmware 3.2.2 was the pin name - for some reason
M591 D0 P7 C"e0stop"...does not work, butM591 D0 P7 C"e0_stop"...does. Unsure if that is a bug in the Duet firmware or intended behaviour though. -
@neodue said in how to configure Pulse generating BigTreeTech filament sensor?:
M591 D0 P7 C"e0_stop"... does. Unsure if that is a bug in the Duet firmware or intended behaviour though.
I believe the underscore is being ignored by the firmware, so there might have been something else keeping it from working.
-
@phaedrux I am afraid no, at least as far as I can tell.
The underscore is the only thing I changed in my config.g during these tests (with a reboot afterwards each time), and this fault was repeatable on my machine (tried three times in total before I posted)... as soon as I removed the underscore, I did not get any calibration data with M591 D0 when I printed something. But as soon as I add it, I get calibration data for each print (same file printed in both cases time, tested with three different files so far).
I have however not tried yet if the sensor will work without the underscore being included in the name - even if he does not spit out calibration data.
Edit: files were printed from the SD card each time by the way.
-
@neodue I'll take a look tomorrow and see if I can duplicate.
