After some difficulties registering directly with the kinetic forums and being unable to reach anyone by email, I thought I would try here.
Basically, we are looking to receive TISB data through our unit. I know it is capable of doing so. We are building a piece of software to assist in tracking planes. The usual ADS-B transmissions are fine, but we are hoping to read TISB signals as well in the hopes that it will be sending information on planes that do not send ADS-B transmissions, which will hopefully allow us to track more planes as we are currently missing some that are important to us.
We currently read the BaseStation socket output on port 30003, however we have been unable to determine if there is any way to differentiate between TISB signals or otherwise, or even determine if we are actually receiving TISB signals.
We normally work with SBS-1 units, but are trying out an SBS-3 in order to see if this will get us the data we need. I should probably also mention that we are in the US, if that makes any difference. Any help in the right direction would be helpful. Thanks!
Hi and welcome to the forum, I have been able to figure out who you are from your email but I am sure that the forum users would like to know who we and us are, you are under no obligation to disclose that info.
I'm in the US area also. From what I gather, in reading about the FAA planing for the service you need to be in the air. I have not seen the antenna. I think its simular to the antenna they use for the aircraft internet service bongo.
Later
Jamie, sure thing. I work for a small company called Vector Airport Solutions. We are currently developing different solutions for tracking and logging aircraft to assist smaller airports.
Welcome.
Decoding TIS-B messages was a feature of Basestation 155 and a firmware update for the SBS-1eR. However, my understanding (from the UK) is that a TIS-B message are broadcast by ground stations and one must be within line of sight to receive them. The same applies to ADS-R messages (rebroadcast UAT messages).
To receive these messages, where available, you must set the message filtering in Basestation - Settings->Data Settings->Process TIS-B messages and/or Process ADS-R Messages.
There is now available an API for Basestation which may help.
http://www.kinetic.co.uk/DownloadFiles/API/KineticAPIDoc_102.pdf
Chris from Kinetic does visit this forum and, hopefully, he can expand on my reply?
Thank you Matt
Mattk,
If you use PlanePlotter from COAA, DF-18 reports (TIS-B and ADS-R) are shown in the aircraft list in the 'report type' column as type 11.
Note also that TIS-B positions are updated between once every three seconds and once every thirteen seconds.
Tom
Anmer, Thanks, I have done that. However, from what I can tell by reading the message format output on port 30003, as well as the SBS-3 API the messages are pretty much identical or at least I can not see any way to differentiate them. I know there must be otherwise the base station software would automatically receive them without having to turn an option on.
viking9, I will try the software for a while and see if we are at least receiving different data, which may work for us. But I am also looking for a way to differentiate the signals so I can code in the differences and process them differently if need be.
Quote from: mattk on June 05, 2012, 03:30:27 PM
Anmer, Thanks, I have done that. However, from what I can tell by reading the message format output on port 30003, as well as the SBS-3 API the messages are pretty much identical or at least I can not see any way to differentiate them. I know there must be otherwise the base station software would automatically receive them without having to turn an option on.
It's a public holiday here in the UK today (1776 was a better year for some ;D) and Kinetic may not be around until tomorrow.
If PP can differentiate the messages maybe you can too. What email address did you use for Kinetic?
mattk,
If DF=18, then the 3-bit CF (Code Format) field designates whether the ME field holds an ADS-B message or a TIS-B message. For DF=18 transmissions in which CF=0 or 1 (that is, DF=18 Extended Squitters that carry ADS-B Messages), the CF field also specifies what type of address is contained in the AA field. ADS-B Messages use Extended Squitter formats in which DF=17, or in which DF=18 and CF = 0 or 1.
TIS-B Messages use Extended Squitter formats in which DF=18 and CF is in the range from 2 to 5.
Tom
Anmer, thanks, I didnt realize it was a holiday today over there (I must not be paying attention).
viking, thanks, my searching had led me to something similar about the message formats and how they are sent. The current solution I am using parses the messages sent out on the socket output on port 30003 from the BaseStation software but I do not see anything in that output format to differentiate the signals. So I am not sure where to check for those fields you mentioned. I see that information might be contained in the raw output from the unit as described in the SBS3 API, but that might more of a code rewrite than I am looking for at the moment... but if its the only solution.
I guess I need to locate a TISB ground station and get line of sight so I can see if I am getting way more information that way than I currently am. Of course thats easier said than done.
I believe TIS-B can be distinguished from ADS-B by the aircraft ID which is sort of artificial then (starting with a T?). I can't remember the details, though, they are hidden somewhere on this forum.
No holiday here ???
http://www.radarspotters.eu/forum/index.php/topic,5791.0.html
My experience with it mattk.
Cheers
junglejet and kdt, thanks. That looks like it is what I am looking for, however, after reading through your thread kdt, it is a little discouraging as it appears that the TISB data does not include any identifiers for the planes, only their locations. Am I wrong in assuming that? As i mentioned earlier. I am trying to create a solution to track these planes, and if TISB wont tell me which planes they actually are, this wont be much use to me on the ground.
Examples DF-18 captured in the vicinity of a major airport.
90 34 23 45 28 00 06 34 5C 7F B9 00 00 00
90 34 41 D5 30 00 03 E9 B2 6E 84 00 00 00
90 34 34 09 30 00 06 29 28 80 7C 00 00 00
90 34 36 56 33 C9 D3 FE 30 6A 36 00 00 00
90 34 23 49 10 51 83 15 C3 58 20 00 00 00
90 34 23 49 28 00 06 31 B8 85 6E 00 00 00
90 34 41 CC 32 8F 23 F0 CE 74 AB 00 00 00
90 34 34 09 30 00 03 F5 CA 6C 22 00 00 00
90 34 36 56 33 D9 D6 31 6E 7E A2 00 00 00
90 34 36 54 32 DF 43 ED 28 6E 46 00 00 00
90 34 23 50 10 51 83 15 C7 28 20 00 00 00
90 34 23 51 10 51 83 15 C7 38 20 00 00 00
90 34 23 51 28 00 06 2D FC 7D 55 00 00 00
90 34 41 D5 12 0B 58 20 82 08 20 00 00 00
90 34 23 45 10 51 83 15 C3 18 20 00 00 00
90 34 23 45 28 00 06 34 5C 7F B9 00 00 00
90 34 34 09 30 00 06 29 28 80 7C 00 00 00
90 34 41 D5 30 00 03 E9 B2 6E 84 00 00 00
90 34 36 54 32 CF 46 20 B2 82 92 00 00 00
90 34 23 49 10 51 83 15 C3 58 20 00 00 00
90 34 23 49 28 00 06 31 B8 85 6E 00 00 00
90 34 42 09 30 00 06 2A 4E 86 07 00 00 00
90 34 41 04 12 4C 52 60 DE 08 20 00 00 00
90 34 34 09 30 00 03 F5 CA 6C 22 00 00 00
90 34 36 56 33 E9 E6 31 70 7E B1 00 00 00
90 34 41 D5 30 00 06 1D 44 82 D0 00 00 00
90 34 36 54 32 CF 43 ED 36 6E 41 00 00 00
90 34 23 4F 28 00 06 21 AA 81 C0 00 00 00
90 34 23 50 10 51 83 15 C7 28 20 00 00 00
90 34 23 51 10 51 83 15 C7 38 20 00 00 00
90 34 40 D3 12 40 14 01 83 88 20 00 00 00
90 34 34 09 30 00 06 29 28 80 7C 00 00 00
90 34 36 54 32 CF 46 20 C0 82 8D 00 00 00
90 34 40 D3 31 BF B6 30 20 7E 18 00 00 00
90 34 36 54 12 40 14 01 83 38 20 00 00 00
90 34 34 09 30 00 03 F5 CA 6C 22 00 00 00
90 34 41 CC 32 8F 23 F0 E2 74 A2 00 00 00
90 34 34 04 30 00 03 E6 68 74 24 00 00 00
90 34 40 D3 31 9F A3 FC E4 69 B0 00 00 00
90 34 34 09 12 40 14 01 83 2C 60 00 00 00
90 34 36 56 33 F9 F3 FE 36 6A 63 00 00 00
90 34 23 45 10 51 83 15 C3 18 20 00 00 00
90 34 23 45 28 00 06 34 5C 7F B9 00 00 00
90 34 36 54 32 BF 46 20 CA 82 8A 00 00 00
90 34 23 47 10 51 83 15 C3 38 20 00 00 00
90 34 23 47 28 00 06 3B EA 83 6B 00 00 00
JMGarcia, I am not sure what is represented by that data.
I actually went to a major airport and tried to capture some data, but I still ended up with only maybe 15-20% of the planes captured actually having location data. But to be honest, I wasnt even sure if I was picking up actual TISB data or not. I recorded the plane information directly from basestation and even captured some of the socket 30003 output, but again, just not sure if I am getting what I need, or if that data will even contain what I am looking for.\
Honestly, I am not even 100% sure what airports would even be sending the data. I visited the FAA's website and it said BWI, which is the airport I went to. But again, still not sure how to get the data, and whether the data will contain the information i need.
Catches are made in port 10001 directly read SBS-1eR unused BaseStation. I can read directly the SBS-1eR and decode the TCP frames sent by SBS-1eR. There is no possible filter that does not use BaseStation.
Some examples of DF-18 and some data:
DF TRAGET CF TC CALLSING CODE DF-18
18 3440D7 0 2 PAPA 20 90 34 40 D7 12 40 14 01 83 2C 20 00 00 00
18 343657 0 6 PAPA 6 90 34 36 57 30 00 03 E5 C8 6E 0E 00 00 00
18 343657 0 6 PAPA 6 90 34 36 57 30 00 06 19 6A 82 5E 00 00 00
18 344104 0 2 SEI 7 90 34 41 04 12 4C 52 60 DE 08 20 00 00 00
18 344104 0 6 SEI 7 90 34 41 04 30 20 00 08 B6 6F 20 00 00 00
18 344104 0 6 SEI 7 90 34 41 04 30 10 06 3B C2 83 69 00 00 00
18 344104 0 6 SEI 7 90 34 41 04 30 10 00 08 B6 6F 20 00 00 00
18 344104 0 6 SEI 7 90 34 41 04 30 00 00 08 B6 6F 1F 00 00 00
18 342345 0 5 TXLU01 90 34 23 45 28 00 06 34 5C 7F B9 00 00 00
18 342345 0 2 TXLU01 90 34 23 45 10 51 83 15 C3 18 20 00 00 00
18 342348 0 5 TXLU04 90 34 23 48 28 00 06 4C 0E 85 26 00 00 00
18 342349 0 2 TXLU05 90 34 23 49 10 51 83 15 C3 58 20 00 00 00
18 34234F 0 2 TXLU11 90 34 23 4F 10 51 83 15 C7 18 20 00 00 00
18 34234F 0 5 TXLU11 90 34 23 4F 28 00 06 21 AA 81 C0 00 00 00
18 34234F 0 2 TXLU11 90 34 23 4F 10 51 83 15 C7 18 20 00 00 00
18 342350 0 2 TXLU12 90 34 23 50 10 51 83 15 C7 28 20 00 00 00
18 342350 0 2 TXLU12 90 34 23 50 10 51 83 15 C7 28 20 00 00 00
18 342351 0 5 TXLU13 90 34 23 51 28 00 06 2D FC 7D 55 00 00 00
18 342351 0 2 TXLU13 90 34 23 51 10 51 83 15 C7 38 20 00 00 00
18 342351 0 5 TXLU13 90 34 23 51 28 00 06 2D FC 7D 55 00 00 00
18 342351 0 2 TXLU13 90 34 23 51 10 51 83 15 C7 38 20 00 00 00
18 342351 0 5 TXLU13 90 34 23 51 28 00 06 2D FC 7D 55 00 00 00
18 342351 0 2 TXLU13 90 34 23 51 10 51 83 15 C7 38 20 00 00 00
18 342351 0 5 TXLU13 90 34 23 51 28 00 06 2D FC 7D 55 00 00 00
18 342351 0 2 TXLU13 90 34 23 51 10 51 83 15 C7 38 20 00 00 00
18 342351 0 5 TXLU13 90 34 23 51 28 00 06 2D FC 7D 55 00 00 00