Plane Finder Client Beta 4 (3.0.2080)

Status
Not open for further replies.
Lee Armstrong

Lee Armstrong

Administrator
Staff member
Hello everyone,

The latest version is 3.0.2080 and can be found here along with a change log which we will keep updated there too.

This will probably be the final beta and we will possibly block access from older versions soon as this one contains some important fixes under the hood.

Highlights of this release are...
  • MLAT now supported with Radarcape receivers
  • Fixes an issue with data coming from an upcoming FlightAware Dump1090 modification
For those who want the commands for the update it is simply..
Code: 
wget http://client.planefinder.net/pfclient_3.0.2080_armhf.deb
sudo dpkg -i pfclient_3.0.2080_armhf.deb

A huge amount of work for this version has gone into the Radarcape version and that can be updated by the following command.
Code: 
opkg install http://client.planefinder.net/pfclient_3.0.2080_armel.opk
 
Updated both of my RPis. Thanks for the ongoing development! Ever since updating from the old-original pfclient, these various beta versions have been running with no issues for me.

Marty
 
@Lee Armstrong:
Updated both RPis. Thanks, Working fine.

RPi B+ (Receiver 87809)
Code: 
2015-07-04 09:49:26.471968 User location has been verified.
2015-07-04 09:49:21.554892 Successfully sent 39 aircraft updates over the past minute (3.00kb)
2015-07-04 09:48:29.8519 TCP connection established: 127.0.0.1:30005
2015-07-04 09:48:29.2184 Web server is now listening on: http://192.168.2.17:30053
2015-07-04 09:48:29.1327 Echo port is now listening on: 192.168.2.17:30054
2015-07-04 09:48:28.982527 user_longitude = -79.xxxxxx
2015-07-04 09:48:28.982378 user_latitude = 43.xxxxxx
2015-07-04 09:48:28.982226 web_server_port = 30053
2015-07-04 09:48:28.982106 select_timeout = 10
2015-07-04 09:48:28.981986 aircraft_timeout = 30
2015-07-04 09:48:28.981862 data_format = 1
2015-07-04 09:48:28.981741 tcp_port = 30005
2015-07-04 09:48:28.981617 tcp_address = 127.0.0.1
2015-07-04 09:48:28.981475 connection_type = 1
2015-07-04 09:48:28.980663 pfclient (3.0.2080 armhf) started with the following options:


RPi Model2 (Receiver 87806)
Code: 
2015-07-04 09:55:25.142245 User location has been verified.
2015-07-04 09:55:02.673998 Successfully sent 72 aircraft updates over the past minute (4.00kb)
2015-07-04 09:54:09.652643 TCP connection established: 127.0.0.1:30005
2015-07-04 09:54:09.649430 Echo port is now listening on: 192.168.2.27:30054
2015-07-04 09:54:09.648917 Web server is now listening on: http://192.168.2.27:30053
2015-07-04 09:54:09.646451 user_longitude = -79.xxxxxx
2015-07-04 09:54:09.646390 user_latitude = 43.xxxxxx
2015-07-04 09:54:09.646324 web_server_port = 30053
2015-07-04 09:54:09.646280 select_timeout = 10
2015-07-04 09:54:09.646235 aircraft_timeout = 30
2015-07-04 09:54:09.646192 data_format = 1
2015-07-04 09:54:09.646148 tcp_port = 30005
2015-07-04 09:54:09.646100 tcp_address = 127.0.0.1
2015-07-04 09:54:09.646036 connection_type = 1
2015-07-04 09:54:09.645464 pfclient (3.0.2080 armhf) started with the following options:
 
runs smoothly. great work.

2015-07-06 09:26:00.331206 Successfully sent 288 aircraft updates over the past minute (20.00kb)
2015-07-06 09:24:55.703691 Successfully sent 287 aircraft updates over the past minute (19.00kb)
2015-07-06 09:23:51.653392 Successfully sent 197 aircraft updates over the past minute (14.00kb)
2015-07-06 09:23:13.96170 User location has been verified.
2015-07-06 09:22:58.390321 TCP connection established: 127.0.0.1:30005
2015-07-06 09:22:58.386005 Web server is now listening on: http://192.168.1.42:30053
2015-07-06 09:22:58.384923 Echo port is now listening on: 192.168.1.42:30054
2015-07-06 09:22:58.343198 user_longitude = 14.xx
2015-07-06 09:22:58.343052 user_latitude = 51.xx
2015-07-06 09:22:58.342897 web_server_port = 30053
2015-07-06 09:22:58.342776 select_timeout = 10
2015-07-06 09:22:58.342659 aircraft_timeout = 30
2015-07-06 09:22:58.342537 data_format = 1
2015-07-06 09:22:58.342415 tcp_port = 30005
2015-07-06 09:22:58.342289 tcp_address = 127.0.0.1
 
I'm having an issue with this client and the latest version of the dump1090_mutability fork (with mlat forwarding enabled). I see this message frequently:

Code: 
Data too far away for 30003 data format: 671591.874193, A5E0D3

Will this be addressed in a future client update?
 
Matt Dodd said:
I'm having an issue with this client and the latest version of the dump1090_mutability fork (with mlat forwarding enabled). I see this message frequently:

Code: 
Data too far away for 30003 data format: 671591.874193, A5E0D3

Will this be addressed in a future client update?
Click to expand...
Yes and no!

30003 is data already decoded and in our tests we have seen a lot of decoders compromising our data quality so we don't allow aircraft that are past what the ADS-B spec defines for max range. For example that looks quite some distance away from your current location!

The "fix" for you is to switch to Beast Binary format on port 30005 from Dump1090. You will see extra information as well that you don't get from Dump1090 such as the auto pilot data.
 
Hi,
What about receivers provided by your team, must we update it ?? Because may be one time by week, the blue box receivers turn off, and need to unplug the RPI to have all working again.
 
Ye
Riad GUERDOUD said:
Hi,
What about receivers provided by your team, must we update it ?? Because may be one time by week, the blue box receivers turn off, and need to unplug the RPI to have all working again.
Click to expand...
Yes we are slowly making our way through and updating them all.
 
Okay , will try this later , currently feeding via PP on a old Macbook PRO 17 ,
eh , need apply sharing code ?
 
hi everybody
I hope I'm right here with my problem

... my first post is a little problem with plane finder client 3.0 (2080)
sometimes (see copy of log) the Client hangs ? after this error he don't reconnecting with dump1090!

.......................................................................................
2015-07-26 00:32:44.754684 Decoder select timeout occurred, restarting...
2015-07-26 00:08:34.264155 Failed to establish a data proxy connection. Receiver data cannot be sent!
2015-07-26 00:08:34.264155 Failed to connect to all known addresses for host: 'dataupload.planefinder.net'
2015-07-25 22:37:44.73553 Failed to establish a data proxy connection. Receiver data cannot be sent!
2015-07-25 22:37:44.73553 Failed to connect to all known addresses for host: 'dataupload.planefinder.net'
2015-07-25 22:37:02.905081 Failed to establish a data proxy connection. Receiver data cannot be sent!
2015-07-25 22:37:02.905081 Failed to connect to all known addresses for host: 'dataupload.planefinder.net'
2015-07-25 22:05:20.53532 TCP connection established: 127.0.0.1:30002
2015-07-25 22:05:20.53532 Client restarted successfully
2015-07-25 22:05:20.53532 Closed TCP connection: 127.0.0.1:30002
2015-07-25 21:29:54.779000 Failed to establish a data proxy connection. Receiver data cannot be sent!
2015-07-25 21:29:54.779000 Failed to connect to all known addresses for host: 'dataupload.planefinder.net'
2015-07-25 20:56:15.121479 Failed to establish a data proxy connection. Receiver data cannot be sent!
2015-07-25 20:56:15.121479 Failed to connect to all known addresses for host: 'dataupload.planefinder.net'
2015-07-25 18:12:36.230359 Successfully sent 65 aircraft updates over the past minute (6.00kb)
2015-07-25 18:11:35.31452 Successfully sent 147 aircraft updates over the past minute (12.00kb)

...........................................................................................

someone anny idea what is wrong?
 
Looks like networking might get a little messed up on the Pi as it's unable to resolve DNS as well from time to time. What DNS servers are set on the Pi.

Also is there any message after the one in bold. We essentially have detected no data coming from Dump1090 so have restarted our connection to it in case it was that at fault
 
Lee Armstrong said:
Looks like networking might get a little messed up on the Pi as it's unable to resolve DNS as well from time to time. What DNS servers are set on the Pi.

Also is there any message after the one in bold. We essentially have detected no data coming from Dump1090 so have restarted our connection to it in case it was that at fault
Click to expand...


...................................
2015-07-26 07:08:26.795681 Closed TCP connection: 127.0.0.1:30002
2015-07-26 07:07:08.874309 TCP connection established: 127.0.0.1:30002
2015-07-26 07:07:08.874309 Client restarted successfully
2015-07-26 07:07:08.874309 Closed TCP connection: 127.0.0.1:30002
2015-07-26 01:14:51.491090 TCP connection established: 127.0.0.1:30002
2015-07-26 01:14:51.491090 Client restarted successfully
2015-07-26 01:14:51.491090 Closed TCP connection: 127.0.0.1:30002
.
.
.
2015-07-26 00:35:03.563726 Decoder select timeout occurred, restarting...
2015-07-26 00:34:13.830840 TCP connection established: 127.0.0.1:30002
2015-07-26 00:34:13.830840 Client restarted successfully
2015-07-26 00:34:13.830840 Closed TCP connection: 127.0.0.1:30002
2015-07-26 00:34:13.830840 Decoder select timeout occurred, restarting...
2015-07-26 00:32:44.754684 TCP connection established: 127.0.0.1:30002
2015-07-26 00:32:44.754684 Client restarted successfully
2015-07-26 00:32:44.754684 Closed TCP connection: 127.0.0.1:30002
2015-07-26 00:32:44.754684 Decoder select timeout occurred, restarting...
2015-07-26 00:08:34.264155 Failed to establish a data proxy connection. Receiver data cannot be sent!
2015-07-26 00:08:34.264155 Failed to connect to all known addresses for host: 'dataupload.planefinder.net'
2015-07-25 22:37:44.73553 Failed to establish a data proxy connection. Receiver data cannot be sent!
2015-07-25 22:37:44.73553 Failed to connect to all known addresses for host: 'dataupload.planefinder.net'
2015-07-25 22:37:02.905081 Failed to establish a data proxy connection. Receiver data cannot be sent!
2015-07-25 22:37:02.905081 Failed to connect to all known addresses for host: 'dataupload.planefinder.net'
2015-07-25 22:05:20.53532 TCP connection established: 127.0.0.1:30002
2015-07-25 22:05:20.53532 Client restarted successfully
2015-07-25 22:05:20.53532 Closed TCP connection: 127.0.0.1:30002
2015-07-25 21:29:54.779000 Failed to establish a data proxy connection. Receiver data cannot be sent!

................................

that is all
until i shutdown an restart the clientsoftware in the morning that looks like so:

2015-07-26 07:09:22.330790 Successfully sent 149 aircraft updates over the past minute (11.00kb)
2015-07-26 07:08:51.635746 User location has been verified.
2015-07-26 07:08:32.880718 Echo port is shutting down
2015-07-26 07:08:31.520716 Data proxy is shutting down
2015-07-26 07:08:30.910715 TCP connection established: 127.0.0.1:30002
2015-07-26 07:08:30.910715 Echo port is now listening on: 192.168.0.110:30054
2015-07-26 07:08:30.910715 Web server is now listening on: http://192.168.0.110:30053
2015-07-26 07:08:30.900715 user_longitude = 8.xxxxxx
2015-07-26 07:08:30.900715 user_latitude = 53.xxxxxxx
2015-07-26 07:08:30.900715 web_server_port = 30053
2015-07-26 07:08:30.900715 select_timeout = 10
2015-07-26 07:08:30.900715 aircraft_timeout = 30
2015-07-26 07:08:30.900715 data_format = 4
2015-07-26 07:08:30.900715 tcp_port = 30002
2015-07-26 07:08:30.900715 tcp_address = 127.0.0.1
2015-07-26 07:08:30.900715 connection_type = 1
2015-07-26 07:08:30.900715 pfclient (3.0.2080 windows) started with the following options:
2015-07-26 07:08:29.819714 Web server is shutting down
2015-07-26 07:08:27.408693 Shutting down workers...

after a new start the clienstsoft running perfekt?!
 
Hirntod_HD said:
...................................
2015-07-26 07:08:26.795681 Closed TCP connection: 127.0.0.1:30002
2015-07-26 07:07:08.874309 TCP connection established: 127.0.0.1:30002
2015-07-26 07:07:08.874309 Client restarted successfully
2015-07-26 07:07:08.874309 Closed TCP connection: 127.0.0.1:30002
2015-07-26 01:14:51.491090 TCP connection established: 127.0.0.1:30002
2015-07-26 01:14:51.491090 Client restarted successfully
2015-07-26 01:14:51.491090 Closed TCP connection: 127.0.0.1:30002
.
.
.
2015-07-26 00:35:03.563726 Decoder select timeout occurred, restarting...
2015-07-26 00:34:13.830840 TCP connection established: 127.0.0.1:30002
2015-07-26 00:34:13.830840 Client restarted successfully
2015-07-26 00:34:13.830840 Closed TCP connection: 127.0.0.1:30002
2015-07-26 00:34:13.830840 Decoder select timeout occurred, restarting...
2015-07-26 00:32:44.754684 TCP connection established: 127.0.0.1:30002
2015-07-26 00:32:44.754684 Client restarted successfully
2015-07-26 00:32:44.754684 Closed TCP connection: 127.0.0.1:30002
2015-07-26 00:32:44.754684 Decoder select timeout occurred, restarting...
2015-07-26 00:08:34.264155 Failed to establish a data proxy connection. Receiver data cannot be sent!
2015-07-26 00:08:34.264155 Failed to connect to all known addresses for host: 'dataupload.planefinder.net'
2015-07-25 22:37:44.73553 Failed to establish a data proxy connection. Receiver data cannot be sent!
2015-07-25 22:37:44.73553 Failed to connect to all known addresses for host: 'dataupload.planefinder.net'
2015-07-25 22:37:02.905081 Failed to establish a data proxy connection. Receiver data cannot be sent!
2015-07-25 22:37:02.905081 Failed to connect to all known addresses for host: 'dataupload.planefinder.net'
2015-07-25 22:05:20.53532 TCP connection established: 127.0.0.1:30002
2015-07-25 22:05:20.53532 Client restarted successfully
2015-07-25 22:05:20.53532 Closed TCP connection: 127.0.0.1:30002
2015-07-25 21:29:54.779000 Failed to establish a data proxy connection. Receiver data cannot be sent!

................................

that is all
until i shutdown an restart the clientsoftware in the morning that looks like so:

2015-07-26 07:09:22.330790 Successfully sent 149 aircraft updates over the past minute (11.00kb)
2015-07-26 07:08:51.635746 User location has been verified.
2015-07-26 07:08:32.880718 Echo port is shutting down
2015-07-26 07:08:31.520716 Data proxy is shutting down
2015-07-26 07:08:30.910715 TCP connection established: 127.0.0.1:30002
2015-07-26 07:08:30.910715 Echo port is now listening on: 192.168.0.110:30054
2015-07-26 07:08:30.910715 Web server is now listening on: http://192.168.0.110:30053
2015-07-26 07:08:30.900715 user_longitude = 8.xxxxxx
2015-07-26 07:08:30.900715 user_latitude = 53.xxxxxxx
2015-07-26 07:08:30.900715 web_server_port = 30053
2015-07-26 07:08:30.900715 select_timeout = 10
2015-07-26 07:08:30.900715 aircraft_timeout = 30
2015-07-26 07:08:30.900715 data_format = 4
2015-07-26 07:08:30.900715 tcp_port = 30002
2015-07-26 07:08:30.900715 tcp_address = 127.0.0.1
2015-07-26 07:08:30.900715 connection_type = 1
2015-07-26 07:08:30.900715 pfclient (3.0.2080 windows) started with the following options:
2015-07-26 07:08:29.819714 Web server is shutting down
2015-07-26 07:08:27.408693 Shutting down workers...

after a new start the clienstsoft running perfekt?!
Click to expand...
Hmm not sure what is going on there to be honest. Sounds more like a system issue rather than then client maybe
 
Lee Armstrong said:
Hmm not sure what is going on there to be honest. Sounds more like a system issue rather than then client maybe
Click to expand...

it may be the dump1090 + Virtual Server + PFclient are not compatible in order to work combined? software use the same Port? = 30002 i forget the PlanePlotter ;-)
 
Hirntod_HD said:
it may be the dump1090 + Virtual Server + PFclient are not compatible in order to work combined? software use the same Port? = 30002 i forget the PlanePlotter ;-)
Click to expand...
They should be, unless Virtual Server takes up a huge amount of resources and you are using an older Pi. It might be becoming starved of resources.
 
Status
Not open for further replies.
Back
Top