Port 30003 beta testing

tarbat · 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!!

Allocator · July 09, 2009, 09:01:23 PM

Quote from: 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!!

Ha! nice one :-)

I've just emailed the JSTARS author direct regarding the registration codes. Maybe he's away at the moment.

Allocator · 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

Tallyho · July 09, 2009, 10:54:45 PM

Quote from: 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

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?

tarbat · July 10, 2009, 07:33:22 AM

Quote from: Tallyho on July 09, 2009, 10:54:45 PMTarbat 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.

tarbat · 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:

tarbat · July 10, 2009, 10:19:32 AM

Side-by-side view of RB and PP showing the same flights:

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.

tarbat · 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.

AirNav Development · 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.

Allocator · 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.

tarbat · 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.

Allocator · July 12, 2009, 08:37:05 AM

Ahhh.., OK, that's good news :-)