@T3P3Tony said in issue with 1LC+3.5.0RC2 and magnetic filament sensor V3:

When you say you are powering up and down to change the filament monitors, is that just the toolboard or the whole system?

the whole system
yes - no changes in the loom or anything else

@jay_s_uk I am away at the minute, but will have a look and report back. Many thanks

@DocTrucker thanks you

@India Make sure you have updated DWC to the same version as the firmware.

Ian

@claustro Glad to hear of the progress. The mechanics around the MFM are indeed, well, ”delicate”.

Regarding the piece of PTFE tube below the sensor, I am having problems using this because it makes the filament load in the titan quite hard.

As you have a fixed distance between sensor and extruder anyway, there is no need to bridge it with a PTFE tube. To ensure better guidance of the filament through the MFM, however, collet and PTFT help a lot. With your arrangement, it will be sufficient to provide an extremely short piece of PTFE - just cut it directly at the neck of the collet on the MFM housing.

I hope this gives you enough headroom to fiddle the filament into the titan. I bear with you, as I have a titan as well. In my case, the MFM is attached to the titan's lever by a very short piece of PTFE, but free pending otherwise.

Good luck,
mb

@macguyver well, what I do is execute again the configuration command. I can be done while printing and measured distance is reset to cero, but also calibration data too. But this would do the reset you want, just put the config line on the layer change gcode.

@bugpwr Yay! The other 2.85mm filament user! I trust that, like me, everyone you know who switched to 1.75mm gave you their old filament, and you just can't bring yourself to throw it away? I'm still trying to get through my stock, some of which is 6-7 years old, and needs a bit of drying before use!

Ian

@T3P3Tony no, i'm waiting to try it on 3.4.7 or 3.5.0 (not RC)

@dc42 Thanks for adding this in 3.5 rc2 🙂 Very useful 👍
(The sensor here is almost 1m away from the extruder, so in case the signal looks too noisy, that's why)
2023-12-27_00-38-25.png

cc @herrtschaefer

@OwenD Thankyou 🙂
Between the link you sent and this post i think i have it now.
https://forum.duet3d.com/topic/31256/filament-runout-script-doesn-t-work

This worked for me. For future reference in case anyone else is using this with Repetier-Server, the pause.g action did not execute even after the change to my M591 command, but it did send a different notification that I was able to catch via Repetier's G-codes response to event and send the pause command from there. I used this regex in Repetier.

^Filament\serror\son\sextruder\s\d:.*

@dc42 Good news 🙂 With 3.5rc2, all my sensors appear to work for now 🙂 They collect data that seems right, they change status when inserting filament etc.
I haven't tested yet what happens if they actually detect an issue, but so far so good. Will keep you posted if anything weird comes up. Many thanks 🙂

@Johnnie_W

What version of the firmware are you using.

With version 3.4.x a filament sensor triggers an event which needs to be handled:

RRF Events

Perhaps something is missing from your configuration.

Frederick

@jer1001 Sorry I should have said V3

@droftarts
https://forum.duet3d.com/post/118277

@India Did you get it working? If so, please let us know, and what steps you took, so the information is here for other people, and so I can mark the thread as solved.

Ian