Posts made by Bassbadger

@Phaedrux
Got it! Added the config.g file to the system and now I have Wifi connection automatically.

Thanks to all for your help.

@Phaedrux
Thanks. I think I mistook config-network.g for config.g
So I'm guessing config.g calls config-network.g I'll check the Ooznest site for a config.g file.

@Bassbadger

Am I missing the config.g file and if so, where can I find it?
I'm using an Ooznest Workbee with a Duet 2 WiFi

Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.5 (2022-11-30)
Duet WiFi Server Version: 1.27

@Bassbadger
I notice this file is the config-network.g
Is this the same as config.g as I don't seem to have one of those?

@Phaedrux
Connects fine and reachable with DWC

M552 S1
ok
WiFi module started
Error: WiFi module reported: no known networks found
WiFi module is idle
WiFi module is connected to access point TP-Link_1D56, IP address 192.168.1.66

@Bassbadger

@Phaedrux
M588 S”*”
ok
M587
Remembered networks: none
ok
M587 S”TP-Link_1D56” P”70259605”
ok
M587
Remembered networks:
TP-Link_1D56 IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
ok

But when I disconnect USB and switch on the PSU it does not connect.

Should there be an IP in the Remembered networks or should it be 0.0.0.0?

@Bassbadger said in Duet does not auto-connect to WiFi:

@Phaedrux
Yes, it does.

M587
Remembered networks:
TNCAP2FCC19 IP=192.168.1.14 GW=0.0.0.0 NM=0.0.0.0
PLUSNET-3X9K IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
Office IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
TP-Link_1D56 IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
ok

Ah, the correct network is TP-Link_1D56. Should the IP be 0.0.0.0?

@Phaedrux
Yes, it does.

M587
Remembered networks:
TNCAP2FCC19 IP=192.168.1.14 GW=0.0.0.0 NM=0.0.0.0
PLUSNET-3X9K IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
Office IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
TP-Link_1D56 IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
ok

@gloomyandy

@gloomyandy
M552 S1
ok
WiFi module started
WiFi module is connected to access point TP-Link_1D56, IP address 192.168.1.66

@gloomyandy

Here's the M122 diagnostic:
M122
M552
WiFi module is disabled
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-917DA-G4MSD-6JTDJ-3SJ6N-KBTZ9
Used output buffers: 1 of 26 (12 max)
=== RTOS ===
Static ram: 23836
Dynamic ram: 73384 of which 0 recycled
Never used RAM 14860, free system stack 184 words
Tasks: NETWORK(ready,7.5%,517) HEAT(notifyWait,0.0%,388) Move(notifyWait,0.0%,363) MAIN(running,92.4%,428) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:04:08 ago, cause: power up
Last software reset time unknown, reason: StuckInSpinLoop, none spinning, available RAM 14860, slot 1
Software reset code 0x0092 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0040080f BFAR 0xe000ed38 SP 0x200034c4 Task NETW Freestk 539 ok
Stack: 0045e223 0045d046 6100f000 41d718fb 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 3f800000 00000000 4354c416 ba0afaff 41a6ac0a 00000000 00419773 00000000 0045e223 20016be8 00000000 00000000 200173f4
Error status: 0x00
Step timer max interval 0
MCU temperature: min 22.1, current 22.8, max 23.0
Supply voltage: min 0.5, current 0.5, max 0.5, 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: 8.87ms; 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.9ms, 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 -1 -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: 0.20ms; 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 2779096485, notready 2779096485, noresp 2779096485
Socket states: 0 0 0 0 0 0 0 0
ok

Hi all,

I'm sure this is a very basic newbie issue but it's driving me crazy!

I'm on my Mac, connecting by USB to the Duet and using SerialTools to add my WiFi network and connect and this works fine. The WiFi LED on the Duet glows purple and I can connect to it using DWC in my browser. But when I disconnect the USB and power up the Workbee the WiFi LED glows red but the module does not auto-connect so I can no longer access the Duet. Back on a USB connection I can see that the Duet still has the correct settings stored to join the network.

Looking at the config.g file from DWC I can see that the M552 S1 command seems to be active.

Why won't it join automatically?