Am I correct in understanding that all live data from port 30003 on the new V2.1 upgrade will be delayed by 5mins.
Yes again this has been mentioned many times before.
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.
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.
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.
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?
Why is port 30003 being 5 min delayed? will that mean that Squawkbox and programmes like Planeplotter will also be time delayed ? Regards Lou
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.
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.
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
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
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.
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.
Robbie, you can find SquawkBox at http://www.gfrost.co.uk/SquawkBox (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.
Quote from: Andy Frost on February 19, 2009, 12:18:24 PM
Robbie, you can find SquawkBox at http://www.gfrost.co.uk/SquawkBox (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
Quoteandy i have squawbox-connected its says waiting for flights,it was working ok
the first time,doing something wrong now.
Robbie, do you have flights with positional data (Lat/Lon) in your RadarBox MyFlights table? If not SquawkBox will not report any flights, it only outputs live flights where the positions are known. Otherwise what has changed since you first ran SquawkBox and you had it working? Have you tried restarting SquawkBox or RadarBox?
Quote from: DaveReid on 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.
Looking at a recording of the socket, it looks like they just stick some zero's on there to match the number of elements expected.
My suggestion to RB central would be to make the groundspeed and groundtrack a floating-point XXX.X or 1 digit accuracy, and to populate the boolean bits with actual data.
Course when they go to a 5 minute delay, maybe the socket won't be used.
Thanks Andy will try it in the morning, on live flights.
thanks again.
Quote from: OKC-Steve on February 19, 2009, 10:16:07 PM
Course when they go to a 5 minute delay, maybe the socket won't be used.
The socket output will still be available - I believe that it was just a programming error that resulted in it being live rather than 5 minutes delayed - as it has been in all the earlier versions of RB.
andy.
got it up and working, i like the squawk box its brilliant,and the Google earth is great
far better than the radar box map,thanks for that andy.your a star