I think my new Magnetic Filament Monitor is dead.
-
Oh, do I put that 25.10mm/rev into my config.g now?
-
Yes I think so based on this:
Calibration
If you haven't done so already, send the M591 command with the correct parameters to tell the firmware about the sensor.
Run M591 D# where # is the extruder number and check that the sensor angle is reported, to confirm that communication from the filament monitor to the Duet is working.
Start a print.
During and after the print, as soon as sufficient filament has been extruded you can use M591 D# (where # is the extruder number) to report the measured mm/rev averaged over the print thus far, and its variation.
If you pause and then resume the print, calibration will be re-started and the values accumulated from before you paused will be discarded.
The mm/rev value goes into the L parameter of the M591 command. Use a positive or negative sign as reported by M591. Set the R (tolerance) parameter to somewhat more than the reported variation. -
@shinook said in I think my new Magnetic Filament Monitor is dead.:
I guess it just needed me to give up on it before it would put forth its best effort....
Sometimes that's the way it goes.
-
So, got more pauses and an “Extruder 0 report sensor not working” error. It’s otherwise working great. But, not sure what to do. Having my printer stop because of the sensor is getting frustrating.
-
-
A screen shot in one of your previous posts showed that you are running firmware 2.05. Please upgrade to firmware 2.05.1. It might fix the issue, although more likely it won't.
-
Please keep a close eye on the AGC value reported by M591. If it goes much above 100 then we'll replace your filament monitor.
-
-
Ok. I’ll update the firmware.
-
Update the firmware.
I keep getting random pauses from “too much” or “too little” movement. Though they aren’t as common as the good old “ sensor not working”. My AGC is still in the low 90’s. And every time I check the status of the monitor(while its working) the results are between 99% and 103%.Honestly, it’s causing more problems than its worth. If I can’t get it to stop pausing my prints, I’ll need to find a more reliable monitor.
-
@shinook said in I think my new Magnetic Filament Monitor is dead.:
I keep getting random pauses from “too much” or “too little” movement.
What do you have the min and max allowed percentages set to?
-
70% to 130%
-
It’ll work great for multiple prints, then pause a 3 hour print 5 times.
-
Have the "sensor not working" errors gone completely, or not?
-
No, I get them several times a day.
-
I wish that it at least kept the calibration data from before a pause. Or gave some data about the pause. But it deletes it all and makes trouble shooting it from a logical data driven method near impossible.
-
But, at this point, with the AGC still showing good, I think it’s just got something wrong with the brains of the thing.
-
My guess is that there is occasional corruption in the received data. This isn't necessarily due to interference, it could just be caused by the processor load causing interrupts to be delayed. There is a parity check on the data, but of course that will only detect a single bit error.
Does your system include a PanelDue, and if so, does it use the default baud rate of 57600 or a different one?
-
No, I’m using a. Maestro with the LCD 12864F-3.
-
If you think it will help, I could unplug the display and see if that helps. I only use it as a display, and not to control the printer.
-
I tried disconnecting the LCD, and was able to get 88% of a print done before it paused.
-
So, if nobody has any other suggestions for me to try, can I return this and get another one? Or will I need to find a different filament sensor to try that doesn’t cost so much that wont pause my prints for unknown reasons.....
I don’t want to give up on it, but I’ve been fighting this for too long with zero progress. I can’t keep having my prints pause for no reason, its lowering my productivity and costing me money.
-
Please provide a M122 report taken after you have done quite a lot of printing with the filament monitor active. I'm interested in the number of parity and framing errors reported by the filament monitor. If it's zero then we need to send you a new filament monitor. If it's a high number then that suggests my theory about undetected data corruption is correct.
