Is there a way to see more arrivals/departures for a specific airport than just the past 1-2 days? The flight history for specific aircraft/flight numbers goes back 365 days in my case as a Gold member, but for airports it's extremely limited. I know the data is already in the database of flights/aircraft movements, so I'm just wondering how to find the flights to/from a specific airport for a longer period of time.
↧
Longer airport arrivals/departure history?
↧
RSSI Column Not Populating - Blank Column With White Background
I have performed the steps to add RSSI column to map display.
The RSSI column is there but is blank.
No values. White background.
The column does sort when clicked as I can see the other columns adjust.
Have used Firefox, Chrome, and Safari with same results.
Any help would be appreciated.
My setup is a FA antenna, FA filter, FA Pro Plus Dongle to a Pi3B+.
Feeding FR24, FA, and PF with no problems feeding.
The RSSI column is there but is blank.
No values. White background.
The column does sort when clicked as I can see the other columns adjust.
Have used Firefox, Chrome, and Safari with same results.
Any help would be appreciated.
My setup is a FA antenna, FA filter, FA Pro Plus Dongle to a Pi3B+.
Feeding FR24, FA, and PF with no problems feeding.
↧
↧
SBS-3 losing sensitivity over time
Hi all, I've tried Googling for this and searching the forum but can't find anything on this topic, so thought I'd post the question! Here goes...
I've been using the SBS-3 since about 2016, so three years at least. I have an externally mounted co-linear type antenna, a mast-head pre-amp, a run of coax that runs to a bias-T and then into the SBS-3. I've had this installed since in 2016. When I initially installed this the SBS-3 could get contacts over 100 NM away, happy days. Now, with the same hardware and setup etc (nothing has changed, just time) I'm only able to see contacts around 50-60 NM away.
A week or so ago I decided to buy an SDR and connect it to a Raspberry Pi, to feed FR24 (which is up and running). So I could run both FR24 and the SBS-3 side-by-side I built a home-made antenna, just to see if I could get it working. Dump1090 on the Raspberry Pi registers over 200 messages/second using the home made antenna, so happy days with that little set up, and I'm quite happy with what it can see.
Now for the bit that's niggling at me!
Out of curiosity, I took the external antenna connection that's normally connected to the SBS-3 (so the external antenna, pre-amp etc) and connected it into the SDR connected to the Raspberry Pi, Dump1090 shows over 600 messages a second and that gets contacts over 80NM miles away. If I take the connection and plug it back into the SBS-3, it can't see the contact at 80NM miles away, when it used to be able to see contacts at this distance when it was first installed.
I know that the SBS-3 and the SDR are entirely different pieces of equipment, and no the antenna is NOT being shared between two devices simultaneously. I've checked all plugs, loose connections etc and everything is fine. SBS-3 is on the latest version I can see on the Kinetic website and Basestation is the latest version (I upgraded them when I got them and Kinetic haven't released a new version since - Kinetic seem to have gone quiet).
The bit that's niggling at me is that it "seems" that the SBS-3 could see contacts over 100NM away when it was first installed, but seems like it's gone a bit "deaf" and lost sensitivity over time, and now can't see a contact 80NM away when another device can using the same antenna setup, and it used to be able to see to this range when it was first installed.
My question is: has anyone else had a similar experience to this at all, with an SBS-3 losing sensitivity after a while, or going a bit deaf? If so, is there anything that can be done to rectify this or restore the original sensitivity?
Thanks,
Chromic
P.S. Does anyone know what happened to Kinetic as they don't seem to be updating the firmware/software? The website still has a story from 2016 on the homepage...
I've been using the SBS-3 since about 2016, so three years at least. I have an externally mounted co-linear type antenna, a mast-head pre-amp, a run of coax that runs to a bias-T and then into the SBS-3. I've had this installed since in 2016. When I initially installed this the SBS-3 could get contacts over 100 NM away, happy days. Now, with the same hardware and setup etc (nothing has changed, just time) I'm only able to see contacts around 50-60 NM away.
A week or so ago I decided to buy an SDR and connect it to a Raspberry Pi, to feed FR24 (which is up and running). So I could run both FR24 and the SBS-3 side-by-side I built a home-made antenna, just to see if I could get it working. Dump1090 on the Raspberry Pi registers over 200 messages/second using the home made antenna, so happy days with that little set up, and I'm quite happy with what it can see.
Now for the bit that's niggling at me!
Out of curiosity, I took the external antenna connection that's normally connected to the SBS-3 (so the external antenna, pre-amp etc) and connected it into the SDR connected to the Raspberry Pi, Dump1090 shows over 600 messages a second and that gets contacts over 80NM miles away. If I take the connection and plug it back into the SBS-3, it can't see the contact at 80NM miles away, when it used to be able to see contacts at this distance when it was first installed.
I know that the SBS-3 and the SDR are entirely different pieces of equipment, and no the antenna is NOT being shared between two devices simultaneously. I've checked all plugs, loose connections etc and everything is fine. SBS-3 is on the latest version I can see on the Kinetic website and Basestation is the latest version (I upgraded them when I got them and Kinetic haven't released a new version since - Kinetic seem to have gone quiet).
The bit that's niggling at me is that it "seems" that the SBS-3 could see contacts over 100NM away when it was first installed, but seems like it's gone a bit "deaf" and lost sensitivity over time, and now can't see a contact 80NM away when another device can using the same antenna setup, and it used to be able to see to this range when it was first installed.
My question is: has anyone else had a similar experience to this at all, with an SBS-3 losing sensitivity after a while, or going a bit deaf? If so, is there anything that can be done to rectify this or restore the original sensitivity?
Thanks,
Chromic
P.S. Does anyone know what happened to Kinetic as they don't seem to be updating the firmware/software? The website still has a story from 2016 on the homepage...
↧
RPi4 dump1090 not working
Can anyone help please.
Hardware:
Raspberry pi 4 model B
Nooelec NESDR Nano 2
Installed dump1090-mutability ver 1.15~dev and the fr24feed.
Status:
fr24feed.ini
fr24feed log file:
dump1090-mutability log file
Hardware:
Raspberry pi 4 model B
Nooelec NESDR Nano 2
Installed dump1090-mutability ver 1.15~dev and the fr24feed.
Status:
Code:
pi@raspberrypi:~ $ sudo fr24feed-status
[ ok ] FR24 Feeder/Decoder Process: running.
[ ok ] FR24 Stats Timestamp: 2019-07-30 11:47:06.
[ ok ] FR24 Link: connected [UDP].
[ ok ] FR24 Radar: T-EGDY50.
[ ok ] FR24 Tracked AC:.
[ ok ] Receiver: connected (0 MSGS/ SYNC).
[FAIL] FR24 MLAT: not running ... failed!Code:
receiver="beast-tcp"
fr24key="083a900c888d05c1"
host="127.0.0.1:30005"
bs="no"
raw="no"
logmode="1"
windowmode="0"
logpath="/var/log/fr24feed"
mpx="no"
mlat="no"
mlat-without-gps="no"fr24feed log file:
Code:
2019-07-30 12:14:13 | ______ _ _ _ _ _ _____ ___
2019-07-30 12:14:13 | | ___|| |(_) | | | | | | / __ \ / |
2019-07-30 12:14:13 | | |_ | | _ __ _ | |__ | |_ _ __ __ _ __| | __ _ _ __`' / /' / /| |
2019-07-30 12:14:13 | | _| | || | / _` || '_ \ | __|| '__|/ _` | / _` | / _` || '__| / / / /_| |
2019-07-30 12:14:13 | | | | || || (_| || | | || |_ | | | (_| || (_| || (_| || | ./ /___\___ |
2019-07-30 12:14:13 | \_| |_||_| \__, ||_| |_| \__||_| \__,_| \__,_| \__,_||_| \_____/ |_/
2019-07-30 12:14:13 | __/ |
2019-07-30 12:14:13 | |___/
2019-07-30 12:14:13 | [main][i]FR24 Feeder/Decoder
2019-07-30 12:14:13 | [main][i]Version: 1.0.23-8/generic
2019-07-30 12:14:13 | [main][i]Built on Oct 16 2018 08:10:47 (HEAD-2d57e58.git/Linux/static_armel)
2019-07-30 12:14:13 | [main][i]Running on: raspbian10
2019-07-30 12:14:13 | [main][i]Local IP(s):
2019-07-30 12:14:13 | [main][i]Copyright 2012-2018 Flightradar24 AB
2019-07-30 12:14:13 | [main][i]https://www.flightradar24.com
2019-07-30 12:14:13 | [main][i]DNS mode: PING
2019-07-30 12:14:13 | [main][i]Automatic updates are ENABLED
2019-07-30 12:14:13 | [httpd][i]Server started, listening on 0.0.0.0:8754
2019-07-30 12:14:13 | [main][i]Reader thread started
2019-07-30 12:14:13 | [time][i]Synchronizing time via NTP
2019-07-30 12:14:13 | [master][i]Starting processing thread
2019-07-30 12:14:13 | [reader][i]Initializing reader
2019-07-30 12:14:13 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)
2019-07-30 12:14:13 | [reader][e]Could not connect to tcp://127.0.0.1:30005
2019-07-30 12:14:13 | [time][e]Failed to synchronize time
2019-07-30 12:14:13 | [main][w]Failed to synchronize time, waiting 5 seconds
2019-07-30 12:14:18 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)
2019-07-30 12:14:18 | [reader][e]Could not connect to tcp://127.0.0.1:30005
2019-07-30 12:14:18 | [time][i]Synchronizing time via NTP
2019-07-30 12:14:19 | [time][e]Failed to synchronize time
2019-07-30 12:14:19 | [main][w]Failed to synchronize time, waiting 5 seconds
2019-07-30 12:14:23 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)
2019-07-30 12:14:23 | [reader][e]Could not connect to tcp://127.0.0.1:30005
2019-07-30 12:14:24 | [time][i]Synchronizing time via NTP
2019-07-30 12:14:24 | [time][e]Failed to synchronize time
2019-07-30 12:14:24 | [main][w]Failed to synchronize time, waiting 5 seconds
2019-07-30 12:14:28 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)
2019-07-30 12:14:28 | [reader][e]Could not connect to tcp://127.0.0.1:30005
2019-07-30 12:14:29 | [time][i]Synchronizing time via NTP
2019-07-30 12:14:33 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)
2019-07-30 12:14:33 | [reader][i]Connected to the receiver, configuring
2019-07-30 12:14:33 | [reader][i]Configured, processing messagesCode:
Tue Jul 30 12:15:10 2019 BST dump1090-mutability v1.15~dev starting up.
Using sample converter: UC8, integer/table path
Found 1 device(s):
0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
rtlsdr_read_reg failed with -7
rtlsdr_write_reg failed with -7
rtlsdr_read_reg failed with -7
rtlsdr_write_reg failed with -7
rtlsdr_read_reg failed with -7
rtlsdr_write_reg failed with -7
rtlsdr_read_reg failed with -7
rtlsdr_write_reg failed with -7
No supported tuner found
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
Enabled direct sampling mode, input 1
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
Max available gain is: 0.00 dB
Setting gain to: 0.00 dB
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_write_reg failed with -7
rtlsdr_write_reg failed with -7
Gain reported by device: 0.00 dB
Allocating 15 zero-copy buffers
Tue Jul 30 12:15:28 2019 BST No data received from the dongle for a long time, it may have wedged
Tue Jul 30 12:17:28 2019 BST No data received from the dongle for a long time, it may have wedged
Tue Jul 30 12:18:28 2019 BST No data received from the dongle for a long time, it may have wedged
Tue Jul 30 12:19:29 2019 BST No data received from the dongle for a long time, it may have wedged
Tue Jul 30 12:20:29 2019 BST No data received from the dongle for a long time, it may have wedged↧
Antenna
I am new to the forum and have searched for answer but havnt found it which is why I am posting.
Silly question maybe, but I have the USB-dongle with a small indoor antenna (starter pack). Can I just get an adapter for the TV-antenna and plug that in instead for better coverage?
As I said, I am a beginner, but willing to learn.
Regards
Silly question maybe, but I have the USB-dongle with a small indoor antenna (starter pack). Can I just get an adapter for the TV-antenna and plug that in instead for better coverage?
As I said, I am a beginner, but willing to learn.
Regards
↧
↧
Sharing Key - Two feeds
Folks,
Been sharing FA and FR24 for some time now, I reside in UK and my FR24 devices is at a friend's home in US
Now I have run the FR24 script to feed on my UK device but used the same sharing key shown on my account, should I have used a new sharing key?
Geffers
Been sharing FA and FR24 for some time now, I reside in UK and my FR24 devices is at a friend's home in US
Now I have run the FR24 script to feed on my UK device but used the same sharing key shown on my account, should I have used a new sharing key?
Geffers
↧
Antenna mount question (gutter)
I've done some searching on these forums and googling to see if I can answer my own question but so far I'm not finding what I am hoping to find.
I have this antenna for my Flightradar24 receiver: FlightAware 1090 MHz ADS-B Antenna - 66 cm / 26 in
I would like to find a mount so I can install this antenna to the gutters on my house. Has anyone seen or run across such a thing?
My gutters look like this:
amerimax-home-products-gutters-1800700120-64_1000.jpg
I have this antenna for my Flightradar24 receiver: FlightAware 1090 MHz ADS-B Antenna - 66 cm / 26 in
I would like to find a mount so I can install this antenna to the gutters on my house. Has anyone seen or run across such a thing?
My gutters look like this:
amerimax-home-products-gutters-1800700120-64_1000.jpg
↧
change settings
Hello all,
yesterday I received my new antenna (https://www.ebay.de/itm/1pcs-ADS-B-P...E/253915016420) and also my RTl-SDR dongle. (https://www.rtl-sdr.com/buy-rtl-sdr-dvb-t-dongles/) All to improve my reception.
I connected the dongle to my raspberry and rebooted my raspberry. I am wondering do I have to change the settings in myip:8754.
Do I have to change the receiver in the RTL-SDR dongle.
I am also feeding to FlightAware and Planefinder. Installed dump1090fa.
As always thanks for all the advice
yesterday I received my new antenna (https://www.ebay.de/itm/1pcs-ADS-B-P...E/253915016420) and also my RTl-SDR dongle. (https://www.rtl-sdr.com/buy-rtl-sdr-dvb-t-dongles/) All to improve my reception.
I connected the dongle to my raspberry and rebooted my raspberry. I am wondering do I have to change the settings in myip:8754.
Do I have to change the receiver in the RTL-SDR dongle.
I am also feeding to FlightAware and Planefinder. Installed dump1090fa.
As always thanks for all the advice
↧
Naïve question?
Hi all,
this afternoon I compared my Flightradar view with Flightaware skyview.
I do not understand why I do not see all the planes e.g in the Dusseldorf area. It looks like I can "see: that area, when I look at the screenshot from the Flightware sky view.
I added the two screenshots. Perhaps a naïve or even stupid question but I hope there is someone how is willing to explain this.
Thanks
Screenshot 2019-08-04 at 16.57.40.jpg. Screenshot 2019-08-04 at 16.57.51.jpg
this afternoon I compared my Flightradar view with Flightaware skyview.
I do not understand why I do not see all the planes e.g in the Dusseldorf area. It looks like I can "see: that area, when I look at the screenshot from the Flightware sky view.
I added the two screenshots. Perhaps a naïve or even stupid question but I hope there is someone how is willing to explain this.
Thanks
Screenshot 2019-08-04 at 16.57.40.jpg. Screenshot 2019-08-04 at 16.57.51.jpg
↧
↧
Change of flights schedule times for AIR SENEGAL flights
We noticed flight schedule times for AIR SENEGAL (HC- SZN) are always changed prior to departure. Initially times are published in local times, but suddently some days before departure they are changed to UTC (see for sample Paris Dakar Paris flights).
Please AIR SENEGAL S.A. publishes its schedule in LOCAL TIME; therefore departure and arrival must always be in Local Times.
Check and advise.
Please AIR SENEGAL S.A. publishes its schedule in LOCAL TIME; therefore departure and arrival must always be in Local Times.
Check and advise.
↧
About FR24feed log file..? How to view and suggestions?
Hi, I am a new feeder.
I found different suggestions regarding how to deal with FR24feed log file:
somebody is suggesting to keep Raspberry setting to 1 (rotate every 24h) and others to disable it, in order to save SD life.
What is yours?
Finally, what is the best, easy way to view it? What is going there?
I tried the command "nano fr24feed" when in log directory, but the opened file is empty...
Tnx. Cheers.
I found different suggestions regarding how to deal with FR24feed log file:
somebody is suggesting to keep Raspberry setting to 1 (rotate every 24h) and others to disable it, in order to save SD life.
What is yours?
Finally, what is the best, easy way to view it? What is going there?
I tried the command "nano fr24feed" when in log directory, but the opened file is empty...
Tnx. Cheers.
↧
Steady Red Light on RaspBerry Pi 3
After having successfully followed all FlighRadar24 website procedure to set my RaspBerryPi3, everything is now up and running.
Just wondering if the steady red light on my RaspBerry is normal.
During restart I have steady red, plus a blinking yellow close to it which disappear after initialisation process leaving the steady red alone.
By surfing the internet it looks like a Red Steady Light means there is power but no readable boot instructions on the SD, which looks strange to me as everything is working...
Any advice?
Just wondering if the steady red light on my RaspBerry is normal.
During restart I have steady red, plus a blinking yellow close to it which disappear after initialisation process leaving the steady red alone.
By surfing the internet it looks like a Red Steady Light means there is power but no readable boot instructions on the SD, which looks strange to me as everything is working...
Any advice?
↧
client crashing after awhile, linux + mr-dump1090
my previously stable setup went unstable without me knowing, now that key is gone so I was given a new key.
this new configuration is unstable,
it crashes out and with no more service 127.0.0.1:8754
after this crash I
it reports
i use mr-dump1090
fr24 config
proper key
dvdb
/usr/lib/fr24/mr-dump1090
--net --net-http-port 38080
RAW YES or NO
as usual the above does start & stop mr-dump1080 on port 38080
I've rebooted the machine and the service on 8754 dies after awhile, did this several times.
any ideas how to fix?
also dmesg reports
[ 102.306605] th_network_clie[1686]: segfault at 141fbbdc ip 00000000080abf8d sp 00000000f41fbb50 error 6 in fr24feed[8048000+a7000]
...
[ 3519.904533] th_network_clie[3590]: segfault at 141fdbdc ip 00000000080abf8d sp 00000000f41fdb50 error 6 in fr24feed[8048000+a7000]
[19873.246463] th_network_clie[19477]: segfault at 142fbbdc ip 00000000080abf8d sp 00000000f42fbb50 error 6 in fr24feed[8048000+a7000]
[95869.872263] th_network_clie[2572]: segfault at 142fdbdc ip 00000000080abf8d sp 00000000f42fdb50 error 6 in fr24feed[8048000+a7000]
this new configuration is unstable,
it crashes out and with no more service 127.0.0.1:8754
after this crash I
Code:
# sudo service fr24feed statusCode:
Aug 06 13:23:46 nc4400 systemd[1]: fr24feed.service: Found left-over process 19462 (mr-dump1090) in control group while starting unit. Ignoring
Aug 06 13:23:47 nc4400 fr24feed[943]: * Starting FR24 feeder fr24feed
Aug 06 13:23:47 nc4400 fr24feed[943]: ...done.
Aug 06 13:23:46 nc4400 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Aug 06 13:23:46 nc4400 systemd[1]: Starting LSB: Flightradar24 Decoder & Feeder...fr24 config
proper key
dvdb
/usr/lib/fr24/mr-dump1090
--net --net-http-port 38080
RAW YES or NO
as usual the above does start & stop mr-dump1080 on port 38080
I've rebooted the machine and the service on 8754 dies after awhile, did this several times.
any ideas how to fix?
also dmesg reports
[ 102.306605] th_network_clie[1686]: segfault at 141fbbdc ip 00000000080abf8d sp 00000000f41fbb50 error 6 in fr24feed[8048000+a7000]
...
[ 3519.904533] th_network_clie[3590]: segfault at 141fdbdc ip 00000000080abf8d sp 00000000f41fdb50 error 6 in fr24feed[8048000+a7000]
[19873.246463] th_network_clie[19477]: segfault at 142fbbdc ip 00000000080abf8d sp 00000000f42fbb50 error 6 in fr24feed[8048000+a7000]
[95869.872263] th_network_clie[2572]: segfault at 142fdbdc ip 00000000080abf8d sp 00000000f42fdb50 error 6 in fr24feed[8048000+a7000]
↧
↧
RTL-SDR Blog V3 Dongle problem
Hi
I have been happily feeding FR24 data for a few months using a very cheap, generic dingle. My range is constantly about 75NM despite the using several differing aerials. In an attempt to improve my coverage I have bought and installed an RTL-SDR Blog V3 dongle; my coverage has now all but vanished.
Often the status on my dashboard shows as "Online - No Data" and when it seems to be running without issue I only get very few hits and no increase in positions received.
The aerial connection seems good, which I have tested by running the dongle with SDR software. It works well and looses reception as I unplug the aerial, suggesting that there is no problem.
I guess that I don't have to make any configuration changes when moving to the RTL-SDR dongle? Any suggestions as to what my problem may be, or things I can try?
Thank you.
I have been happily feeding FR24 data for a few months using a very cheap, generic dingle. My range is constantly about 75NM despite the using several differing aerials. In an attempt to improve my coverage I have bought and installed an RTL-SDR Blog V3 dongle; my coverage has now all but vanished.
Often the status on my dashboard shows as "Online - No Data" and when it seems to be running without issue I only get very few hits and no increase in positions received.
The aerial connection seems good, which I have tested by running the dongle with SDR software. It works well and looses reception as I unplug the aerial, suggesting that there is no problem.
I guess that I don't have to make any configuration changes when moving to the RTL-SDR dongle? Any suggestions as to what my problem may be, or things I can try?
Thank you.
↧
Could not connect to LocalHost
Recently installed an fr24 feed to my PiAware system, all seems to be working fine, data shows up on FR24 web page statistics.
Wee bit puzzled as to fr24feed.log entries as follows;
The last two lines are repeated several times, not sure how important (or not) these lines are but the netstat command shows my machine as listening on port 30005
Geoff
Wee bit puzzled as to fr24feed.log entries as follows;
Code:
2019-08-07 10:57:39 | [httpd][i]Server started, listening on 0.0.0.0:8754
2019-08-07 10:57:39 | [reader][e]Could not connect to tcp://localhost:30005
2019-08-07 10:57:40 | [time][i]Synchronizing time via NTP
2019-08-07 10:57:44 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
2019-08-07 10:57:44 | [reader][e]Could not connect to tcp://localhost:30005Geoff
↧
wanting webserver parameters for dump1090-mutability v1.15~dev
my stable feeding computer has become unstable,
fr24 feed segfaulting ...
I was using fr24's
mr-dump1090
--net --net-http-port 38080
+ raw
+ decoded
I was serving well.
I'm now trying mutability but it does not open a mini webserver on desired port
--net --net-http-port 38080
netstat -t -p -l |grep dump1090
nul
I'm not seeing the parameters to get a miniserver up,
what am I missing?
/var/log not containing any errors
fr24 feed segfaulting ...
I was using fr24's
mr-dump1090
--net --net-http-port 38080
+ raw
+ decoded
I was serving well.
I'm now trying mutability but it does not open a mini webserver on desired port
--net --net-http-port 38080
netstat -t -p -l |grep dump1090
nul
I'm not seeing the parameters to get a miniserver up,
what am I missing?
/var/log not containing any errors
↧
Installing "Active Diapason" Antenna from Jetvision
I just got the antenna in the subject ith no manual included. The box contains the antenna, a cable and a "bias tee" with a micro usb cable. The manuals can not be downloaded tom jetvission and they do not answer emails.
Can anyone help med with installation and also explan what "Bias Tee (for power supply of the LNA over USB-jack of a Computer)" means?
I dont know what LNA is and i do not know what a Bias tee is.
Maybe someone has been able to download the manual?
Can anyone help med with installation and also explan what "Bias Tee (for power supply of the LNA over USB-jack of a Computer)" means?
I dont know what LNA is and i do not know what a Bias tee is.
Maybe someone has been able to download the manual?
↧
↧
Dynamic Range improvement.
For some time I’ve been using a discone antenna a few metres above the house roof with around 15m of good quality coax feeding a Pro Stick Plus with reasonable but not great results.
I recently decided to upgrade, replacing the discone with a FlightAware aerial and a Rtl SDR-Radio Blog filtered LNA a few metres from the antenna. The original 15m coax still delivers the amplified signals to the receiver.
First of all the Pro stick plus had to go as its internal LNA was now being swamped with too much signal, so my RTL V3 dongle took its place with some improvement.
Despite running the dongle at 0db gain, aircraft taking off a few miles away were still dropping out so this was eventually fixed by inserting a 20db attenuator at the dongle end of the coax.
The system is working fine and is much better than the original setup, but there is clearly a trade off between reliable decoding of strong local signals and getting higher message counts with longer range which is presumably down to the dynamic range the dongle is capable of handling.
I wonder if anyone has progressed to alternatives such as the Airspy and managed better local and distant reception.
I recently decided to upgrade, replacing the discone with a FlightAware aerial and a Rtl SDR-Radio Blog filtered LNA a few metres from the antenna. The original 15m coax still delivers the amplified signals to the receiver.
First of all the Pro stick plus had to go as its internal LNA was now being swamped with too much signal, so my RTL V3 dongle took its place with some improvement.
Despite running the dongle at 0db gain, aircraft taking off a few miles away were still dropping out so this was eventually fixed by inserting a 20db attenuator at the dongle end of the coax.
The system is working fine and is much better than the original setup, but there is clearly a trade off between reliable decoding of strong local signals and getting higher message counts with longer range which is presumably down to the dynamic range the dongle is capable of handling.
I wonder if anyone has progressed to alternatives such as the Airspy and managed better local and distant reception.
↧
[FAIL] Receiver: down ... failed!
Hi
I am a total newbi to Raspberry Pi.
After seeing a webpage describing how easy it is to feed data, I bought a 3B+ and a RTL-SDR V3-based kit. I setup the Pi with a new install, updated the system with sudo apt-get update and sudo apt-get upgrade-dist.
I then ran the command
to install the feed. Followed the questions and filled out everything and I ended up with a working installation, or so I thought.
I can access the webpage on the ip-address:8754 but it does not feed any aircraft.
At first I checked for the fr24feed-status and get the following result:
So, the Receiver is down, but I'm not quite sure as to why or how to fix it. When testing the dongle, it seems it is fine and working as described in a post here:
When running the fr24feed directly I do get the following output with the ERROR: rmmod: ERROR: Module dvb_usb_rtl28xxu is not currently loaded. Is this the problem?
After that, I tried to start the service again and get the following error messages.
How can I fix this to connect to the receiver? Thanks a lot for your help.
I am a total newbi to Raspberry Pi.
After seeing a webpage describing how easy it is to feed data, I bought a 3B+ and a RTL-SDR V3-based kit. I setup the Pi with a new install, updated the system with sudo apt-get update and sudo apt-get upgrade-dist.
I then ran the command
Code:
sudo bash -c "$(wget -O - hxxp://repo.feed.flightradar24.com/install_fr24_rpi.sh)"I can access the webpage on the ip-address:8754 but it does not feed any aircraft.
At first I checked for the fr24feed-status and get the following result:
Code:
pi@raspberrypi:~ $ fr24feed-status
[ ok ] FR24 Feeder/Decoder Process: running.
[ ok ] FR24 Stats Timestamp: 2019-08-10 12:19:18.
[ ok ] FR24 Link: connected [UDP].
[ ok ] FR24 Radar: T-VHHH169.
[ ok ] FR24 Tracked AC:.
[FAIL] Receiver: down ... failed!
[FAIL] FR24 MLAT: not running ... failed!Code:
pi@raspberrypi:~ $ sudo systemctl stop fr24feed
pi@raspberrypi:~ $ sudo systemctl stop dump1090-mutability
pi@raspberrypi:~ $ rtl_test -t
Found 1 device(s):
0: Realtek, RTL2838UHIDIR, SN: 00000001
Using device 0: Generic RTL2832U OEM
Found Rafael Micro R820T tuner
Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6
[R82XX] PLL not locked!
Sampling at 2048000 S/s.
No E4000 tuner found, aborting.Code:
pi@raspberrypi:~ $ sudo systemctl start dump1090-mutability
pi@raspberrypi:~ $ sudo fr24feed
2019-08-10 20:20:44 | ______ _ _ _ _ _ _____ ___
2019-08-10 20:20:44 | | ___|| |(_) | | | | | | / __ \ / |
2019-08-10 20:20:44 | | |_ | | _ __ _ | |__ | |_ _ __ __ _ __| | __ _ _ __`' / /' / /| |
2019-08-10 20:20:44 | | _| | || | / _` || '_ \ | __|| '__|/ _` | / _` | / _` || '__| / / / /_| |
2019-08-10 20:20:44 | | | | || || (_| || | | || |_ | | | (_| || (_| || (_| || | ./ /___\___ |
2019-08-10 20:20:44 | \_| |_||_| \__, ||_| |_| \__||_| \__,_| \__,_| \__,_||_| \_____/ |_/
2019-08-10 20:20:44 | __/ |
2019-08-10 20:20:44 | |___/
2019-08-10 20:20:44 | [main][i]FR24 Feeder/Decoder
2019-08-10 20:20:44 | [main][i]Version: 1.0.23-8/generic
2019-08-10 20:20:44 | [main][i]Built on Oct 16 2018 08:10:47 (HEAD-2d57e58.git/Linux/static_armel)
2019-08-10 20:20:44 | [main][i]Running on: raspbian10
2019-08-10 20:20:44 | [main][i]Local IP(s): 192.168.5.59
2019-08-10 20:20:44 | [main][i]Copyright 2012-2018 Flightradar24 AB
2019-08-10 20:20:44 | [main][i]DNS mode: PING
2019-08-10 20:20:44 | [main][i]Automatic updates are ENABLED
2019-08-10 20:20:44 | ERROR: rmmod: ERROR: Module dvb_usb_rtl28xxu is not currently loaded
2019-08-10 20:20:44 | [httpd][i]Server started, listening on 0.0.0.0:8754
2019-08-10 20:20:44 | [main][i]Reader thread started
2019-08-10 20:20:44 | [reader][i]Initializing reader
2019-08-10 20:20:44 | [main][i]MLAT data feed started
2019-08-10 20:20:44 | [reader][i]Connecting to DVBT receiver via (exe:///usr/lib/fr24/dump1090 --raw --mlat)
2019-08-10 20:20:44 | [master][i]Starting processing thread
2019-08-10 20:20:44 | [mlat][i]Waiting for MLAT configuration
2019-08-10 20:20:44 | [reader][i]Connected to the receiver, configuring
2019-08-10 20:20:44 | [reader][i]Configured, processing messages
bash: /usr/lib/fr24/dump1090: No such file or directory
2019-08-10 20:20:44 | [reader][i]Connection terminated
2019-08-10 20:20:44 | [main][i]Terminating child process 1317 with SIGTERM
2019-08-10 20:20:45 | [time][i]Synchronizing time via NTP
2019-08-10 20:20:50 | [reader][i]Connecting to DVBT receiver via (exe:///usr/lib/fr24/dump1090 --raw --mlat)
2019-08-10 20:20:50 | [reader][i]Connected to the receiver, configuring
2019-08-10 20:20:50 | [reader][i]Configured, processing messages
bash: /usr/lib/fr24/dump1090: No such file or directory
2019-08-10 20:20:50 | [reader][i]Connection terminated
2019-08-10 20:20:50 | [main][i]Terminating child process 1327 with SIGTERM
...
bash: /usr/lib/fr24/dump1090: No such file or directory
2019-08-10 20:21:34 | [reader][i]Connection terminated
2019-08-10 20:21:34 | [main][i]Terminating child process 1366 with SIGTERM
2019-08-10 20:21:35 | [feed][i]configuring decoder
2019-08-10 20:21:35 | [feed][c]Max range AIR: 350.0nm
2019-08-10 20:21:35 | [feed][c]Max range GND: 100.0nm
2019-08-10 20:21:35 | [feed][i]configuration changed
2019-08-10 20:21:35 | [feed][i]defined 3 servers
2019-08-10 20:21:35 | [feed][c]Timestamps: optional
2019-08-10 20:21:35 | [feed][n]VHHXXNNN@185.xx.xx.xx:8099/UDP
2019-08-10 20:21:35 | [stats][i]Stats thread started
2019-08-10 20:21:35 | [feed][n]connecting
2019-08-10 20:21:36 | info | Stopping ReceiverACSender threads for feed
2019-08-10 20:21:36 | info | Configured ReceiverACSender: 185.xx.xx.xx:8099,185.xx.xx.xx:8099,185.xx.xx.xx:8099, feed: VHHXXNNN, send_interval: 5s, max age: 15s, send metadata: true, mode: 1, filtering: true
2019-08-10 20:21:36 | info | Network thread connecting to 185.xx.xx.xx:8099 for feed VHHXXNNN
2019-08-10 20:21:36 | [feed][n]connected via UDP (fd 14)
2019-08-10 20:21:36 | [feed][i]Feed connected
2019-08-10 20:21:36 | [feed][n]working
...
2019-08-10 20:22:18 | [reader][i]Connecting to DVBT receiver via (exe:///usr/lib/fr24/dump1090 --raw --mlat)
2019-08-10 20:22:18 | [reader][i]Connected to the receiver, configuring
2019-08-10 20:22:18 | [reader][i]Configured, processing messages
bash: /usr/lib/fr24/dump1090: No such file or directory
2019-08-10 20:22:18 | [reader][i]Connection terminated
2019-08-10 20:22:18 | [main][i]Terminating child process 1377 with SIGTERM
2019-08-10 20:22:23 | [reader][i]Connecting to DVBT receiver via (exe:///usr/lib/fr24/dump1090 --raw --mlat)
2019-08-10 20:22:23 | [reader][i]Connected to the receiver, configuring
2019-08-10 20:22:23 | [reader][i]Configured, processing messages
bash: /usr/lib/fr24/dump1090: No such file or directory
2019-08-10 20:22:23 | [reader][i]Connection terminated
2019-08-10 20:22:23 | [main][i]Terminating child process 1378 with SIGTERM
^C2019-08-10 20:22:24 | [main][i]Terminating on user request
2019-08-10 20:22:24 | [main][i]Terminating worker threads
2019-08-10 20:22:24 | [reader][i]Terminating on request
2019-08-10 20:22:24 | [master][i]Terminating on request
2019-08-10 20:22:24 | [feed][x]Feeding thread terminated
2019-08-10 20:22:24 | [feed][n]busy
2019-08-10 20:22:24 | [feed][i]Feed disconnected
2019-08-10 20:22:24 | [feed][n]disconnected
2019-08-10 20:22:24 | info | Stopping ReceiverACSender threads for feed VHHXXNNN
2019-08-10 20:22:24 | warning | Exited network thread for feed VHHXXNNN
2019-08-10 20:22:24 | info | Joined network thread for feed VHHXXNNN
2019-08-10 20:22:26 | [httpd][d]Master thread terminated
2019-08-10 20:22:26 | [main][i]Terminated successfullyCode:
pi@raspberrypi:~ $ sudo systemctl start fr24feed
Job for fr24feed.service failed because the control process exited with error code.
See "systemctl status fr24feed.service" and "journalctl -xe" for details.Code:
pi@raspberrypi:~ $ systemctl status fr24feed.service
● fr24feed.service - Flightradar24 Decoder & Feeder
Loaded: loaded (/etc/systemd/system/fr24feed.service; enabled; vendor preset: enabled)
Active: activating (start-pre) since Sat 2019-08-10 20:23:11 HKT; 18s ago
Cntrl PID: 1805 (install_dump109)
Tasks: 4 (limit: 1604)
Memory: 68.9M
CGroup: /system.slice/fr24feed.service
Aug 10 20:23:11 raspberrypi systemd[1]: Starting Flightradar24 Decoder & Feeder...
Aug 10 20:23:30 raspberrypi systemd[1]: fr24feed.service: Control process exited, code=exited
Aug 10 20:23:30 raspberrypi systemd[1]: fr24feed.service: Failed with result 'exit-code'.
Aug 10 20:23:30 raspberrypi systemd[1]: Failed to start Flightradar24 Decoder & Feeder.
pi@raspberrypi:~ $ journalctl -xe
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
--
-- Automatic restarting of the unit fr24feed.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Aug 10 20:23:31 raspberrypi systemd[1]: Stopped Flightradar24 Decoder & Feeder.
-- Subject: A stop job for unit fr24feed.service has finished
-- Defined-By: systemd
--
-- A stop job for unit fr24feed.service has finished.
--
-- The job identifier is 1300 and the job result is done.
Aug 10 20:23:31 raspberrypi systemd[1]: Starting Flightradar24 Decoder & Feeder...
-- Subject: A start job for unit fr24feed.service has begun execution
-- Defined-By: systemd
--
-- A start job for unit fr24feed.service has begun execution.
--
-- The job identifier is 1300.
Aug 10 20:23:46 raspberrypi systemd[1]: Reloading.
pi@raspberrypi:~ $How can I fix this to connect to the receiver? Thanks a lot for your help.
↧
emergency landing in dublin last day
hi i am not sure to the right forum section i have seen last day on the flightradar24 a emergency landing in dublin the squak was 7700 and i will information was the emergency was the airline was air canada rouge and the sighn was ac1901 and rou1901 from athen to toronto please for more information.
↧