I am using an Reach RTK and a M+ Side by Side for testing and only experience this problems on the M+. The classic Reach one works fine with all the same settings.
I use NTRIP Client for Correction Input and also Position output via Bluetooth.
I use the newest DEV Version 2.17 on both.
When I connect on the M+, It starts normally, but after 3-4 seconds it stops collecting data from my phone and it starts to switch between “Timeout” and “connected to host”. When I disconnect in NTRIP Client, this continues for some period of time and only stops when I switch to the Bluetooth tab (I guess some updating is happening then). After that I get the "Recv error (111) which would be expected when I disconnect.
On the Reach RTK with 2.17, all this works fine as always. Correction input works and when I disconnect on my phone in NTRIP Client, I get the "REcv error (111) immediatly.
This time it was a little different. It did continue to say “connected to local host” even though the status page said single and the NTRIP client app said “no data”
