Board not connecting to Wifi: no know networks found

Phaedrux

Wifi server is 1.25?

Can out send m122 and post the result?

quilby7

=== Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1-diabase running on Duet WiFi 1.02 or later + DueX5<LF>Board ID: 08DGM-917NK-F23T0-6JKF8-3SJ6P-TZ8NG<LF>Used output buffers: 1 of 24 (24 max)<LF>=== RTOS ===<LF>Static ram: 26128<LF>Dynamic ram: 95004 of which 0 recycled<LF>Exception stack ram used: 352<LF>Never used ram: 9588<LF>Tasks: NETWORK(ready,1100) HEAT(blocked,1232) DUEX(suspended,144) MAIN(running,4120) IDLE(ready,160)<LF>Owned mutexes:<LF>=== Platform ===<LF>Last reset 00:05:22 ago, cause: power up<LF>Last software reset time unknown, reason: Heat task stuck, spinning module Platform, available RAM 9280 bytes (slot 3)<LF>Software reset code 0x00a0 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0040080f BFAR 0xe000ed38 SP 0x20004954 Task 0x4e49414d<LF>Stack: 0044f997 0044f778 61000000 3f800000 3fdb4e81 00000000 00000000 3331bb4c 41880000 3e178897 3e1cd04f bda02214 3e3a3498 3e638fa9 3e924a09 3bc8553b c0a00000 3f800000 3f800000 20000010 ffffffff 20009354 00000000<LF>Error status: 4<LF>Free file entries: 10<LF>SD card 0 detected, interface speed: 20.0MBytes/sec<LF>SD card longest block write time: 0.0ms, max retries 0<LF>MCU temperature: min 28.7, current 32.5, max 32.8<LF>Supply voltage: min 0.6, current 0.7, max 0.7, under voltage events: 0, over voltage events: 0, power good: no<LF>Driver 0: ok, SG min/max not available<LF>Driver 1: ok, SG min/max not available<LF>Driver 2: ok, SG min/max not available<LF>Driver 3: ok, SG min/max not available<LF>Driver 4: ok, SG min/max not available<LF>Driver 5: ok, SG min/max not available<LF>Driver 6: ok, SG min/max not available<LF>Driver 7: ok, SG min/max not available<LF>Driver 8: ok, SG min/max not available<LF>Driver 9: ok, SG min/max not available<LF>Date/time: 1970-01-01 00:00:00<LF>Cache data hit count 533347494<LF>Slowest loop: 100.12ms; fastest: 0.05ms<LF>I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0<LF>=== Move ===<LF>Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms<LF>Bed compensation in use: none, comp offset 0.000<LF>=== DDARing ===<LF>Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0<LF>=== Heat ===<LF>Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1<LF>=== GCodes ===<LF>Segments left: 0<LF>Stack records: 2 allocated, 0 in use<LF>Movement lock held by null<LF>http is idle in state(s) 0<LF>telnet is idle in state(s) 0<LF>file is idle in state(s) 0<LF>serial is ready with "M122" in state(s) 0<LF>aux is idle in state(s) 0<LF>daemon is idle in state(s) 0<LF>queue is idle in state(s) 0<LF>autopause is idle in state(s) 0<LF>Code queue is empty.<LF>=== Network ===<LF>Slowest loop: 1.25ms; fastest: 0.00ms<LF>Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)<LF>HTTP sessions: 0 of 8<LF>- WiFi -<LF>Network state is running<LF>WiFi module is idle<LF>Failed messages: pending 0, notready 0, noresp 0<LF>WiFi firmware version 1.23<LF>WiFi MAC address ec:fa:bc:02:18:54<LF>WiFi Vcc 3.45, reset reason Turned on by main processor<LF>WiFi flash size 4194304, free heap 30176<LF>Socket states: 0 0 0 0 0 0 0 0<LF>ok<LF>

A Former User

@quilby7 said in Board not connecting to Wifi: no know networks found:

M587

whats the output of just M587? does it include the SSID you added, and is the network a 2.4Ghz network? Any special characters in SSID or password?

quilby7

M122<CR>
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1-diabase running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-917NK-F23T0-6JKF8-3SJ6P-TZ8NG
Used output buffers: 1 of 24 (24 max)
=== RTOS ===
Static ram: 26128
Dynamic ram: 95004 of which 0 recycled
Exception stack ram used: 352
Never used ram: 9588
Tasks: NETWORK(ready,1100) HEAT(blocked,1232) DUEX(suspended,144) MAIN(running,4120) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:05:22 ago, cause: power up
Last software reset time unknown, reason: Heat task stuck, spinning module Platform, available RAM 9280 bytes (slot 3)
Software reset code 0x00a0 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0040080f BFAR 0xe000ed38 SP 0x20004954 Task 0x4e49414d
Stack: 0044f997 0044f778 61000000 3f800000 3fdb4e81 00000000 00000000 3331bb4c 41880000 3e178897 3e1cd04f bda02214 3e3a3498 3e638fa9 3e924a09 3bc8553b c0a00000 3f800000 3f800000 20000010 ffffffff 20009354 00000000
Error status: 4
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 28.7, current 32.5, max 32.8
Supply voltage: min 0.6, current 0.7, max 0.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 533347494
Slowest loop: 100.12ms; 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 = -1 -1 -1 -1, chamberHeaters = -1 -1
=== 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.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 ec:fa:bc:02:18:54
WiFi Vcc 3.45, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 30176
Socket states: 0 0 0 0 0 0 0 0
ok

quilby7

@bearer
The output for M587 is:

Remembered networks:
Diabase IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
ok

The password does have the ! $ @ sybols in it

quilby7

Looks like I was mistaken. The WiFi Firmware is actually 1.23

A Former User

@quilby7 said in Board not connecting to Wifi: no know networks found:

The password does have the ! $ @ sybols in it

I'd try without the @ and $

quilby7

Alright, I'll try that. It's not my personal network so I'll have to contact someone to change it, which may take a while. I'll post back here if it does (or doesn't) work

Phaedrux

You may want to try using a macro to add the wifi network. That can avoid any capitalization changes that the USB terminal may do. It's also easier than having to type it a bunch of times.

Something like this saved as a macro called addwifi and placed in the macros folder. Then you can send M98 P"addwifi" to execute it.

; Add default wifi network
;
M291 R"Add default WIFI network? Y/N" P"This will add duetwifi access point." S3 T10

M552 S0			; Disable network module
G4 S5			; wait 5 seconds
M587 S"NETWORKNAME" P"PASSWORD"			; Add duet wifi SSID to remembered networks list
G4 S5			; wait 5 seconds
M552 S1			; reenable wifi module

M291 R"duetwifi SSID added." P"Check console to verify IP address."

Since the network is not under your control, you could use access point mode to test that the wifi module is otherwise working.

https://duet3d.dozuki.com/Wiki/Gcode#Section_M589_Configure_access_point_parameters

quilby7

@Phaedrux
I am trying access point mode currently
I input: M589 S"NetworkName" P"Password" lnnn.nn.nn
It returns: M589: Bad or missing parameter
The WiFi module is Idle. I think that the part I am messing up on is the IP. I am pretty new to this, can the IP be just any random numbers, or is there a format it has to follow?

Phaedrux

Yes you will need to specify an actual ip address.

192.168.0.1 would be suitable.

Example command: M589 S"DuetSSID" P"password" I"192.168.0.1" C1

quilby7

@Phaedrux
It worked! Not a permanent solution, but it’s good to see some progress. I’ll stil try to get that password changed. Thanks for your help

dc42

@quilby7 said in Board not connecting to Wifi: no know networks found:

@Phaedrux
It worked! Not a permanent solution, but it’s good to see some progress. I’ll stil try to get that password changed. Thanks for your help

How did you send the password in the M587 command originally? AFAIK the ! $ @ symbols should be OK in a password. OTOH, many GCode sending programs force all characters to uppercase (which will mess up any lowercase characters in the password), also I don't think the WiFi firmware supports accented characters.

A Former User

@dc42 said in Board not connecting to Wifi: no know networks found:

AFAIK the ! $ @ symbols should be OK in a password.

ah, they were in a warning for SSIDs in the docs, but that doesn't apply to the password then?

Given OP's output from M587 showing mixed case and no special characters I presumed the issue would be the password, signal strength or frequency band (or could technically still be SSID case sensitivity I guess)

quilby7

I was sending the gcode commands using YAT, which I believe can send lowercase characters.

A Former User

@quilby7 said in Board not connecting to Wifi: no know networks found:

I was sending the gcode commands using YAT, which I believe can send lowercase characters.

Yes it does, that is why I asked you for the output of M587 with no paramters. It shows the SSID is stored with both upper and lower case so we know you're not using a upper case terminal.

Can you confirm the network is 2.4GHz and that the case is exactly as shown in M587. Duet does not support 5GHz.

quilby7

I am pretty sure the network was 2.4GHz. I’ll double check with the admin when they change the password. Because of Covid restrictions, it may be a while before I am actually able to test anything out.