2 NEW DUET 2 WIFI's W/EXTERNAL ANTENNA WILL NOT CONNECT

[GBusy24]

Long time member here and I have 2 new duet 2 Wifi's w/external antenna that won't connect. I'm puzzled and can't resolve using suggestions I've seen in similar posts and need help. Here's some info from YAT terminal. Any help if appreciated. Thanks.YAT Terminal.txt

[Phaedrux]

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.5.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2024-09-18 11:25:32
ok
M587
Error: M587: use M552 to abandon the current connection attempt before using this command
ok
M552
WiFi module is changing mode
ok
Error: WiFi module reported: Timed out
WiFi module is idle
M587
Error: M587: use M552 to abandon the current connection attempt before using this command
ok
M552 S0
ok
Error: WiFi module reported: Timed out
WiFi module is idle
M587
Remembered networks:
<ETX><ETB><STX> IP=0.23.2.0 GW=5.45.2.0 NM=0.23.2.0
Gregs WIFI IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
TNCAPF318D9 IP=192.168.1.14 GW=0.0.0.0 NM=0.0.0.0
ok
M552 S1
ok
M552 S0
ok
Error: WiFi module reported: Timed out
WiFi module is idle
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.3 (2024-09-18 11:25:32) running on Duet WiFi 1.02 or later
Board ID: 0JD6M-99APT-NU4SN-6J9F4-3SN6M-14QKK
Used output buffers: 1 of 26 (10 max)
Error in macro line 1 while starting up: Bad command: 
=== RTOS ===
Static ram: 23376
Dynamic ram: 71596 of which 0 recycled
Never used RAM 15652, free system stack 180 words
Tasks: NETWORK(1,ready,6.9%,344) HEAT(3,nWait 5,0.0%,378) Move(4,nWait 5,0.0%,359) MAIN(1,running,92.7%,500) IDLE(0,ready,0.3%,29), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:04:26 ago, cause: power up
Last software reset details not available
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 21.3, current 26.3, max 26.5
Supply voltage: min 0.3, current 1.6, max 1.7, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/40/12, 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: 80.54ms; 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, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
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 ===
Movement locks 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
Q0 segments left 0
Code queue 0 is empty
=== Network ===
Slowest loop: 0.66ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
=== WiFi ===
Interface state: idle
Module is idle
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.1.0
MAC address 00:00:00:00:00:00
Module reset reason: Power up, Vcc 2.66, flash size 2097152, free heap 47772
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok

This error

Error in macro line 1 while starting up: Bad command: 

It looks like you have some bad characters in your config.g that may be causing it to stop executing correctly?

Can you upload your config.g file?

[GBusy24]

@Phaedrux Thanks for your answer. Looks like I've omitted some steps. I was following the getting connected guide and assumed I left the config.g as is when I received the boards as it had FWc 3.5.3 installed(fairly recent FW even though I had been runninng 3.5.4 on the boards I'm replacing) Here's the config.g you asked for, but let me go ahead and upload the results of the RepRap configurator and I'll get back with you with. Thanks

[GBusy24]

@Phaedrux, I have directly uploaded the results of thr RRF configurator tool directly onto the SD card into the root directory thru USB beings I can access DWC at this time or so it seems. I don't remember having to go thru all of this a couple years back when I dropped a new duet 2 Wifi in my CR-10 S4. Anyway, I know they talked about movinig some stuff around on the SD card when updating FW here (https://docs.duet3d.com/User_manual/RepRapFirmware/Updating_firmware), but I didn't do that because it didn't immediately dawn on me how to go about that and am calling back out to you(you've helped me out tons in the past and I'm appreciative). I would like to add that after doing what I've done, I attempted to view the new config.g on the card so I could share it with you and it's empty. Thanks

[GBusy24]

@Phaedrux, these are the files it talks about moving around..............
1.Also copy the relevant IAP file (see Required Files, above) into /sys
2.If your board is a Duet WiFi, also copy the new DuetWiFiServer.bin file into /sys

I have now performed those operations or at least they show up in .sys folder, but I still can't get connected. Thanks

[Phaedrux]

I'm a bit confused now about what state you're currently in.

Have you been following this guide?
https://docs.duet3d.com/en/How_to_guides/Getting_connected/Getting_connected_to_your_Duet

If you are replacing a board, do you already have an existing configuration from the old board?

[GBusy24]

@Phaedrux yes the SD cards seems to have all of the data still intact from the two boards I'm replacing

[GBusy24]

@Phaedrux so I guess maybe I could just switch out the cards right?

[Phaedrux]

@GBusy24 said in 2 NEW DUET 2 WIFI's W/EXTERNAL ANTENNA WILL NOT CONNECT:

@Phaedrux so I guess maybe I could just switch out the cards right?

For the most part yes as long as the firmware version was at least close in version.

The wifi SSID and password need to be re-added because they are stored on the module, so you'd still want to use the getting connected guide I linked above.

[GBusy24]

@Phaedrux Understood and thanks.

[GBusy24]

@Phaedrux, I've moved over to the second new board and inserted the SD card from the old board just for a fresh start. Here's the YAT terminal stuff to show what I've done. At this point, I've got myself confused. Look this over and let me know what you think. Thanks.Phaedrux File.txt I will add that the getting started article confuses me as far as the M552 commands. In step 4, it says to send M552 S1 to stop the wifi and then later after explaining setting the network with M587, it says send M552 S1 to connect the wifi. The green wifi light never flashes or stays lit.

[GBusy24]

@Phaedrux Here's the config.g from the old SD card that I inserted to the new board. Thought you'd want to see it too.config.g

[GBusy24]

@Phaedrux 111.txt

[Phaedrux]

Did you follow this section to add your SSID and password to get connected again?

https://docs.duet3d.com/en/How_to_guides/Getting_connected/Getting_connected_to_your_Duet#h-5-connect-duet-to-network

[GBusy24]

@Phaedrux yes

[GBusy24]

@Phaedrux one of my posts to you last night seems to be deleted or at least it's grayed out and I don't know if you saw it so I'm going to reshare the link I had in the post. Here it is...M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.5.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2024-09-18 11:25:32
ok
M587
Remembered networks:
Gregs WIFI IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
TNCAPF318D9 IP=192.168.1.14 GW=0.0.0.0 NM=0.0.0.0
ok
M552 S0
ok
M552 S1
ok
Error: WiFi module reported: no known networks found
WiFi module is idle
Error: WiFi module reported: no known networks found
WiFi module is idle
Error: WiFi module reported: no known networks found
WiFi module is idle
Error: WiFi module reported: no known networks found
WiFi module is idle
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.3 (2024-09-18 11:25:32) running on Duet WiFi 1.02 or later
Board ID: 0JD6M-99APT-NU4SN-6J9F4-3SD6K-14PTL
Used output buffers: 1 of 26 (1 max)
=== RTOS ===
Static ram: 23376
Dynamic ram: 72792 of which 0 recycled
Never used RAM 17308, free system stack 194 words
Tasks: NETWORK(1,ready,7.0%,339) HEAT(3,nWait 5,0.0%,328) Move(4,nWait 5,0.0%,359) MAIN(1,running,92.9%,501) IDLE(0,ready,0.1%,29), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:20:56 ago, cause: power up
Last software reset details not available
Error status: 0x00
MCU temperature: min 25.7, current 30.8, max 31.9
Supply voltage: min 0.2, current 1.4, max 1.8, 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: 99.91ms; 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 3.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
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 ===
Movement locks 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
Q0 segments left 0
Code queue 0 is empty
=== Network ===
Slowest loop: 0.73ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
=== WiFi ===
Interface state: changingMode
Module is idle
Failed messages: pending 0, notrdy 0, noresp 0
Failed to get WiFi status
Socket states: 0 0 0 0 0 0 0 0
ok
Error: failed to retrieve WiFi status message: bad reply format version
WiFi module is idle
Error: WiFi module reported: no known networks found
WiFi module is idle
Error: WiFi module reported: no known networks found
WiFi module is idle
Error: WiFi module reported: no known networks found
WiFi module is idle
Error: WiFi module reported: no known networks found
WiFi module is idle
Error: WiFi module reported: no known networks found
WiFi module is idle
Error: WiFi module reported: no known networks found
WiFi module is idle
Error: WiFi module reported: no known networks found
WiFi module is idle
Error: WiFi module reported: no known networks found
WiFi module is idle
Error: WiFi module reported: no known networks found
WiFi module is idle

[jay_s_uk]

@GBusy24 can you post a photo of the board?

[GBusy24]

@jay_s_uk unfortunately, I'm at work right now

[GBusy24]

@jay_s_uk may I ask what you would be looking for on the board and maybe I can help her memory. It is one of the newer boards with the external Wi-Fi antenna

[jay_s_uk]

@GBusy24 just checking that everything looks ok. as the wifi module appears to be working, the antenna is either not connected correctly or is not functioning.
I've seen cases of antennas not working correctly