Wifi 2 SPI Timeout

[elmoret]

Tagging @dc42 @T3P3Tony - does this board need exchanging?

[krohelm]

This morning I downgraded the main firmware to 2.03 just to rule out any weirdness with a mismatched function from the 2.03 wifi firmware. Same sad state unfortunately. What information can I provide to help?

[krohelm]

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

I just went through all the network library again and saw this little footnote. So I read the gcode that came out of the configurator and noticed that it does not use a M552 S0. So I added

; Network
M552 S0                                  ; Put wifi in idle mode.  If you don't do this apparently it does not start up.

and it does connect now. I don't know why the module does not seem to turn on with the configurator-provided M552 S1 but hey it turns on now and I can reach the web interface.

[A Former User]

Curious was this all done through config.g and not the serial port?

Important! Do not use M587 within config.g. As well as being a security hazard, writing the access point parameters to WiFi chip every time you start the Duet may eventually wear out the flash memory. Also, the wifi module does not get enabled until the end of running config.g. It is better to use a macro to send M587 (source: https://forum.duet3d.com/post/42798)

[krohelm]

The firmware configuration tool spat out m587 into config.g yes. Through trial and much error I took it out and ran that via serial. The m587 seems to have been somehow poisoning the startup of the wifi chip.

[A Former User]

Thats unfortunate. Wonder how that could be adressed to avoid others experiencing the same thing.

At least you got it working in the end though!

[dc42]

@krohelm said in Wifi 2 SPI Timeout:

The firmware configuration tool spat out m587 into config.g yes. Through trial and much error I took it out and ran that via serial. The m587 seems to have been somehow poisoning the startup of the wifi chip.

The firmware config tool should not put M587 commands in config,g. We're looking into it.

[A Former User]

Could introduce wifi.g to be executed after config.g if no networks are stored in the wifi module maybe? Would simplify the setup being able to put it all on the sd card, and it could even reconnect if you for some reason replace the wifi module.

[dc42]

@bearer said in Wifi 2 SPI Timeout:

Could introduce wifi.g to be executed after config.g if no networks are stored in the wifi module maybe? Would simplify the setup being able to put it all on the sd card, and it could even reconnect if you for some reason replace the wifi module.

Leaving your network password on the SD card is a security risk. Don't do it.

[krohelm]

@dc42 said in Wifi 2 SPI Timeout:

Leaving your network password on the SD card is a security risk. Don't do it.

In fact this is the only reason it occurred to me to remove from config.g. If that data were not somewhat sensitive I would have left it and never found the solution.

A oneshot.g or something could work though - read once and deleted by the firmware. Or just decline to provide the m587 at all and let users find the command. I'm sure you're more than capable of doing the right thing for rrf on this minor issue. Thanks for looking into it!