Thanks for the reply. Turns out it’s all working now with the new duet board! I expected the card to mount and run the runonce.g for the network settings. When it didn’t assumed same issue. However did some Googling and found that file doesn’t work (?) so programmed the network the usual way through YAT. Now all working perfectly.
Thanks for all the help. Now I have to tackle the layer shift problem it’s got. No successful prints yet. Does the duet need active cooling?
Just to draw a line under this, layer shift was a mechanical problem, nothing to do with Duet3D...which is simply, amazing. I will start another topic on quality of prints though - my 2014 ultimaker original seems to outperform the Duet with the same hardware, not sure if I can tune it out.
Just to draw a line under this, layer shift was a mechanical problem, nothing to do with Duet3D...which is simply, amazing. I will start another topic on quality of prints though - my 2014 ultimaker original seems to outperform the Duet with the same hardware, not sure if I can tune it out.
Thanks for the reply. Turns out it’s all working now with the new duet board! I expected the card to mount and run the runonce.g for the network settings. When it didn’t assumed same issue. However did some Googling and found that file doesn’t work (?) so programmed the network the usual way through YAT. Now all working perfectly.
Thanks for all the help. Now I have to tackle the layer shift problem it’s got. No successful prints yet. Does the duet need active cooling?
@dc42 said in SD card doesn't auto mount, Wifi module won't auto start:
M98 P"config.g"
Well, this is very frustrating. I've got a new SD card, and a replacement Duet wifi 2. I have exactly the same problem, the card is not mounting. Its not running config.g or the runonce.g, so the only way i can set a network up is through YAT manually. I am at a complete loss! The firmware was compiled using RFF config tool, correct version selected. Not sure what to do next?
Thanks for the help everyone.
I’ve tried reformatting a few times with no joy. Just ordered a new SD card so will give that a go tomorrow.
The duet I got second hand off eBay, so it’s quite possible it’s of the generation that suffers from the connection/soldering issue.
My suspicion is that it’s a hardware issue, but new card tomorrow will confirm hopefully.
Many thanks,
Anthony
This is what I get:
M39
SD card in slot 0: capacity 7.86GB, partition size 7.85GB, free space 7.83GB, speed 20.00MBytes/sec, cluster size 32kB
ok
No issues with the card in the laptop.
Cheers,
Anthony
; Configuration file for Duet WiFi (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.16 on Fri Apr 21 2023 15:21:05 GMT+0100 (BST)
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"My Printer" ; set printer name
; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet
; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S0 ; physical drive 1 goes backwards
M569 P2 S0 ; physical drive 2 goes backwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z200.00 E492.25 ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X10000.00 Y10000.00 Z1200.00 E3000.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X1200 Y1200 Z1200 E1250 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X210 Y210 Z205 S0 ; set axis maxima
; Endstops
M574 X1 S1 P"!xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin !xstop
M574 Y1 S1 P"!ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin !ystop
M574 Z1 S1 P"!zstop" ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin !zstop
; Z-Probe
M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed
M557 X15:210 Y15:195 S20 ; define mesh grid
; Heaters
M308 S0 P"spi.cs1" Y"rtd-max31865" ; configure sensor 0 as PT100 on pin spi.cs1
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 R0.267 K0.253:0.000 D2.42 E1.35 S1.00 B0 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"spi.cs2" Y"rtd-max31865" ; configure sensor 1 as PT100 on pin spi.cs2
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C
; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H1 T28 ; set fan 0 value. Thermostatic control is turned on
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H-1 ; set fan 1 value. Thermostatic control is turned off
M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
M106 P2 S1 H1 T45 ; set fan 2 value. Thermostatic control is turned on
; Tools
M563 P0 D0 H1 F0:1 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C
; Custom settings are not defined
; Miscellaneous
T0 ; select first tool
Hi,
Thanks for the reply. There are non M22 commands in the config.g; I used rrf config and not fettled it. If i use the suggested command (M98), it doesn't seem to stay mounted, still has errors if I try to upload a gcode file, or change the config.g and save in DWC. If i refresh DWC, error message saying no files on card. If I M21 in YAT, I can get back on.
Hi,
Fresh boot:
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917NK-F2MS4-7J9F6-3S06P-9YSSD
Used output buffers: 1 of 26 (1 max)
=== RTOS ===
Static ram: 23836
Dynamic ram: 74984 of which 12 recycled
Never used RAM 13248, free system stack 195 words
Tasks: NETWORK(ready,11.2%,380) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,363) MAIN(running,87.5%,423) IDLE(ready,1.3%,30), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:01:12 ago, cause: power up
Last software reset at 2023-04-20 22:29, reason: User, GCodes spinning, available RAM 13104, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 0
MCU temperature: min 13.1, current 18.1, max 18.5
Supply voltage: min 1.3, current 1.4, max 3.2, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok, SG min n/a
Driver 1: ok, SG min n/a
Driver 2: ok, SG min n/a
Driver 3: ok, SG min n/a
Driver 4: ok, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 1970-01-01 00:00:00
Cache data hit count 3016920628
Slowest loop: 300.17ms; fastest: 0.14ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 0.3ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== 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 ready with "M122" 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: 99.89ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
= WiFi =
Network state is disabled
WiFi module is disabled
Failed messages: pending 0, notready 0, noresp 3
Socket states: 0 0 0 0 0 0 0 0
ok
With the SD Mounted:
M21
T0:21.2 /0.0 B:19.9 /0.0
SDHC card mounted in slot 0, capacity 7.86Gb
ok
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917NK-F2MS4-7J9F6-3S06P-9YSSD
Used output buffers: 1 of 26 (11 max)
=== RTOS ===
Static ram: 23836
Dynamic ram: 74984 of which 12 recycled
Never used RAM 13248, free system stack 193 words
Tasks: NETWORK(ready,10.4%,380) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,363) MAIN(running,89.6%,420) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:02:57 ago, cause: power up
Last software reset at 2023-04-20 22:29, reason: User, GCodes spinning, available RAM 13104, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 0
MCU temperature: min 18.0, current 19.2, max 19.4
Supply voltage: min 1.3, current 1.4, max 1.4, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok, SG min n/a
Driver 1: ok, SG min n/a
Driver 2: ok, SG min n/a
Driver 3: ok, SG min n/a
Driver 4: ok, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 1970-01-01 00:00:00
Cache data hit count 4294967295
Slowest loop: 300.17ms; fastest: 0.14ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 0.3ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== 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 ready with "M122" 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: 1.02ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
= WiFi =
Network state is disabled
WiFi module is disabled
Failed messages: pending 0, notready 0, noresp 3
Socket states: 0 0 0 0 0 0 0 0
ok
Thanks,
Anthony
Hi there,
I've just installed my Duet 2 Wifi on my ultimaker printer. Installation was a breeze and super impressed with the hardware. However I have a strange issue which is making it all pretty useless.
The SD card does no auto mount on powering on, therefore it doesnt run through the start up Gcode file for the wifi, so no connection. If I manually mount in YAT with M21, and then start wifi with M552 S1 I can connect to the web control. From here I can start the heater etc, but if I try and do anything which requires writing to the SD card such as edit gcode, it unmounts again and I lose connection.
Any thoughts on how I can resolve this? I need to tweak the gcode to get things set up, but the only way, annoyingly, is to pull the SD card from the unit.