Hi,
I have a Hololens2 and I want to connect it with my RX Device to get RTK via NMEA Messages.
As far as I understand RX offers two Bluetooth Connections - Rfcomm with NMEA Messages and BLE for Emlid Flow in “binary Style”.
In the beginning I thought I could connect the RX Device with Emlid Flow via BLE to handle NTRIP and in addition connect the Hololens via Rfcomm so that I can receive the precise positioning.
But then I noticed (at least on my device) the rfcomm connection closes once I have connected the RX to Emlid Flow.
Now I am a little bit lost.
My question is:
Is it possible to bypass emlid flow and create a two way connection directly with the rx ? So I send data from my ntrip caster via hololens to the rx and receive then the desired accurate positioning?
Or can I receive raw data from the rx and calculate the correction with ntrip data on my own? (If this is even remotely possible)
Unfortunately there are no 3rd Party that I could use on Hololens afaik (Universal Windows Plattform).
Sound like you are building something fun! You can try to connect using Bluetooth Classic SPP, if it is available on Hololens. You can send correction data in RTCM3 format from your caster to that virtual COM port and the receiver will calculate the RTK solution for you and send back NMEA data. You don’t have to use Emlid Flow for this to work.
Bluetooth SPP is something I hadn’t considered before, thanks for the tip! It seems the HoloLens 2 doesn’t support this, though.
I could, however, use a PC or a Raspberry Pi in between. So let’s say instead of the HoloLens, I’m using a PC. I still don’t fully understand the device connections in your example. You mean I have a connection between the PC and the RX via a virtual COM port, and then I send the correction data from the caster via the PC to the rx and receive the NMEA data back? Do you have more information (an API or something) on how to communicate with the RX?
With Raspberry Pi you can pair and connect with Reach RX and that will create a tty port, from which you should see a stream of NMEA messages. If you send RTCM3 corrections to the same tty, Reach RX is going to parse them and apply to improve the accuracy of positioning. I am using Bluetooth SPP/virtual com/tty terms interchangeably as the naming might depend on the system or library that you end up using.
