Ken McGuire

Next thing to try is an android device connected to the node and see what it says. This will tell us whether it is the firmware of the app. To...

It could be either the firmware or the app, it is most likely not TinyGPS++ since the position report in the log is correct. Sorry I have no clue about...

I don't do IOS, I looked at my android app and don't see a spot for heading, so help needed from someone with a clue about IOS. I might be...

@garthvh so your display is correct where you are the US, whereas @paoloponzano has an incorrect display in Italy. Also Imperial vs metric units, but degrees are the same in...

If your friends are using LiliGo boards, and it's not an Imperial vs. Metric issue, and the heading is only displayed on iPhone/iPad, then I have to believe that it...

The firmware does some rudimentary sanity checks, TinyGPS++ sets course to 0 if the RMC sentence has a bad checksum, and GPS.cpp will log a warning if the course >360....

I have setup a NMEA simulator and connected it to my Chatter 2. I set the position to roughly @paoloponzano 's location and the Heading to 90 degrees. Works ok...

@paoloponzano I was able to borrow my wife's iPhone and using my NMEA simulator I injected position data into my Chatter 2 node. I set the position to roughly your...

The u-blox standard precision product line can be roughly divided into 2 categories, Pre F9/M9 and post F9/M9. The F9/M9 generation (Chip type 9140) introduced the VALSET/VALGET/VALDEL key value pair...

Just built an ran your code, there is a corner case that you need to address, that is when the GPS is asleep and you use the user button to...