AirNav Systems Forum

AirNav RadarBox and RadarBox24.com => AirNav RadarBox and RadarBox24.com Discussion => Topic started by: tarbat on July 08, 2009, 02:13:52 PM

Title: Port 30003 beta testing
Post by: tarbat on July 08, 2009, 02:13:52 PM
Any suggestions for other addons to test for SBS-1 compatible port 30003 output.  So far, I've got:
- Planeplotter
- sbsplotter
- sbssim

Important that we focus on testing the addons that will be most useful to Radarbox users, particularly with the 5-minute delay.  So, for example, there seems little point in testing BSAlert, since any alerts would appear 5-minutes late!!
Title: Re: Port 30003 beta testing
Post by: Allocator on July 08, 2009, 02:23:08 PM
I wanted to try JSTARS and the author was very keen to help with RB integration, but there just wasn't the rught info coming out of port 30003

http://jstars.altervista.org/
Title: Re: Port 30003 beta testing
Post by: tarbat on July 08, 2009, 02:28:05 PM
Okay, I'll try JSTARS.  Some success also with Overflight Logger, and at least now we can attach more than one program to the 30003 output.
Title: Re: Port 30003 beta testing
Post by: tarbat on July 08, 2009, 02:41:05 PM
Re: JSTARS.  Not too sure what to expect from this software, but appears to be detecting aircraft okay.  Any suggestions on what specifically I should test in JSTARS?

(http://farm4.static.flickr.com/3508/3700707063_64273f4505_o.jpg)
Title: Re: Port 30003 beta testing
Post by: Allocator on July 08, 2009, 06:00:24 PM
JSTARS looks to be working OK now, but I'm still playing with it as before it didn't work at all.

However, I'm not seeing any callsigns (Flight ID) - should these be coming via the port 30003 data.  I'm using Windows HyperTerminal to capture raw data too, and I can't see any callsigns here either.

Tatbat, what other port 30003 add-ons are you playing with?

Edit: Here is some log data from JSTARS.  I think that it is using its internal database to flag the operator, as shown for the EZY aircraft.

43C23F,null,ZR323,A109,,17:34:52,08/07/09
400DA0,null,G-DBCI,A319,,17:35:10,08/07/09
400A6B,null,G-EZED,A319,,17:35:38,08/07/09
400CD2,null,G-EZIS,A319,,17:35:45,08/07/09
40097C,null,G-EUUA,A320,,17:35:57,08/07/09
4006C4,null,G-VIIS,B772,,17:36:13,08/07/09
4004C9,null,G-DOCA,B734,,17:36:24,08/07/09
400A78,null,G-JEDR,DH8D,,17:36:26,08/07/09
A8637F,null,N64GG,B350,,17:39:56,08/07/09
4CA15C,null,EI-CVC,A320,,17:40:01,08/07/09
4009DB,null,G-EUUN,A320,,17:40:33,08/07/09
40089B,null,G-EZJB,B737,,17:40:34,08/07/09
8990D8,null,B-16709,B77W,,17:40:47,08/07/09
400A6B,null,G-EZED,A319,,17:40:56,08/07/09
405636,null,G-EZDH,A319,EZY - easyJet,17:41:12,08/07/09
4CA5D8,null,EI-RJV,B462,,17:41:12,08/07/09
76CD63,null,9V-SKC,A388,,17:41:14,08/07/09
400CD0,null,G-EZIP,A319,,17:41:24,08/07/09
4008F2,null,G-EUPY,A319,,17:41:32,08/07/09
4CA253,null,EI-DCS,B738,,17:41:47,08/07/09


And here is the raw port 30003 data captured using HyperTerminal

MSG,3,0,0,34134D,0,2009/07/08,17:37:05.906,2009/07/08,17:42:05.906,,14625,,,51.1421,-1.1189,,,,,,
MSG,3,0,0,400972,0,2009/07/08,17:37:05.906,2009/07/08,17:42:05.906,,11000,,,51.6210,-0.7513,,,,,,
MSG,3,0,0,400972,0,2009/07/08,17:37:05.906,2009/07/08,17:42:05.906,,11025,,,51.6220,-0.7513,,,,,,
MSG,3,0,0,400A14,0,2009/07/08,17:37:05.906,2009/07/08,17:42:05.906,,11800,,,51.5398,-0.8764,,,,,,
MSG,3,0,0,400A14,0,2009/07/08,17:37:05.906,2009/07/08,17:42:05.906,,11825,,,51.5391,-0.8759,,,,,,
MSG,3,0,0,400A7C,0,2009/07/08,17:37:05.906,2009/07/08,17:42:05.906,,7975,,,51.5903,-0.4341,,,,,,
MSG,3,0,0,400A7C,0,2009/07/08,17:37:05.906,2009/07/08,17:42:05.906,,8000,,,51.5896,-0.4325,,,,,,
MSG,3,0,0,495147,0,2009/07/08,17:37:05.906,2009/07/08,17:42:05.906,,5550,,,51.4529,-0.7406,,,,,,
MSG,3,0,0,4CA2A9,0,2009/07/08,17:37:05.906,2009/07/08,17:42:05.906,,11100,,,51.9045,0.0020,,,,,,
MSG,3,0,0,4D2024,0,2009/07/08,17:37:05.906,2009/07/08,17:42:05.906,,25350,,,52.4019,-1.0647,,,,,,
MSG,3,0,0,8003E4,0,2009/07/08,17:37:05.906,2009/07/08,17:42:05.906,,6900,,,51.6356,-0.0689,,,,,,
MSG,4,0,0,34134D,0,2009/07/08,17:37:05.906,2009/07/08,17:42:05.906,,,,,,,,,,,,
MSG,4,0,0,4006C4,0,2009/07/08,17:37:05.906,2009/07/08,17:42:05.906,,,210.8,256.6,,,1152,,,,,
MSG,4,0,0,400972,0,2009/07/08,17:37:05.906,2009/07/08,17:42:05.906,,,306.0,4.7,,,2112,,,,,
MSG,4,0,0,400972,0,2009/07/08,17:37:05.906,2009/07/08,17:42:05.906,,,307.1,4.9,,,2112,,,,,
MSG,4,0,0,40097C,0,2009/07/08,17:37:05.906,2009/07/08,17:42:05.906,,,269.9,263.2,,,-256,,,,,
MSG,4,0,0,400A14,0,2009/07/08,17:37:05.906,2009/07/08,17:42:05.906,,,349.1,151.2,,,3072,,,,,
MSG,4,0,0,400A7C,0,2009/07/08,17:37:05.906,2009/07/08,17:42:05.906,,,266.5,131.0,,,64,,,,,
MSG,4,0,0,400A7C,0,2009/07/08,17:37:05.906,2009/07/08,17:42:05.906,,,267.2,129.2,,,0,,,,,
Title: Re: Port 30003 beta testing
Post by: tarbat on July 08, 2009, 06:22:24 PM
Problem with callsign missing already reported to A..  The port 30003 "ID" messages had an extra space character in them ("ID ").

I'm sucessfully running Overflight Logger v3.3, and that also appears to be working okay, but with missing callsigns.  Unfortunately the skies in northern Scotland are very quiet today, so not a lot to test with :(

Local vs. UTC timestamps is causing a problem with Planeplotter, but again that's been reported to A. and will be fixed.  SBS-1 outputs local times on port 30003, not UTC.

The Overflight Logger colour-coded altitude reception map (I need more aircraft, please send some north!!!):

(http://farm3.static.flickr.com/2511/3702064184_cc45a482b2_o.jpg)


Some other addons to test are listed at http://www.homepages.mcb.net/bones/Kinetic/Utilities/Kinetic_Utilities5_Utils.htm
Title: Re: Port 30003 beta testing
Post by: Allocator on July 08, 2009, 06:58:48 PM
I keep getting a debug error message with Overflight Logger, but it was working fine until that point. I'm using MS Office 2007.

Maybe it's because I've got so much traffic down here near Heathrow - lol

Title: Re: Port 30003 beta testing
Post by: tarbat on July 08, 2009, 07:01:31 PM
I'm also using Office 2007.  Did you install and register the OSWINSCK DLL?
http://www.ostrosoft.com/oswinsck.asp
Title: Re: Port 30003 beta testing
Post by: Allocator on July 08, 2009, 07:12:35 PM
Yep, did that.

I seem to remember that I had the same problem last time I tried this.  You get the error message and the choices are to Debug, or stop running.

EDIT: OK, I think that I've found the problem.  The 'log to html' was on and trying to log to a non-existent directory.
Title: Re: Port 30003 beta testing
Post by: tarbat on July 08, 2009, 07:31:39 PM
Glad you got it working.  It's actual quite a useful addon.
Title: Re: Port 30003 beta testing
Post by: Allocator on July 08, 2009, 07:32:46 PM
Overflight Viewer working nicely now :-)

You can see the EGLL climbouts to the SW and one of the holds to the NE.

Title: Re: Port 30003 beta testing
Post by: tarbat on July 09, 2009, 06:31:54 PM
JSTARS appears to be fully working now.  Allocator, do you have a registered version to fully test this out?

(http://farm3.static.flickr.com/2493/3704247421_99ae9f4288_o.jpg)
Title: Re: Port 30003 beta testing
Post by: tarbat on July 09, 2009, 06:36:54 PM
And Overflight Logger is working perfectly apart from the missing Flight IDs.  Here's a days worth of logging showing the Altitude Map.  Clearly shows Inverness and Aberdeen approach and departure traffic.

(http://farm3.static.flickr.com/2462/3704255531_4aa9b78ef2_o.jpg)
Title: Re: Port 30003 beta testing
Post by: Allocator on July 09, 2009, 08:49:46 PM
JSTARS appears to be fully working now.  Allocator, do you have a registered version to fully test this out?

I've paid for the registration, but no response from the author yet.
Title: Re: Port 30003 beta testing
Post by: Allocator on July 09, 2009, 08:54:05 PM
But I am getting Flight ID's now with the latest exe.
Title: Re: Port 30003 beta testing
Post by: tarbat on July 09, 2009, 08:58:32 PM
Yep.  Looks like JSTAR gets the Flight IDs from the ID messages, whereas other addons like Planeplotter and Overflight Logger get Flight ID from the MSG,1 messages.

Its all a bit of a mess really.  Shame Airnav's port 7879 format couldn't be adopted by Kinetic!!
Title: Re: Port 30003 beta testing
Post by: Allocator on July 09, 2009, 09:01:23 PM
Yep.  Looks like JSTAR gets the Flight IDs from the ID messages, whereas other addons like Planeplotter and Overflight Logger get Flight ID from the MSG,1 messages.

Its all a bit of a mess really.  Shame Airnav's port 7879 format couldn't be adopted by Kinetic!!

Ha! nice one :-)

I've just emailed the JSTARS author direct regarding the registration codes.  Maybe he's away at the moment.
Title: Re: Port 30003 beta testing
Post by: Allocator on July 09, 2009, 09:03:12 PM
A short JSTARS log output with Flight ID data.

40048E,null,G-BPED,B752,,21:52:08,09/07/09
405635,EZY6454,G-EZDF,A319,,21:52:10,09/07/09
8990D5,EVA68,B-16706,B773,,21:52:46,09/07/09
34134C,IBE3168,EC-HAG,A320,,21:53:17,09/07/09
A4380D,null,N371FP,GLF4,,21:53:31,09/07/09
400934,BAW769,G-EUPX,A319,,21:54:14,09/07/09
40068F,BAW31,G-CIVN,B744,,21:54:17,09/07/09
400901,BMA772,G-WWBM,A332,,21:54:21,09/07/09
3C4D63,null,D-ACKC,CRJ9,,21:54:29,09/07/09
4910D3,NJE362A,CS-DFS,C560,,21:54:49,09/07/09
3C4D63,DLH7YW,D-ACKC,CRJ9,,21:55:24,09/07/09
405B65,null,G-EZDL,A319,EZY [U2] easyJet,21:55:55,09/07/09
3C6585,DLH5NV,D-AILE,A319,,21:56:03,09/07/09
400A66,BMA919,G-MEDJ,A321,,21:56:08,09/07/09
71BC04,KAL908,HL7404,B744,,21:57:14,09/07/09
4CA2DB,null,EI-DLO,B738,,21:57:28,09/07/09
405B65,EZY175A,G-EZDL,A319,EZY [U2] easyJet,21:57:28,09/07/09
4CA2DB,RYR419,EI-DLO,B738,,21:57:28,09/07/09
3C1194,DLH1AR,D-AVRB,B462,,21:58:20,09/07/09
400AF7,EZY47CE,G-EZAM,A319,,21:58:35,09/07/09
4007FA,BAW15,G-YMMO,B772,,21:58:36,09/07/09
400AF7,EZY76YS,G-EZAM,A319,,21:58:46,09/07/09
473401,WZZ543L,HA-LPA,A320,,21:58:48,09/07/09
4CA1D4,RYR2BY,EI-DAN,B738,,21:58:48,09/07/09
49D04E,CSA648,OK-CGK,B735,,21:58:59,09/07/09
4CA286,null,EI-FXE,AT43,,21:59:09,09/07/09
400620,null,G-BTPA,ATP,,21:59:14,09/07/09
4CA1B4,RYR5952,EI-DAE,B738,,21:59:38,09/07/09
400A34,EXS232Q,G-CELB,B733,,21:59:52,09/07/09
400F43,null,G-FBEB,E195,,22:00:05,09/07/09
4CA1F1,null,EI-DAT,B738,,22:00:17,09/07/09
4CA1F1,RYR1285,EI-DAT,B738,,22:00:26,09/07/09
300063,AZA209,I-BIXG,A321,,22:00:48,09/07/09
400620,NPT572,G-BTPA,ATP,,22:01:36,09/07/09
400DA0,BMA4LN,G-DBCI,A319,,22:01:36,09/07/09
Title: Re: Port 30003 beta testing
Post by: Tallyho on July 09, 2009, 10:54:45 PM
Any suggestions for other addons to test for SBS-1 compatible port 30003 output.  So far, I've got:
- Planeplotter

Tarbat did you get this new version working with PP, I tried but failed, the only option that got some sporadic output was MODE S source RB TCP?
Title: Re: Port 30003 beta testing
Post by: tarbat on July 10, 2009, 07:33:22 AM
Tarbat did you get this new version working with PP, I tried but failed, the only option that got some sporadic output was MODE S source RB TCP?

Yes, tested and working with the following input options:
1. SBS1 tcp (port 30003)
2. RadarBox tcp (port 7879)

As expected, it doesn't work with the RadarBox 30003 input option, because the port 30003 output is now SBS1 compliant.

Obviously there's now a 5-minute delay on both port 7879 and 30003 output.  So:

1. You'll need a value > 5min in the "Omit Aircraft After".  I used 7min for testing.

2. Predicted aircraft positions will be innacurate where an aircraft isn't in straight level flight.
Title: RB Millog v1
Post by: tarbat on July 10, 2009, 07:53:27 AM
RB Millog v1

Another one tested out and working.  Successfully auto-uploaded all my military flights to http://www.live-military-mode-s.eu/ using live upload:

(http://farm3.static.flickr.com/2670/3705944983_4832a84465.jpg) (http://www.flickr.com/photos/tarbat/3705944983/sizes/o/)
Title: Re: Port 30003 beta testing
Post by: tarbat on July 10, 2009, 10:19:32 AM
Side-by-side view of RB and PP showing the same flights:

(http://farm3.static.flickr.com/2585/3706140411_8e1b323171_m.jpg) (http://www.flickr.com/photos/tarbat/3706140411/sizes/o/)

Obviously the 5 minute delay on the tcp port causes some problems with the position prediction routine in PP for aircraft manouvering or on approach/departure.
Title: Re: Port 30003 beta testing
Post by: tarbat on July 11, 2009, 06:00:36 PM
Okay, with the new beta, both Planeplotter and Overflight Logger are now seeing Flight IDs on port 30003.  So both these addons appear to work perfectly with port 30003 output.
Title: Re: Port 30003 beta testing
Post by: AirNav Development on July 11, 2009, 06:07:41 PM
Great. We plan to release the public V3.0 Beta Patch 1 this Wednesday so please test it as much as you can until then.
Title: Re: Port 30003 beta testing
Post by: Allocator on July 12, 2009, 08:24:48 AM
JSTARS V1.2.1 registered working well :-)

Is the port 30003 data live rather than delayed with V3.0 Beta Patch 1?  JSTARS seems to detect the aircraft at the same time as I get the RB alert.
Title: Re: Port 30003 beta testing
Post by: tarbat on July 12, 2009, 08:26:54 AM
I think JSTARS uses the ID messages which are LIVE on port 30003.  All MSG type messages are still 5 minutes delayed.
Title: Re: Port 30003 beta testing
Post by: Allocator on July 12, 2009, 08:37:05 AM
Ahhh.., OK, that's good news :-)