Magnetic Filament Sensor error
-
Good morning, during my prints I keep on having a "Sensor error" wich pause the print itself, here's the M122:
=== Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later Board ID: 08DLM-996RU-N85T0-6JKFJ-3SD6R-9SSHN Used output buffers: 10 of 26 (26 max) === RTOS === Static ram: 23836 Dynamic ram: 76120 of which 0 recycled Never used RAM 8020, free system stack 98 words Tasks: NETWORK(notifyWait,16.6%,211) HEAT(notifyWait,0.0%,312) Move(notifyWait,2.7%,282) MAIN(running,80.6%,438) IDLE(ready,0.1%,30), total 100.0% Owned mutexes: === Platform === Last reset 00:35:03 ago, cause: software Last software reset at 2022-12-23 10:54, reason: User, GCodes spinning, available RAM 8140, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x04 Aux0 errors 0,0,0 Step timer max interval 0 MCU temperature: min 32.6, current 33.5, max 34.0 Supply voltage: min 23.6, current 23.8, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/7, heap memory allocated/used/recyclable 2048/130/0, gc cycles 0 Events: 1 queued, 0 completed Driver 0: standstill, SG min 0 Driver 1: standstill, SG min 0 Driver 2: standstill, SG min 0 Driver 3: standstill, SG min 0 Driver 4: standstill, SG min n/a Driver 5: Driver 6: Driver 7: Driver 8: Driver 9: Driver 10: Driver 11: Date/time: 2022-12-23 11:29:22 Cache data hit count 4294967295 Slowest loop: 144.54ms; fastest: 0.10ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 8 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 2.3ms, write time 45.2ms, max retries 0 === Move === DMs created 83, segments created 52, maxWait 135763ms, bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves 42258, completed 42258, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.4 Heater 1 is on, I-accum = 0.4 === GCodes === Segments left: 0 Movement lock held by Autopause HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is idle 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 Daemon is idle in state(s) 0 Autopause is doing "G4 S20 " in state(s) 0 28, running macro Code queue is empty === Filament sensors === Extruder 0: pos 318.16, errs: frame 0 parity 0 ovrun 0 pol 1 ovdue 0 === Network === Slowest loop: 131.42ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(1) 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.27 WiFi MAC address 84:0d:8e:b3:bc:96 WiFi Vcc 3.45, reset reason Turned on by main processor WiFi flash size 4194304, free heap 22368 WiFi IP address 192.168.1.7 WiFi signal strength -35dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 2 0 4 0 0 0 0 0```=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N85T0-6JKFJ-3SD6R-9SSHN
Used output buffers: 7 of 26 (26 max)
=== RTOS ===
Static ram: 23836
Dynamic ram: 76120 of which 0 recycled
Never used RAM 8020, free system stack 98 words
Tasks: NETWORK(notifyWait,16.1%,211) HEAT(notifyWait,0.0%,312) Move(notifyWait,2.7%,282) MAIN(running,81.2%,438) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:48:13 ago, cause: software
Last software reset at 2022-12-23 10:54, reason: User, GCodes spinning, available RAM 8140, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 33.2, current 33.7, max 34.1
Supply voltage: min 23.7, current 24.0, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/7, heap memory allocated/used/recyclable 2048/130/0, gc cycles 0
Events: 2 queued, 1 completed
Driver 0: standstill, SG min 0
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min 0
Driver 3: standstill, SG min 0
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2022-12-23 11:42:31
Cache data hit count 4294967295
Slowest loop: 19.88ms; fastest: 0.10ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 8
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 1.4ms, write time 1.5ms, max retries 0
=== Move ===
DMs created 83, segments created 52, maxWait 53979ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 58544, completed 58544, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.4
Heater 1 is on, I-accum = 0.4
=== GCodes ===
Segments left: 0
Movement lock held by Autopause
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle 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
Daemon is idle in state(s) 0
Autopause is doing "G4 S20 " in state(s) 0 28, running macro
Code queue is empty
=== Filament sensors ===
Extruder 0: pos 329.77, errs: frame 0 parity 0 ovrun 0 pol 1 ovdue 0
=== Network ===
Slowest loop: 100.34ms; fastest: 0.09ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(1)
HTTP sessions: 2 of 8
= WiFi =
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 2
WiFi firmware version 1.27
WiFi MAC address 84:0d:8e:b3:bc:96
WiFi Vcc 3.44, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 24248
WiFi IP address 192.168.1.7
WiFi signal strength -36dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 2 0 0 0 0 0 0 0Any Idea? Duet 2WiFi -
@TheDragonLord do the filament sensor wires run close to any stepper motor wires?
What AGC value does the filament sensor report?
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 -
@dc42 said in Magnetic Filament Sensor error:
@TheDragonLord do the filament sensor wires run close to any stepper motor wires?
yes....
-
@TheDragonLord in that case, I recommend you use shielded cable to connect the filament monitor. You can use the shield as the ground connection, so 2 cores + shield is sufficient.
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 -
@dc42 said in Magnetic Filament Sensor error:
@TheDragonLord in that case, I recommend you use shielded cable to connect the filament monitor. You can use the shield as the ground connection, so 2 cores + shield is sufficient.
I already use a shielded cable
-
@TheDragonLord what AGC value does the sensor report? Send M591 D# where # is the extruder number to check.
