January 22, 2019, 11:01 pm
Hi everybody,
I'm new here and eager to learn more about FR24, navigation and communications.
I have a running Pi24 system at the moment, feeding data to FR24.
I'd like to plot down some statistics about the data I am collecting (and sending tofr24) and I wonder which could be the best approach.
I see dump1090's Mode-s "decoded data" output on port 30003, which could be a good starting point.
I wonder if it's possible/feasable to pipe the same kind of data out of dump1090 to a file on a local/remote machine for offline processing.
Still, I'm not that familiar with dump1090 and linux pipes. So, maybe someone here did something similar and may help me with a few preliminary considerations before delving too much into the wrong path.
Suggestions?
Thx :-)
↧
January 24, 2019, 11:37 am
Hi. I have uploaded a basestation outline(OUT), but cannot see it to use. Any assistance would be appreciated.
Thanks.
Bob
↧
↧
January 25, 2019, 2:08 pm
Hi there,
I am using the FR24 image on a raspberry Pi. And I have struggled to get the range rings. I edited /etc/default/dump1090-mutability and entered my lat lon, and also edited the range ring values to 50, 100 and 150 NM. I also checked that range ring was true, and everything looked ok. Restared, but still no mark, range rings etc.
Tried fr24.ini and set lat lon etc. but still nothing.
The I entered --lat --lon in the settings.html file as processing arguments, and then the mark and range rings showed up, but NOT at 50, 100 and 150 NM. It looks like it is 100, 150 and 200NM (but not sure). Where do I edit this to get them at 50, 100 and 150NM ?
↧
January 26, 2019, 4:20 am
Hey,
I'm a happy user of my.flightradar24 user. I'm trying to get the list of my flights so I can do some visualization myself but I'm a bit confused by the way it works.
The API endpoint that's used by the frontend is that one and the offset at the end can be incremented by 50 to paginate through the flights, unfortunately I'm unable to get the first 2 flights as the lowest offset I can set is 1 (so the first flight I get is the one at index 2). Is there a way to get all of them?
HTML Code:
/public-scripts/flight-list/dewey/1
Thanks!
↧
January 26, 2019, 11:25 am
I've been using a RasPi with the official Flight Radar pi image since the new year and have been getting around 250 aircraft tracked per day. Last week, this fell to zero. I've rebooted the pi and checked connection etc but can't figure out what the problem is.
I started a new log file and rebooted the pi earlier - here's a sample: (edit - it won't accept my log file as it thinks it contains links. Here's a cut down version):
2019-01-26 19:07:00 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw)
2019-01-26 19:07:00 | [reader][i]Connected to the receiver, configuring
2019-01-26 19:07:00 | [reader][i]Configured, processing messages
2019-01-26 19:07:00 | [reader][i]Connection terminated
2019-01-26 19:07:00 | [main][i]Terminating child process 4188 with SIGTERM
2019-01-26 19:07:03 | [feed][n]ping 53
2019-01-26 19:07:04 | [feed][n]syncing stream result: 1
A minute or so after reboot it appears to settle into a regular connect to receiver/terminate process set of steps, and a ping every 30 seconds.
Is there anything clearly wrong here?
Thanks for the help.
↧
↧
January 27, 2019, 5:52 am
Hey,
I'm trying to set up FR on my windows 10 machine and the errors I'm getting seem to point towards a dead dongle.
First of all I'm using this dongle: ADS-B USB Dongle (R820T2) from JetVision, plugged into USB 2 on my motherboard, also had the same issues when plugged into a powered USB 3 hub and directly into a Rasberry Pi.
These are the errors/issues:
Zadig
Dongle shows up as
Code:
Unknown USB Device (Device Descriptor Request Failed)
instead of the expected Bulk Device and driver installation fails.
fr24feed
Loads the software okay but then repeats this error message:
Code:
[reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe --net-http-port 8080 --raw)
[reader][i]Connected to the receiver, configuring
[reader][i]Configured, processing messages
[reader][i]Connection terminated
The web page setup doesn't seem to show any errors:
chrome_2019-01-27_13-48-08.png
chrome_2019-01-27_13-48-22.jpg
I have also tried using the dongle on a Raspberry Pi 3b+ with both the pi24 image and Rasbian Stretch Lite following steps on the forum but cannot get any results there either.
Do these signs point towards a dead dongle or am I missing something in my set up.
I have search the forums and generally on the internet but couldn't find anything that fixed these issues.
Any ideas? Thanks!
↧
January 27, 2019, 8:54 am
All,
Despite having successfully had RTL1090 feeding Planeplotter on an old laptop, I am failing miserably to set up my new laptop.
RTL1090 is running fine.
However Planeplotter will not connect. It gives me a screen with seven lines of what look like satellite data, and an error message:
Failed to connect: 10061. Start server (BS/ANRB/etc) check details and try again.
Things I have tried
- Ensured that Planeplotter allows exceptions through the firewall
- Deleted McAfee bloatware
- Tried ADSBScope and the data from RTL1090 will not feed that either.
Any ideas?
Thanks
'77
↧
January 27, 2019, 1:20 pm
Hi there,
I have only feed FR24 for a few days. And the first day I had about 40k hits reported, and about 22,5k positions reported (a bit more than 50% positions reports vs. hits reports). Day two was a bit less than 50% position reports vs. hits reports. And it has become severely worse. Today I have about 29.1k positions reported, but only about 4000 positions reported ?!? My feeder is named T-ENNO9 if you want to look at the numbers.
Is there any reason why there is so few position reports ? A friend of mine is living a few hundred meteres away. He has only a indoor antenna, and of course a lower range than me, and also fewer position reports (SIGNIFICANTLY fewer). But today he has more positions reported than me. Why ?
↧
February 1, 2019, 1:20 am
Hallo,
Is it possible to share 2 filtered flights with another user?
Thank you
Dom
↧
↧
February 4, 2019, 7:58 am
I just noticed FlightAware have released a new 1090MHz Bandpass filter with a smaller passband (
here), so I wondered if I need one as I already have one of
the original filters.
A bit of searching and of course abcd567 has already highlighted
the exact steps needed to work it out... :D
These are a couple of sections from my result (with the original filter in place), so given how much brighter 925-960MHz is than 1090MHz it looks like I'd benefit from the smaller frequency range of the new filter.
original-filter.png
Thanks, abcd567. :D
↧
February 5, 2019, 3:21 am
Hi all,
There is a problem when the following two aircrafts are flying in South America because they do not appear on Flight Radar map. Please find below aircraft and flights details as when these aircraft were operating European routes, they appeared in the map:
- A330-200 EC-MTU operate the route SCL-BOG (LAN072) and BOG-SCL (LAN0575) every day
345657
EC-MTU
A332
Airbus A330-223
469
WAMOS AIR
PLM
PLM
04/13/2018
- A330-200 EC-MTT operate the route SCL-BOG (LAN076) and BOG-SCL (LAN0577) every day
345656
EC-MTT
A332
Airbus A330-223
454
WAMOS AIR
PLM
PLM
2018/03/29
Both aircraft operated these routes on behalf of Latam Airlines some months ago and appeared on Flight Radar map.
Please, could you check it in order to can see these aircraft flying on the map?
Many thanks
Kind regards!
↧
February 6, 2019, 11:23 am
Last time I flew, on August 11 last year, I was on Norwegian Air Gatwick to Denver DI7171. Daytime flight.
About half way over I was startled to see a green and white plane that I have since tracked down via this site to be the Aer Lingus return flight EI144 from LAX to Dublin. It was visible over the starboard wing, flying in the exact opposite direction to us.
What startled me was the lack of height difference between us. I am not experienced in visual judgement of distances. Its horizontal distance was obviously something within a mile. It was only visible through the porthole for less that 3 seconds.
According to FR24 records on Aug 11 its height should have been 39K and ours was 38K. It would be futile to try to convince an expert that the height separation was insufficient, all I can say is that 1000 feet is about 5 times the length of the Airbus 330 and this plane seemed significantly less than five times its length in height separation.
I just wondered if anyone had any comment?
I tried to attach an image, not of the actual incident but a fairly comparable image of a plane at a similar elevation, but this is my first post and I don't think I am allowed yet.
↧
February 8, 2019, 5:44 am
Someone has the green adapter for (ads-b FlightStick radarbox24) radar Im going crazy, I look at gqrx and I notice signals from adsb (I think) but with the dump1090 from linux I do not see airplanes and with the black skewer (from tdt) yes
Should we add some special parameter or something? I have tried with different gains. Thank you.
↧
↧
February 8, 2019, 7:08 am
Hi guys,
Yesterday I have tried to install the fr24 feeder on Debian OS.
But I have selected the wrong receiver in step 4.1
fr24feeder 4.1.JPG
Now I'm on step 4.3A and want to go back to select the correct one.
fr24feeder 4.3A.JPG
How can I solve this issue?
I new on linux os systems.
Thank you for your help.
Regards,
Aerotower
↧
February 10, 2019, 6:13 pm
Figured have a chat here rather than polluting the Dbase section..
Does it come of a concern to anyone else how close we are to the mandates around the planet to requirement to have full WORKING ADSB transponders we are, yet the operators and owners - who are at the hands of the safety of themselves and others don't seem to be grasping the importance of the requirements?
I know the 'rest of the world' doesn't usually concern themselves/recognise the FAA. But they do tend to have their own administration with the role of Aircraft management. Or presumably arranging intercontinental movements/flightplans wouldn't happen?..
I wouldn't have expected a group of hobbiests at home who don't themselves fly (the majority that is), to seemingly be at the forefront to be the ones able to spot and advise operators (there appears to have been a recent increase in owner/operators installing/taking over newer ADSB units?) that the configuration they're attempting to continue with jepordises the mandates.
I've seen numerous FAA run case studies around inconsistencies with South America (and others) and the difficulty with aligning a proper registrar management and allocation. Surprisingly, it appears to be only Mexico that has an impending deadline
https://www.aopa.org/go-fly/aircraft...b-out-required
They seem to be able to control those who actively request checks for errors and advise to remedy, but it seems unless you are TXing your true tailnumber for the flight for ATC to advise or contact each operators register to advise the owner there doesn't seem to be a way to track back who the wrong ones are and get them changed.
Bit of a worry when we've been able to on a public forum huh?
↧
February 11, 2019, 12:13 pm
Over the last 4 days I have been experiencing random dropouts of anything from a few minutes to half an hour, previously my feed has been rock solid.
I have tried rebooting both my router and the FR24 box but the dropouts keep returning.
The FR log file has repeated entries along the line of:
2019-02-11 19:48:22 | [w]Fall back to HTTP for error: Peer certificate cannot be authenticated with given CA certificates
However the log file still shows data as being sent during the outages
When I look at the stats page (
https://www.flightradar24.com/accoun...stats/?id=4114) it shows me as connected but with an upload rate of 0 Bytes/s during the outages.
Has anyone seen this behaviour from a FR24 box? And more importantly can anyone suggest how to fix it?
Is it an error with the FR24 certificate server?
↧
February 11, 2019, 3:25 pm
Hello all,
I work as an aircraft refueler, and use FR24 to track my inbound aircraft. I recently began using the alerts feature to directly send me notifications when an aircraft for an airline I fuel gets within a certain range of my airport. However, I'm running into an issue: when I create a filter for a carrier that has regional airlines fly for them (American, for instance) I only get notifications for mainline aircraft. I know FR24 has the ability to sort codeshare flights, as the filter feature is able to sort out Skywest American from Skywest United, for example. Anyone have any ideas for how to get this to work?
Thanks for your help!
↧
↧
February 11, 2019, 8:26 pm
Hi, I have noticed that a red crosshair, or plus symbol has showed up on the map. I tried zooming in but there is no information on it. Have I turned something "ON" without realising it?
Are you able to tell me what it is?
Screen Shot 02-12-19 at 02.18 PM.jpg
EDIT - UPDATE
After reloading the page a few times it has now vanished. Not sure what I did.
↧
February 12, 2019, 7:17 pm
I just setup Raspian and installed PiAware and it works great, I then setup the ADSBExchange script and that worked too
I went through the config for FlightRadar but zero airfract tracked, and I got the following in the log
HTML Code:
2019-02-12 21:00:18 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
2019-02-12 21:00:18 | [reader][e]Could not connect to tcp://localhost:30005
2019-02-12 21:00:23 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
2019-02-12 21:00:23 | [reader][e]Could not connect to tcp://localhost:30005
2019-02-12 21:00:28 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
2019-02-12 21:00:28 | [reader][e]Could not connect to tcp://localhost:30005
2019-02-12 21:00:33 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
2019-02-12 21:00:33 | [reader][e]Could not connect to tcp://localhost:30005
2019-02-12 21:00:38 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
2019-02-12 21:00:38 | [reader][e]Could not connect to tcp://localhost:30005
2019-02-12 21:00:43 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
2019-02-12 21:00:43 | [reader][e]Could not connect to tcp://localhost:30005
2019-02-12 21:00:47 | [feed][n]ping 9
2019-02-12 21:00:48 | [feed][n]syncing stream result: 1
2019-02-12 21:00:48 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
2019-02-12 21:00:48 | [reader][e]Could not connect to tcp://localhost:30005
2019-02-12 21:00:53 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
2019-02-12 21:00:54 | [reader][e]Could not connect to tcp://localhost:30005
2019-02-12 21:00:59 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
2019-02-12 21:00:59 | [reader][e]Could not connect to tcp://localhost:30005
I played around with some settings and ended up with it set on beast-tcp looking at port 30002.
Now I have this
HTML Code:
2019-02-12 21:05:53 | [feed][n]KAAP22@185.218.24.22:8099/UDP
2019-02-12 21:05:53 | [feed][n]connecting
2019-02-12 21:05:53 | info | Stopping ReceiverACSender threads for feed
2019-02-12 21:05:53 | info | Configured ReceiverACSender: 185.218.24.22:8099,185.218.24.23:8099,185.218.24.24:8099, feed: KAAP22, send_interval: 5s, max age: 15s, send metadata: true, mode: 1, filtering: true
2019-02-12 21:05:53 | info | Network thread connecting to 185.218.24.22:8099 for feed KAAP22
2019-02-12 21:05:53 | [feed][n]connected via UDP (fd 32)
2019-02-12 21:05:53 | [feed][i]Feed connected
2019-02-12 21:05:53 | [feed][n]working
2019-02-12 21:06:23 | [feed][n]ping 1
2019-02-12 21:06:24 | [feed][n]syncing stream result: 1
2019-02-12 21:06:53 | [feed][n]ping 2
2019-02-12 21:06:54 | [feed][n]syncing stream result: 1
2019-02-12 21:07:23 | [feed][n]ping 3
2019-02-12 21:07:24 | [feed][n]syncing stream result: 1
2019-02-12 21:07:53 | [feed][n]ping 4
2019-02-12 21:07:54 | [feed][n]syncing stream result: 1
2019-02-12 21:08:23 | [feed][n]ping 5
2019-02-12 21:08:24 | [feed][n]syncing stream result: 1
2019-02-12 21:08:53 | [feed][n]ping 6
2019-02-12 21:08:54 | [feed][n]syncing stream result: 1
2019-02-12 21:09:23 | [feed][n]ping 7
2019-02-12 21:09:24 | [feed][n]syncing stream result: 1
2019-02-12 21:09:53 | [feed][n]ping 8
2019-02-12 21:09:54 | [feed][n]syncing stream result: 1
But still zero planes tracked...
Can someone point me in the direction of what the correct settings should be for a bone stock Raspian install with PiAware installed on-top?
↧
February 13, 2019, 2:01 am
Map of Pi24/fr24feed
PI24 Map1.14.png
Map after carrying out modification detailed below
PI24 Map1.15~dev.png
How it is achieved:
- Pi24 / fr24feed installs dump1090-mutability ver 1.14, which has Google map and displays Water Mark if you dont have Google API Key.
- The dump1090-mutability ver 1.15~dev has OpenStreet map, which does not require a key, and does not display Water Mark.
- The trick is to replace html folder of dump1090-mutability ver 1.14 by html folder of dump1090-mutability ver 1.15~dev
Here is step-by-step method:
STEP-1
The Pi24 image has "read-only file system"
Change read-only file system temporarily to read & write system
Code:
sudo mount -o remount,rw /
STEP-2
Download the dump1090-mutability ver 1.15~dev files from github
Code:
sudo apt install git
cd ~/
git clone https://github.com/mutability/dump1090.git
STEP-3
The above commands will download a folder dump1090, which contains another folder public_html
Copy the folder public_html to folder /usr/share/dump1090-mutability
Code:
sudo cp -r dump1090/public_html /usr/share/dump1090-mutability/public_html
STEP-4
4.1 - Go to folder dump1090-mutability
Code:
cd /usr/share/dump1090-mutability
4.2 - First change name of folder html to html-orig
This preserves the original html folder, and enables revert in case something goes wrong
Code:
sudo mv html html-orig
4.3 - Now change the name of folder public_html to html
Code:
sudo mv public_html html
STEP-5
Revert the file system back to original read-only
Code:
sudo mount -o remount,ro /
DONE!
Go to map at
http://IP-OF-PI/dump1090/gmap.html
Clear broswer cache (Ctrl+Shift+Delete) and Reload browser (Ctrl+F5)
Enjoy new map :)
↧