constant pause

Monster Delta

@poohzaza what do you mean by logic of filament sensing?

poohzaza

t do you mean by logic of filament sensing?
you mention before that it triggered constantly maby invert that logic or the sensor is broken or recheak you config.g resume.g and pause.g

JamesM

For an issue like this I would start by either copying the data from the SD card and re-formatting it or just get a new SD card and copy everything over from the old one. a 16gig class 10 microsd card is rather cheap.

dc42

Please see the other thread about a similar issue experienced by another user with a magnetic filament monitor.

I intend to take a detailed look at issues with magnetic filament monitors later this week.

Monster Delta

@dc42 did you get chance to look into this

droftarts

What wiring are you using? I think the advice is to use shielded twisted pair cable, as the sensitivity of the sensor can be influenced if it runs near stepper motors and/or other cabling. There's a couple of other threads that might be worth checking:
https://forum.duet3d.com/topic/12182/magnetic-sensor
https://forum.duet3d.com/topic/3371/filament-monitor-working-well
https://forum.duet3d.com/topic/12005/magnetic-filament-monitor-calibration

Ian

themelle

@Monster-Delta said in constant pause:

Any one.

I had quite similar issues with the rotating magnet filament monitor (see https://forum.duet3d.com/topic/11591/rotating-magnet-filament-monitor-frame-errors/22).
Turned out to be a faulty monitor, which I got replaced by Duet3D. The new one works as expected, throwing no more errors and putting out way more reliable data.

As for the wiring I can - for my setup - confirm that braided but otherwise unshielded wires do work very well. But be sure to double check the crimp connections, and redo them in case of slightest doubts.

Monster Delta

Its not the wiring as it worka fine with the laser version. Im just about out of ideas i think I'll send it back and see if the folks at duet can figure it out

DarylMcM

I just installed our magnetic filament monitor and about 4 layers into a 400 layer print, I was optimistic, it started pausing. Tried a bunch of things but nothing worked. It would pause within seconds of resuming. I ended up setting the R parameter to 1/330 and it started printing again. Realizing that almost defeats the purpose of the monitor, I ran the 591 reports every few minutes.
They showed a somewhat smaller sensitivity then the 28.4 I started out with and a min variation of 2% while the max variation was around 113%.
I reset the L parameter on the fly with the gcode console to a value close to what it was reporting, 26.4 I believe and immediately got a pause, which I immediately resumed. Within a few layers the min variation was up to 28% and the max was 117%. After a few more layers the sensitivity was reading 27.13 and kinda holding there so again I set the L parameter on the fly and again got a pause and resumed.
The print is 75% done and I just changed the L parameter to 27.88 and now the min variation is 48% and the max is 112%. So it is really close to the 60% spread of the original 70/130.
The print show some impact at 4-6 layer area because of the the stuff I was trying, but it is not a wasted print.
I think the big problem is crap filament that the customer supplied and is the reason for the filament monitor purchase in the first place.
I guess the takeaway is patients and insist on buying your own filament.
I do notice that the monitor we received blinks red and green, one flash each constantly if filament is not moving. This behavior is not mentioned anywhere in the documentation, but it dose not seem to indicate anything other than no motion.
Don't know if this applies to the original posting, but it may help someone.

dc42

@DarylMcM said in constant pause:

I do notice that the monitor we received blinks red and green, one flash each constantly if filament is not moving. This behavior is not mentioned anywhere in the documentation, but it dose not seem to indicate anything other than no motion.

That is the expected behaviour when the filament monitor detects no motion, and the filament monitor is running version 2 firmware. The green flashes are position reports, the red ones are status reports.

Monster Delta

replacement received and all is working as it should now