Quantcast
Channel: Flightradar24 Forum
Viewing all 5745 articles
Browse latest View live

Prop aircraft not showing up at parking spots

$
0
0
Hi,
I noticed in flight radar 24 that when the smaller prop aircraft land at a particular airport- it dosent track it right up to the parking stand- the line following the aircraft stops on the runway not like with the larger aircraft where the line stops at the parking stand. Why is this.

Simpe fix for RPi Feeder knocked down by auto upgrade to 1.0.19-2

$
0
0
CASE - 1:
Pi already had dump1090-fa or dump1090-mutability installed PRIOR to upgrade
(Raspbian or Piaware image)

Following method was TESTED by me and found successful

Step 1:
Open file /etc/rc.local for editing
Code:

pi@piaware:~$ sudo nano /etc/rc.local
OR
pi@raspberrypi:~$ sudo nano /etc/rc.local

Step 2:
Add a line sudo systemctl restart fr24feed ABOVE LAST LINE i.e. above exit 0

The file will become like shown below.

Code:

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

sudo systemctl restart fr24feed

exit 0

Step 3:
Save file (Ctrl+o) and close file (Ctrl+x)

Step 4:
Restart Pi
Code:

sudo reboot
Step 5:
Wait for 5 minutes after giving restart command, then check if fr24feed is working

(a) Type in your Browser's address bar ip-of-pi:8754 and see the status

(b) Give following command and see status
Code:

fr24feed-status

CASE - 2:
Pi24 image
CAUTION: This method is not tested by me as I did not have Pi24 Image running when Auto-update took place.

@Oblivion: If you have Pi24 image which was affected by this upgrade, can you please check/test this method and post results? Thank you.


(1) First of all make a backup copy of your settings file /etc/fr24feed.ini so that you can revert in case something breaks
Code:

#Make copy
sudo cp /etc/fr24feed.ini    /etc/fr24feed.ini.bak

#Check if copy has been made by giving command ls or dir
#If copying successful, you will see both the files fr24feed.ini AND fr24feed.ini.bak
ls

(2) Type in your Browser's address bar ip-of-pi:8754/settings.html

(3) Change settings as follows
- Change Receiver from DVB-T to AVR-TCP
- In HOST field, enter localhost:30002
- In COM/DEV/PATH field, remove any entry (such as /usr/lib/fr24/dump1090 OR /usr/bin/dump1090-mutability) and leave this field BLANK

(4) Click "Save" button, then "Restart" button. Both buttons are at bottom-right of settings page. Clicking save button will save current settings in the file /etc/fr24feed.ini

(5) Carry out All Steps of CASE-1 above.

"Talking" to the raspberry pi

$
0
0
I'm trying to set up a Raspberry with WiFi.
I'm an absolute noon on this.

Will I be able to hook the pi up to a TV with HDMI and configure the password etc from there, or is there no OS on a raspberry or was it an OS that I installed on it when I downloaded that file from flightradar24?

If there is no graphics, I read the alternative was to type in a bunch of commands in to the pi.

Sounds easy enough, IF YOU KNOW WHERE TO TYPE THEM!

Any help guys?

This is in a vacation house so I have to be prepared when I go there.

Best regards

Planespotting on the RUNWAY at London Heathrow airport Video!

$
0
0
Hey guys im new around here but wanted to share a planespotting video i made inside london Heathrow airport. Practically on the runway and really up close and personal with a variety of aircraft.

I cant post the link as im new but if you copy what i put below in to youtube it will be the first one to come up and be sure to let me know what you think either by replying to this thread or commenting on the video on YouTube.

One last thing if you do enjoy the video then please subscribe and like the video it really does help me out to keep doing what im doing! Anywhere heres the video, Enjoy!

https://www.youtube.com/watch?v=55Dg...qsqorV2afCyyRA

Many thanks,

James

RP3 FR24 image + integrated wifi not working

$
0
0
Hi guys!

I ve a RP3 with the official FR24 image (Jessie Lite) install on it. I would like to connect by wifi. Is it possible?

I have tried to connect by command line but is not working.

pi.png
Any idea?
Attached Images

dump1090 issues in latest feeder package

$
0
0
I just upgraded the fr24feed package on my RasPi from 1.0.18-9 to 1.0.19-2 and now dump1090 is missing in /usr/lib/fr24. Is this intentional?

Boeing 767-306(ER) Ceiba Intercontinental at Valencia

$
0
0
Boeing 767-306(ER) Ceiba Intercontinental “KIE-NTEM” (3C-LLU) Guinea Ecuatorial takeoff runway 30 Manises Valencia Airport (VLC)

Feed stats show off line after upgrade to 19.2 and 19.5 update?

$
0
0
Hi,

My PiZero operating OK for months,
Been having problem last few days with feeds status showing offline at flightradar24.com/account/feed-stats
Understand this was due to faulty 19.2 update.

Pi has done an automatic update to 19.5...still offline.
Powered off/on.
Stuck now and don't know how to fix being a linux and fr24 numpty.
Would appreciate any help,
Interestingly, the feed status bar chart does show that it went on line for about an our earlier this morning by itself, then went offline again.
Thanks.

SSH into pi shows:-

● fr24feed.service - Flightradar24 Decoder & Feeder
Loaded: loaded (/etc/systemd/system/fr24feed.service; disabled)
Active: active (running) since Sat 2018-01-20 10:42:52 UTC; 10min ago
Process: 572 ExecStartPre=/bin/chmod a+rwx /var/log/lighttpd (code=exited, status=0/SUCCESS)
Process: 569 ExecStartPre=/bin/chown -R nobody:nogroup /run/dump1090-mutability /var/log/fr24feed /run/fr24feed /dev/shm/decoder.txt (code=exited, status=0/SUCCESS)
Process: 566 ExecStartPre=/bin/touch /dev/shm/decoder.txt (code=exited, status=0/SUCCESS)
Process: 563 ExecStartPre=/bin/mkdir -p /run/dump1090-mutability /var/log/fr24feed /run/fr24feed /var/log/lighttpd (code=exited, status=0/SUCCESS)
Process: 559 ExecStartPre=/usr/lib/fr24/install_dump1090.sh (code=exited, status=0/SUCCESS)
Main PID: 575 (fr24feed)
CGroup: /system.slice/fr24feed.service
└─575 /usr/bin/fr24feed

Flightradar24 Feeder/Decoder
Linux/generic/static_arm/1.0.19-5
Updated: 10:53:27 GMT+0000 (GMT Standard Time)
FR24 Link: Connected via UDP
FR24 Radar Code: T-EGUA13
Aircraft Tracked (ModeS & ADS-B): 0
Aircraft Uploaded: N/A
Receiver: avr-tcp, Connected
MLAT running: NO
Actions:
Settings
Restart software
Terminate software
Show tracked aircraft list
Show status variables (*)

ac_map_size="3072"
build_arch="static_arm"
build_flavour="generic"
build_os="Linux"
build_revision="T201801191038"
build_timetamp="Jan 19 2018 10:38:52"
build_version="1.0.19-5"
cfg_baudrate=""
cfg_bs="no"
cfg_host="localhost:30002"
cfg_mpx="no"
cfg_path=""
cfg_raw="no"
cfg_receiver="avr-tcp"
cfg_windowmode="0"
d11_map_size="0"
feed_alias="T-EGUA13"
feed_configured_mode="UDP"
feed_current_mode="UDP"
feed_current_server="83.140.21.87"
feed_last_attempt_time="1516445383"
feed_last_config_attempt="1516445014"
feed_last_config_info=""
feed_last_config_result="success"
feed_last_connected_time="1516445383"
feed_last_disconnected_time="1516445375"
feed_status="connected"
feed_status_message=""
fr24key="f82c75cf8ca7ad54"
last_json_utc="1516445573"
last_rx_connect_status="E1"
mlat-ok="NO"
mlat-started="YES"
mlat_problem="no-config"
msg_ring_full="0"
msg_ring_length="0"
offline-mode="no"
rx_connected="0"
shutdown="no"
time_update_utc="1516445562"
time_update_utc_s="2018-01-20 10:52:42"
timing_is_valid="1"
timing_last_drift="-0.0001"
timing_last_offset="-0.0001"
timing_last_result="success"
timing_source="NTP"
timing_time_last_attempt="1516445014"
timing_time_last_success="1516445014"
timing_time_since_last_success="1516445014"

Fix for RPi Feeder knocked down by auto upgrade to 1.0.19-2

$
0
0
CASE - 1:
Pi already had dump1090-fa or dump1090-mutability installed PRIOR to upgrade
(Raspbian or Piaware image)

Following method was TESTED by me and found successful

Step 1:
Open file /etc/rc.local for editing
Code:

pi@piaware:~$ sudo nano /etc/rc.local
OR
pi@raspberrypi:~$ sudo nano /etc/rc.local

Step 2:
Add a line sudo systemctl restart fr24feed ABOVE LAST LINE i.e. above exit 0

The file will become like shown below.

Code:

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

sudo systemctl restart fr24feed

exit 0

Step 3:
Save file (Ctrl+o) and close file (Ctrl+x)

Step 4:
Restart Pi
Code:

sudo reboot
Step 5:
Wait for 5 minutes after giving restart command, then check if fr24feed is working

(a) Type in your Browser's address bar ip-of-pi:8754 and see the status

(b) Give following command and see status
Code:

fr24feed-status

CASE - 2:
Pi24 image
EDIT: This method is NOW tested by me as shown in next post below

(1) First of all make a backup copy of your settings file /etc/fr24feed.ini so that you can revert in case something breaks
Code:

#Make copy
sudo cp /etc/fr24feed.ini    /etc/fr24feed.ini.bak

#Check if copy has been made by giving command ls or dir
#If copying successful, you will see both the files fr24feed.ini AND fr24feed.ini.bak

(2) Type in your Browser's address bar ip-of-pi:8754/settings.html

(3) Change settings as follows
- Change Receiver from DVB-T to AVR-TCP
- In HOST field, enter localhost:30002
- In COM/DEV/PATH field, remove any entry (such as /usr/lib/fr24/dump1090 OR /usr/bin/dump1090-mutability) and leave this field BLANK

(4) Click "Save" button, then "Restart" button. Both buttons are at bottom-right of settings page. Clicking save button will save current settings in the file /etc/fr24feed.ini

My raspberry stopped is offline without any reason, please help

$
0
0
Hi folks,
I need help.
I've my own raspberry PI feeding data to Flightradar since a lot of time.
on Tuesday, it stopped work but I can't find out why.

on the raspberry everything seems ok, the page returns this status:

Flightradar24 Feeder/Decoder
Linux/generic/static_arm/1.0.19-2
Updated: 17:33:42 GMT+0100 (ora solare Europa occidentale)
FR24 Link: Connected via TCP
FR24 Radar Code: T-LICT1
Aircraft Tracked (ModeS & ADS-B): 0
Aircraft Uploaded: N/A
Receiver: dvbt, Connected
MLAT running: NO

If I go to my data sharing page, I stopped to share information since 2018-01-16 05:52:11.
I rebooted the Raspberry, nothing seems to give problem...

What have I to check ?

Please help!

my service status is:
pi@raspberrypi:/var/log $ sudo service fr24feed status
● fr24feed.service - Flightradar24 Decoder & Feeder
Loaded: loaded (/etc/systemd/system/fr24feed.service; enabled)
Active: active (running) since Wed 2018-01-17 12:57:43 CET; 1 day 4h ago
Main PID: 668 (fr24feed)
CGroup: /system.slice/fr24feed.service
└─668 /usr/bin/fr24feed

Jan 18 17:37:23 raspberrypi fr24feed[668]: 2018-01-18 17:37:23 | [reader][i]Configured, processing messages
Jan 18 17:37:23 raspberrypi fr24feed[668]: bash: /usr/lib/fr24/dump1090: No such file or directory
Jan 18 17:37:23 raspberrypi fr24feed[668]: 2018-01-18 17:37:23 | [reader][i]Connection terminated
Jan 18 17:37:23 raspberrypi fr24feed[668]: 2018-01-18 17:37:23 | [main][i]Terminating child process 27363 with SIGTERM
Jan 18 17:37:28 raspberrypi fr24feed[668]: 2018-01-18 17:37:28 | [reader][i]Connecting to DVBT receiver via (exe:///usr/lib/fr24/dump1090 --raw --mlat)
Jan 18 17:37:28 raspberrypi fr24feed[668]: 2018-01-18 17:37:28 | [reader][i]Connected to the receiver, configuring
Jan 18 17:37:28 raspberrypi fr24feed[668]: 2018-01-18 17:37:28 | [reader][i]Configured, processing messages
Jan 18 17:37:28 raspberrypi fr24feed[668]: bash: /usr/lib/fr24/dump1090: No such file or directory
Jan 18 17:37:28 raspberrypi fr24feed[668]: 2018-01-18 17:37:28 | [reader][i]Connection terminated
Jan 18 17:37:28 raspberrypi fr24feed[668]: 2018-01-18 17:37:28 | [main][i]Terminating child process 27364 with SIGTERM

USA Jet MD83 take off, DTW

$
0
0
USA Jet McDonnell Douglas MD83, N831US departing Detroit metro DTW runway 21R after clearing customs 1-20-18

fr24feed cannot connect

$
0
0
Hi, I want to ask a question,
yesterday suddenly I found that dump1090 was disappeared from my raspberry, I reinstalled it but from then, even though even though dump1090 and fr24feed are running fr24feed cannot connect to the server.
Can you help me
Thank you

Basic RaspberryPi with FR24 - halted as so many others - got it running again

$
0
0
There are numerous threads here about all sorts of configs, it is very confusing to read as a non-regular user of FR24.
Last year I just had a raspberry pi lying arond doing nothing, and so I bought the usb dongle, and set it up, it has worked nicely for quite a while.
Or, at least I thought so, because some ninkapoo 'upgraded' the software, and everything went dark.

The least you can expect is that the software works in the most basic setup, no extra frills, features or anything, and almost no direct access to it, it just feeds the FR24 site.
I got it quick fixed yesterday, the faulty software was at 1.0.19-2, by reimaging it to 1.0.18... and I was happy.
This morning I oddly went it to look at it again (I never do that), and it was now upgraded to 1.0.19-5, and AGAIN it didn't work.
Come on, how can you build an update package that doesn't work in the most basic form, on a clean install??? :mad:

So digging in to it, it seems that the problem is the dump1090 package, I read through most of the posts, and read a lot of 'definite solutions', that seemed to be a lot of work, and with a lot of extra's in it, I don't need that.

So now I've followed the advice in dump1090-issues-in-latest-feeder-package
It got it updated to 1.0.19-5, but still didn't work after that.
The dump1090 wasn't installed.

So I executed the lines from a bit further up in the thread that was highlighted in red.
That got it installed, and it started working immediately.
Now I have to spend my time observing that it works, sigh, why? :confused:

One good thing came of all this, I found the /dump1090 page, never knew that was there. Pretty fancy watching the neighboorhood airplanes as seen by you own receiver (though i haven't gotten it to know where I am, as of yet :) ).


P.S. Sorry about no links to the articles, I've been on a lot of forums, but never experienced one that was this restricted, stupid.

getting error code

$
0
0
Ive had my raspberry up for a year or longer now but i checked on it the other day and im getting a error could anyone help correct the issue


Active: failed (Result: start-limit) since Sat 2018-01-20 20:59:59 CST; 1 day

Jan 22 11:57:08 raspberrypi systemd[1]: fr24feed.service start request repeated too quickly, refusing to start.
Jan 22 11:57:08 raspberrypi systemd[1]: Failed to start Flightradar24 Decoder & Feeder.
Jan 22 11:57:08 raspberrypi systemd[1]: Unit fr24feed.service entered failed state.
pi@raspberrypi:~ $

FR24 Link: unknown ... failed!

$
0
0
[ ok ] FR24 Feeder/Decoder Process: running.
[ ok ] FR24 Stats Timestamp: 2018-01-19 23:07:24.
[FAIL] FR24 Link: unknown ... failed!
[ ok ] Receiver: connected (41988 MSGS/0 SYNC).
[FAIL] FR24 MLAT: not running ... failed!

Here's the log below. NTP is enabled and working on the system. If I manually run sudo fr24feed command it seems to run and sync the time correctly but I can't run it manually every time - and running it manually doesn't seem to update the web status page either. I am able to ping external sites also, so I don't think it's a networking issue.

Anyways, here's the log.

2018-01-19 16:39:54 | [main][i]FR24 Feeder/Decoder
2018-01-19 16:39:54 | [main][i]Version: 1.0.19-5/generic
2018-01-19 16:39:54 | [main][i]Built on Jan 19 2018 10:38:52 (T201801191038/Linux/static_arm)
2018-01-19 16:39:54 | [main][i]Copyright 2012-2018 Flightradar24 AB
2018-01-19 16:39:54 | [main][i]www dot flightradar24 dot com
2018-01-19 16:39:54 | [main][i]DNS mode: PING
2018-01-19 16:39:54 | [main][i]Automatic updates are ENABLED
2018-01-19 16:39:54 | [httpd][i]Server started, listening on 0.0.0.0:8754
2018-01-19 16:39:54 | [main][i]Reader thread started
2018-01-19 16:39:54 | [master][i]Starting processing thread
2018-01-19 16:39:54 | [main][i]MLAT data feed started
2018-01-19 16:39:54 | [reader][i]Initializing reader
2018-01-19 16:39:54 | [reader][i]Connecting to AVR-TCP receiver via (avr-tcp://10.10.1.116:30002)
2018-01-19 16:39:54 | [mlat][i]Waiting for MLAT configuration
2018-01-19 16:39:54 | [reader][e]Could not connect to avr-tcp://10.10.1.116:30002
2018-01-19 16:39:55 | [time][i]Synchronizing time via NTP
2018-01-19 16:39:56 | [time][e]Failed to synchronize time
2018-01-19 16:39:56 | [main][w]Failed to synchronize time, waiting 5 seconds
2018-01-19 16:39:59 | [reader][i]Connecting to AVR-TCP receiver via (avr-tcp://10.10.1.116:30002)
2018-01-19 16:40:00 | [reader][i]Connected to the receiver, configuring
2018-01-19 16:40:00 | [reader][i]Configured, processing messages
2018-01-19 16:40:01 | [reader][w]Setting new UTC offset: 0!
2018-01-19 16:40:01 | [time][i]Synchronizing time via NTP
2018-01-19 16:40:03 | [time][e]Failed to synchronize time
2018-01-19 16:40:03 | [main][w]Failed to synchronize time, waiting 5 seconds
2018-01-19 16:45:23 | [time][i]Synchronizing time via NTP
2018-01-19 16:45:25 | [time][e]Failed to synchronize time
2018-01-19 16:45:25 | [main][w]Failed to synchronize time, waiting 5 seconds
2018-01-19 16:45:30 | [time][i]Synchronizing time via NTP
2018-01-19 16:45:31 | [time][e]Failed to synchronize time
2018-01-19 16:45:31 | [main][w]Failed to synchronize time, waiting 5 seconds
2018-01-19 16:45:36 | [time][i]Synchronizing time via NTP
2018-01-19 16:45:37 | [time][e]Failed to synchronize time
2018-01-19 16:45:37 | [main][w]Failed to synchronize time, waiting 5 seconds
2018-01-19 16:45:42 | [time][i]Synchronizing time via NTP
2018-01-19 16:45:43 | [time][e]Failed to synchronize time
2018-01-19 16:45:43 | [main][w]Failed to synchronize time, waiting 5 seconds
2018-01-19 16:45:48 | [time][i]Synchronizing time via NTP
2018-01-19 16:45:50 | [time][e]Failed to synchronize time
2018-01-19 16:45:50 | [main][w]Failed to synchronize time, waiting 5 seconds
2018-01-19 16:45:55 | [time][i]Synchronizing time via NTP
2018-01-19 16:45:56 | [time][e]Failed to synchronize time
2018-01-19 16:45:56 | [main][w]Failed to synchronize time, waiting 5 seconds
2018-01-19 16:46:01 | [main][i]Feed Network client started
2018-01-19 16:46:01 | [feed][i]Downloading configuration
2018-01-19 16:46:01 | [e]Could not connect to feed.flightradar24 dot com, errno: 101
2018-01-19 16:46:01 | ERROR
2018-01-19 16:46:01 | [e]Could not retrieve configuration from Flightradar24
2018-01-19 16:46:01 | [feed][i]Failed on start, Sleeping 120 seconds
2018-01-19 16:46:03 | [time][i]Synchronizing time via NTP
2018-01-19 16:46:04 | [time][e]Failed to synchronize time
2018-01-19 16:46:06 | [time][i]Synchronizing time via NTP
2018-01-19 16:46:07 | [time][e]Failed to synchronize time

Actual flights not shown around SMV/LSZS St. Moritz/Davos, CH

$
0
0
Did you notice?
No actual flights are shown in a circle around the above airport, probably because of the world ecomonic summit and the world leaders gathering in Davos. Davos is close to St. Moritz.

Start error "Active:failed (result: start-limit)"

$
0
0
Dear.

Today my feeder installed on a dedicated pi went offline.

I updated the version for fix problems that I read on the last posts but after that when I try to restart my RBPi it don't work showing this error:

Active: failed (Result: start-limit)

What can I do?

have a nice day
Jacopo

How can I watch raw data on my Raspberry Pi ?

$
0
0
I searched the forum and didn't see this - so I'm asking here:

I am using a RaspberryPi to feed FR24 data. Is there a way I can open up a terminal connection to the R-Pi and observe the raw data that it is sending to FR24?

Thanks!

Jim

My FR24 feed failed three days ago

$
0
0
I have just noticed that my FR24 feed failed 22 Jan 11:48 and has not returned. I am running a Raspberry Pi in my loft with dump1090 installed which I believe is the FA version. Dump1090 looks ok when I log into the map so it seems to be just the feed. I have rebooted, sudo apt-get update and also I think I have installed the latest version of FR24 feed. A top command doesnt seem to show the process running either. Not sure where to go from here.

Fewer flights than expected displayed

$
0
0
I've suspected for some time now that I'm seeing only a fraction of the flights that should be visible. I have a silver subscription and all my settings are at default.

A couple of days ago, someone in a technical forum posted a link to an online article about how eastbound flights on the northern transatlantic route take advantage of the jetstream to boost their ground speed. The FR24 screenshot in the article showed many times the number of aircraft I could see the next day at about the same time of day.

I've just had a look at the route again and the display shows many more westbound flights than I usually see but very few eastbound traffic - fewer, in fact, than I normally see.

Is this normal? If not, what could be the reason? Here's a screenshot of what I got about half an hour ago (around 1:27 pm UTC):

Screenshot 1857 hrs IST.jpg
Attached Images
Viewing all 5745 articles
Browse latest View live