Duet 3 Mini 5+ wifi works with USB, not through PSU

jay_s_uk

@fakeerror what firmware versions are you running? an output of M122 when the wifi module is enabled with confirm

fakeerror

@jay_s_uk here is the output for "M122":

=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: ZWBG6-5196U-D65J0-40KMS-JY03Z-RTZ63
Used output buffers: 1 of 40 (11 max)
=== RTOS ===
Static ram: 98732
Dynamic ram: 107800 of which 36 recycled
Never used RAM 38648, free system stack 142 words
Tasks: NETWORK(ready,207) HEAT(blocked,315) CanReceiv(blocked,947) CanSender(blocked,372) CanClock(blocked,362) TMC(blocked,106) MAIN(running,426) IDLE(ready,20) AIN(blocked,269)
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:01:55 ago, cause: software
Last software reset time unknown, reason: User, GCodes spinning, available RAM 38648, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
Supply voltage: min 0.0, current 23.8, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 0, standstill, SG min/max 0/0, read errors 1, write errors 1, ifcnt 19, reads 9627, writes 9, timeouts 0, DMA errors 0
Driver 1: position 0, assumed not present
Driver 2: position 0, standstill, SG min/max 0/0, read errors 1, write errors 1, ifcnt 19, reads 9627, writes 9, timeouts 0, DMA errors 0
Driver 3: position 0, assumed not present
Driver 4: position 0, assumed not present
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2023-11-18 23:09:50
Cache data hit count 238218993
Slowest loop: 8.55ms; fastest: 0.12ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.3ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, 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 = 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 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
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: 10.00ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address 
WiFi Vcc 3.39, reset reason Power up
WiFi flash size 2097152, free heap 25648
WiFi IP address 
WiFi signal strength -63dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
=== CAN ===
Messages queued 1041, send timeouts 1039, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 16
ok

jay_s_uk

@fakeerror i would be updating to 3.4.6 and wifi firmware 1.27

fakeerror

@jay_s_uk I'll try, thanks for your help! Let me go through the manual quickly, I'll report when finished.

fakeerror

@jay_s_uk done. The problem remains. First the board will try on its own and eventually connect to 255.255.255.255. Then I start the wifi module again and it works.

Here's the new "M122" output:

=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.6 (2023-07-21 14:09:13) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: ZWBG6-5196U-D65J0-40KMS-JY03Z-RTZ63
Used output buffers: 1 of 40 (13 max)
=== RTOS ===
Static ram: 103712
Dynamic ram: 110332 of which 12 recycled
Never used RAM 27656, free system stack 160 words
Tasks: NETWORK(ready,12.5%,242) HEAT(notifyWait,0.0%,358) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,342) TMC(notifyWait,0.0%,124) MAIN(running,86.5%,411) IDLE(ready,0.2%,30) AIN(delaying,0.8%,272), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:02:38 ago, cause: software
Last software reset at 2023-11-18 23:47, reason: User, GCodes spinning, available RAM 27656, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 158544, completed 158544, timed out 0, errs 0
Step timer max interval 1488
MCU temperature: min 22.0, current 22.7, max 22.9
Supply voltage: min 1.1, current 1.3, 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, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 1: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 2: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 3: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 4: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 5: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 6: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2023-11-18 23:50:29
Cache data hit count 310171962
Slowest loop: 99.43ms; fastest: 0.12ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: mesh, 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
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
=== CAN ===
Messages queued 1425, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 793/0/0
Tx timeouts 0,0,792,0,0,631 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 99.89ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
= WiFi =
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address
WiFi Vcc 3.39, reset reason Power up
WiFi flash size 2097152, free heap 25808
WiFi IP address 255.255.255.255
WiFi signal strength -66dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok

Exerqtor

Thought i should weigh in with some of my own experiences here with my Mini 5+ WiFi.

I recently went from a "allways on" 24V powering the Duet, to a 5V "allways on" and relays to turn on/off the 24V rail to the Duet.

And when i did that i noticed that the WiFi module wouldn't start/boot/enable when the board was powered by 5V alone and thought that was the expected behaviour, even though it does seem somewhat strange.

I didn't have time to fiddle with that so i ended up deploying M80 at the very start of config,g and running the board with 24V "allways on" anyways.

All this is with the newest beta firmware in standalone mode by the way (2.1beta4 for the WiFi server and RRF 3.5.0rc1+ at the time of writing).

droftarts

@Exerqtor no, it’s not expected behaviour for the WiFi not to work on 5V only. Does it work on USB power? How are the 5V_Select and Disable_5V_Internal jumpers set?

Ian

Exerqtor

@droftarts Well then it smells like it's a FW or HW oversight somewhere 😅

When powered by USB it works just fine.

On my machine the jumpers are set like this:

5V_Select = 5V_EXT_IN

5V_Disable = Jumped

I just took a picture even:
alt text

droftarts

@Exerqtor I can’t see why disabling the internal 5V would disable the WiFi, but maybe @dc42 could answer that one.

Is the OP @fakeerror using external 5V? I can’t see them say that anywhere. Though I see an entry for ‘Lerdge power module’ in config.g

Ian

Exerqtor

@droftarts said in Duet 3 Mini 5+ wifi works with USB, not through PSU:

@Exerqtor I can’t see why disabling the internal 5V would disable the WiFi, but maybe @dc42 could answer that one.

I have no idea, but from my understanding of the docs we are meant to disable the internal 5V when running external 5V aren't we? 🤔

Is the OP @fakeerror using external 5V? I can’t see them say that anywhere. Though I see an entry for ‘Lerdge power module’ in config.g

Ian

I haven't seen any mentioning of it either, but i assumed they were powering it by external 5V based on the voltage readings on from the M122's they posted while the board was "powered by PSU".

Want to weigh in on this one @dc42? 😇

fakeerror

Dear fellow nerds, geeks and dorks,

After having a number of private matters interrupt my 3D-printing activities, I managed to make some time for myself and work on the printer. Taking the advise from @jay_s_uk, the last thing I did was update the firmware of the board. The next thing I did, which ended up solving the issue, was updating the firmware of my routers. I made sure the static IP address was set again and now everything works like a charm.

I want to thank everyone in this thread profusely for giving their insights. I will be back to printing figures and gifts, peace!