Using the 1.8 image for a C2, I generated a customized installation for my development rig.
Raspberry Pi 3 with 5V power adapter
microSD created with Etcher
PiTFT LCD with appropriately patched config.txt file with driver
Robo board rev 2.1.4 with USB Type B cable
19V power brick
This is then a highly-mobile rig which allows me to visit numerous hotspot zones to test this connectivity.
What did you expect to happen?
Upon entering the Utilities -> Network -> Configure Wi-Fi screen, I expected to see one or more available wi-fi zones.
What happened instead?
The interface never discovers any zones for this version. I took the rig to multiple sites and it was not able to discovery any zones. This includes the cellphone hotspot for my iPhone right next to it.
Additionally, I removed/replaced a microSD clone of an earlier image (Version 1.3.3 -> master) for my printer, placing it in this same rig and it was able to see the wifi routers for the same zones. The problem seems to be following the new code or the generation method in roboGenesis.
Further troubleshooting can help to decide whether the generation method is at fault or if it is something in the 1.8 image itself.
BUG
What were you doing?
Using the 1.8 image for a C2, I generated a customized installation for my development rig.
This is then a highly-mobile rig which allows me to visit numerous hotspot zones to test this connectivity.
What did you expect to happen?
Upon entering the Utilities -> Network -> Configure Wi-Fi screen, I expected to see one or more available wi-fi zones.
What happened instead?
The interface never discovers any zones for this version. I took the rig to multiple sites and it was not able to discovery any zones. This includes the cellphone hotspot for my iPhone right next to it.
Additionally, I removed/replaced a microSD clone of an earlier image (Version 1.3.3 -> master) for my printer, placing it in this same rig and it was able to see the wifi routers for the same zones. The problem seems to be following the new code or the generation method in roboGenesis.
Further troubleshooting can help to decide whether the generation method is at fault or if it is something in the 1.8 image itself.
Branch & Commit or Version of OctoPrint
roboOS_1.8.1-c2.0.robo-c2
Printer model & used firmware incl. version
Robo C2