AirNav RadarBox
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
 


« previous next »
Pages: 1 [2] 3

Author Topic: Post 30003 socket output format/emulation/compatibility  (Read 41649 times)

0 Members and 1 Guest are viewing this topic.

DaveReid

  • Hero Member
  • *****
  • Posts: 1815
    • Heathrow last 100 ADS-B arrivals
Re: Post 30003 socket output format/emulation/compatibility
« Reply #15 on: June 28, 2009, 12:32:26 PM »
Quote from: Harry on June 28, 2009, 11:57:58 AM
I have been away for a few months from this forum and I cannot find the answer in all the messages with the release of Beta 3: is airnav going to do something about the socket output or not?

As far as I can see, there's no change to the socket output in the 3.0 Beta, so it would seem unlikely that it's going to be in the released version.

But given that AirNav have been asking detailed questions about the format, and about its incompatibility with the SBS spec that it's supposed to be emulating, I'm reasonably optimistic that it will be addressed at some stage.
Logged
This post has been scanned for any traces of negativity, bias, sarcasm and general anti-social behaviour

Fenris

  • Guest
Re: Post 30003 socket output format/emulation/compatibility
« Reply #16 on: June 28, 2009, 12:39:23 PM »
I thought that it was supposed to be modified to only time delay positional messages, not those without position information.
Logged

DaveReid

  • Hero Member
  • *****
  • Posts: 1815
    • Heathrow last 100 ADS-B arrivals
Re: Post 30003 socket output format/emulation/compatibility
« Reply #17 on: June 28, 2009, 12:44:10 PM »
Quote from: Fenris on June 28, 2009, 12:39:23 PM
I thought that it was supposed to be modified to only time delay positional messages, not those without position information.

That was certainly suggested, but I don't recall any undertaking being made to implement it.
Logged
This post has been scanned for any traces of negativity, bias, sarcasm and general anti-social behaviour

jmhayes

  • Jr. Member
  • **
  • Posts: 62
Re: Post 30003 socket output format/emulation/compatibility
« Reply #18 on: June 28, 2009, 03:32:42 PM »
Quote from: DaveReid on June 28, 2009, 12:32:26 PM
As far as I can see, there's no change to the socket output in the 3.0 Beta, so it would seem unlikely that it's going to be in the released version.
I think the big change between v2.1 and v3.0 is that the non-positional aircraft are finally available.  It's still kind of a curious mess, but it's way better than it was.
Logged

DaveReid

  • Hero Member
  • *****
  • Posts: 1815
    • Heathrow last 100 ADS-B arrivals
Re: Post 30003 socket output format/emulation/compatibility
« Reply #19 on: June 28, 2009, 04:24:51 PM »
Quote from: jmhayes on June 28, 2009, 03:32:42 PM
I think the big change between v2.1 and v3.0 is that the non-positional aircraft are finally available.  It's still kind of a curious mess, but it's way better than it was.

You're absolutely correct, I hadn't picked up on that.
Logged
This post has been scanned for any traces of negativity, bias, sarcasm and general anti-social behaviour

Fenris

  • Guest
Re: Post 30003 socket output format/emulation/compatibility
« Reply #20 on: June 28, 2009, 04:55:06 PM »
Quote from: jmhayes on June 28, 2009, 03:32:42 PM
Quote from: DaveReid on June 28, 2009, 12:32:26 PM
As far as I can see, there's no change to the socket output in the 3.0 Beta, so it would seem unlikely that it's going to be in the released version.
I think the big change between v2.1 and v3.0 is that the non-positional aircraft are finally available.  It's still kind of a curious mess, but it's way better than it was.

And are these non-positional aircraft records 5 min delayed or not?
Logged

jmhayes

  • Jr. Member
  • **
  • Posts: 62
Re: Post 30003 socket output format/emulation/compatibility
« Reply #21 on: June 28, 2009, 04:58:55 PM »
Quote from: Fenris on June 28, 2009, 04:55:06 PM
are these non-positional aircraft records 5 min delayed or not?
All data on port 30003 is 5-minute delayed in v3.0 beta.
Logged

Fenris

  • Guest
Re: Post 30003 socket output format/emulation/compatibility
« Reply #22 on: June 28, 2009, 05:00:51 PM »
OK, so that will break Squawkbox then...
Logged

tarbat

  • ShipTrax Beta Testers
  • Hero Member
  • *
  • Posts: 4219
    • Radarbox at Easter Ross
Re: Post 30003 socket output format/emulation/compatibility
« Reply #23 on: June 28, 2009, 05:49:29 PM »
Quote from: Fenris on June 28, 2009, 05:00:51 PM
OK, so that will break Squawkbox then...

Squawkbox works okay with v3.0, albeit 5-min delayed.  Maybe this might get implemented - http://www.airnavsystems.com/forum/index.php?topic=1284
Logged

Harry

  • Jr. Member
  • **
  • Posts: 98
Re: Post 30003 socket output format/emulation/compatibility
« Reply #24 on: July 02, 2009, 09:57:32 AM »
Thanks for the feedback.

Is it me or are only hexcodes with call signs on the port output?

Harry


Quote from: DaveReid on June 28, 2009, 04:24:51 PM
Quote from: jmhayes on June 28, 2009, 03:32:42 PM
I think the big change between v2.1 and v3.0 is that the non-positional aircraft are finally available.  It's still kind of a curious mess, but it's way better than it was.

You're absolutely correct, I hadn't picked up on that.
Logged

tarbat

  • ShipTrax Beta Testers
  • Hero Member
  • *
  • Posts: 4219
    • Radarbox at Easter Ross
Re: Post 30003 socket output format/emulation/compatibility
« Reply #25 on: July 02, 2009, 09:59:53 AM »
I get aircraft without callsigns on port 30003, using v3.0 beta.  Maybe not in v2.0
Logged

Harry

  • Jr. Member
  • **
  • Posts: 98
Re: Post 30003 socket output format/emulation/compatibility
« Reply #26 on: July 02, 2009, 10:10:27 AM »
Quote from: tarbat on July 02, 2009, 09:59:53 AM
I get aircraft without callsigns on port 30003, using v3.0 beta.  Maybe not in v2.0

Ok. thanks. I'm looking at port 7879 right now, so maybe there is a differance.

Harry
Logged

tarbat

  • ShipTrax Beta Testers
  • Hero Member
  • *
  • Posts: 4219
    • Radarbox at Easter Ross
Re: Post 30003 socket output format/emulation/compatibility
« Reply #27 on: July 02, 2009, 10:47:15 AM »
Are you running v2.0 or v3.0 beta.  Looking at port 7879, I also see aircraft without callsigns/FlightIDs.

EG:
<MODESMESSAGE>
  <DATETIME>20090702103928</DATETIME>
  <MODES>A8BD53</MODES>
  <ALTITUDE>10700</ALTITUDE>
  <VRATE>0</VRATE>
  <AIRSPEED>000</AIRSPEED>
  <LATITUDE>0</LATITUDE>
  <LONGITUDE>0</LONGITUDE>
  <SQUAWK>000</SQUAWK>
</MODESMESSAGE>
Logged

AirNav Development

  • AirNav Systems
  • Hero Member
  • *****
  • Posts: 2545
    • AirNav Systems
Re: Post 30003 socket output format/emulation/compatibility
« Reply #28 on: July 04, 2009, 10:32:58 AM »
We are happy to announce that RadarBox V3.0 Beta - Patch 1 is now fully compatible with SBS-1 output messages. We changed the way this is processed so all messages will be worked when they are received straight from the box. All formats mentioned above are support including AIR, ID and SEL messages.

We are passing a test exe to 2 beta testers and waiting for their feedback.
Logged

DaveReid

  • Hero Member
  • *****
  • Posts: 1815
    • Heathrow last 100 ADS-B arrivals
Re: Post 30003 socket output format/emulation/compatibility
« Reply #29 on: July 04, 2009, 10:40:22 AM »
Quote from: AirNav Development on July 04, 2009, 10:32:58 AM
We are happy to announce that RadarBox V3.0 Beta - Patch 1 is now fully compatible with SBS-1 output messages. We changed the way this is processed so all messages will be worked when they are received straight from the box. All formats mentioned above are support including AIR, ID and SEL messages.

That's very good news indeed.
Logged
This post has been scanned for any traces of negativity, bias, sarcasm and general anti-social behaviour
Pages: 1 [2] 3
« previous next »