About the scanner thing, it’s not that simple and there is no way you could feed this data directly into the mic-in of your computer. Just check the ModeS specification and your sound card sampling rate + scanners are generally focused on receiving audio and not digital transmission, it’s not acars.

A couple of times they’ve promised OSX software for the SBS-1, but never delivered.

According to their support downloads page, they’ve release a firmware update that gets rid of the data transmission delay. Since I think the delay requirement was what caused them to encrypt the control mechanism in the first place, the removal a delay require removes the need for encryption?

So they could un-encrypt, publish the interface specs and the linux/OSX worldwide community could have the software written in about 7 days (and 7 lines of PERL code).

Or should we just all go out and buy scanners that receive 1090MHz, feed the audio into the Mac’s mic port and write some software to decode from there? Makes the cost of the SBS-1 look a bit outrageous, doesn’t it?

I’ve had mine about 2 years now, sitting in the cupboard waiting for them to produce the long-promised OSX software. :^(

Instead having to have work-arrounds – SBS-1 should be produced Mac compatible!

Is anyone still working on the project, or done???

I have the RadarBox and was wondering if anyone had written anything for OS-X that I could play with?

Keep up the good work!

The first 5 bits are the downlink format (DF) code, but combined with the next 3 bits, make it a byte boundary.

DF11 (01011XXX) is different than DF4, and 5, in that the 24 bit ICAO address comes next, while in DF4, 5 it comes last.

On DF4, 5 the next data is a 5 bit data field, followed by a 6 bit data field, followed by a 13 bit data field. Again, this makes it run on a byte boundary.

Course, this example is encrypted, so we don’t know whether it is a DF4,5, or 11 in there. DF17, 20, and 21 are Long Messages (112 bits).

All this is available on the internet under the ICAO Annex 10 Volume IV publication.

I think Piotr probably has a handle on that!

4060CE

The message starts at byte number eight and the 56 bits looks like this:

01001010100110101101000000011000001100111001010110010011

The first 18 bits are the control section (transponder capabillities and stuff), the next 24 is the ICAO Hex and the last 14 bits are supposed to be parity bits (but they dont make sense to me in this message).

So sorry Max for jumping to conclusions.

That’s what I like about standards–there’s so many of them!!