Duet Maestro 2 stops mid print
-
@dc42 Thank you for the assistance. How can I know for sure. I tried doing a event log, but that did not complete. As if if did not write once the reset happened. What else can I try?
-
Is the Duet connected by USB to a PC? If so then see the wiki page on USB ground loops.
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 No - Only Ethernet.
-
@dc42 m122
=== Diagnostics ===
RepRapFirmware for Duet 2 Maestro version 2.05.1 running on Duet Maestro 1.0
Board ID: 08DJM-9X66L-LG3SN-6J1FD-3SJ6M-9BZAR
Used output buffers: 14 of 24 (15 max)
=== RTOS ===
Static ram: 19804
Dynamic ram: 87356 of which 0 recycled
Exception stack ram used: 300
Never used ram: 23612
Tasks: NETWORK(ready,764) HEAT(blocked,1296) MAIN(running,3896) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:01:35 ago, cause: reset button
Last software reset at 2020-03-30 11:00, reason: User, spinning module GCodes, available RAM 23612 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04427000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 15.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 37.3, current 37.6, max 37.6
Supply voltage: min 24.1, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, read errors 0, write errors 0, ifcount 21, reads 62, timeouts 0
Driver 1: standstill, read errors 0, write errors 0, ifcount 21, reads 62, timeouts 0
Driver 2: standstill, read errors 0, write errors 0, ifcount 21, reads 62, timeouts 0
Driver 3: standstill, read errors 0, write errors 0, ifcount 15, reads 62, timeouts 0
Driver 4: standstill, read errors 0, write errors 0, ifcount 13, reads 62, timeouts 0
Driver 5: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 62
Driver 6: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 62
Date/time: 2020-03-30 16:40:13
Slowest loop: 0.86ms; fastest: 0.06ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 7, completed moves: 7, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
lcd is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 3.40ms; fastest: 0.05ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 2 of 8
Interface state 5, link 100Mbps full duplex
Error: Could not flush remaining data while finishing upload
Error: Uploaded file size is different (0 vs. expected 1112 bytes)
Error: Could not flush remaining data while finishing upload
Error: Uploaded file size is different (0 vs. expeError: Could not flush remaining data while finishing upload
Error: Uploaded file size is different (0 vs. expected 1112 bytes) -
I see the last reset was done by a reset button- What does that mean?
-
And.. The diag light stays on. Using a BL Touch
-
@dc42 Tasks: NETWORK(ready,900) HEAT(blocked,1296) MAIN(running,3896) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:00:55 ago, cause: software
Last software reset time unknown, reason: User, spinning module GCodes, available RAM 23804 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0400f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d -
Lets try again - I'm posting 2 M122 Diagnostic files.
The first one, was done a few seconds before the machine stopped, the 2nd one right after.. Lets hope you can make something from this..
------------------------------------------FIRST------------------------------------------------------
01/04/2020, 09:20:50: M122: === Diagnostics ===
RepRapFirmware for Duet 2 Maestro version 3.01-RC5 running on Duet Maestro 1.0
Board ID: 08DJM-9X66L-LG3SN-6J1FD-3SJ6M-9BZAR
Used output buffers: 1 of 24 (17 max)
=== RTOS ===
Static ram: 22012
Dynamic ram: 88460 of which 20 recycled
Exception stack ram used: 368
Never used ram: 20212
Tasks: NETWORK(ready,976) HEAT(blocked,1328) MAIN(running,2020) IDLE(ready,84)
Owned mutexes:
=== Platform ===
Last reset 00:11:01 ago, cause: power up
Last software reset at 2020-04-01 07:25, reason: User, spinning module GCodes, available RAM 20632 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0400f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 9
SD card 0 detected, interface speed: 15.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 37.0, current 37.6, max 37.8
Supply voltage: min 23.9, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: ok, read errors 0, write errors 0, ifcount 12, reads 974, timeouts 0
Driver 1: ok, read errors 0, write errors 0, ifcount 12, reads 974, timeouts 0
Driver 2: standstill, read errors 0, write errors 0, ifcount 12, reads 974, timeouts 0
Driver 3: ok, read errors 0, write errors 0, ifcount 8, reads 974, timeouts 0
Driver 4: standstill, read errors 0, write errors 0, ifcount 6, reads 974, timeouts 0
Driver 5: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 973
Driver 6: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 974
Date/time: 2020-04-01 09:20:49
Slowest loop: 3.29ms; fastest: 0.12ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0(0), FreeDm: 166, MinFreeDm: 158, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 3938, completed moves: 3917, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: 3
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = 0 -1, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.1
Heater 1 is on, I-accum = 0.3
=== 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 X-4.045 Y5.452 E2.82853" 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: 4.93ms; fastest: 0.04ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex------------------------------------------2nd ------------------------------------------------------
01/04/2020, 09:21:21: M122: === Diagnostics ===
RepRapFirmware for Duet 2 Maestro version 3.01-RC5 running on Duet Maestro 1.0
Board ID: 08DJM-9X66L-LG3SN-6J1FD-3SJ6M-9BZAR
Used output buffers: 3 of 24 (6 max)
=== RTOS ===
Static ram: 22012
Dynamic ram: 88260 of which 20 recycled
Exception stack ram used: 204
Never used ram: 20576
Tasks: NETWORK(ready,976) HEAT(blocked,1360) MAIN(running,2020) IDLE(ready,84)
Owned mutexes:
=== Platform ===
Last reset 00:00:28 ago, cause: reset button
Last software reset at 2020-04-01 07:25, reason: User, spinning module GCodes, available RAM 20632 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0400f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 15.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 37.1, current 37.4, max 37.9
Supply voltage: min 0.0, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, read errors 0, write errors 1, ifcount 19, reads 1145, timeouts 0
Driver 1: standstill, read errors 0, write errors 1, ifcount 19, reads 1145, timeouts 0
Driver 2: standstill, read errors 0, write errors 1, ifcount 19, reads 1145, timeouts 0
Driver 3: standstill, read errors 0, write errors 1, ifcount 15, reads 1145, timeouts 0
Driver 4: standstill, read errors 0, write errors 1, ifcount 13, reads 1145, timeouts 0
Driver 5: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 1151
Driver 6: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 1151
Date/time: 1970-01-01 00:00:00
Slowest loop: 3.25ms; fastest: 0.11ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, 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, chamberHeaters = -1 -1
=== 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: 104.32ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex -
@dc42 I've uploaded 2 M122 files above. Please see if you can spot an issue. This is very frustrating.
-
Presumably you haven't pressed the reset button, maybe some pictures showing the mounting of the board and wires that are run near the reset swtich can help dc42 in his investigation. Understandably its a difficult issue to diagnose.
-
I know it is rough, but is a work in progress...
-
One more thing I've noticed, not sure if it is an issue... The prints look wrong before the reset... Infill looks wacked!
-
@bearer Nope. Not touching the reset button. I did read on the forum that some of them Maestro Reset buttons do get stuck. I did try to release it a bit with tweezers. I must say the reset button is VERY stiff. But not convinced that the button is the problem as yet.. That is why I'm asking.. If that error can only be generated by the button, then I guess it is time for shipping a new board, as this one is new.
-
@massynrt said in Duet Maestro 2 stops mid print:
If that error can only be generated by the button
Afaik, it is, but lets defer to dc42 on that one; with the pictures I'm sure he'll have a clearer idea of what could possibly affect it but to the untrained eye it doesn't look like mechanical forces or electrical noise should be a likely culprit.
-
@massynrt what PSU are you using? Is the wiring firmly connected to the Duet screw terminals? Also, when and where did you purchase the Duet? Warranty is 6 months, so if recent, that’s fine. You’ll need to follow the warranty procedure of the place you bought it from, which usually involves getting an okay from me, dc42 or Phaedrux here on the forum. But before that, let’s see what dc42 says about the M122 reports.
Ian
-
I use a Mean Well 450w 24v PSU. Yes the connectors are secure. The heat bed is 220v with a SSR. Thus no load on PSU..
I bough it on the 02/03/2020 directly for your website. Order no: 7975.
Problem is I was forced to buy it from you directly as the local distributor informed me that they won't stock Duet anymore. Thus to ship back, and pay shipment and import duties again will just make this very expensive.
-
@massynrt okay, thanks. Let’s try and resolve the problem without shipping it back! Out of interest, who is your local distributor?
Ian
-
Da Vincy Lab.. I see they do have Maestros in stock according to there website. I think my query was for a Duet 3, and I just assumed it was for the Maestro also. And the fact that you had the Maestro on discount, which was not the case in South Africa.
-
If you guys come to the conclusion that the switch can be faulty ... if it were my board and the alternative was to pay shipping and taxes I'd be inclined to remove the switch; but lets not get ahead of ourselves.
-
@bearer i'm all for removing the switch.. But dont want to do somehthing that can damage my warranty (for now)
