Duet will not connect to WiFi
-
I just finished the assembly and setup of a SeeMeCNC RostockMax V4. I have been unable to successfully connect to my WiFi. I am trying to connect to a 2.4Ghz WiFi network, set to channel 6 (wouldn't work on 11 either). I have tried following various setup guides online but nothing has worked. Any help would be appreciated.
The terminal simply repeats non-stop:
WiFi reported error: no known networks found
WiFi module is idleHere is the output from M115:
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet
FIRMWARE_VERSION: 2.02(RTOS)
ELECTRONICS: Duet WiFi 1.02 or later
FIRMWARE_DATE: 2018-12-24b1M122:
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MSJ-6JTDA-3SD6R-KSN3A
Used output buffers: 1 of 20 (11 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98820 of which 0 recycled
Exception stack ram used: 360
Never used ram: 6368
Tasks: NETWORK(ready,544) HEAT(blocked,1232) MAIN(running,3644) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:46:36 ago, cause: software
Last software reset time unknown, reason: User, spinning module GCodes, available RAM 6316 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
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 26.1, current 26.2, max 26.5
Supply voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 4294967295
Slowest loop: 1.19ms; fastest: 0.08ms
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: 11, completed moves: 11
Bed compensation in use: mesh
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.0
=== GCodes ===
Segments left: 0
Stack records: 2 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.03ms; 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 18
Failed to get WiFi status
Socket states: 0 0 0 0 0 0 0 0
ok
Error retrieving WiFi status message: bad reply format versionM587:
M587: Failed to retrieve network list
ok
Error retrieving WiFi status message: bad reply format version -
I wonder if maybe your wifi server version is out of step with the firmware.
If you place the Duetwifiserver.bin file from the 2.02 release on the SD card and then send M552 S0 to turn off the network module, then send M997 S1 to update the wifi server firmware.
Then after it reboots, send M552 S0 to disable the wifi module again, and then send the M587 command to add your wifi network and then M552 S1 to re-enable the network module.
