wifi not connecting

zshoe

@phaedrux m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3SJ-6JTD4-3S86K-TAXZF
Used output buffers: 1 of 24 (1 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 93140 of which 0 recycled
Exception stack ram used: 256
Never used ram: 11964
Tasks: NETWORK(ready,1268) HEAT(blocked,1232) MAIN(running,3836) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:02:51 ago, cause: power up
Last software reset time unknown, reason: Heat task stuck, spinning module Platform, available RAM 11560 bytes (slot 1)
Software reset code 0x00a0 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0043380f BFAR 0xe000ed38 SP 0x2000495c Task 0x4e49414d
Stack: 0044d797 00445546 6100f000 00000000 000004d9 00000000 00000000 3331bb4c 41880000 3e178897 3e1cd04f baa06630 3e3a3325 3e638e29 3e924925 35c8ffca 397d66d2 c0a00000 00000000 60000010 20003258 20008a10 0044d797
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 24.1, current 30.3, max 30.4
Supply voltage: min 0.1, current 1.5, max 1.5, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 272106402
Slowest loop: 1.07ms; fastest: 0.05ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
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
serial is ready with "m122" in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 1.25ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8

WiFi -
Network state is running
WiFi module is idle
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address 60:01:94:2e:a9:0a
WiFi Vcc 3.40, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 27920
Socket states: 0 0 0 0 0 0 0 0
ok

Phaedrux

Ok thanks that shows that your duet firmware and wifi firmware are matched up.

It would help to know what errors you actually get.

Send these commands and report back with what they return.

M552

M552 S-1

M552 S0

M552 S1

M587

Then try clearing any saved networks with M588 S"*"

Then try adding your network again with M587 and enable the module again with M552 S1.

record any error messages.

zshoe

@phaedrux everything works as it should up untill i runn m552 s1 and then i get "wifi reported error, no networks found, wifi module is idle" and then it just repeats that over and over. i run m587 and i get this

m587
Remembered networks:
TNCAP2FCC19 IP=192.168.1.14 GW=0.0.0.0 NM=0.0.0.0
Shoemaker IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
ok
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle

it looks like it remembers my network but the ip is all blank which doesnt make sense to me.

zshoe

@phaedrux m588 s"*"
M588: Failed to reset the WiFi module to factory settings
ok
Error retrieving WiFi status message: bad reply format version
WiFi module is idle

this is what i get when i try to reset it.

zshoe

@phaedrux m587 S"Shoemaker" P""
M587: Failed to add SSID to remembered list
ok
Error retrieving WiFi status message: bad reply format version
WiFi module is idle

i blocked out my password but i entered it in and i got this whenever i try to add my network again

Phaedrux

Can you try sending M997 S1 to reflash the module?

zshoe

@phaedrux WiFi module is idle

m997 s1
M997: File DuetWiFiServer.bin not found
ok

zshoe

@zshoe that made me check something because i remembered that file being added specifically so i went back and pulled the sd card and now i see that theres a lot of files in this "www" folder and in the file i got from here for the new firmware it had it all as individual files idk how that happened but could that be an issue? i just pulled all the individual files out of that folder inlcuding the one that m997 said was missing and put them on the main part of the sd card and im going to see if that did anything rn

zshoe

@phaedrux M997: Firmware binary "Duet2CombinedFirmware.bin" not found
now i get this

Phaedrux

Can you post a screen shot of your folder layout?

There should be a /sys/ folder with your config.g and homing files and the firmware bin files.
There should also be a /www/ folder with some HTML files and a CSS folder etc.

There shouldn't be anything but folders in the root of the card.

Phaedrux

@zshoe said in wifi not connecting:

@phaedrux M997: Firmware binary "Duet2CombinedFirmware.bin" not found
now i get this

To do just the WiFi server you need m997 s1

zshoe

@phaedrux Screenshot (2).png Screenshot (1).png

zshoe

@zshoe Screenshot (3).png

zshoe

@phaedrux you say those firmware bin files should be in the sys folder huh? maybe thats my issue

Phaedrux

That is preventing us from flashing the firmwares anyway. Not sure it will help with the WiFi problem but reflashing is a good first step.

zshoe

@phaedrux its still telling me duet wifi server.bin not found even tho i put it in the sys folder

when run m997 s1

jay_s_uk

@zshoe can you show a screenshot of the sys folder?

zshoe

@jay_s_uk Screenshot (4).png

Phaedrux

https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip

Download this zip file, extract it, and copy over the .bin files to the sys folder overwriting the ones that are there. Perhaps something has been corrupted.

zshoe

@phaedrux so i ended up getting into a really bad car accident on the 28th at 230 omw to work or i would have tried this much earlier but it seems like that worked thank you all for the help i really appreciate it.