MFM no data received issue
-
So my customer’s printer is having an issue with their magnetic filament sensor that they’re less than pleased with and I’m unable to provide solutions for them. The sensor has been more of a hinderance to them than help and it’s frustrating on my end since I’ve had decent success with an indirect laser sensor for over a year now.
The issue is that while printing the sensor is flashing red and green as it should and the m591 reports good measurements. As soon as I enable filament sensing it errors out saying no data retrieved, which makes no since when I can watch the sensor working in the object model section. It seems I’m not the only one having issues with the sensor so until I can see the issues have been sorted out on the forums I just need to keep it shut off from doing it’s job…
Here are the machine status reports:
M591 D0
Duet3D rotating magnet filament monitor v3 on pin io6.in, disabled, sensitivity 24.50mm/rev, allow 20% to 220%, check all moves every 5.0mm, version 3, mag 129 agc 90, measured sensitivity 25.64mm/rev, min 95% max 105% over 2499.2mmM122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.0beta6 (2021-11-06 11:39:32) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: Q9LL5-B296U-D65J0-40KM0-N503Z-Z51M7
Used output buffers: 3 of 40 (24 max)
=== RTOS ===
Static ram: 103876
Dynamic ram: 113484 of which 28 recycled
Never used RAM 20652, free system stack 118 words
Tasks: NETWORK(ready,6.4%,234) ACCEL(notifyWait,0.0%,346) HEAT(notifyWait,0.5%,340) Move(notifyWait,19.3%,265) CanReceiv(notifyWait,0.0%,942) CanSender(notifyWait,0.0%,358) CanClock(delaying,0.3%,331) TMC(notifyWait,23.2%,71) MAIN(running,33.5%,414) IDLE(ready,0.6%,29) AIN(delaying,16.2%,264), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 21:50:27 ago, cause: power up
Last software reset at 2021-12-22 16:54, reason: User, GCodes spinning, available RAM 20972, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 78627634, completed 78627633, timed out 0, errs 0
Step timer max interval 1476
MCU temperature: min 27.4, current 57.3, max 58.4
Supply voltage: min 23.8, current 23.9, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/5, heap memory allocated/used/recyclable 2048/328/248, gc cycles 4
Driver 0: pos 46292, standstill, SG min 0, read errors 0, write errors 0, ifcnt 41, reads 4106, writes 41, timeouts 0, DMA errors 0
Driver 1: pos -1819, standstill, SG min 0, read errors 0, write errors 0, ifcnt 41, reads 4106, writes 41, timeouts 0, DMA errors 0
Driver 2: pos 46131, standstill, SG min 0, read errors 0, write errors 0, ifcnt 41, reads 4106, writes 41, timeouts 0, DMA errors 0
Driver 3: pos 0, ok, SG min 0, read errors 0, write errors 0, ifcnt 103, reads 4044, writes 103, timeouts 0, DMA errors 0
Driver 4: pos 0, ok, SG min 0, read errors 0, write errors 0, ifcnt 103, reads 4044, writes 103, timeouts 0, DMA errors 0
Driver 5: pos 0, ok, SG min 0, read errors 0, write errors 0, ifcnt 38, reads 4109, writes 38, timeouts 0, DMA errors 0
Driver 6: pos 0, standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 4138, writes 9, timeouts 0, DMA errors 0
Date/time: 2022-01-25 12:03:55
Cache data hit count 4294967295
Slowest loop: 999.36ms; fastest: 0.06ms
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 4.9ms, write time 142.4ms, max retries 0
=== Move ===
DMs created 83, segments created 34, maxWait 41482150ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 236112, completed 236083, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 3], CDDA state 3
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1, chamber heaters -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.3
Heater 1 is on, I-accum = 0.8
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X254.676 Y318.277 E21.66278" in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Filament sensors ===
Extruder 0: pos 205.31, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
=== CAN ===
Messages queued 707809, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 16), ts 393137/0/0
Tx timeouts 0,167,393136,0,0,314502 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 217.36ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 2 of 8- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address f0:08:d1:03:81:17
WiFi Vcc 3.35, reset reason Power up
WiFi flash size 2097152, free heap 21384
WiFi IP address 10.18.86.16
WiFi signal strength -61dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
- WiFi -
-
I believe the sensor should be replaced.
Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.
Sorry for the inconvenience.
-
Ok I’ll contact my reseller. The thing I’m worried of is this is the second sensor I’ve had to buy for them. I’m really hoping third time’s the charm…
