Hello, first I introduce myself since it is my first intervention in this forum. My name is Pedro, I am from Spain, I have an ultralight plane and I like to fly and program my own instruments for my plane.
I am building the Bluetooth adapter to be able to send the autopilot information from Skydemon to an old TRUTRAK DIGIFLIGHT II autopilot but it is not capable of recognizing the NMEA sentences that the Skydemon sends it.
I have been analyzing the NMEA sentences that the Garmin GPSMAP 296 GPS sends and they are like this:
$GPRMC,111231,A,4041.3941,N,00036.84755,W,0.0,227.3,190225,0.8,W,D*11
$GPRMB,A,0.00,R,,EDNT,4859.7560,N,01053.0926,E,656.923,44.7,,V,D*41
$GPRMC,111232,A,4041.3941,N,00036.84755,W,0.0,227.3,190225,0.8,W,D*12
$GPRMB,A,0.00,R,,EDNT,4859.7560,N,01053.0926,E,656.923,44.7,,V,D*41
$GPRMC,111233,A,4041.3941,N,00036.84755,W,0.0,227.3,190225,0.8,W,D*13
$GPRMB,A,0.00,R,,EDNT,4859.7560,N,01053.0926,E,656.923,44.7,,V,D*41
However, the NMEA sentences that Skydemon currently throws are like this:
$GPRMC,111343,A,41$GPRMB,A,0.76,R,OR$GPRMC,111344,A,41$GPRMB,A,0.76,R,OR$GPRMC,111345,A,41$GPRMB,A,0.76,R,OR$GPRMC,111346,A,41$GPRMB,A,0.76,R
That is, the NMEA frames of the Skydemon are missing all the information fields and also do not end with CR+LF (0x0D + 0x0A) so the TRUTRAK autopilot is not able to interpret the NMEA sentences correctly.
Could you please check and correct it.
PD.-
Thank you very much Tim for having implemented the new Bluetooth functions, it is something that has been needed for a long time to be able to use Skydemon as the main route planning source.