Planeplotter problem

[DoctorM]

Been trying to link up my box to PP, without any luck. Ive followed the airnav guide and the one by John, but cant get it to show the aircraft im picking up.

I can receive fine.

All I get when i click start on PP is "processing ANRB log data".

Am I missing something like a patch or sharing file?

Thanks

Doc

[tarbat]

If you're running ANRB v3.01 beta, then the best input option for Planeplotter is "Radarbox tcp".  That uses data on port 7879.  Also ensure that you have an "Omit Aircraft After" setting of > 5 minutes (I use 7 mins).

If you're using ANRB v2, then use the input option "Radarbox v2 30003".

[DoctorM]

Thanks for the reply, working fine using the Radarbox TCP setting.

Mucho appreciated.

I think the Airnav setup web page needs updating with this info.

Doc

[DoctorM]

Hello again

For some reason the aircraft callsigns and squawks arent showing up on Planeplotter, yet they are showing fine on my radarbox.

Everything else is showing fine, position, speed, altitude etc.

If anyone knows of any fix, it would be greatly appreciated.

Thanks

Dunk

[DaveReid]

For some reason the aircraft callsigns and squawks arent showing up on Planeplotter, yet they are showing fine on my radarbox.

Everything else is showing fine, position, speed, altitude etc.

If anyone knows of any fix, it would be greatly appreciated.

The port 7879 output definitely has provision for the callsign, so if it's showing on your RB screen then it's being sent to PlanePlotter.  It's 5 minutes delayed, of course, so you won't see it on PP until it's been on the RB screen for 5 minutes.

Squawk, OTOH, always appears as "000" in the port 7879 output, so PlanePlotter can't display it until AirNav fix that bug.

[viking9]

It's 5 minutes delayed, of course, so you won't see it on PP until it's been on the RB screen for 5 minutes.

Not totally true Dave, except for local traffic. If PP has sharing on then a user will often see an aircraft on the PP screen long before it apears live on RB. He will also see most non-positional flights on PP long before they appear on RB as they do not appear on the RB network at all.

Tom

[DaveReid]

Not totally true Dave, except for local traffic.

But the only traffic that's output on port 7879 is local traffic.

[tarbat]

For some reason the aircraft callsigns and squawks arent showing up on Planeplotter, yet they are showing fine on my radarbox.

Planeplotter definately does show the callsign.  See this comparison screenshot of Planeplotter side-by-side with Radarbox.  Using port 7879.

[DoctorM]

Thanks again, ive checked the port is correct, but nothing doing, very odd!

[DaveReid]

Thanks again, ive checked the port is correct, but nothing doing, very odd!

What versions of RadarBox and PlanePlotter are you running ?

[DoctorM]

Hi

ive got 3.01b on the RB and version 5.4.2.1 on PP

have the following boxes ticked on PP:

input - mode s/ads-b
mode s source - radarbox tcp
output data - log sbs
udp/ip output - mode s
dde output - mode s

[DaveReid]

ive got 3.01b on the RB and version 5.4.2.1 on PP

have the following boxes ticked on PP:

input - mode s/ads-b
mode s source - radarbox tcp
output data - log sbs
udp/ip output - mode s
dde output - mode s

OK, and can you confirm that when you run NetStat in a DOS box, you can definitely see the port 7879 connection ?

[DoctorM]

yup its there:

TCP 127.0.0.1:7879 Dunk2009:65151 Established

[viking9]

Make sure that only 'ModeS/ADS-B' and 'UDP/IP data from net' are the only ones checked in Input Data.

[tarbat]

have the following boxes ticked on PP:
input - mode s/ads-b
mode s source - radarbox tcp
output data - log sbs
udp/ip output - mode s
dde output - mode s

Only difference to my setup is that I don't have any PP outputs ticked.

Also, make sure your "Omit Aircraft After" setting is > 5mins - I use 7 minutes.