Flightradar24 decoder/feeder BETA testing (Win/RPi/Linux/OSX)

[piopawlu]

There's now a build 1.0.9-3 ready for all platforms. It fixes the crash when using 30003 port output under MS Windows and prevents termination of feeder if port 30003 cannot be used (in use by another app) on all platforms.

[Oblivian]

Works a treat now

But may still be limiting if the server cannot handle more than 3? simultaneous connections. I'm finding VRS server doing a re-attach check at times when there are no more slots free, so shuts down due to my database capture, Mode-S Mil update and VRS all connecting together.

[piopawlu]

I forgot to fix that,, will increase the number in the next build,, but this may be after xmas.

[awg]

I'm using build 1.0.9-3 on windows xp:

[time][i]Synchronizing time via NTP
[time][e]Time synchronized, offset -20.0143 seconds, drift +0.0000 seconds
[time][w]Clock drift -0.0071 is too high, suspending data feed

Is it normal?

[equi]

Try to adjust your XP (OS) clock and the message will disappear

[piopawlu]

This message indicates that your clock is drifting faster than the maximum allowed threshold. It does not matter if your system time is in sync as long as there is no significant drift. I will, however, try to make sure the drift detection is working correctly as it may give false positives at this point.

[awg]

System time is synced as far as I can see. Last sync this morning.

[piopawlu]

System time is synced as far as I can see. Last sync this morning.

Is that message repeating all the time or did it appear once? From what you quoted the time offset was more than 20 seconds off the NTP time at the time of sync.. Is it possible that your system clock is drifting that fast?

[awg]

Is that message repeating all the time or did it appear once? From what you quoted the time offset was more than 20 seconds off the NTP time at the time of sync.. Is it possible that your system clock is drifting that fast?

It appears every few minutes, but the clock seems always synced. There is a way to send you a complete log?

[piopawlu]

Not under Windows at the moment.. Can you tell me if the offset displayed by consequent syncs is changing?

[awg]

Not under Windows at the moment.. Can you tell me if the offset displayed by consequent syncs is changing?

I've rebooted the pc. First time syncing:

[time][i]Synchronizing time via NTP
[i]Removed 0 of 3 AC
[feed][i]sent 3 planes in 1 packets
[time][e]Time synchronized, offset +1.0984 seconds, drift +0.0000 seconds
[time][w]Clock drift -1.0773 is too high, suspending data feed

After some minutes:

[time][i]Synchronizing time via NTP
[feed][i]sent 3 planes in 1 packets
[i]Removed 0 of 5 AC
[time][e]Time synchronized, offset +1.0903 seconds, drift +0.0000 seconds
[time][w]Clock drift -0.0080 is too high, suspending data feed

[piopawlu]

You can ignore it for now.. I will try to investigate it further and get a new build after xmas.

[equi]

Have a look on this KB mate

http://support.microsoft.com/kb/821893

[eshabi]

I had this time drifting issue too (windows version). Rolled back to previous working version.

[loplo]

Micro$oft is "killing" the feeders
Switch to a Rpi or a Bananapi, it will save you money and no more headaches.