I think my new Magnetic Filament Monitor is dead.
-
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.
-
I’m having trouble doing “a lot of printing with the monitor” due to the pauses. I’ll try to get something today, but this is super frustrating.
-
OK. I'm done. I can't print with this thing. Its constant pauses for random "too much" "not enough" "not working". Here are the M122's that I'm able to get today. either let me return it and try another one, or give me something else to try. But as of now, I'm disabling the filament monitor and unplugging it. I have prints that need printed so I can get paid. Constant pausing due to my filament monitor is unacceptable, especially for a monitor that I paid premium money for.
console 3.txt console 4.txt console 5.txt console 6.txt console 7.txt
-
Thanks, looks like you are getting quite a lot framing errors (but interestingly, no parity errors). So I think it's likely that the errors are caused by reception of bad data that isn't detected as such. I was already planning to change the firmware to ignore isolated data points that are out of line with other data. I'll bring this work forward, I may well start on it tomorrow.
Please post your config.g file, it may help me to reproduce the problem.
Does the filament monitor cable run close to the extruder motor cable (or any other stepper motor cable) for an appreciable distance?
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
At what point are you going to say this is a bad unit and give the man a new one? Is there a rash of mfm's going bad due to firmware? I have one. Works fine. From a support perspective, this looks to be bad hardware. My two cents. It works, then it doesn't. Then it does for a bit, then stops. No change to anything on the system. Now he's at a halt. In addition, shinook is an absolute duet fanboi. He got ME into the mfm even though I didn't want to. So glad he did because I love it. Let's move this guy forward.
@dc42 said in I think my new Magnetic Filament Monitor is dead.:
Thans, looks like you are getting quite a lot framing errors (but interestingly, no parity errors). So I think it's likely that the errors are caused by reception of bad data that isn't detected as such. I was already planning to change the firmware to ignore isolated data points that are out of line with other data. I'll bring this work forward, I may vebe start on it tomorrow.
Please post your config.g file, it may help me to reproduce the problem.
Does the filament monitor cable run close to the extruder motor cable (or any other stepper motor cable) for an appreciable distance?
-
While I agree that replacement seems to be the indicated solution, a lot of times issues may not appear when the defective unit is shipped back. If there are systemic issues such as poor communication, then it would make sense to try and isolate the issues to some degree.
Maybe it's time to send out a replacement and leave the defective unit with the OP to help in fine tuning the monitor ?
From my point of view - I was all geared up to get two of the magnetic monitors but had to wait for a while due to lack of stock. In that period I noticed so much "sometimes it doesn't work" and other weird issues, that I have decided to hold off until these units get reasonably reliable. The whole reason for installing one of these is to get more reliable printing and if you can't get that from such a premium priced unit then it makes you wonder why one would bother.
Last but probably not least, and this might not have anything to do with the issue at hand, I wonder if some of the issues are due to a poorly functioning extruder and even though it might print fine, the monitor might pick up errors that are not seen under normal circumstances. It might be worthwhile to increase the allowable deviation window. -
I'm very willing to supply @shinook with a replacement if he would like one, I just think it's unlikely to solve the problem.
-
Here is my config.g.
I'm running a direct drive setup with an E3D Hemera. I have sort of a double sleeve going for the cables, and that lets me have the wires for the filament monitor running in parallel, but not absolutely against the other wires. It's sort of visible in one of the pictures above. Not really sure how else to do it in a direct drive setup.If you think you can fix the issue with firmware, that is great. but at this point I have almost no fait that the filament monitor I have is reliable. while I have gotten some prints finished without it pausing, they are the minority. overall its been an unpleasant experience with near constant pauses and ruined prints.
Like I said, I'm willing to try to get this working. but I'm not willing to keep with the current way this is going. I need to be printing parts that have been ordered. So, for now, the monitor is disconnected. I've been playing this the way Duet3D says I have to, but I'd have returned this for another one or my money back a month ago if I could. Overall, this product and its implementation seems more like a beta product than a premium product ready to go off the shelf.
-
@shinook, you can leave the filament monitor connected but disabled, by using S0 in the M591 command instead of S1. Then RRF will still count errors it detects when receiving data. This would be useful, because the number of framing errors logged over a period of 12 hours (or whatever other time period is convenient for you) will give us a benchmark against which to compare changes to the hardware or firmware.
Although I doubt that this is a hardware issue, it would be good to eliminate a hardware fault, so I suggest we send you another filament monitor. Who did you purchase it from?
-
Thanks! I’ll make that change, and hopefully it does collect some good data that can help. I really do want this to work.
Filasturder order #53356
-
-
Unfortunately there is no filament monitor data in that report, so either the report was truncated or the filament monitor wasn't configured at all.
-
Sorry about that. I went in and changed it to S0, and I guess I forgot to uncomment the line.
I’ll hopefully get some useful data tomorrow. -
Thanks.
Unfortunately both we and Filastruder are out of stock of magnetic filament monitors, so it may be a little while before we can get you another one to try. It's the housings we have run out of, so we may be able to send you just the board.
-
Well, it will be a bit... Hemera gear broke today.
-
Sorry about the delay in this testing... my Hemera gear broke, then we moved to another city and it took me a while to get the printer going again.
But, that said, I'm having more problems even with the the command changed to S0 for debugging.. I'm still getting pauses for extruder not working. I have commented out the line because I'd really like to at least get a print going. But if there is anything I can check or do, I'm open for suggestions.
-
@shinook said in I think my new Magnetic Filament Monitor is dead.:
I'm open for suggestions.
I think we were going to try replacing it if you're still interested in doing that. I'm not sure what the current stock situation is, but check with filastruder if they can replace and if not fill out the form here to see if you can get something directly from Duet. https://www.duet3d.com/warranty
In either case, refer to this thread.
