You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a SimpleRTK2B Pro board from Ardusimple with the esp32-xbee WiFi module.
I'm using Locus GIS on Android as the GPS client.
Here's what works: connecting the base station to u-center and setting up the server through u-center allows me to connect Locus GIS to the u-center server and get an RTK Fixed solution.
However, when using the WiFi module, I cannot get Locus GIS to stay connected through either the caster or the server.
The messages that I've setup on the SimpleRTK2B Pro board are the same as the ones enabled for u-center (on for USB and UART2), the ESP32-XBEE is configured to use UART2.
Here's the example for 1005, it's the same config for all other RTCM messages
This is a screenshot of Locus GIS working through the u-center server:
I'm not sure if I'm configuring something wrong or if I'm missing something.
Any help appreciated.
Thanks in advance.
The text was updated successfully, but these errors were encountered:
Hello,
I have a SimpleRTK2B Pro board from Ardusimple with the esp32-xbee WiFi module.
I'm using Locus GIS on Android as the GPS client.
Here's what works: connecting the base station to u-center and setting up the server through u-center allows me to connect Locus GIS to the u-center server and get an RTK Fixed solution.
However, when using the WiFi module, I cannot get Locus GIS to stay connected through either the caster or the server.
The messages that I've setup on the SimpleRTK2B Pro board are the same as the ones enabled for u-center (on for USB and UART2), the ESP32-XBEE is configured to use UART2.
Here's the example for 1005, it's the same config for all other RTCM messages
This is a screenshot of Locus GIS working through the u-center server:
I'm not sure if I'm configuring something wrong or if I'm missing something.
Any help appreciated.
Thanks in advance.
The text was updated successfully, but these errors were encountered: