It was disconnected pin, I got hung up with short to ground error and was focusing on trying to find a short. Looks like on the side closest to the fuses one or more pins weren't connected, I did skimp a bit on the heat on that edge due to proximity of other components so ran a dry soldering iron over each pin and back to life now with all drivers working again. Many thanks.
Posts made by Via
-
RE: Have I totally killed it? - Duet2 stepper replacement
-
Have I totally killed it? - Duet2 stepper replacement
I previously destroyed Z stepper driver on my Duet2 due to own stupidity (mixed phases, let the smoke out and reports over temperature / short to ground).
This board has since been replaced so thought I would try repairing myself. So I cracked out the reflow station and after a short while old driver was removed and new driver installed. Visually apart from a bit of a scorch to plastic for plugs everything looks good.
However I still get over temperature / short to ground error coming up from driver 2 but now on top of this none of the other drivers work all reporting phase A/B may be disconnected.
Is it totally dead? As mentioned visually I cannot see any issues even under magnifying glass all pins look lined up perfectly and no shorts to neighbouring pin (except intended pairs).
As mentioned not crucial as I have replaced but would be nice to have a spare for another project.
-
RE: Reset during print Part 2 - Duet 3.1.1 / 3.2beta3 - Duet3+SBC
@dc42 received replacement board from E3D today and working as expected in standalone, will get round to putting SBC back in this week but happy there shouldn't be any further issues.
Thank's again to yourself and @chrishamm for the help
-
RE: Reset during print Part 2 - Duet 3.1.1 / 3.2beta3 - Duet3+SBC
@dc42 MCU was over reading by ~2C so adjusted to compensate and showing ~35C now.
Installed new firmware and...
30/11/2020, 13:26:02 Finished printing file 0:/gcodes/[PLA] CFFFP_Top - ReRender - zero temps.gcode, print time was 1h 41m
So looked promising so without changing anything I reran print to make sure it was not a fluke and sure enough it was ...
=== Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.2-beta4+4 running on Duet 3 MB6HC v0.6 or 1.0 (standalone mode) Board ID: 08DJM-956L2-G43S4-6J9FA-3S86T-1B5LD Used output buffers: 1 of 40 (12 max) === RTOS === Static ram: 123212 Dynamic ram: 168584 of which 704 recycled Never used RAM 99692, free system stack 122 words Tasks: NETWORK(ready,165) ETHERNET(blocked,105) HEAT(blocked,297) CanReceiv(blocked,947) CanSender(blocked,352) CanClock(blocked,349) TMC(blocked,20) MAIN(running,1113) IDLE(ready,19) Owned mutexes: === Platform === Last reset 00:12:51 ago, cause: software Last software reset at 2020-11-30 14:18, reason: MemoryProtectionFault mmarValid daccViol, Move spinning, available RAM 99692, slot 1 Software reset code 0x4164 HFSR 0x00000000 CFSR 0x00000082 ICSR 0x00427004 BFAR 0xb6d799a8 SP 0x2045ff58 Task MAIN Stack: 00000060 000000c0 00000091 96969694 00000001 00468c29 00469614 8100000e 00455a21 0045f237 00000000 2040e064 a5000001 008e0d8e 2040e064 a5000001 00000000 00000001 204281fc 00469d17 0000a5c7 204103b4 2042820c 204281f0 204281fc 20428370 00000000 Error status: 0x00 MCU temperature: min 34.2, current 34.3, max 36.3 Supply voltage: min 23.9, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0 Driver 0: position -3200, standstill, reads 61020, writes 17 timeouts 0, SG min/max 0/156 Driver 1: position -800, standstill, reads 61021, writes 17 timeouts 0, SG min/max 0/319 Driver 2: position 2000, standstill, reads 61022, writes 17 timeouts 0, SG min/max 0/184 Driver 3: position 0, standstill, reads 61024, writes 17 timeouts 0, SG min/max 0/182 Driver 4: position 0, standstill, reads 61027, writes 14 timeouts 0, SG min/max 0/0 Driver 5: position 0, standstill, reads 61031, writes 11 timeouts 0, SG min/max 0/0 Date/time: 2020-11-30 14:31:40 Slowest loop: 12.11ms; fastest: 0.21ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 0.9ms, write time 0.0ms, max retries 0 === Move === FreeDm 375 (min 372), maxWait 727688ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 13, completed moves 13, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], 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 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -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 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: 12.92ms; fastest: 0.03ms 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 0 0 0 Socket states: 5 2 2 2 2 0 0 0 === CAN === Messages queued 3089, send timeouts 6944, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 47
-
RE: Reset during print Part 2 - Duet 3.1.1 / 3.2beta3 - Duet3+SBC
@dc42 Thank you, will get in touch with E3D. Many thanks for your help.
-
RE: Reset during print Part 2 - Duet 3.1.1 / 3.2beta3 - Duet3+SBC
@dc42 thanks for your time looking into this. Purchase was from E3D but I have just gone over the 6 months now (purchased 13th May), will you be able to authorise warranty replacement as reported prior?
-
RE: Reset during print Part 2 - Duet 3.1.1 / 3.2beta3 - Duet3+SBC
@dc42 Failed again on beta4 (M122 at bottom) they are posted already but will group together here.
[PLA] CFFFP_Top - ReRender - zero temps (1).gcode
full sys directory: https://www.viaraix.net/duet3-sys.zip
=== Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.2-beta4 running on Duet 3 MB6HC v0.6 or 1.0 (standalone mode) Board ID: 08DJM-956L2-G43S4-6J9FA-3S86T-1B5LD Used output buffers: 1 of 40 (11 max) === RTOS === Static ram: 123212 Dynamic ram: 168584 of which 704 recycled Never used RAM 99692, free system stack 188 words Tasks: NETWORK(ready,169) ETHERNET(blocked,110) HEAT(blocked,298) CanReceiv(blocked,947) CanSender(blocked,371) CanClock(blocked,358) TMC(blocked,54) MAIN(running,1113) IDLE(ready,19) Owned mutexes: === Platform === Last reset 00:00:19 ago, cause: software Last software reset at 2020-11-27 11:41, reason: MemoryProtectionFault mmarValid daccViol, GCodes spinning, available RAM 99692, slot 2 Software reset code 0x4163 HFSR 0x00000000 CFSR 0x00000082 ICSR 0x0044a804 BFAR 0x00000000 SP 0x204100c8 Task MAIN Stack: 00000002 ffffffff 00434a29 20410308 000002bc 00469483 0046a3c8 610f0000 2042565c 004691bf 2042565c 00000000 000002bb 0000000a 2042565c 204256c8 00000000 00000001 00000000 00468e53 204256c8 00000000 204256c8 004691bf 00000000 00000000 20425540 Error status: 0x00 MCU temperature: min 39.0, current 39.4, max 39.9 Supply voltage: min 23.9, current 24.0, max 24.0, 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 Driver 0: position 0, standstill, reads 32774, writes 14 timeouts 0, SG min/max 0/0 Driver 1: position 0, standstill, reads 32775, writes 14 timeouts 0, SG min/max 0/0 Driver 2: position 0, standstill, reads 32776, writes 14 timeouts 0, SG min/max 0/0 Driver 3: position 0, standstill, reads 32777, writes 14 timeouts 0, SG min/max 0/0 Driver 4: position 0, standstill, reads 32779, writes 14 timeouts 0, SG min/max 0/0 Driver 5: position 0, standstill, reads 32782, writes 11 timeouts 0, SG min/max 0/0 Date/time: 2020-11-27 11:41:21 Slowest loop: 6.06ms; fastest: 0.15ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 0.7ms, write time 0.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, 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, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 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, chamberHeaters = -1 -1 -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 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: 17.56ms; fastest: 0.03ms 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 0 0 0 Socket states: 5 2 2 2 2 0 0 0 === CAN === Messages queued 79, send timeouts 177, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 47
-
RE: Reset during print Part 2 - Duet 3.1.1 / 3.2beta3 - Duet3+SBC
@dc42 Thank you.
Config attached, not been changed from assertation failure (or from 3.1.1). No filament monitors.
-
RE: Reset during print Part 2 - Duet 3.1.1 / 3.2beta3 - Duet3+SBC
Simulation loop ran for 4 1/2 hours (~380 loops) with no issues.
Ripped 24V PSU out of another printer today and unplugged heaters and fans so just steppers and sensors plugged in and done another test print, again this did not complete.
This time M122 back to Memory Protection Fault
=== Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.2-beta3.2 running on Duet 3 MB6HC v0.6 or 1.0 (standalone mode) Board ID: 08DJM-956L2-G43S4-6J9FA-3S86T-1B5LD Used output buffers: 2 of 40 (11 max) === RTOS === Static ram: 122236 Dynamic ram: 168580 of which 376 recycled Never used RAM 101000, free system stack 200 words Tasks: NETWORK(ready,161) ETHERNET(blocked,109) HEAT(blocked,297) CanReceiv(blocked,948) CanSender(blocked,371) CanClock(blocked,356) TMC(blocked,54) MAIN(running,1111) IDLE(ready,19) Owned mutexes: === Platform === Last reset 00:00:20 ago, cause: software Last software reset at 2020-11-21 19:46, reason: MemoryProtectionFault mmarValid daccViol, Platform spinning, available RAM 101000, slot 1 Software reset code 0x4160 HFSR 0x00000000 CFSR 0x00000082 ICSR 0x00427804 BFAR 0x00038100 SP 0x2040aa78 Task TMC Stack: 00000001 2040a928 00000000 00410210 00000000 00469d0f 00415682 21000000 427a0001 3c800001 00000000 3d000001 00000000 00000000 37533333 43d697a0 00000000 41dde946 43fa0000 44a80000 2040ff38 00469d0f 00000000 40078000 20400020 00415681 0000001e Error status: 0x00 MCU temperature: min 39.2, current 39.9, max 40.0 Supply voltage: min 23.9, current 24.0, max 24.0, 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 Driver 0: position 0, standstill, reads 35967, writes 14 timeouts 0, SG min/max 0/0 Driver 1: position 0, standstill, reads 35968, writes 14 timeouts 0, SG min/max 0/0 Driver 2: position 0, standstill, reads 35969, writes 14 timeouts 0, SG min/max 0/0 Driver 3: position 0, standstill, reads 35970, writes 14 timeouts 0, SG min/max 0/0 Driver 4: position 0, standstill, reads 35971, writes 14 timeouts 0, SG min/max 0/0 Driver 5: position 0, standstill, reads 35975, writes 11 timeouts 0, SG min/max 0/0 Date/time: 2020-11-21 19:46:54 Slowest loop: 6.26ms; fastest: 0.15ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 0.8ms, write time 0.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, 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, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 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, chamberHeaters = -1 -1 -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 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: 5.46ms; fastest: 0.03ms 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 0 0 0 Socket states: 5 2 2 2 2 0 0 0 === CAN === Messages sent 82, send timeouts 82, longest wait 0ms for type 0, free CAN buffers 46
-
RE: Reset during print Part 2 - Duet 3.1.1 / 3.2beta3 - Duet3+SBC
@dc42 Stopped overthinking it and just added the M37/M23/M24 to the end of gcode which is looping properly now.
Has done ~130 loops with no issues in simulation.
-
RE: Reset during print Part 2 - Duet 3.1.1 / 3.2beta3 - Duet3+SBC
@dc42 I've ran the file as a normal simulation which completes fine.
Trying to do a macro to loop it but my gcode knowledge is terrible and keep freezing the board can you point me in right direction?
Was thinking this (I know never ending loops are bad in themselves but was just going to let it run until I reset it) but looks like it is just buffering all the M24s in one go how would I go about waiting for it to finish one before starting the next?
M37 S1 M23 "[PLA] CFFFP_Top - ReRender - zero temps.gcode" while true M24
-
RE: Reset during print Part 2 - Duet 3.1.1 / 3.2beta3 - Duet3+SBC
@dc42 Many thanks.
Is it worth trying with DuetPi Lite? Was going to try earlier but work got in the way
-
RE: Reset during print Part 2 - Duet 3.1.1 / 3.2beta3 - Duet3+SBC
@chrishamm No luck again on standalone with 3.2.0-beta3.2, this time "AssertionFailed"
I will have another try later with duetpi lite.
=== Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.2-beta3.2 running on Duet 3 MB6HC v0.6 or 1.0 (standalone mode) Board ID: 08DJM-956L2-G43S4-6J9FA-3S86T-1B5LD Used output buffers: 1 of 40 (11 max) === RTOS === Static ram: 122236 Dynamic ram: 168580 of which 376 recycled Never used RAM 101000, free system stack 180 words Tasks: NETWORK(ready,165) ETHERNET(blocked,109) HEAT(blocked,293) CanReceiv(blocked,948) CanSender(blocked,371) CanClock(blocked,358) TMC(blocked,54) MAIN(running,1111) IDLE(ready,19) Owned mutexes: === Platform === Last reset 00:00:28 ago, cause: software Last software reset at 2020-11-19 11:11, reason: AssertionFailed, GCodes spinning, available RAM 101000, slot 0 Software reset code 0x4123 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00427000 BFAR 0x00000000 SP 0x2040fd54 Task MAIN Stack: 00000599 004886b0 00468ce5 00000000 ffffffff 20427700 2040e2a0 20427ab0 ffffffff 00000000 56a3ba63 a5a5a5a5 00468d9b 2040fda4 00000000 20423aa8 004664d5 20427aa0 00440cc3 00000000 20427aa4 20408001 2040fdb4 00000101 00469700 0046972e 61000000 Error status: 0x00 MCU temperature: min 37.1, current 37.8, max 38.0 Supply voltage: min 13.0, current 13.0, max 13.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 Driver 0: position 0, standstill, reads 9148, writes 14 timeouts 0, SG min/max 0/0 Driver 1: position 0, standstill, reads 9149, writes 14 timeouts 0, SG min/max 0/0 Driver 2: position 0, standstill, reads 9151, writes 14 timeouts 0, SG min/max 0/0 Driver 3: position 0, standstill, reads 9152, writes 14 timeouts 0, SG min/max 0/0 Driver 4: position 0, standstill, reads 9153, writes 14 timeouts 0, SG min/max 0/0 Driver 5: position 0, standstill, reads 9157, writes 11 timeouts 0, SG min/max 0/0 Date/time: 2020-11-19 11:12:08 Slowest loop: 6.68ms; fastest: 0.21ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 1.2ms, write time 0.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, 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, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 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, chamberHeaters = -1 -1 -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 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: 11.39ms; fastest: 0.03ms 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 0 0 0 Socket states: 5 2 2 2 2 0 0 0 === CAN === Messages sent 113, send timeouts 113, longest wait 0ms for type 0, free CAN buffers 47
-
RE: Reset during print Part 2 - Duet 3.1.1 / 3.2beta3 - Duet3+SBC
@chrishamm Thanks for the update.
Would using the non-gui version of duetpi and forgoing connected screen work around this issue for the short term keeping SBC control?
Have updated standalone to 3.2.0-b3.2 and running test again now.
-
RE: Reset during print Part 2 - Duet 3.1.1 / 3.2beta3 - Duet3+SBC
I've put Duet3 into standalone now, retried print using 3.1.1 and print failed again. M122 shows Memory protection fault at time of failure.
=== Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v0.6 or 1.0 (standalone mode) Board ID: 08DJM-956L2-G43S4-6J9FA-3S86T-1B5LD Used output buffers: 1 of 40 (11 max) === RTOS === Static ram: 154604 Dynamic ram: 162852 of which 44 recycled Exception stack ram used: 272 Never used ram: 75444 Tasks: NETWORK(ready,364) ETHERNET(blocked,436) HEAT(blocked,1200) CanReceiv(suspended,3820) CanSender(suspended,1488) CanClock(blocked,1452) TMC(blocked,204) MAIN(running,4472) IDLE(ready,76) Owned mutexes: === Platform === Last reset 00:00:47 ago, cause: software Last software reset at 2020-11-18 11:53, reason: Memory protection fault, spinning module GCodes, available RAM 75108 bytes (slot 0) Software reset code 0x4163 HFSR 0x00000000 CFSR 0x00000001 ICSR 0x04427804 BFAR 0x00000000 SP 0x204175c4 Task MAIN Stack: 0000000a 0000000a 40070000 20417668 204176b9 00000015 00000000 0000000d 0046207b 00000052 20417630 Error status: 0 MCU temperature: min 37.2, current 37.4, max 38.0 Supply voltage: min 13.0, current 13.0, max 13.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 Driver 0: standstill, reads 38262, writes 14 timeouts 0, SG min/max 0/0 Driver 1: standstill, reads 38263, writes 14 timeouts 0, SG min/max 0/0 Driver 2: standstill, reads 38263, writes 14 timeouts 0, SG min/max 0/0 Driver 3: standstill, reads 38264, writes 14 timeouts 0, SG min/max 0/0 Driver 4: standstill, reads 38264, writes 14 timeouts 0, SG min/max 0/0 Driver 5: standstill, reads 38268, writes 11 timeouts 0, SG min/max 0/0 Date/time: 2020-11-18 11:54:07 Slowest loop: 6.14ms; fastest: 0.14ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 0.8ms, write time 0.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, 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 -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 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. === Network === Slowest loop: 9.70ms; fastest: 0.03ms 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 0 0 0 Socket states: 5 2 2 2 2 0 0 0 === CAN === Messages sent 190, longest wait 0ms for type 0 === Linux interface === State: 0, failed transfers: 0 Last transfer: 47750ms ago RX/TX seq numbers: 0/1 SPI underruns 0, overruns 0 Number of disconnects: 0 Buffer RX/TX: 0/0-0
-
RE: Duet 3 standalone not starting
@Phaedrux No
Added and needless to say it works now. Can I suggest the networking one being added to getting started. I presumed network would be always on.
Also the paneldue one to the paneldue bit on getting started as well, checked that to know to change wiring and what IO to use but was previously used on Duet2 with RRF2 so worked out of the box without any config.
-
RE: Duet 3 standalone not starting
@bearer YAT seems to stay connected to the port (which remains the same excluding switching to / from bossa). I have also tried putty which more annoyingly does disconnect but even with finger hovering over connect button for when I hit reset gives me nothing.
Speed is set as default at 9600 only change to YAT was changing end of line to <LF> as per Duet2 guide (https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7?lang) couldn't see any mention of speed on that (or I really am going blind!) but screenshot shows 9600.
(edit full settings) data bits: 8, parity: none, stop bits: 1, flow control: none
-
RE: Duet 3 standalone not starting
@bearer reset and totally powered off and back on. Board shows up as "USB Serial Device" not bossa.
-
RE: Duet 3 standalone not starting
Swear I am going blind firmware flashed and verified now...
Still does not see to be starting up though, powering on I get a flashing diag led, nothing on ethernet port / switch and paneldue still sits on connecting.
Should Duet3 output anything to serial port on boot like Duet2? Opening serial terminal and resetting board I get absolutely nothing through.