DOA Wifi Module???
-
I'm building a RailcoreII 300ZL kit I received earlier this week. Completed my wiring, passed my smoke test, but Duet 2 Wifi will not connect. I have latest firmware and latest Wifi firmware (DuetWiFiServer version 1.23 to the sys folder followed by a successful M997 S1 command), and can connect with USB through YAT. No success with any M558 commands. My M122 can be found below. Any help is much appreciated.
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-917DA-G4MS4-6J9D4-3S86R-19YVA
Used output buffers: 1 of 20 (1 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98840 of which 0 recycled
Exception stack ram used: 272
Never used ram: 6436
Tasks: NETWORK(ready,544) HEAT(blocked,1232) MAIN(running,3868) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:01:47 ago, cause: power up
Last software reset details not available
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 25.2, current 31.2, max 31.3
Supply voltage: min 0.0, current 1.6, max 1.7, 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
Driver 5: ok, SG min/max not available
Driver 6: ok, SG min/max not available
Driver 7: ok, SG min/max not available
Driver 8: ok, SG min/max not available
Driver 9: ok, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 262667517
Slowest loop: 1.55ms; fastest: 0.06ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.6
=== 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: 1001.09ms; 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 changing mode
WiFi module is idle
Failed messages: pending 0, notready 0, noresp 0
Failed to get WiFi status
Socket states: 0 0 0 0 0 0 0 0
ok
Error retrieving WiFi status message: bad reply format version
WiFi module is idle
WiFi reported error: no known networks found
- WiFi -
-
@jwalbridge said in DOA Wifi Module???:
Network state is changing mode
That state should not persist for more than a second or two. Please try copying the DuetWiFiServer 1.23 file to /sys again, rename it to exactly DuetWiFiServer.bin if it is called anything else (e.g. DuetWiFiServer-1.23.bin), restart the Duet, and run M997 S1 again.
-
I was able to connect after I disabled Beamforming Transmission(BFR) and Beamforming Reception(BFE) for the 2.4GHz signal on my router. I'm using a Nighthawk AC1900 Wifi Cable Modem Router. Was this likely the issue? Or did it just decide to start working? Did not have to run M997 S1 again.
-
@jwalbridge said in DOA Wifi Module???:
I was able to connect after I disabled Beamforming Transmission(BFR) and Beamforming Reception(BFE) for the 2.4GHz signal on my router. I'm using a Nighthawk AC1900 Wifi Cable Modem Router. Was this likely the issue? Or did it just decide to start working? Did not have to run M997 S1 again.
No, I don't think that was the issue. Try enabling beam forming again.
