Time delay on Basestation

[ANDYS]

Nice easy problem but I cannot remember how to get rid of it.

I have had to reinstall my Basestation and it now has the annoying 15minute(?) delay for certain flights.

Can anyone point me in the right direction to sort it?

Thanks in advance

Andy S

[Anmer]

Can you explain more about the "delay"?

How does this manifest itself?

[ANDYS]

Anmer,

thanks for the reply. As I understand it, when Basestation was first setting up, there was an inbuilt delay of 15 minutes so that it never showed the true picture of aircraft flying over. This was done for 'security' reasons.

At some point a patch was issued that fixed this issue.

Recently, I have had to reinstall my whole set up and did not even think of this issue. Everything seemed to be OK but today I noticed a USAF C130 flying my way. On Planeplotter and ADSB I could see it coming and I heard it coming over me hidden by the ever present cloud. However on my BS display it did not show at all. After the delay it duly showed up tracking as normal.

The patch was a simple affair and removes this delay.

Another thought has occurred as I am running an old version (1.2.4.184) I will update and see if this clears the issue.

Hope this makes things clearer and thanks for your help.

Andy S

[Anmer]

Thanks for that.

I've been using BaseStation since 2005 and never experienced any delay.  I do recall AirNav delaying it's shared data by 15 minutes but that had nothing to do with BaseStation.

BaseStation version 1.2.4.184 is tha last release, apart from 185 which is actually the same. 

Are you sure your C130 was the same aircraft that was showing on PP and ADS-B Exchange?

I assume other aircraft on BaseStation's map are/were in realtime?  If so, there's definitely nothing to fix.

[mhm]

I have to agree with Mike here I am using the latest edition of Base station. All aircraft passing overhead into Manchester match what is on my display.

[DaveReid]

Prior to version 1.2.3.145, which was a very, very long time ago (November 2009) the socket data sent to Port 30003 was subject to a 5-minute delay.

But that doesn't sound like what's happening here.

[Anmer]

Prior to version 1.2.3.145, which was a very, very long time ago (November 2009) the socket data sent to Port 30003 was subject to a 5-minute delay.

Thanks Dave.

But, correct me if I'm wrong, Basestation wasn't (normally) using data on port 30003?

[Ospreyv22]

Hi,

Just a thought but is your firmware up to date with Basestation.

Plus another trick to try is.

Open Device Manager on your pc.
A box will open, look down the list until you see (Ports(COM & LPT)
click on the little arrow at the side and that will open up.
Right click on each one of them and a box opens and click on update driver.

This worked for me a while back as my sbs is using the usb port on desktop and it updated the port.

Ian

[Anmer]

Just a thought but is your firmware up to date with Basestation.

If it worked before, the firmware should be OK and not a contributing factor.  Though a valid suggestion.

The key questions, already asked, are:

Are you sure your C130 was the same aircraft that was showing on PP and ADS-B Exchange?

I assume other aircraft on BaseStation's map are/were in realtime?  If so, there's definitely nothing to fix.

[ANDYS]

Thanks everyone for your inputs. I will keep an eye on the situation.

As Anmer said, all the other aircraft show up OK so everything should also be OK.

I will pray that we get some clear weather, wait for another C130 and see what I can see.

Thanks

Andy S

[Anmer]

Thanks.  My guess is there were two C130's.  One sending ADS-B data, the other not.

[mhm]

Best to put up FR24 and another like freedar to compare with SBS freedar does not block Military or private aircraft like some others

[DaveReid]

Prior to version 1.2.3.145, which was a very, very long time ago (November 2009) the socket data sent to Port 30003 was subject to a 5-minute delay.

Thanks Dave.

But, correct me if I'm wrong, Basestation wasn't (normally) using data on port 30003?

The socket data on 30003 was generated by Basestation, so yes, it was an output rather than an input.