September 9, 2018, 10:05 am
Dear FR24-Team and -Feeders,
I have stopped feeding several weeks ago due to a reorganisation of my feeding equipment. I am planning to put a J-Pole Antenna through a venting hole to the top of the roof of my flat. Some day... (my landlord will freak out when she finds out, LOL).
Well today I tried rebooting my Raspberry running minibian with dump1090 and fr24feed but my Radar T-EDSB36 seems to be gone for good? With the former URL I used to check my reception there seems to be another user to be linked to the ID 5070 (sorry I cannot link directly due to the 4-Posts limitation).
Do I have to register a new radar or can I still use my old sharing key?
Sincerely yours
Michael, T-EDSB36.
↧
September 10, 2018, 12:00 am
Hey guys,
since Friday my feed is not feeding the network and i don't know how to solve it. Apparently my dump1090 is working fine and also AC's are tracked. But for some reasons the flights are not uploaded to fr24. I already updated the software on my pi and also restarted the pi/software but i still get stuck at this fr24 (8754) status page:
Linux/generic/static_arm/1.0.19-15
Updated: 08:57:45 GMT+0200 (W. Europe Daylight Time)
FR24 Link: Disconnected (connection error)
FR24 Radar Code: N/A
Local IP(s): XXX.XXX.XXX.XXX 2a02:908:e658:100:baed:123:dbd8:17e7
Aircraft Tracked:
(ModeS & ADS-B) 82
Aircraft Uploaded: N/A
Receiver: avr-tcp, Connected
MLAT running: NO
Any ideas/suggestions how to get him connected again?
↧
↧
September 10, 2018, 1:16 am
I am fairly new to sharing ADS-B data so am not too familiar with the correct setup.
I am having problems setting up my RSPDuo on Windows 7.
I connect the SDR to my computer via a USB cable and am not sure the correct path to add to question 4.3a during the initial setup procedure. I have tried /dev/tty/usb0004 with no joy.
My RSPDuo works on this computer ok with other software with no problem.
Any help would be appreciated,
Mick
↧
September 10, 2018, 10:40 am
I am logged into my account, but when I click on my Searched Aircraft and go to 3 -D View I cannot see the Normal Screen where the Distance between the 2 Cities and actual Miles flown and how many miles that are left and time to land.
I have tried to expand my Page I tried for over ( 1 Hour ) today and I wish they would extend the Yellow Scroll Bar to the East
Thanks
↧
September 10, 2018, 12:38 pm
I just recently received and installed a NooElec NESDR Mini 2. I used zadig and installed the dongle with the libusbK driver. I then downloaded and installed fr24feed and the initial setup went just fine but then when I went to launch it again it was giving me connection terminated message. I closed down the app and even went into task manager to make sure everything was shut down and tried it again. Still the same error message. I then tried running it as admin and that didn't help. I restarted my and tried again but still got the same message. My question is what is the device supposed to show up as in device manager and what category is it under?
Code:
[main][i]FR24 Feeder/Decoder
[main][i]Version: 1.0.19-15/generic
[main][i]Built on Feb 6 2018 10:20:41 (???/Windows/i386)
[main][i]Running on: Windows10.0
[main][i]Local IP(s):
[main][i]Copyright 2012-2018 Flightradar24 AB
[main][i]Had to remove this line because it contained a link
[main][i]Reader thread started
[master][i]Starting processing thread
[reader][i]Initializing reader
[time][i]Synchronizing time via NTP
[httpd][i]Server started, listening on 0.0.0.0:8754
[reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe --raw)
[reader][i]Connected to the receiver, configuring
[reader][i]Configured, processing messages
[time][i]Time synchronized correctly, offset +2.0214 seconds
[main][i]Feed Network client started
[main][i]RAW data server started
[feed][i]Downloading configuration
[raw][i]Initializing server
[raw][i]Starting server on 0.0.0.0:30002
[feed][c]Interval: 5s
[feed][c]Latitude: 42.1630
[feed][c]Longitude: -76.8959
[feed][c]GND: YES
[feed][c]NonADSB: YES
[feed][c]Timestamps: optional
[feed][c]Max range AIR: 350.0nm
[feed][c]Max range GND: 100.0nm
[feed][i]defined 4 servers
[stats][i]Stats thread started
[feed][n]KELM1@185.218.24.24:8099/UDP
[feed][n]connecting
[feed][n]connected via UDP (fd 980)
[feed][n]working
[reader][i]Connection terminated
[reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe --raw)
[reader][i]Connected to the receiver, configuring
[reader][i]Configured, processing messages
[reader][i]Connection terminated
[reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe --raw)
[reader][i]Connected to the receiver, configuring
[reader][i]Configured, processing messages
[reader][i]Connection terminated
↧
↧
September 10, 2018, 7:25 pm
All flights, flight time is more than 100 hours, the IOS version is normal.
捕获.PNG
↧
September 11, 2018, 3:15 am
Hi,
I am a premium member, in fact I joined just to remove the two icons for Google and App store.
but they are still showing, please help!
↧
September 11, 2018, 6:06 am
Hello guys,
I recently started feeding to FR24 and purchased: ADS-B USB Dongle (R820T2) from Jetvision. I am using Raspberry Pi 3 B+ and have placed the indoor antenna outside and the feeder currently has a maximum range of
120nm :) and average of
33nm :(.
Here comes my questions:
- What is the maximum range one can achieve using this dongle?
- Can you achieve 350nm by changing the antenna or do I need to purchase a better feeder hardware as well?
My feeder:
T-ESGG44
↧
September 11, 2018, 7:59 am
Hi, everyone! Not sure if anyone had done this already, so I just made this thread for new guys like me to create an intro. Anyway, newbie here. I'm glad to have found this great online air traffic community. I'm hoping to learn more from the other members here. Cheers!
↧
↧
September 5, 2018, 1:53 pm
Hi All,
I'm using an RTL-SDR dongle, so somewhere around 43dB of ADC dynamic range. I find that I rarely see aircraft more than 80 nautical miles away. Being located midway between Heathrow and Luton and under several airways, I have a large number of aircraft flying nearby.
Assuming I've got a setup that has aircraft 1 nm away at -3dBFS, is 100 nm range the absolute best I can reasonably expect? (100 being 40 dB more than 1 and 80 not being much different to 100 on a log scale).
If the receiver was somewhere different and so didn't have to cope with aircraft so close, could I tweak the gain up and see further as a result? For the purpose of the question I'm ignoring that this will raise the noise floor. I'm trying to understand if it's the ADC and nearby a/c which are limiting the receiver's range rather than something at RF.
Freddie
↧
September 12, 2018, 2:25 am
I heard a whining high pitched aircraft overhead just now, clearly on its way in to Northolt (this location in Stoke Poges is right under the lined up landing flight path in to Northolt from the West) and so hit Flightradar 24 expecting to see no flight plot at all (which is now the case for most military or UK government aircraft using this airport, although one used to be able to see the flight track but not the official origin or destination with most such flights, including the Queen's own helicopter).
So anyway I was impressed to find that with this Piaggio P180 aircraft from Bordeaux (which looks like a private business jet bringing someone back from either smart summer holidays or a major professional wine buying research trip) that at long last Northolt (NHT) is finally shown by Flightradar24 as an actual destination airport for the small number of flights in to the airport (there are never more than 20 inbound and outbound movements a day at the very most and frequently much less than this with a general declining trend since Farnborough and Biggin Hill etc began complaining about unfair competition from the military and/or making spiteful interventions about safety standards at the airport) who's transponder information is not now blacked out by this website as a result of some kind of agreement with the military and the government.
A copy of the screen capture for the said event is shown below.
I
Northolt P180 Flight.jpg
↧
September 12, 2018, 4:40 pm
Is there an explanation for why planes on the ground have such spotty coverage. I'm assuming it has to do with a combination of factors including coverage near the airport, old aircraft without ADS-B, buildings blocking receivers, etc?
For example, look at LAX. It would appear that there is good coverage on the south half of the field, but not the north. Would that indicate a receiver south of the field with a clear line of site to aircraft on the south, but when they go to the other side of the terminal, the terminal building blocks the signal?
Is there any way to determine where the receivers are located near an airport? It would be useful for figuring out where additional receiver(s) would be best placed for better ground coverage.
Also, will satellite-based receivers fix this in the future? Or will they only be used for areas not covered by ground stations?
Thanks!
↧
September 10, 2018, 12:04 pm
I recently purchased a NooElec NESDR Mini 2 and went through the setup procedures and everything seemed to be working fine. I installed the driver for the usb without an issue but when I went to start up fr24feed.exe after doing the initial setup it was giving connection terminated message. I shut down the program completely and check in my processes to make sure it still wasn't working and tried it again. Same thing with the connection terminated messages. So I tried again running it as admin but still got the same message. What should the device show up as in device manager once it has the correct driver installed and what category should it be under on windows 10.
Code:
[main][i]FR24 Feeder/Decoder
[main][i]Version: 1.0.19-15/generic
[main][i]Built on Feb 6 2018 10:20:41 (???/Windows/i386)
[main][i]Running on: Windows10.0
[main][i]Local IP(s):
[main][i]Copyright 2012-2018 Flightradar24 AB
[main][i]Took this line out because i was getting an error message about posting links
[main][i]Reader thread started
[reader][i]Initializing reader
[time][i]Synchronizing time via NTP
[httpd][i]Server started, listening on 0.0.0.0:8754
[master][i]Starting processing thread
[reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe --raw)
[reader][i]Connected to the receiver, configuring
[reader][i]Configured, processing messages
[reader][i]Connection terminated
[time][i]Time synchronized correctly, offset +1.0057 seconds
[main][i]Feed Network client started
[main][i]RAW data server started
[feed][i]Downloading configuration
[raw][i]Initializing server
[raw][i]Starting server on 0.0.0.0:30002
[feed][c]Interval: 5s
[feed][c]Latitude: 42.1630
[feed][c]Longitude: -76.8959
[feed][c]GND: YES
[feed][c]NonADSB: YES
[feed][c]Timestamps: optional
[feed][c]Max range AIR: 350.0nm
[feed][c]Max range GND: 100.0nm
[feed][i]defined 4 servers
[stats][i]Stats thread started
[feed][n]KELM1@185.218.24.22:8099/UDP
[feed][n]connecting
[feed][n]connected via UDP (fd 920)
[feed][n]working
[reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe --raw)
[reader][i]Connected to the receiver, configuring
[reader][i]Configured, processing messages
[reader][i]Connection terminated
[reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe --raw)
[reader][i]Connected to the receiver, configuring
[reader][i]Configured, processing messages
[reader][i]Connection terminated
[reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe --raw)
[reader][i]Connected to the receiver, configuring
[reader][i]Configured, processing messages
[reader][i]Connection terminated
↧
↧
September 13, 2018, 7:46 am
Hello,
i have installed flightradar on my raspberry Pi with raspbian stretch. Unfortunately, I always get the following error message by the fr24feed-status command:
Code:
[FAIL] FR24 MLAT: not running ... failed!
I have been trying to fix the problem for more than 2 days.
Unfortunately without success. I use the official FR24 image! This should work out of the box in my opinion after registering the radar. But do not do it! I'll install Debian 8 "jessie" for a test to see if it works with it.
IP.of.the.pi:8754 says:
Code:
FR24 Link: Connected via UDP
FR24 Radar Code:
Local IP(s): 192.168.178.20
Aircraft Tracked:
(ModeS & ADS-B) 0
Aircraft Uploaded: N/A
Receiver: dvbt, Connected
MLAT running: NO
↧
September 15, 2018, 12:53 am
Hi there,
Today I received my ADS-B dongle and ariel. Set up FR24 Feed on my Raspberry Pi. I have various challenges, including the IPv6 issue not allowing initial validation of my email address/location and the an error with DUMP1090 not working. I have, with the helpof this forum overcome all of these issues. I am now down to my last problem with MLAT. When I run sudo fr24feed-status I get the following:
[ ok ] FR24 Feeder/Decoder Process: running.
[ ok ] FR24 Stats Timestamp: 2018-09-15 07:41:34.
[ ok ] FR24 Link: connected [UDP].
[ ok ] FR24 Radar: T-YPPH91.
[ ok ] FR24 Tracked AC:.
[ ok ] Receiver: connected (0 MSGS/0 SYNC).
[FAIL] FR24 MLAT: not running ... failed!
I have stopped and started fr24feed and it occasionally works. But only brielfy when it does. I can use localhost and dump1090...gmap.html to view tracked aircraft when it does connect and occasionally it shows me online via the FR24 app on my iPad.
What have I done/missing to get MLAT working? I am fairly new to the Raspberry Pi so it could be something obvious!
Thank you in advance.
Richard.
↧
September 17, 2018, 12:02 pm
I have noticed that here in NW Germany a lot of aircrafts who send full ADS-B position data (says my sbs basestation) are tracked by MLAT (T-MLAT1). I always thought MLAt was for AC that do not send position data (mode-s only). Why are ADS-B AC tracked with MLAT? Thank You!
↧
September 17, 2018, 5:01 pm
My R-Pi has been working great for over a year. It's only fallen offline once or twice and rebooting it has always got it going again. I'm feeding to FR24 and FlightAware simultaneously. It's always worked great.
My system fell offline the other day. I rebooted it and both feeds came back online. When I used Putty to try to get into the R-Pi, it would not accept my password. That's very strange. So, now I can't get into it to see what it's problem is although both feeds are currently running fine. For now.
So two questions for the group:
1) How do I go about getting into my R-Pi if it is not liking my password? (and)
2) I would like to re-load the entire feeder software for both feeds. Is there a single script that I can get that will load both feeds? Where do I find that?
Thanks all,
Jim
↧
↧
September 17, 2018, 9:57 pm
Hi
I'm a Swiss living in Sydney and last Sunday i couldn't believe, when i spotted Edelweiss Air (EDW2018) approaching Sydney Intl' Airport. Has anyone an idea, what this plane is doing over here? Couldn't find any flightradar24 data...
Regards, Antonio
↧
September 18, 2018, 3:59 pm
Since you're here we'll assume you love flight tracking and have a passion for ADS-B hardware. Whether you've assembled a receiver kit or spent hours perfecting your own set-up, we know you're excited by the technology and flights you can follow. We're hiring someone to share that excitement with the aviation enthusiasts and professionals around the world who share data with Flightradar24 as our IoT Technical Support Specialist. This tech savvy Flightradar24 enthusiast will help data sharers get the most out of their hardware by providing them with up-time and coverage solutions. This position is open both to applicants who can work from our Stockholm, Sweden office and to applicants who are interested in working remotely with occasional travel to Stockholm.
Learn more about the position and apply today at
https://careers.flightradar24.com/jo...ecialist-ads-b
↧
September 19, 2018, 12:45 pm
Does anyone know what are the criteria based on which the planes are associated with radar sites on the web page?
For example, my radar site picks up a plane that took of from an airport close-by. I look on FR24 live tracker and it's there, and down, where that radar dish is shown it says Radar "T-KPHF1" and shows my site. Good.
The plane flies away, I can still see it on my local web-page (ADS-B), but, at not even 5 miles from me, the "Radar" changes to F-KFKN1. Well, that's a station at least 30-40 miles away, and probably it just picked up that plane. Why was it switched from my feed?
Why I ask this? Because most of the time, when I filter the Live tracker page I see zero planes as being associated to my radar. But I see multiple associated with other sites (mostly F-KFKN1, F-7NC21).
My question is... why? Is something that makes my data un-trusty or un-reliable? Because then, I would like to fix that.
Is that based on the maximum range? One of the sites doesn't share it's stats, the other indeed has a bigger range. I was imagining that the hand-over happens when I drop the signal, another radar is selected (from the many that are seeing that plane). Not that is preemptively switched at 10 miles out.
↧