I’m wondering what I’m suddenly doing wrong using a Postcard and PointPerfect NTRIP corrections. I had this setup working flawlessly on two different Postcards getting great accuracy and then after working on some other projects for the last month I came back to them this week and suddenly I can’t get anything better than a Single GPS fix with SW Maps (doesn’t even go into Float).
The postcard is running v3.3 with the A06 firmware on the LG290P. SW Maps is version 1.4. I sucessfully connect to the Postcard via Generic NMEA (Bluetooth LE), and successfully connect to the Point Perfect correction service and shows a data stream. The GPS never gets out of single fix and accuracy stays the same as non-corrected. I’ve tried this both on a iOS device and an Android device and get the same results. I have reset the Postcard to factory settings with no change.
What might else I be missing? All I can think of is SW Maps upgraded from 1.3 to 1.4 in the interim. Thanks in advance!
It’s very possible that upgrading SW Maps caused the problem. That’s happened on several occasions in the past. For me, the last known working version of SW MAPS was 1.3.0
BTW: I select “SparkFun RTK” as the Instrument Model in SW MAPS, maybe that will help ya?
I’ll upgrade to the latest and test some PostCards this weekend.
I suspected it was SW Maps, but then I gave the demo version of SurPad a try this morning and that didn’t work either (it still stayed in single mode). I then reset the postcard to factory settings, increased the priority for the bluetooth correction to the top of the list and now I’m in float mode. I dug my second postcard out and did all the same things and I’m also now getting float from that one too, and even had a fix for a few seconds but I can’t get it to go back to being fixed. The antenna is in the wide open seeing ~27-36 satellites. The base distance reported by NTrip is about 6 miles.
For kicks, I updated the firmware for one of the postcards to 2.01 and I’m not seeing any improvement on that one.
I’ve used both “SparkFun RTK” and Generic as the Instrument Model in SW Maps, doesn’t seem to make much of a difference.
Since you’ve reset to factory defaults, ya might want to adjust the NMEA rates again. It’s easy to overload the 2-way Bluetooth link and cause dropped(incomplete) RTCM corrections, which means more time is spent in Float.
IMHO, the defaults are way too aggressive and don’t contribute to the solution in a meaningful way - but rather the opposite.