Will Depart in...
Started by blueskydriver, January 14, 2018, 04:01:20 AM
0 Members and 2 Guests are viewing this topic.
Quote from: RayS on May 10, 2022, 08:57:18 AMEverything works on this Avidyne EX5000 MFD except the Altitude data. Took it for a flight last night to test the LAT/LON conversion accuracy. It's spot-on.I have a whole bunch of ARINC-429 test gear on the way to help me figure out how to get ALT data into this thing....
Quote from: RayS on May 10, 2022, 04:36:03 PMI've tried the Following: $GPGGA,210230,3855.4487,N,09446.0071,W,1,07,1.1,370.5,M,-29.5,M,,*$GNGGA,001043.00,4404.14036,N,12118.85961,W,1,12,0.98,1113.0,M,-21.3,M*However I think the $GPGGA and $GNGGA is for Fixes and not for Ownship, as the Avidyne doesn't show any altitude info using $GPGGA. (It does correctly show everything else in that sentence and instead of the center target being an aircraft outline, it's just a white + sign.I would so much rather do this through the NMEA protocol rather than ARINC429, but I think this MFD is unique in that it gets ALT/HDG data from the EXP5000 PFD, then it's processed as TAWS data in the MFD.
Quote from: RayS on May 10, 2022, 07:24:25 PMThanks for checking those sentences. Both of them parse and are accepted by the Avidyne without issue.If the incoming NMEA data isn't valid the unit will report "Nav Source Data Format Error", or "Nav Data is NOT Valid!"(Maybe that parser needs the checksum as well?)Regardless, I'll keep experimenting with it but I suspect you are correct in that the unit won't accept altitude data from a GPS source because of the margin for error.
Quote from: ame on May 10, 2022, 10:25:59 PMThe two randomly chosen online parsers probably do expect a checksum. I'm surprised that your instrument accepts NMEA strings without them
Page created in 0.124 seconds with 36 queries.