What is wrong with the statistics?
- Thread starter Falcon
- Start date
We made some changes to standardise it across all clients as some people were unfairly "gaming" the system. This was mainly PlanePlotter based users.
Other instances were people using the same share code on multiple machines.
Ideally you will be on our new client and this has the best decoding and therefore the best chance for stats!
You can download the latest version on http://planefinder.net/sharing
All of the top sharers use this client
Other instances were people using the same share code on multiple machines.
Ideally you will be on our new client and this has the best decoding and therefore the best chance for stats!
You can download the latest version on http://planefinder.net/sharing
All of the top sharers use this client
Last edited:
The new client is not supported on Windows XP and should not have installed in the first place.
Not even Microsoft are supporting Windows XP now!
Not even Microsoft are supporting Windows XP now!
The older clients are being phased out as they caused incorrect data to be inserted into the systems and we will be requiring people to be on the latest client I'm afraid.
Sorry but we cannot support this, we tend to go by support from the manufacturers. I notice you are using 30003 as a data format inout which we will be getting rid of soon too. Please switch to a raw data format.
Beast Binary or AVR-TCP will work fine, I think VRS can output this too. You will find the 30003 option gone in the latest version of the client
Oz Wald
New Member
@Lee Armstrong - Hi, I see from the installation instructions under sharing that the current sharecode can't be used with the latest client. Does this mean that you become, in effect a new user and have to wait 30 days to see the relative strength of the set up?
Yes that is correct. The PlanePlotter share codes are not long enough for the amount of sharers we have!
Oz Wald
New Member
@Lee Armstrong Thanks. Since yesterday, client has received 6 (failed) remote requests to restart per minute before reporting the normal updates. Is this a result of the master system upgrade?
I haven't updated my client yet and only found out about the update while checking to see if there were any system glitches.
I haven't updated my client yet and only found out about the update while checking to see if there were any system glitches.
Not sure on that point, the server will send down a restart of the client request if the system time is really far off. Don't post any share codes here but suggest contacting [email protected]
Actually, I just see you in the list and your client is the latest version already so I wouldn't worry.
https://planefinder.net/sharing/receiver/88677
Oz Wald
New Member
@Lee Armstrong Well, that's odd. I just did the update, opened up the log viewer and saw the expected failure messages and then got:
1 established message
notice of 84 aircraft updates
a failed remote restart request
verification of location
Then nothing.
I checked the config of RTL1090 against the settings and RTL was set to port 31012, client to 31001 (set both to 31001)
Client reported 12645 updates sent
Then nothing.
Think I'm headed to support town!
1 established message
notice of 84 aircraft updates
a failed remote restart request
verification of location
Then nothing.
I checked the config of RTL1090 against the settings and RTL was set to port 31012, client to 31001 (set both to 31001)
Client reported 12645 updates sent
Then nothing.
Think I'm headed to support town!
@airbus340 We found some issues with the latest windows version of the client. You can download the old one from the website. (3.0.2080). Please give this a go.
Thank you very much Lee! I am sorry I was wrong, I only restart my old radar laptop once in a while and thats it, so I forgot that it is really Windows 7 and not XP as I said... Since I checked all out and changed to the correct format it has all been working perfect without crashes. So maybe it crashed because I had wrong format? Do you still want me to go back to the version you mention or can I stay with the new version?
Something else while I write, is there an explanation about how the statistics on the sharer list works? In the client web browser it say that I send about 2,5 million messages to you per day and as I understand in the list it is positions that counts. Every day when I go to bed I check the list to see what number I am at in the list and how many positions I have in total and every morning I wake up and check again and it is always less than in the evening before... So it is very difficult to climb in the ranking...
Something else while I write, is there an explanation about how the statistics on the sharer list works? In the client web browser it say that I send about 2,5 million messages to you per day and as I understand in the list it is positions that counts. Every day when I go to bed I check the list to see what number I am at in the list and how many positions I have in total and every morning I wake up and check again and it is always less than in the evening before... So it is very difficult to climb in the ranking...
We found a bug in the Windows version so for now roll back to 3.0.2080. Chances are a new version will be out tomorrow as we've had some excellent assistance from @Oz Wald
The 2.5 million is what you locally decode. Every 10 seconds the latest data is aggregated and sent to the server and everyone there is on a level playing field. Granted it does favour those in busy areas I.e. London but it gives a rough idea on things. I'd start a new thread on optimising your setup. There are a few things you can do such as antenna placement or buying a dedicated ADS-B receiver.
The 2.5 million is what you locally decode. Every 10 seconds the latest data is aggregated and sent to the server and everyone there is on a level playing field. Granted it does favour those in busy areas I.e. London but it gives a rough idea on things. I'd start a new thread on optimising your setup. There are a few things you can do such as antenna placement or buying a dedicated ADS-B receiver.
