Hi,
I’ve been testing rtcm ntrip server in tcp settings, via WiFi “ap” I have managed to connect a client once for a few seconds, but 99% of the time, the postcard reboots on client connection.
Postcard with portability shield
Running on good charged battery
RTk e v 2.2
Gnss firmware v5
SW maps connects for a few seconds showing correction data before crashing.
I’m wondering if I have too much stuff going on? Maybe stop the NMEA or something?
thanks for advice
Yes, you are probably on the right track for your specific question. These multi-band chips deal with a lot of information. It’s helpful to turn OFF all messages that are not important to your application.
I’d use the NTRIP Client in SW Maps instead.
Let the PostCard do positioning stuff, and SW Maps handle the NTRIP connection.
You’ll already have a Bluetooth connection from Smartphone-to-PostCard anyway for the data pipe.
If you have an application that requires a “headless” RTK unit (no data collector), then the built-in Client in RTK Everywhere is neat. IMHO, that’s it’s main use case.
Hi there, great info, thanks. I’m getting a stable service now I’ve turned off the NMEA strings. SW Maps seems to connect and stay alive now.
However, if I try using NTRIP Checker app (really useful BTW), it crashes and reboots, so maybe it’s sending something the postcard doesn’t like.
Make sure you’re using BLE mode for the BT on your Iphone