What is the changelog for version 1.0.18-7 (2016-07-12)?
Announcement
Collapse
No announcement yet.
Archived - Beta test MLAT software for Raspberry Pi
Collapse
This topic is closed.
X
X
-
Originally posted by JohnnyBravo View PostIt would actually be helpful if some people are willing to give it a try, just to see how often this error occurs.
- copy the ini file (sudo cp /etc/fr24feed.ini /etc/fr24feed-backup.ini): just in case
- stop the fr24feed service (sudo service fr24feed stop)
- do the "sudo apt-get upgrade"
- start the fr24feed service (sudo service fr24feed start)
: success
uname-a.png
sudoaptgetupgrade.png
fr24feederstatus.pngJRF: T-EDNY19
South Germany
Comment
-
It seems like the error has been found, but it doesn't manifest itself on Raspbian hence only certain people are affected.
A big thank you to Swen for helping to test a corrected build of the feeder!
I have asked FR24 support if the correction will be applied to all future upgrades on the standard repository that everyone uses and their reply was:
---------
Glad to hear that. Well, that's upto the developers to decide, I can't really say anything about that.
Best Regards,
Muazzam
Flightradar24
---------
Needless to say I am very disappointed with this response...
Myself and others go out of their way to get to the bottom of an error, pointing out exactly where the problem is, helping to test a rectified build and reporting back to FR24. To then only get the response of: we may implement it, but we may also not do it...
Dissapointed
Comment
-
any idea after the install some are failed?
[ ok ] FR24 Feeder/Decoder Process: running.
[ ok ] FR24 Stats Timestamp: 2016-07-31 20:34:59.
[ ok ] FR24 Link: connected [UDP].
[ ok ] FR24 Radar: T-KVYS1.
[ ok ] FR24 Tracked AC:.
[FAIL] Receiver: down ... failed!
[FAIL] FR24 MLAT: not running ... failed!
Comment
-
@nick223
This error message indicates that receiver (here dump1090-mutability) is either not running, or not connected to FR24 feeder.
Does map show planes? If yes, then receiver is running, and problem is in connection, may be due to wrong configuration. You can also check status of dump1090 by command
Code:sudo service dump1090-mutability status
See below my configurations. You can see and adjust your settings from browser by going to page http://<local ip of your pi>:8754/settings.html.
Screenshot of my settings.html page
settings.html.jpgLast edited by abcd567; 2016-07-31, 22:54.
Comment
-
Originally posted by abcd567 View Post@nick223
This error message indicates that receiver (here dump1090-mutability) is either not running, or not connected to FR24 feeder.
Does map show planes? If yes, then receiver is running, problem is in connection, may be due to wrong configuration. See below my configurations. You can see and adjust your settings from browser by going to page http://<local ip of your pi>:8754/settings.html.
Screenshot of my settings.html page
[ATTACH=CONFIG]7858[/ATTACH]
Would need to store externally and share link instead.Posts not to be taken as official support representation - Just a helpful uploader who tinkers
Comment
-
Still getting the last 2 fail. Plans are appearing on the dump but the receiver and Mlat failed on FR24
sudo service dump1090-mutability status
● dump1090-mutability.service - LSB: dump1090 daemon (mutability variant)
Loaded: loaded (/etc/init.d/dump1090-mutability)
Active: active (running) since Sun 2016-07-31 15:31:14 CDT; 2h 35min ago
Process: 363 ExecStart=/etc/init.d/dump1090-mutability start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/dump1090-mutability.service
└─404 /usr/bin/dump1090-mutability --net --ppm 0 --fix --lat 41.33...
Jul 31 15:31:14 raspberrypi systemd[1]: Started LSB: dump1090 daemon (mutabi....
Hint: Some lines were ellipsized, use -l to show in full.
Comment
-
Originally posted by nick223 View PostStill getting the last 2 fail. Plans are appearing on the dump but the receiver and Mlat failed on FR24
sudo service dump1090-mutability status
● dump1090-mutability.service - LSB: dump1090 daemon (mutability variant)
Loaded: loaded (/etc/init.d/dump1090-mutability)
Active: active (running) since Sun 2016-07-31 15:31:14 CDT; 2h 35min ago
Process: 363 ExecStart=/etc/init.d/dump1090-mutability start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/dump1090-mutability.service
└─404 /usr/bin/dump1090-mutability --net --ppm 0 --fix --lat 41.33...
Jul 31 15:31:14 raspberrypi systemd[1]: Started LSB: dump1090 daemon (mutabi....
Hint: Some lines were ellipsized, use -l to show in full.
When running DEV mode of Dump1090 (or any other separate version) it needs to be set to AVR(TCP) and connect to the AVR output (30002 usually) with servers OFF - as per ABCDs screenshot.
If it is configured correctly but still occuring, You need to stop FR24feed, And start it without service (sudo fr24feed start) to view what is happening.Posts not to be taken as official support representation - Just a helpful uploader who tinkers
Comment
-
Originally posted by nick223 View PostSo my dump says 7/25
so 7 with positions and 25 total? So am i only reporting planes? What about the other 18?
Screenshot and more info as to where you are reading this?
Remember Dump1090 virtual view can 'hang on' to aircraft for up to 2mins after being lost. FR24feed only counts ACTIVE data so may not match on-screen figures.
And tracked have full GPS information, mode-s (mlat) do not so are listed in the totalPosts not to be taken as official support representation - Just a helpful uploader who tinkers
Comment
Comment