Duet 3 + Tool board stops mid-print and reports 100% complete

evomotors

9/6/2020, 4:14:49 PM	M122 B121
Diagnostics for board 121:
Board TOOL1LC firmware 3.1.0 (2020-05-15b1)
Never used RAM 8.5Kb, max stack 584b
HEAT 1048 CanAsync 1392 CanRecv 1380 TMC 188 AIN 524 MAIN 2308
Last reset 00:14:50 ago, cause: power up
Driver 0: standstill, SG min/max 0/20, read errors 0, write errors 0, ifcount 13, reads 49738, writes 13, timeouts 1, DMA errors 0, failedOp 0x80
Moves scheduled 25, completed 25, hiccups 0
VIN: 24.2V
MCU temperature: min 48.6C, current 62.2C, max 62.3C
Ticks since heat task active 174, ADC conversions started 889143, completed 889142, timed out 0
Last sensors broadcast 00000002 found 1 177 ticks ago
Free CAN buffers: 36
NVM user row b1d088a9 fffff8bb 20002a18 b
TSENS 001847 GAIN 014ffc OFFS 00273f CAL 1f2a
9/6/2020, 4:14:32 PM	M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956L2-G43S8-6JKDL-3SJ6L-1802G
Used output buffers: 1 of 40 (11 max)
=== RTOS ===
Static ram: 154604
Dynamic ram: 162928 of which 60 recycled
Exception stack ram used: 520
Never used ram: 75104
Tasks: NETWORK(ready,1972) HEAT(blocked,1188) CanReceiv(suspended,3388) CanSender(suspended,1428) CanClock(blocked,1436) TMC(blocked,68) MAIN(running,2672) IDLE(ready,76)
Owned mutexes:
=== Platform ===
Last reset 00:14:33 ago, cause: power up
Last software reset at 2020-09-06 20:50, reason: User, spinning module LinuxInterface, available RAM 75624 bytes (slot 1)
Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 38.0, current 43.6, max 43.7
Supply voltage: min 23.8, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.2, max 12.3, under voltage events: 0
Driver 0: standstill, reads 2465, writes 20 timeouts 0, SG min/max 0/420
Driver 1: standstill, reads 2465, writes 20 timeouts 0, SG min/max 0/1015
Driver 2: standstill, reads 2466, writes 20 timeouts 0, SG min/max 0/1013
Driver 3: standstill, reads 2466, writes 20 timeouts 0, SG min/max 0/999
Driver 4: standstill, reads 2466, writes 20 timeouts 0, SG min/max 0/1005
Driver 5: standstill, reads 2467, writes 20 timeouts 0, SG min/max 0/492
Date/time: 2020-09-06 21:14:31
Slowest loop: 8.49ms; fastest: 0.13ms
=== 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 ===
Hiccups: 0(0), FreeDm: 375, MinFreeDm: 367, MaxWait: 416505ms
Bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 482, completed moves: 482, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is ready with "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.
=== Network ===
Slowest loop: 0.83ms; fastest: 0.01ms
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: 0 of 8
- Ethernet -
State: disabled
Error counts: 0 0 0 0 0
Socket states: 0 0 0 0 0 0 0 0
=== CAN ===
Messages sent 4528, longest wait 3ms for type 6012
=== Linux interface ===
State: 0, failed transfers: 0
Last transfer: 23ms ago
RX/TX seq numbers: 25913/25914
SPI underruns 0, overruns 0
Number of disconnects: 1
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.1.1
File:
Buffered code: G1 X247.109 Y320.100 E11.7503
Buffered code: G1 X245.109 Y318.100 E11.8378
Buffered code: G1 X178.109 Y318.100 E13.9103
Buffered code: G1 X171.900 Y311.891 E14.1819
Buffered code: G1 X171.900 Y268.888 E15.5120
Buffered code: G1 X168.904 Y265.893 E15.6431
Buffered code: G1 X168.899 Y249.127 E16.1617
Buffered code: G1 X171.900 Y246.117 E16.2932
Buffered code: G1 X171.900 Y203.109 E17.6235
Buffered code: G1 X178.109 Y196.900 E17.8951
Buffered code: G1 X178.275 Y197.300 F18000
Buffered code: G92 E0.0000
Buffered code: G1 X245.275 Y197.300 E2.0724 F1800
Buffered code: G1 X247.275 Y195.300 E2.1599
Buffered code: G1 X267.725 Y195.300 E2.7925
Buffered code: G1 X269.725 Y197.300 E2.8800
Buffered code: G1 X336.725 Y197.300 E4.9524
Buffered code: G1 X342.700 Y203.275 E5.2138
Buffered code: G1 X342.700 Y246.275 E6.5439
Buffered code: G1 X345.700 Y249.275 E6.6751
Buffered code: G1 X345.700 Y265.725 E7.1839
Buffered code: G1 X342.700 Y268.725 E7.3152
Buffered code: G1 X342.700 Y311.725 E8.6452
Buffered code: G1 X336.725 Y317.700 E8.9066
Buffered code: G1 X269.725 Y317.700 E10.9790
Buffered code: G1 X267.725 Y319.700 E11.0665
Buffered code: G1 X247.275 Y319.700 E11.6991
Buffered code: G1 X245.275 Y317.700 E11.7866
Buffered code: G1 X178.275 Y317.700 E13.8590
Buffered code: G1 X172.300 Y311.725 E14.1204
Buffered code: G1 X172.300 Y268.722 E15.4505
Buffered code: G1 X169.304 Y265.727 E15.5816
==> 1524 bytes
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 15.00
File /opt/dsf/sd/gcodes/test-fixed.gcode is selected, processing

Phaedrux

Can you provide the M122 for the mainboard as well?

And can you try enabling the debug mode?

https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Monitoring_optional

Does this happen with every print?

Can you share the gcode file as well?

evomotors

@Phaedrux said in Duet 3 + Tool board stops mid-print and reports 100% complete:

Can you provide the M122 for the mainboard as well?

M122 is for both, main board starts at line 17

evomotors

@evomotors said in Duet 3 + Tool board stops mid-print and reports 100% complete:

@Phaedrux said in Duet 3 + Tool board stops mid-print and reports 100% complete:

Can you provide the M122 for the mainboard as well?

M122 is for both, main board starts at line 17

It doesn't happens on every print, the same gcode file did work when I started printing again from the beginning. It happened to me 3 or 4 times since I upgraded to Duet board few weeks ago.

I will enable diagnostics