5
$\begingroup$

I am decoding Compact Position Reporting (CPR) positions from ADS-B frames (the airborne position and surface position frames).

Most of my results give realistic longitude/latitude values, but some return things like 0,781518968485169 177,220642089844; or 1,76377118644068 -0,664306640625; or 2,12129237288136 -2,838134765625.

I have a feeling like I must be missing some kind of validation or some kind of frame type identification. Where can I find more information about the decoding process?

Improve this question
$\endgroup$
6
  • 2
    $\begingroup$ I think some people are unfamiliar with ADS-B and didn't realize that your question had to do with transponder signal coding. $\endgroup$
    – J W
    Commented Jan 21, 2016 at 12:25
  • $\begingroup$ Welcome to Aviation.Se! $\endgroup$
    – DeltaLima ♦
    Commented Jan 22, 2016 at 11:39
  • $\begingroup$ Do you use global decoding or local decoding? $\endgroup$
    – DeltaLima ♦
    Commented Jan 22, 2016 at 11:40
  • $\begingroup$ Can you explain how you do the decoding, it is impossible to see from result what is wrong. $\endgroup$
    – DeltaLima ♦
    Commented Jan 23, 2016 at 9:04
  • $\begingroup$ Are you using a specific library like Dump1090 - we are having similar issues lately $\endgroup$
    – Jeef
    Commented Nov 3, 2017 at 10:40

1 Answer 1

Reset to default
2
$\begingroup$

We were decoding Airborne Position frames having TypeCode 0, 9-18 and 20-22. Apparently, frames with TypeCode 20-22 and possibly 0 have to be decode a different way.

(For now I think that I get enough information out of TypeCode 9-18 frames so I'll just skip the other ones.)

Improve this answer
$\endgroup$
4
  • 1
    $\begingroup$ Type codes 20-22 have the same coding as 9-18, all are Airborne Position messages. 19 is Velocity, there is no CPR in there. 0 is a "no position message", there is basically only altitude in there. 1-4 is identity & emitter type. 5-8 is surface position & velocity. 5-8 have a slightly different position coding than 9-18,20-22. $\endgroup$
    – DeltaLima ♦
    Commented Jan 22, 2016 at 11:38
  • 1
    $\begingroup$ In addition, if you see type 20-22 I'd expect there is something wrong with your receiver or decoder as these messages are really, really rare. $\endgroup$
    – DeltaLima ♦
    Commented Jan 22, 2016 at 11:38
  • $\begingroup$ Sorry I mistyped '8-19' for '9-18'. We don't receive 20-22 now, but why would that mean there is something wrong. $\endgroup$
    – TTT
    Commented Jan 22, 2016 at 14:09
  • 1
    $\begingroup$ 20-22 has very high position integrity which is not achieved with current day avionics. $\endgroup$
    – DeltaLima ♦
    Commented Jan 22, 2016 at 15:55

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .