The device does not seem to send position messages. SW Maps is able to connect to the device in either Rover or Base mode but in either mode, the status is blank and the skyplot is blank. Tried several Android devices with the same result on all.
The ESP FW on the device is 3.3 and the u-blox firmware is HPG 1.32.
All that shows up in the serial console when connected to the ESP32 port is battery Voltage and Accuracy, no NEMA messages. The menus work fine too.
Everything looks great in u-center . The GPS/u-blox part is clearly working. I am also able to connect to the ESP via WIFI, though the save settings feature seems to only work sometimes. It appears that all the hardware is working but there is no output.
Hi @StuartFrancis,
Please check you have the standard five NMEA messages enabled - the surveying defaults. They may have been turned off?
https://docs.sparkfun.com/SparkFun_RTK_ … _messages/
You won’t see the NMEA messages through the ESP32 Serial Console, only via a Bluetooth terminal:
https://docs.sparkfun.com/SparkFun_RTK_ … bluetooth/
I hope this helps,
Paul
I have done a bit more investigation. I have tried turning on NEMA messages both through the web interface and through the serial console. I have also tried the defaults, and as a resort, enabling all messages. Still not seeing anything on Bluetooth. I have tried connecting with two Android devices, an iPhone (int BLE mode) and a Mac computer using QGIS. All successfully pair and connect but don’t receive data. I have not had luck with Wndows 10 and the serial over Bluetooth. It will pair but not connect. This seems to be a Windows thing based on some online research.
I enabled display of position information in the ESP console and it is correctly showing position, so the position data is clearly making it from the UBlox to the ESP. I can further try enabling the NEMA messages and verifying the '1’s in the web interface to make sure they are on, but I suspect there is something else going on. I also tried down revving the UBlox firmware and re updating it. No luck with ether firmware version.
Right now, I’m out of ideas… Sorry! You seem to be doing everything correctly.
I’ll ask Sparky if he has seen this issue before.
Best wishes,
Paul
Issue resolved. The problem was that the Bluetooth/Ext Cntr dip switch on the front of the board was not set to Bluetooth.
I found another forum post with the same symptoms but, in that case, it was the PPS/NEMA switch on the back.
Excellent detective work - glad that’s working for you,
Paul
Yep - that switch can get moved. Sorry for the hassle. I recommend a piece of tape or other permanent/partially permanent fastener to keep it from happening when you least expect it!