I am planning on using a Reach GPS module with a rover that will have no WiFi access point nearby for the most part. The device works just fine when it is connected to a WiFI access point, and also works fine if I tell it to enter hotspot mode then bring down the access point and connect to the Reach’s network.
But, if I boot up the Reach without an access point nearby that it knows how to connect to, I cannot access ReachView. It does create it’s hotspot network reach:XX:XX
, and I can connect to reach.local:5000
, where it prompts me to connect it to a WiFi access point.
Don’t know if this is at all related, probably not, but thought I would share it anyway. I am also still able to SSH into it. I did a bit of digging around, and I noticed that some systemd
modules were not loading correctly, namely nginx
(log sub-directory is non-existent), but I later noticed that the same modules were not loading when the system was working properly as well.
ReachView version: v2.4.0-r0 (updated/installed again today)
Firmware version: 2.3 (downloaded and flashed again today)
Is is possible to have the Reach enter hotspot mode on boot? With the intended application of the GPS, it would be a nuisance to have to connect it to a WiFi network every time to get it started.
Any help is greatly appreciated.