Why did my print pause?

alankilian

I don't understand why my print paused.
The reading from the filament monitor doesn't show anything out of range.

Any ideas or anything I should grab next time it does this?

3/1/2021, 12:13:38 PM 	m115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.2 ELECTRONICS: Duet Ethernet 1.02 or later FIRMWARE_DATE: 2021-01-05
3/1/2021, 12:12:55 PM 	M24
Printing resumed
3/1/2021, 12:12:30 PM 	m591 d0
Duet3D rotating magnet filament monitor v3 with switch on pin e0stop, enabled, sensitivity 27.00mm/rev, allow 10% to 200%, check every 20.0mm, version 3, mag 130 agc 114, measured sensitivity 28.00mm/rev, min 55% max 104% over 5461.2mm
3/1/2021, 11:43:48 AM 	Printing paused at X36.9 Y-4.2 Z0.6
3/1/2021, 11:43:45 AM 	Resume state saved
3/1/2021, 11:03:18 AM 	M32 "0:/gcodes/Divider_12.gcode"
File 0:/gcodes/Divider_12.gcode selected for printing

alankilian

What causes NEGATIVE extrusion amounts to be measured?

Extruder 0 reported 'tooLittleMovement'

m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2 running on Duet Ethernet 1.02 or later
Board ID: 08DGM-95BLL-N6PSS-6JKD2-3S46Q-1JSRL
Used output buffers: 3 of 24 (20 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 68540 of which 60 recycled
Never used RAM 20020, free system stack 108 words
Tasks: NETWORK(ready,177) HEAT(blocked,309) MAIN(running,452) IDLE(ready,19)
Owned mutexes:
=== Platform ===
Last reset 02:34:18 ago, cause: software
Last software reset at 2021-03-01 12:14, reason: User, GCodes spinning, available RAM 19920, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 22.5, current 23.9, max 24.5
Supply voltage: min 12.7, current 12.9, max 13.2, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 25961, standstill, SG min/max 0/557
Driver 1: position 25961, standstill, SG min/max 0/534
Driver 2: position 25961, standstill, SG min/max 0/546
Driver 3: position 0, standstill, SG min/max 0/341
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-03-01 14:48:25
Cache data hit count 4294967295
Slowest loop: 73.64ms; fastest: 0.10ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 2.1ms, write time 4.9ms, max retries 0
=== Move ===
DMs created 83, maxWait 917775ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 7394, completed moves 7394, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.7
Heater 1 is on, I-accum = 0.7
=== 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 14.69ms; fastest: 0.07ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex
=== Filament sensors ===
Extruder 0: pos 46.41, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0

M591 D0
Duet3D rotating magnet filament monitor v3 with switch on pin e0stop, enabled, sensitivity 27.00mm/rev, allow 10% to 200%, check every 20.0mm, version 3, mag 130 agc 114, measured sensitivity 27.59mm/rev, min -1% max 103% over 5622.2mm

alankilian

ARGH!!!!!

Nevermind.

The damn filament end is stuck in the spool.

This darn MatterHackers filament has a giant hook on it so it doesn't let go of the spool and sometimes I forget to get in there with a knife and cut it off.

alankilian

By the way, this is EXACTLY why I bought this in the first place.

The MatterHackers MHBuild series filament just gets stuck to the spool at the end and didn't trigger my filament runout switch, so this was a COMPLETE success for the filament motion sensor.

T3P3Tony

Glad to hear it!