Commissioning a new Duet3 H6C board
-
Well folks, it is official, I should not be let loose on a Duet printer.
I tried another SD card, a known good card, which gave me the exact same results. This card had good test results with M122. I could ping the machine without any issues but no dice on the web page.
After a lot of head scratching, it finally dawned on me - by default I restrict what can and can not happen on my web browser. It is fairly restricted and a lot of sites do not load without me specifically telling NoScript to allow the web site. All my in-use ip addresses are white listed. Well I have never used that particular IP address so it was still being locked down
Once white listed, it loaded absolutely fine ..... GRRRRRRR ...... That's probably 6 hrs I will never get back again!So, it boils down to operator problems although I still consider the SD card defective.
As mentioned, the card contains two partitions, one that is used if the printer is direct connected and one partition that is used if the printer is connected via a pi.I would like to repeat my request for a link to an image file that I can use to recreate the original SD card as it is shipped. I would be using Balena Etcher to burn the card.
For completeness, here is the output of M122:
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2.2 running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-9P63L-DJ3T0-6J9F0-3SN6L-TU37A
Used output buffers: 1 of 40 (16 max)
=== RTOS ===
Static ram: 149788
Dynamic ram: 92060 of which 624 recycled
Never used RAM 116360, free system stack 184 words
Tasks: NETWORK(ready,193) ETHERNET(blocked,110) HEAT(blocked,356) CanReceiv(blocked,927) CanSender(blocked,371) CanClock(blocked,352) TMC(blocked,51) MAIN(running,1105) IDLE(ready,19)
Owned mutexes:
=== Platform ===
Last reset 00:23:15 ago, cause: power up
Last software reset details not available
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 18.1, current 32.6, max 32.7
Supply voltage: min 23.8, current 23.8, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
Driver 0: position 0, standstill, reads 39964, writes 14 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 39965, writes 14 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 39965, writes 14 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 39968, writes 11 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 39968, writes 11 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 39969, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2021-06-28 08:02:17
Slowest loop: 20.36ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 3.3ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, 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 = -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: 20.53ms; fastest: 0.02ms
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 1 0 0
Socket states: 5 2 2 2 2 0 0 0
=== CAN ===
Messages queued 0, send timeouts 6975, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 48
The output from M122 P104 is
SD read speed for 10.0Mbyte file was 0.70Mbytes/sec
SD write speed for 10.0Mbyte file was 0.56Mbytes/secPlease note that the printer is NOT configured correctly so some of the M122 results may be odd.
- Ethernet -
-
So you need to use an SBC right now?
Did you see this:
https://duet3d.dozuki.com/Wiki/SBC_Setup_for_Duet_3
Frederick
-
@fcwilt, no I am configured as a direct connected board and not using the pi for the moment. Less to screw up
-
@jens55 said in Commissioning a new Duet3 H6C board:
@fcwilt, no I am configured as a direct connected board and not using the pi for the moment. Less to screw up
Well then you don't need to worry about creating an SD card with the two partitions.
For "standalone" SD mode you only need a FAT32 formatted SD card and the files mentioned here:
https://duet3d.dozuki.com/Wiki/SD_Card
Frederick
-
@fcwilt said in Commissioning a new Duet3 H6C board:
So you need to use an SBC right now?
Did you see this:
https://duet3d.dozuki.com/Wiki/SBC_Setup_for_Duet_3
Frederick
While I have gone through this wiki several times, I did not consider the possibility of that file having both partions on it. I downloaded the img file and it looks like I might have screwed up that one as well. I will give a try and write the image file later today and see what I get.
Thanks !!
-
@fcwilt said in Commissioning a new Duet3 H6C board:
Well then you don't need to worry about creating an SD card with the two partitions.
I want the card to cover both configurations - the same way as it is shipped originally
-
@jens55 said in Commissioning a new Duet3 H6C board:
@fcwilt said in Commissioning a new Duet3 H6C board:
Well then you don't need to worry about creating an SD card with the two partitions.
I want the card to cover both configurations - the same way as it is shipped originally
Hmm...
I just loaded the SD card I used with the SBC and it only has one partition on it.
Can you even use one card in both modes?
If so what would be the benefit?
Thanks.
Frederick
-
@fcwilt, yes, the currently shipping SD card can be used for both modes, stand-alone and SBC mode.
Remember I mentioned to you that a windows computer might not show you both partitions .....The benefit of course is simplicity, you don't need to be concerned which mode the card is for. If you run stand-alone and a pi falls into your lap, you can just connect it, pull the SD card out of the Duet and stick it into the pi. I am not sure if the customization of one mode is also carried over to the other mode so while one card may be used for both modes, you might have to re-do the configuration when you switch modes.
-
Well there must be a way to create both partitions and place the needed file in each partition.
I downloaded the Raspberry Pi Imager so will get to see what that allows.
Frederick
-
@fcwilt, as it turns out, the image file you pointed out to me does indeed provide for both partitions. Just burned it, installed it and it pops right up like one would expect it to.
Perfect!!!Thanks again!