PORT 30003

lambertw · February 15, 2009, 03:24:51 PM

Am I correct in understanding that all live data from port 30003 on the new V2.1 upgrade will be delayed by 5mins.

AirNav Support · February 15, 2009, 03:26:23 PM

Yes again this has been mentioned many times before.

Tramline · February 15, 2009, 04:13:55 PM

Am I the only person who has no idea what Port 30003 is?

I just plug in the USB into my Laptop and it works. Being a technonumpty I sit here unable to take part in the discussion or understand what Port 30003 means for the 'user'.

Can someone explain the gist of 30003 in very simple terms?

Thanks.

tarbat · February 15, 2009, 04:28:53 PM

The position of all aircraft received by your Radarbox hardware is output on TCP port 30003. A port is like a pipe that lets data be passed from one program to another.

This enables other programs, such as Squawkbox and Planeplotter, to use that data. So, Squawkbox uses the port 30003 data to display the textual interpretation of the aircrafts squawkcode, and Planeplotter uses the port 30003 data to display the aircraft positions.

jgrloit · February 15, 2009, 04:33:32 PM

Only Msg 3 - positional data is currently passed through Port 30003.
I have asked that the Other message types, that include Sqwark information are added - on a future upgrade.
The MSG data information is listed on another site, mentioned in another thread.
I found it by hunting for socket data and following a link to :-
http://www.homepages.mcb.net/bones/index.htm and looking at article 2.

jmhayes · February 15, 2009, 09:22:05 PM

Quote from: AirNav Support on February 15, 2009, 03:26:23 PM
Yes again this has been mentioned many times before.

Have you announced a feature list for v2.1?

Lou · February 16, 2009, 09:34:37 PM

Why is port 30003 being 5 min delayed? will that mean that Squawkbox and programmes like Planeplotter will also be time delayed ? Regards Lou

jgrloit · February 16, 2009, 10:00:37 PM

I have asked if non-positional data, could if Port 30003 data is delayed as planned, be moved to another undelayed port.
This should enable SQWarkbox to show ALL translated SQWARK details, ond NOT compromise the intention of the positional delayed data.

Andy Frost · February 16, 2009, 10:21:21 PM

Yes jgrloit, I will be able to change SquawkBox to read a different port in which non-positional live aircraft details are output. Presumably this will be added to version 2.1 at the same time as port 30003 data is delayed. It was first raised here http://www.airnavsystems.com/forum/index.php?topic=1714.15

What is rather a shame though is that output of positional information has to be delayed even if it is just used for the purpose of a third-party software relaying that information back to the same user that provided that positional information in the first place. For example, SquawkBox displays a live 3D view of a user's flights in Google Earth using port 30003 data. The issue here is really one of preventing a third-party software from relaying live positional information further to others on a network, which we've heard would break the security restrictions on such data.

One idea might be to go along the route taken by Google Maps. Each third-party software that wants to use Google Maps has to apply for a key first. If that third-party software "misbehaves" then Google Maps can revoke that key, so blocking that software from accessing their maps.

DaveReid · February 17, 2009, 11:23:34 AM

Quote from: Andy Frost on February 16, 2009, 10:21:21 PMYes jgrloit, I will be able to change SquawkBox to read a different port in which non-positional live aircraft details are output. Presumably this will be added to version 2.1 at the same time as port 30003 data is delayed.

With luck, you shouldn't have to do that. AirNav have stated that the port 30003 output is supposed to emulate the equivalent SBS port output (so that add-on applications work without modification) and that the current RB output is a work-in-progress.

From that I infer (and hope) that RB V2.1 will feature a fully-compatible port 30003 output, but so far AirNav support have neither confirmed or denied that, despite several requests - maybe they would care to comment this time around?

For info, the non-delayed SBS socket messages are AIR (new hex code) and ID (new callsign). You will be aware that neither, alas, contains the squawk.

Dave

OKC-Steve · February 19, 2009, 01:00:38 AM

Maybe a programmer can tell us:

Does the boolean bits on the end of the socket data really work?

They should be alert, emergency, spi, and onground.

It looks like they just stay 0??

Thanks,

Steve

DaveReid · February 19, 2009, 08:51:32 AM

I don't recall having seen Alert, Emergency or Ident bits set. Could change with V2.1.

And I certainly haven't seen an OnGround bit, but then I wouldn't expect to from my location.

robbieinderry · February 19, 2009, 12:05:29 PM

Quote from: AirNav Support on February 15, 2009, 03:26:23 PM
Yes again this has been mentioned many times before.

thanks for explaining port 30003 where do i dowmload SquawkBox from
please reply before this post is locked lol.

Andy Frost · February 19, 2009, 12:18:24 PM

Robbie, you can find SquawkBox at http://www.gfrost.co.uk/SquawkBox, it needs the .Net framework pre-installed (there's a link on the website) to run. You'll need to pre-install Google Earth if you want to use those specfic features of SquawkBox.

robbieinderry · February 19, 2009, 08:20:35 PM

Quote from: Andy Frost on February 19, 2009, 12:18:24 PM
Robbie, you can find SquawkBox at http://www.gfrost.co.uk/SquawkBox, it needs the .Net framework pre-installed (there's a link on the website) to run. You'll need to pre-install Google Earth if you want to use those specfic features of SquawkBox.

sorry for the last post,i deleted it.
andy i have squawbox-connected its says waiting for flights,it was working ok
the first time,doing something wrong now.
robbie