@droftarts said in Duet 3 Extruder control disabled:
@Ralms said in Duet 3 Extruder control disabled:
Hm, ok, quick question, I don't have yet a Raspberry Pi to control the Duet.
How straight forward / safe is it to do when using the duet directly over the network?
Should be fine. You should be able to upload the Duet2and3Firmware-3.1.1.zip
file in DWC from https://github.com/Duet3D/RepRapFirmware/releases/tag/3.1.1 to update firmware and DWC at the same time. 3.1.1 is a very stable release, but do read the update notes.
Ian
Man, this was stressfull...
Ok after trying 3 times to upgrade the firmware, it eventually did it successfully.
First, Bossa got stuck saying "Writing Page 0 (0%)".
I've waited around 5 mins and nothing, so I decided to stop it.
Turn everything back off, turn back on, then Bossa didn't want to write, then was crashing....
Eventually, restarted Bossa, reselected everything including the bin file.
Tried to do "Read", which it did. So I was like: Ok, lets try to Write then and Verify.
Bossa Wrote the firmware and verify was successfully, however I noticed that the .bin file had it's Modified Date changed and was significantly bigger.
Try to boot the Duet and nothing, stuck in Diag mode.
Ok, lets do this a third time.
Download the firmware again.
Erase everything, connect the USB cable, click Reset, Duet connected to the PC.
Restart Bossa, Select the COM port, new download firmware file, tick the boxes, Write, Verify, success.
Press Reset and Duet booted.
Takeaways from this:
The documentation for the Duet 3 on this part could be a bit better, in terms of what is the expected behaviors.
Also, please make it more clear that you have to have the duet PSU on while doing this, initially I wasn't sure.
And add a note saying that if you Read, it will overwrite the file you have selected in "Browse", Bossa is not very clear on this.
Moving forward:
I can't find any information on how to update the Duet Web Control and I'm still in 2.1.0.
Can anyone provide a link on how to do it?
I assume I will have to do it with an micro SD card reader which I have, just would like to know the steps to achieve it.
Thanks,
Ralms.
P.S.: Here is my updated M122 command output:
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956L2-G43S8-6JKDJ-3S46K-9S2YD
Used output buffers: 2 of 40 (11 max)
=== RTOS ===
Static ram: 154604
Dynamic ram: 161152 of which 20 recycled
Exception stack ram used: 296
Never used ram: 77144
Tasks: NETWORK(ready,364) ETHERNET(blocked,436) HEAT(blocked,1416) CanReceiv(suspended,3820) CanSender(suspended,1488) CanClock(blocked,1424) TMC(blocked,204) MAIN(running,5368) IDLE(ready,76)
Owned mutexes:
=== Platform ===
Last reset 00:00:30 ago, cause: power up
Last software reset time unknown, reason: User, spinning module GCodes, available RAM 76324 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 21.7, current 26.8, max 26.8
Supply voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 11.2, current 11.3, max 11.3, under voltage events: 0
Driver 0: standstill, reads 19049, writes 11 timeouts 0, SG min/max 0/0
Driver 1: standstill, reads 19050, writes 11 timeouts 0, SG min/max 0/0
Driver 2: standstill, reads 19050, writes 11 timeouts 0, SG min/max 0/0
Driver 3: standstill, reads 19051, writes 11 timeouts 0, SG min/max 0/0
Driver 4: standstill, reads 19052, writes 11 timeouts 0, SG min/max 0/0
Driver 5: standstill, reads 19052, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2020-08-10 20:32:37
Slowest loop: 5.14ms; fastest: 0.14ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.4ms, 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 = -1 -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.53ms; 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 0, longest wait 0ms for type 0
=== Linux interface ===
State: 0, failed transfers: 0
Last transfer: 30662ms ago
RX/TX seq numbers: 0/1
SPI underruns 0, overruns 0
Number of disconnects: 0
Buffer RX/TX: 0/0-0