RRF3.4 RC2 Filament/sensor error

BoA

I updated to 3.4rc2, and I am getting some random filament sensor error.

Duet3 standalone

=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0rc2 (2022-02-22 17:04:17) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956L2-G43S8-6J1D6-3SJ6R-KA0YG
Used output buffers: 9 of 40 (27 max)
=== RTOS ===
Static ram: 150984
Dynamic ram: 98404 of which 0 recycled
Never used RAM 81388, free system stack 130 words
Tasks: NETWORK(ready,23.3%,199) ETHERNET(notifyWait,0.1%,168) HEAT(notifyWait,0.1%,321) Move(notifyWait,0.8%,254) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,356) CanClock(delaying,0.0%,333) TMC(notifyWait,8.7%,58) MAIN(running,67.1%,1016) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes: LwipCore(NETWORK)
=== Platform ===
Last reset 00:29:09 ago, cause: power up
Last software reset at 2022-03-06 15:52, reason: User, GCodes spinning, available RAM 81480, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 135
MCU temperature: min 20.6, current 45.6, max 45.9
Supply voltage: min 5.2, current 27.2, max 27.5, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 4.5, current 12.2, max 12.3, under voltage events: 0
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/30/0, gc cycles 0
Events: 1 queued, 1 completed
Driver 0: pos 15715, ok, SG min 0, mspos 926, reads 20833, writes 22 timeouts 0
Driver 1: pos 21332, standstill, SG min 0, mspos 984, reads 20834, writes 22 timeouts 0
Driver 2: pos 893, ok, SG min 0, mspos 314, reads 20842, writes 14 timeouts 0
Driver 3: pos 0, standstill, SG min 0, mspos 8, reads 20845, writes 11 timeouts 0
Driver 4: pos 0, ok, SG min 0, mspos 186, reads 20838, writes 18 timeouts 0
Driver 5: pos 0, ok, SG min 0, mspos 42, reads 20838, writes 18 timeouts 0
Date/time: 2022-03-07 23:25:14
Slowest loop: 61.24ms; fastest: 0.05ms
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 4.0ms, write time 24.3ms, max retries 0
=== Move ===
DMs created 125, segments created 30, maxWait 521301ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 10333, completed 10324, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], 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 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters 3 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.2
Heater 1 is on, I-accum = 0.8
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X171.425003 Y101.862925 E.14892831" 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 269.30, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
Extruder 1: pos 0.00, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
=== CAN ===
Messages queued 15746, received 0, lost 0, boc 2
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 8749/0/0
Tx timeouts 0,0,8747,0,0,6996 last cancelled message type 4514 dest 127
=== Network ===
Slowest loop: 83.26ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- Ethernet -
State: active
Error counts: 0 0 1 0 0
Socket states: 5 2 2 2 2 2 0 0

Only message logged is:

Error: Filament error on extruder 0: sensorError

Print is paused, and after resuming everything works fine

With RRF3.3 no such issues

Phaedrux

Can you share your M592 command and the results of sending M592 D0?

BoA

@phaedrux M592? I do not use M592 anywhere in config.

And M592 D0 is:

M592 D0
Drive 0 nonlinear extrusion coefficients: A=0.000, B=0.0000, limit=0.20

Perhaps You had M591 in mind.

M591 D0 P3 C"io5.in" S1 L25.4 R50:150 E12.7 A0           ; configure magnetic filament monitor on io5
M591 D1 P3 C"io7.in" S1 L25.4 R50:150 E12.7 A0           ; configure magnetic filament monitor on io7

M591 D0
Duet3D rotating magnet filament monitor v3 on pin io5.in, disabled, sensitivity 25.40mm/rev, allow 50% to 150%, check printing moves every 12.7mm, version 3, mag 132 agc 64, measured sensitivity 25.61mm/rev, min 94% max 106% over 5312.6mm

I see it is reported as disabled, as I disabled it after this error message just before resuming print just to avoid next pause.

Phaedrux

Sorry, I meant M591,

BoA

@phaedrux I posted M591 also

Phaedrux

And when you return to 3.3 the problem goes away entirely?

BoA

@phaedrux Yes

charliedrums

This just happened to me on a 14 hour print. I updated to RRF3.4. Came here to see what it could be. I resumed the print and is printing fine now. the print is still going as I write.

=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0rc2 (2022-02-22 17:04:17) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TN-6JTD0-3SJ6S-1V82V
Used output buffers: 10 of 40 (40 max)
=== RTOS ===
Static ram: 150984
Dynamic ram: 66520 of which 28 recycled
Never used RAM 129804, free system stack 114 words
Tasks: SBC(resourceWait:,0.7%,494) HEAT(notifyWait,0.0%,321) Move(notifyWait,1.7%,248) CanReceiv(notifyWait,0.0%,772) CanSender(notifyWait,0.0%,346) CanClock(delaying,0.0%,339) TMC(notifyWait,8.4%,58) MAIN(running,89.1%,923) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 15:54:21 ago, cause: power up
Last software reset at 2022-03-09 01:00, reason: HardFault, GCodes spinning, available RAM 130308, slot 1
Software reset code 0x4063 HFSR 0x80000000 CFSR 0x00000000 ICSR 0x00400803 BFAR 0x00000000 SP 0x2041b4f8 Task MAIN Freestk 1672 ok
Stack: 20429f28 2042c2d8 2041b594 00000001 0000002e 0045c81b 0045c676 61070000 20419a7c 2042bf34 00000000 00000001 00000000 004844d7 2042bf34 00000000 00000000 0048481f 003ffff0 004849f7 20429860 ffffffff 0934d918 2042bf34 20419a7c 2042c2dc ffffffff
Error status: 0x04
Aux0 errors 0,0,0
Step timer max interval 135
MCU temperature: min 47.3, current 47.5, max 47.7
Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/160/126, gc cycles 0
Events: 2 queued, 2 completed
Driver 0: pos 60689, ok, SG min 0, mspos 928, reads 41145, writes 0 timeouts 0
Driver 1: pos 14056, ok, SG min 0, mspos 616, reads 41145, writes 0 timeouts 0
Driver 2: pos 50096, standstill, SG min 0, mspos 72, reads 41145, writes 0 timeouts 0
Driver 3: pos 0, standstill, SG min 0, mspos 664, reads 41146, writes 0 timeouts 0
Driver 4: pos 0, standstill, SG min 0, mspos 152, reads 41146, writes 0 timeouts 0
Driver 5: pos 0, standstill, SG min 0, mspos 104, reads 41145, writes 0 timeouts 0
Date/time: 2022-03-09 16:28:53
Slowest loop: 31.03ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 20, maxWait 796ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 678710, completed 678677, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], 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 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.3
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP* is doing "M122" in state(s) 0 0, running macro
Telnet is idle in state(s) 0
File* is doing "G1 X453.419006 Y257.640015 E-0.570000" 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: no data received
=== CAN ===
Messages queued 15065, received 12407, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 268, free buffers 50 (min 47), ts 3026/3026/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 4, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 15043/15043
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0, IAP RAM available 0x2b8b0
Buffer RX/TX: 1520/2544-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4-rc2
File /opt/dsf/sd/gcodes/Pandero11in_Escalas_0.6n_0.3mm_PLA_13h57m.gcode is selected, processing
HTTP:
Executing macro 0:/macros/Diagnostics, started by M98 P"0:/macros/Diagnostics"
> Next stack level
File:
Buffered code: G1 X453.419 Y257.64 E-.57
Buffered code: G1 E-.03 F2400
Buffered code: G1 Z63.02 F720
Buffered code: G1 X457.643 Y264.663 F10800
Buffered code: G1 Z62.62 F720
Buffered code: G1 E.6 F2400
Buffered code: G1 F4200
Buffered code: G1 X458.599 Y265.619 E.09391
Buffered code: G1 F8640
Buffered code: G1 X457.643 Y264.663 E-.35695
Buffered code: G1 E-.24305 F2400
Buffered code: G1 Z63.02 F720
Buffered code: G1 X459.911 Y269.805 F10800
Buffered code: G1 Z62.62 F720
Buffered code: G1 E.6 F2400
Buffered code: G1 F4200
Buffered code: G1 X460.905 Y270.799 E.09959
Buffered code: G1 F8640
Buffered code: G1 X459.911 Y269.805 E-.37085
Buffered code: G1 E-.22915 F2400
Buffered code: G1 Z63.02 F720
Buffered code: G1 X463.158 Y276.331 F10800
Buffered code: G1 Z62.62 F720
Buffered code: G1 E.6 F2400
==> 992 bytes
Code buffer space: 1552
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 39.36, max time between full transfers: 44.0ms, max pin wait times: 29.1ms/8.3ms
Codes per second: 18.47
Maximum length of RX/TX data transfers: 3928/1628

charliedrums

That print finished without any more faults. Started another print, this one 17 hours long and by hour 5 I got the

3/10/2022, 3:12:23 AM 	Error: Filament error on extruder 0: sensorError

I don't get any other filament errors as I was very careful in installing the sensor correctly. This is the M591

3/10/2022, 10:14:45 AM 	M591 D0
Duet3D rotating magnet filament monitor v3 on pin 121.io1.in, enabled, sensitivity 28.80mm/rev, allow 35% to 130%, check printing moves every 20.0mm, version 3, mag 129 agc 85, measured sensitivity 24.72mm/rev, min 99% max 101% over 1626.0mm

Diagnostics:

3/10/2022, 10:08:44 AM 	=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0rc2 (2022-02-22 17:04:17) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TN-6JTD0-3SJ6S-1V82V
Used output buffers: 6 of 40 (40 max)
=== RTOS ===
Static ram: 150984
Dynamic ram: 66520 of which 28 recycled
Never used RAM 129876, free system stack 128 words
Tasks: SBC(resourceWait:,14.6%,504) HEAT(notifyWait,0.3%,321) Move(notifyWait,17.9%,248) CanReceiv(notifyWait,0.5%,772) CanSender(notifyWait,0.2%,346) CanClock(delaying,0.1%,339) TMC(notifyWait,185.9%,58) MAIN(running,156.5%,923) IDLE(ready,0.1%,30), total 376.1%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 13:18:07 ago, cause: power up
Last software reset at 2022-03-10 01:24, reason: AssertionFailed, GCodes spinning, available RAM 129804, slot 2
Software reset code 0x4123 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x2041b53c Task MAIN Freestk 1689 ok
Stack: 00000599 004a3b00 00484adb 20429860 ffffffff 9b6a2e4b 2042c2dc 20419a7c 2042e1c4 ffffffff 00000000 9b6a2e7a 00484b0d 2041b58c 20429f28 20421e98 0048229f 2042e1c0 0045c7f3 00000000 2042e1c4 00000000 2041b59c 00000101 00000000 00000000 00000000
Error status: 0x04
Aux0 errors 0,0,0
Step timer max interval 180
MCU temperature: min 35.1, current 45.6, max 48.3
Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/100/60, gc cycles 0
Events: 1 queued, 1 completed
Driver 0: pos 40039, ok, SG min 0, mspos 725, reads 50511, writes 17 timeouts 0
Driver 1: pos 16068, ok, SG min 0, mspos 530, reads 50512, writes 17 timeouts 0
Driver 2: pos 16792, ok, SG min 0, mspos 437, reads 50512, writes 17 timeouts 0
Driver 3: pos 0, ok, SG min 0, mspos 715, reads 50512, writes 17 timeouts 0
Driver 4: pos 0, ok, SG min 0, mspos 267, reads 50512, writes 17 timeouts 0
Driver 5: pos 0, ok, SG min 0, mspos 149, reads 50512, writes 17 timeouts 0
Date/time: 2022-03-10 14:38:24
Slowest loop: 977.23ms; fastest: 0.04ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 17, maxWait 24379276ms, bed compensation in use: mesh, comp offset -0.455
=== MainDDARing ===
Scheduled moves 290327, completed 290301, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], 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 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.2
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP* is doing "M122" in state(s) 0 0, running macro
Telnet is idle in state(s) 0
File* is doing "G1 Z20.799999 F720" 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: no data received
=== CAN ===
Messages queued 704031, received 981440, lost 0, boc 0
Longest wait 2ms for reply type 6026, peak Tx sync delay 279, free buffers 50 (min 45), ts 239437/239436/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 4, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 35269/35269
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0, IAP RAM available 0x2b8b0
Buffer RX/TX: 2064/3296-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4-rc2
File /opt/dsf/sd/gcodes/Pandero 14in escalas_0.6n_0.3mm_PLA_18h27m.gcode is selected, processing
HTTP:
Executing macro 0:/macros/Diagnostics, started by M98 P"0:/macros/Diagnostics"
> Next stack level
File:
Buffered code: G1 Z20.4 F720
Buffered code: G1 E.6 F2400
Buffered code: G1 F4200
Buffered code: G1 X311.863 Y149.869 E.138
Buffered code: G1 F8640
Buffered code: G1 X313.184 Y148.549 E-.4928
Buffered code: G1 E-.1072 F2400
Buffered code: G1 Z20.8 F720
Buffered code: G1 X311.471 Y154.535 F10800
Buffered code: G1 Z20.4 F720
Buffered code: G1 E.6 F2400
Buffered code: G1 F4200
Buffered code: G1 X310.523 Y154.629 E.06607
Buffered code: G1 X308.988 Y154.828 E.1074
Buffered code: G1 X309.043 Y154.72 E.00841
Buffered code: G1 X309.595 Y154.092 E.05804
Buffered code: G1 X310.231 Y153.463 E.06202
Buffered code: G1 X310.72 Y152.835 E.05527
Buffered code: G1 X311.017 Y152.207 E.04823
Buffered code: G1 X311.163 Y151.578 E.04476
Buffered code: G1 X311.183 Y150.95 E.04362
Buffered code: G1 X311.061 Y150.322 E.04441
Buffered code: G1 X310.743 Y149.693 E.04886
Buffered code: G1 X310.565 Y149.491 E.01873
Buffered code: G1 X307.182 Y150.524 E.24546
==> 1104 bytes
Pending code: G1 X307.075 Y150.73 E.01612
Pending code: G1 X306.5 Y150.911 E.04182
Code buffer space: 2056
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 37.64, max time between full transfers: 83.8ms, max pin wait times: 62.5ms/6.9ms
Codes per second: 6.04
Maximum length of RX/TX data transfers: 3712/1716

Still printing at time of writing with 22.4 % complete and about 13ish hours to go.
Edited to add tool board 1lc diagnostics

3/10/2022, 10:21:58 AM 	M122 B121
Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.4.0rc2 (2022-02-22 10:15:02)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 2204, free system stack 17 words
Tasks: Move(notifyWait,4.4%,99) HEAT(notifyWait,4.8%,95) CanAsync(notifyWait,0.0%,55) CanRecv(notifyWait,0.8%,74) CanClock(notifyWait,0.3%,65) ACCEL(notifyWait,0.0%,61) TMC(notifyWait,51.5%,57) MAIN(running,153.6%,351) IDLE(ready,0.0%,26) AIN(delaying,84.1%,142), total 299.6%
Last reset 13:31:22 ago, cause: VDD brownout
Last software reset data not available
Driver 0: pos 22986108, 405.0 steps/mm,standstill, SG min 0, read errors 20, write errors 0, ifcnt 13, reads 28334, writes 13, timeouts 7, DMA errors 0, CC errors 0, failedOp 0x41, steps req 25729946 done 25729946
Moves scheduled 288224, completed 288224, in progress 0, hiccups 125, step errors 0, maxPrep 665, maxOverdue 8517, maxInc 8517, mcErrs 0, gcmErrs 0
Peak sync jitter 1/6, peak Rx sync delay 232, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 24.1, current 24.3, max 24.5
MCU temperature: min 37.8C, current 51.0C, max 53.2C
Last sensors broadcast 0x00000002 found 1 81 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 997750, send timeouts 0, received 726318, lost 0, free buffers 37, min 36, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 617, adv 35626/74661
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 3, other errors 0
=== Filament sensors ===
Interrupt 4 to 97us, poll 8 to 2542us
Driver 0: pos 285.47, errs: frame 88 parity 0 ovrun 0 pol 0 ovdue 0

charliedrums

Happened again at 44.5% of the print the same error code:

3/10/2022, 2:47:01 PM 	Error: Filament error on extruder 0: sensorError

This time I did the diagnostic codes before I resumed the print.
M122

3/10/2022, 4:32:40 PM 	M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0rc2 (2022-02-22 17:04:17) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TN-6JTD0-3SJ6S-1V82V
Used output buffers: 8 of 40 (40 max)
=== RTOS ===
Static ram: 150984
Dynamic ram: 66520 of which 28 recycled
Never used RAM 129828, free system stack 128 words
Tasks: SBC(ready,120.2%,504) HEAT(notifyWait,2.6%,321) Move(notifyWait,231.3%,248) CanReceiv(notifyWait,4.1%,772) CanSender(notifyWait,3.2%,346) CanClock(delaying,0.9%,339) TMC(notifyWait,1474.5%,58) MAIN(running,2710.9%,923) IDLE(ready,0.1%,30), total 4547.8%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 19:42:02 ago, cause: power up
Last software reset at 2022-03-10 01:24, reason: AssertionFailed, GCodes spinning, available RAM 129804, slot 2
Software reset code 0x4123 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x2041b53c Task MAIN Freestk 1689 ok
Stack: 00000599 004a3b00 00484adb 20429860 ffffffff 9b6a2e4b 2042c2dc 20419a7c 2042e1c4 ffffffff 00000000 9b6a2e7a 00484b0d 2041b58c 20429f28 20421e98 0048229f 2042e1c0 0045c7f3 00000000 2042e1c4 00000000 2041b59c 00000101 00000000 00000000 00000000
Error status: 0x04
Aux0 errors 0,0,0
Step timer max interval 149
MCU temperature: min 45.4, current 47.2, max 48.7
Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/160/120, gc cycles 0
Events: 2 queued, 2 completed
Driver 0: pos 36230, standstill, SG min 0, mspos 104, reads 17097, writes 0 timeouts 0
Driver 1: pos -35430, standstill, SG min 0, mspos 904, reads 17097, writes 0 timeouts 0
Driver 2: pos 40272, standstill, SG min 0, mspos 312, reads 17097, writes 0 timeouts 0
Driver 3: pos 0, standstill, SG min 0, mspos 840, reads 17097, writes 0 timeouts 0
Driver 4: pos 0, standstill, SG min 0, mspos 392, reads 17098, writes 0 timeouts 0
Driver 5: pos 0, standstill, SG min 0, mspos 24, reads 17098, writes 0 timeouts 0
Date/time: 2022-03-10 21:02:19
Slowest loop: 50.08ms; fastest: 0.04ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 19, maxWait 1260ms, bed compensation in use: mesh, comp offset -0.455
=== MainDDARing ===
Scheduled moves 602559, completed 602559, 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 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.2
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" 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
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: no data received
=== CAN ===
Messages queued 494841, received 472277, lost 0, boc 0
Longest wait 5ms for reply type 6024, peak Tx sync delay 301, free buffers 50 (min 45), ts 115176/115176/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 4, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 22180/22180
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0, IAP RAM available 0x2b8b0
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4-rc2
File /opt/dsf/sd/gcodes/Pandero 14in escalas_0.6n_0.3mm_PLA_18h27m.gcode is selected, paused
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 39.26, max time between full transfers: 77.9ms, max pin wait times: 60.7ms/10.7ms
Codes per second: 14.20
Maximum length of RX/TX data transfers: 3768/1716

M122 B121

3/10/2022, 4:33:34 PM 	M122 B121
Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.4.0rc2 (2022-02-22 10:15:02)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 2204, free system stack 17 words
Tasks: Move(notifyWait,2.4%,99) HEAT(notifyWait,1.2%,95) CanAsync(notifyWait,0.0%,55) CanRecv(notifyWait,0.4%,74) CanClock(notifyWait,0.1%,65) ACCEL(notifyWait,0.0%,61) TMC(notifyWait,13.3%,57) MAIN(running,60.9%,351) IDLE(ready,0.0%,26) AIN(delaying,21.7%,142), total 100.0%
Last reset 19:42:58 ago, cause: VDD brownout
Last software reset data not available
Driver 0: pos 35910153, 405.0 steps/mm,standstill, SG min 0, read errors 10, write errors 0, ifcnt 13, reads 15749, writes 0, timeouts 3, DMA errors 0, CC errors 0, failedOp 0x06, steps req 16566495 done 16566495
Moves scheduled 560607, completed 560607, in progress 0, hiccups 0, step errors 0, maxPrep 681, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter 1/8, peak Rx sync delay 235, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 24.1, current 24.3, max 24.3
MCU temperature: min 37.8C, current 48.2C, max 53.2C
Last sensors broadcast 0x00000002 found 1 70 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 457092, send timeouts 0, received 473045, lost 0, free buffers 37, min 36, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 601, adv 35676/74660
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 0, other errors 0
=== Filament sensors ===
Interrupt 4 to 34us, poll 8 to 2477us
Driver 0: pos 139.92, errs: frame 206 parity 0 ovrun 0 pol 0 ovdue 0

M591 D0

3/10/2022, 4:37:28 PM 	M591 D0
Duet3D rotating magnet filament monitor v3 on pin 121.io1.in, enabled, sensitivity 28.80mm/rev, allow 35% to 130%, check printing moves every 20.0mm, version 3, mag 129 agc 85, measured sensitivity 24.74mm/rev, min 98% max 103% over 33743.9mm

Phaedrux

@charliedrums You've kind of taken over someone else's thread. To keep things clear can you please create a new thread with your issue?

charliedrums

@phaedrux Sure thing will do Sorry about that.

Phaedrux

@charliedrums said in RRF3.4 RC2 Filament/sensor error:

@phaedrux Sure thing will do Sorry about that.

No problem. I'd be curious to know if your issue also goes away when going back to fw 3.3

charliedrums

@phaedrux

I made a thread on the issue.

Once this 17 hour print finishes I have a 20 hour print I have to do after this one. I can downgrade to 3.3 and see if it finishes without any problem but If you could point me in the right direction on how to downgrade I'd appreciate it. Also would I have to downgrade the tool board (1lc) as well?

BoA

Catched again. This time I executed M122 and M591 D0 before resuming the print.

11.03.2022, 19:21:28 	M24
Printing resumed

11.03.2022, 19:21:21 	M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0rc2 (2022-02-22 17:04:17) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956L2-G43S8-6J1D6-3SJ6R-KA0YG
Used output buffers: 1 of 40 (40 max)
=== RTOS ===
Static ram: 150984
Dynamic ram: 98404 of which 0 recycled
Never used RAM 81364, free system stack 116 words
Tasks: NETWORK(ready,26.6%,199) ETHERNET(notifyWait,1.6%,166) HEAT(notifyWait,2.0%,321) Move(notifyWait,50.4%,243) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,355) CanClock(delaying,0.4%,333) TMC(notifyWait,89.7%,58) MAIN(running,47.4%,967) IDLE(ready,0.1%,30), total 218.2%
Owned mutexes:
=== Platform ===
Last reset 49:04:02 ago, cause: software
Last software reset time unknown, reason: User, GCodes spinning, available RAM 85132, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,1,0
Step timer max interval 184
MCU temperature: min 36.9, current 47.2, max 48.9
Supply voltage: min 12.2, current 27.2, max 27.5, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 11.4, current 12.2, max 12.5, under voltage events: 0
Heap OK, handles allocated/used 99/6, heap memory allocated/used/recyclable 2048/1440/1260, gc cycles 0
Events: 2 queued, 2 completed
Driver 0: pos 0, standstill, SG min 0, mspos 296, reads 27362, writes 179 timeouts 0
Driver 1: pos 40000, standstill, SG min 0, mspos 408, reads 27360, writes 181 timeouts 0
Driver 2: pos 5685, standstill, SG min 0, mspos 600, reads 27471, writes 70 timeouts 0
Driver 3: pos 0, standstill, SG min 0, mspos 8, reads 27525, writes 16 timeouts 0
Driver 4: pos 0, standstill, SG min 0, mspos 72, reads 27407, writes 134 timeouts 0
Driver 5: pos 0, standstill, SG min 0, mspos 904, reads 27408, writes 134 timeouts 0
Date/time: 2022-03-11 19:21:12
Slowest loop: 79.06ms; fastest: 0.05ms
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 5.0ms, write time 131.1ms, max retries 0
=== Move ===
DMs created 125, segments created 31, maxWait 8354511ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 254484, completed 254484, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 3], 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 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters 3 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.2
Heater 1 is on, I-accum = 0.6
Heater 3 is on, I-accum = 0.0
=== 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 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
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 161.72, errs: frame 12 parity 0 ovrun 0 pol 0 ovdue 0
Extruder 1: pos 0.00, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
=== CAN ===
Messages queued 1589784, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 883214/0/0
Tx timeouts 0,0,883213,0,0,706569 last cancelled message type 4514 dest 127
=== Network ===
Slowest loop: 131.55ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- Ethernet -
State: active
Error counts: 0 0 1 0 0
Socket states: 5 2 2 2 2 2 0 0

11.03.2022, 19:21:14 	M591 D0
Duet3D rotating magnet filament monitor v3 on pin io5.in, enabled, sensitivity 25.40mm/rev, allow 50% to 150%, check printing moves every 12.7mm, version 3, mag 131 agc 64, measured sensitivity 25.91mm/rev, min 94% max 107% over 26367.4mm

11.03.2022, 19:11:29 	Resume state saved

11.03.2022, 19:11:27 	Error: Filament error on extruder 0: sensorError

Phaedrux

@boa How do you have your cabling run?

Our best guess is that interference is corrupting the signal from the MFM and that RRF 3.3 wasn't very good at reporting that type of error.

BoA

@phaedrux
Blue path is filament sensor wiring - about 50cm long
Red are motors and heaters

Phaedrux

Well that path seems pretty clear from other cabling.

Is sensor error the only error that you get?

BoA

@phaedrux Yes. That is the only error. If there is a way to enable some debug logging I can do that to get more info.

And... probably not related completly, but I noticed that my stop.g causes chamber heater to go into active state, which was not the case with 3.3

stop.g:

T-1
M104 S0 T0
M104 S0 T1
M140 S0 R0
M141 S0 R0 ; disable chamber heater
M144 S0 ; put heatbed on standby

M106 P0 S0
M220 S100
M221 S100 D0
M221 S100 D1

M84
M300 P300

Phaedrux

@boa said in RRF3.4 RC2 Filament/sensor error:

                                                                                                                            T-1                                                                                                                                                                            M104 S0 T0                                                                                                                                                                            M104 S0 T1                                                                                                                                                                            M140 S0 R0                                                                                                                                                                            M141 S0 R0 ; disable chamber heater                                                                                                                                                                            M144 S0 ; put heatbed on standby

If you send those commands manually does it behave the same with with the chamber heater? And is it active state with 0 temperature?