Unable to attach after network wireless IP change

crchisholm

I had to take a break from Duet for six months for medical reasons and have lost a bit of my memory. During the break, I had to replace a computer and routers so now I have a new IP schema on my local network.

When I fired up the printer with the Duet Wifi v1.04 board, I expected, but didn't see the blue led blink to tell me it;s looking for the network. In YAT with USB attached, I get a message that no networks could be found when I try to run the M552 S0 command. I thought I might need to download and install some duet drivers on the new computer, but could not find any. Am I nuts about the blue light expectation? There are several wireless networks visible when I look. The duet is only about five feet from the router.

HELP!!
Charlie

Phaedrux

Well if you had to replace the wifi router that the Duet used to be connected to then you'd need to add the new WIFI network to the Duet.

You can send M587 to see what networks it has stored.

M588 S"*" will clear out all saved wifi networks

and M587 S"NETWORKNAME" P"PASSWORD" will add your current wifi

https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M587_Add_WiFi_host_network_to_remembered_list_or_list_remembered_networks

This may help as a good refresher: https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7

crchisholm

@Phaedrux when I try to use M588 or M587 I get a message that it failed - no available networks (even though there are many.

Phaedrux

What exactly did you send?

crchisholm

@Phaedrux
Here's what I sent and rceived.

M588 S"*
*WiFi reported error: no known networks found<LF>WiFi module is idle<LF>

M587 S"e***" P"C**********^a^^^^^^^s"**
M587: Failed to add SSID to remembered list<LF>ok<LF>Error retrieving WiFi status message: bad reply format version<LF>WiFi module is idle<LF>

Am I wrong that that the blue light on over the ESP unit flashes when it is trying to connect? That does not flash.

Phaedrux

Can you send M122 and check what wifi firmware version is installed?

If your SSID and password use special characters or capitals and your USB terminal doesn't always respect them, you can create a macro file that has the M587 command in it, save that to the macros folder as addwifi, and then use M98 P"addwifi" to execute it.

Also the Duet will only work with 2.4ghz networks, so if your new router is 5ghz only or uses a combined network name for 2.4 and 5ghz you may need to change that to provide a separate network name for 2.4ghz only.

crchisholm

@Phaedrux said in Unable to attach after network wireless IP change:

Can you send M122 and check what wifi firmware version is installed?

Yes, I get the following....
m122
=== Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later<LF>Board ID: 08DGM-917NK-F23T0-6J9FL-3SD6R-KDB0F<LF>Used output buffers: 1 of 20 (1 max)<LF>=== RTOS ===<LF>Static ram: 25524<LF>Dynamic ram: 98616 of which 0 recycled<LF>Exception stack ram used: 312<LF>Never used ram: 6620<LF>Tasks: NETWORK(ready,1240) HEAT(blocked,1232) MAIN(running,3788) IDLE(ready,200)<LF>Owned mutexes:<LF>=== Platform ===<LF>Last reset 23:45:40 ago, cause: power up<LF>Last software reset at 2020-08-02 14:08, reason: User, spinning module GCodes, available RAM 6608 bytes (slot 2)<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d<LF>Error status: 0<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 22.6, current 35.2, max 38.5<LF>Supply voltage: min 0.4, current 23.8, max 24.4, under voltage events: 5, over voltage events: 0, po[Warning: Maximal number of bytes per line exceeded! Check the EOL (end-of-line) settings or increase the limit in the advanced terminal settings.]

If your SSID and password use special characters or capitals and your USB terminal doesn't always respect them, you can create a macro file that has the M587 command in it, save that to the macros folder as addwifi, and then use M98 P"addwifi" to execute it.

The only special charactor in the pw or ssid is the "@" Other than that it's just a mix of upper and lower case letters and numbers.

Also the Duet will only work with 2.4ghz networks, so if your new router is 5ghz only or uses a combined network name for 2.4 and 5ghz you may need to change that to provide a separate network name for 2.4ghz only.

I turned off the 5gh network when I installed the new router so everything runs through 2.4gh. The router does not seem to see the Duet and I can not ping it. The blue network light is still out. Something seems to be turned off or not working.

Can you think of anything else to try???

Veti

@crchisholm said in Unable to attach after network wireless IP change:

Yes, I get the following....
m122

Please set YAT to <LF> endings:
Terminal->Settings->Text Settings-> EOL sequence <LF>

and report again

crchisholm

@Veti said in Unable to attach after network wireless IP change:

@crchisholm said in Unable to attach after network wireless IP change:

Yes, I get the following....
m122

Please set YAT to <LF> endings:
Terminal->Settings->Text Settings-> EOL sequence <LF>

and report again

I did and here's the result....
<

Executing config.g...Error: M587: Failed to add SSID to remembered list
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: G29: Must home printer before bed probing

Done!
RepRapFirmware for Duet 2 WiFi/Ethernet is up and rWiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
....list keeps comming without stop.

Might the problem be that tellnet and FTP are disabled? Should both be enabled? Where would I set that.

Veti

thats not the output of m122

Veti

@crchisholm said in Unable to attach after network wireless IP change:

M588 S"*

did you send that or

M588 S"*" ?

crchisholm

Sorry grabbed the wrong screen shot. Here is the correct one.

M122

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917NK-F23T0-6J9FL-3SD6R-KDB0F
Used output buffers: 1 of 20 (1 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98616 of which 0 recycled
Exception stack ram used: 256
Never used ram: 6676
Tasks: NETWORK(ready,1240) HEAT(blocked,1232) MAIN(running,3868) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 01:19:57 ago, cause: power up
Last software reset at 2020-08-02 14:08, reason: User, spinning module GCodes, available RAM 6608 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 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 31.9, current 32.7, max 35.9
Supply voltage: min 0.3, current 0.5, max 0.6, 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 4294967295
Slowest loop: 1.08ms; 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: mesh
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== 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.27ms; 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

Phaedrux

Can you send M997 S1 to try and re-flash the wifi module with the bin file currently on the sd card?

When sending M588 S"*" remember to include the double quotes around the asterix.

crchisholm

@Phaedrux said in Unable to attach after network wireless IP change:

M997 S1 t

Yep.

M997 S1
WiFi reported error: no known networks found
WiFi module is idle
Trying to connect at 230400 baud: T0:23.4 /0.0 B:24.0 /0.0
T0:23.5 /0.0 B:24.0 /0.0
T0:23.5 /0.0 B:24.0 /0.0
T0:23.5 /0.0 B:24.0 /0.0
T0:23.5 /0.0 B:24.0 /0.0
success
Erasing 4096 bytes...
Erasing 192512 bytes...
T0:23.5 /0.0 B:24.0 /0.0
T0:23.4 /0.0 B:24.0 /0.0
Uploading file...
T0:23.5 /0.0 B:24.0 /0.0
5% complete
10% complete
T0:23.4 /0.0 B:23.9 /0.0
15% complete
T0:23.5 /0.0 B:23.9 /0.0
20% complete
T0:23.5 /0.0 B:24.0 /0.0
25% complete
T0:23.5 /0.0 B:24.0 /0.0
30% complete
35% complete
T0:23.4 /0.0 B:23.9 /0.0
40% complete
T0:23.5 /0.0 B:24.0 /0.0
45% complete
T0:23.5 /0.0 B:23.9 /0.0
50% complete
T0:23.4 /0.0 B:24.0 /0.0
55% complete
T0:23.4 /0.0 B:23.9 /0.0
60% complete
T0:23.4 /0.0 B:24.0 /0.0
65% complete
70% complete
T0:23.5 /0.0 B:23.9 /0.0
75% complete
T0:23.5 /0.0 B:24.0 /0.0
80% complete
T0:23.5 /0.0 B:23.9 /0.0
85% complete
T0:23.5 /0.0 B:24.0 /0.0
90% complete
T0:23.5 /0.0 B:24.0 /0.0
95% complete
Upload successful
ok

Phaedrux

Ok.

Now send these commands and let us know what it responds with.

M552 S0
M552 S1
M588 S"*"

Now to connect it to your wifi network you need to send the M587 command.

See here for the steps: https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7#s9

crchisholm

@Phaedrux said in Unable to attach after network wireless IP change:

Ok.

Now send these commands and let us know what it responds with.
M552 S0
M552 S1
M588 S"*"
Now to connect it to your wifi network you need to send the M587 command.

See here for the steps: https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7#s9

M552 S0
ok
WiFi reported error: no known networks found
WiFi module is idle

M552 S1
ok
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
---
M558 S"^"
ok
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
---

Sadly, I am beginning to believe the board is dead.

Phaedrux

@crchisholm said in Unable to attach after network wireless IP change:

M558 S"^"

Did you really have ^ ? It should be *

Sadly, I am beginning to believe the board is dead.

There's nothing to indicate this. I think the problem is you just need to add your SSID name and password.

crchisholm

@Phaedrux Darn. To much going on. Yes. I did enter the ^ instead of the *. I guess my printer isn’t the only one with issues. I am away from my home computer so I will rerun these tomorrow.

Phaedrux

You can create a macro like this and place it in the /macros folder. Add your network name and password. Save it as addwifi

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

Then from the USB terminal send M98 P"addwifi"

crchisholm

@Phaedrux First off, I am not sure how to save this as a macro when I can't even get into the device.

I reran the three commands being more careful to avoid typos.....

WiFi module is idle
M552 S0
ok
WiFi reported error: no known networks found
WiFi module is idle
M552 S1
ok
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle

... repeats forever ....

M558 S"*"
ok
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle

... repeats forever ....