I tried to monitor the sensor status, but I suppose I made an error somewhere.

I always get "OK" status when reading the sensor status after an error.

var StatusTest = sensors.filamentMonitors[0].status if {var.StatusTest} = "sensorError" M291 P{var.StatusTest} S1 ;M291 P"Filament Sensor - Sensor Error" S1 M24 M99 if {var.StatusTest} = "noDataReceived" M291 P{var.StatusTest} S1 ;M291 P"Filament Sensor - No data received" S1 M24 M99 if {var.StatusTest} = "tooMuchMovement" M291 P{var.StatusTest} S1 ;M291 P"Filament Sensor - tooLittleMovement" S1 M24 M99 if {var.StatusTest} = "tooLittleMovement" M291 P{var.StatusTest} S1 ;M291 P"Filament Sensor - tooLittleMovement" S1 M25 else M291 P{var.StatusTest} S1

This look like I don't read the right value or it's refreshed since the event was raised and called the filament-error.g

Any help will be appreciated

Here is a short video.
Key principle is:
1: The PTFE tube held by the shuttle wants to move away from the pressure of the fed filament when there is a blockage at the other end (i.e. there is no filament extruding)
2: When there is no blockage at the other end (i.e. filament is being extruded) pressure is released.

Use a fine capillary tube (2.5mm OD - 2mm ID) and drill out the end of the PTFE tube so that it slides easily. Using this method Filament will not get jammed when a new roll of filament is fed behind the old (as there is no way for it to get around the outside of the pushed filament)

Screenshot 2022-06-18 154211.png

Then just remove the M291 OK prompt and just have it as a timed message. One less click.

M24 won't work in this case because it's not a pause, it's a filament change.

You could try adding M25 to the beginning and M24 at the end but I'm not sure that would help in this case since we don't really want to evoke pause.g at all.

@dc42 Yes, I'm pretty sure that filament-error.g is executed. The sensor is configured as M591 D0 P1 C"e0stop" S1. In my case it will trigger when filament is inserted.

filament-error.g looks like this:

; ========================================================================================================= ; ; called when a filament error occurs ; ; ========================================================================================================= ; M291 P"welcome to filament error" echo "welcome to filament error" ; turn sensor off M591 D0 P1 C"e0stop" S0 ; ========================================================================================================= ;

This is what happens, when filament is inserted. First on the Panel first the error message pops-up:

IMG_1515.jpg

Then a split secend later the message from filament-error.g pops-up
IMG_1516.jpg

The console looks like this:

IMG_1517.jpg

Here the message from filament-error.g is displayed first.

According to the documentation the filament-erro message should not be displayed. In my opinion this is the preferrable way of implementation.

https://docs.duet3d.com/User_manual/Reference/Gcodes#m591-configure-filament-sensing
depending on type of filament sensor you are using things change . If its a switch, you need to know if it is normally open or closed that determines whether you have filament or you don't. if you want it to detect and pause during print.
for normally open switch
M591 P1 C"e0stop" S1 D0 ; filament sensing during print
if that didnt work just try P2
you can also setup sensor to detect filament and auto load in new firmware, which you need to make trigger file for. i suggest you get this covered first.

@comediantf2
This is what I put in filament-error.g so that it would work with both 3.3 and 3.4+:

M25 ; first, pause the print as pre-RRF 3.3 did if {param.D == 0} ; now call the right pre-RRF 3.4 subroutines. M98 P"filament-error0.g" elif {param.D == 1} M98 P"filament-error1.g"

That's great. Glad we got it working.

@pjrooster said in Change runout sensor switch closed to open in config:

@fcwilt thanks for the suggestion, I was hoping for a simple solution, unfortunatly that didn't work, it just didn't detect the sensor at all.

Yes, dc42's post explained the problem. Normally the ! would do they trick but not in this case.

Frederick

@t3p3tony Alright! That is very interesting Tony! ! ! This is the first time I hear about the teardrop used in 3D printing, very interesting to read about this. Thank you for explaining and sharing the history, I find it a good history to know.

For the Solidworks folks!
https://github.com/Scrambler73/Duet3D-Rotating-Magnet-Filament-Monitor.git
There you can find the SW files and a STEP assembly, open the STEP to find al the parts inside. From there you can open the STEP parts partially
This is the first time I share anything on github, so if anyone have a problem downloading please share here.

@phaedrux I take that back. I'm still getting no data received.

(Deleted M122 results)

False alarm. My ground wire pin wasn't seated in the Molex connector on the sensor side and, apparently, worked long enough for me to prepare for a print.

Yeah, looks good. Here's the calibration:

Pulse-type filament monitor on pin e0stop, disabled, sensitivity 4.141mm/pulse, allowed movement 95% to 103%, check every 51.0mm, measured sensitivity 4.186mm/pulse, measured minimum 97%, maximum 101% over 1837.5mm

I used the 12x sensor wheel rather than the default 24x wheel (fewer teeth), not sure if that helps or not.

Anyway, thanks for your help guys. I appreciate it.

How do you have it configured? How is it installed? Is it similar to the Duet Magnetic Filament sensor?

@jdebuhr said in Filament sensor Meta Command issue:

Found it:
Field "filamentPresent" is removed from those types of filament monitor that previously supported it. Use "status" instead.

Hi,

I'm glad we were able to be of no help whatsoever. 😉

Seriously though, where did you find the answer?

Frederick

Depends on when you want it to take effect.

Putting the command in config.g would be the easiest way.

https://docs.duet3d.com/en/User_manual/Connecting_hardware/Sensors_filament#configuring-other-filament-out-sensors

@alijambo73 said in Filament sensor problem after upgrade to 3.2:

@phaedrux Will I need to make any config changes?

Not likely.

@huai3895 the issue people have had before with pulse-detecting optical filament sensors is that there isn't a clean transition at the start and end of each pulse. The solution is to use a Schmitt trigger or a comparator with positive feedback to process the output from the opto switch.

@adammhaile said in Filament error when filament loaded:

For now I've added M591 commands to start.g, stop.g, and cancel.g to keep filament monitoring enabled only when actually printing and now I don't get and spurious errors.

For anyone else finding this in the future it can also be useful to put them in the tool change files for multi tool printers.

@lo-fi For the record if anyone is reading this. .5 was too much but I printed different sizes in a batch in the resin printer. The one with .3 added to the inner surface of the lid of the MMF v2 housing got me to the magic agc 110 mag 128 that seems to be working... All magnets vary of course so maybe mine was just a little bit strong.

But if you have a sensor that's reading way high mm/rev sensitivity back your magnet off a tiny amount. the tolerances in the thing are super tight.