All times are UTC - 6 hours [ DST ]




Post new topic Reply to topic  [ 376 posts ]  Go to page Previous  1 ... 12, 13, 14, 15, 16  Next
Author Message
 Post subject: Re: Multilateration (MLAT) now available on PiAware!
PostPosted: Thu Dec 22, 2016 12:04 am 
Offline
HenryAbbott - FlightAware user avatar

Joined: Sat May 28, 2016 9:04 am
Posts: 1
On my stats page:
http://flightaware.com/adsb/stats/user/HenryAbbott

I see three sites. Only the middle one shows m-lat as active. Is there some option that must be activated or selected for the other two sites to also show m-lat as active? Or does it simply mean that other two sites never see any m-lat signals. This is important, as we are mainly interested in seeing small aircraft.

If it is some setting or option that I must activate, please give details.

It might also be that my lat-long info is not accurate. Where do I reset this?

If it is a lack of stations I might just try and get some F24 guys to contribute to FA as well or see if I can get another interested soul with 24h internet connection.

Looking forward to your comments!
Henry


Top
 Profile  
 
 Post subject: Re: Multilateration (MLAT) now available on PiAware!
PostPosted: Thu Dec 22, 2016 6:59 am 
Offline
FlightAware Staff
dbaker - FlightAware user avatar

Joined: Mon Jul 25, 2005 12:00 am
Posts: 2838
Location: FlightAware WHQ
HenryAbbott wrote:
On my stats page:
http://flightaware.com/adsb/stats/user/HenryAbbott

I see three sites. Only the middle one shows m-lat as active. Is there some option that must be activated or selected for the other two sites to also show m-lat as active? Or does it simply mean that other two sites never see any m-lat signals. This is important, as we are mainly interested in seeing small aircraft.

If it is some setting or option that I must activate, please give details.

It might also be that my lat-long info is not accurate. Where do I reset this?

If it is a lack of stations I might just try and get some F24 guys to contribute to FA as well or see if I can get another interested soul with 24h internet connection.

Looking forward to your comments!
Henry


The other sites support it, there's just not enough coverage in your area -- we need more PIAware and FlightFeeders to really do MLAT well in your area.


Top
 Profile  
 
 Post subject: Re: Multilateration (MLAT) now available on PiAware!
PostPosted: Thu Dec 22, 2016 9:21 am 
Offline
FlightAware Staff
ericcarlson - FlightAware user avatar

Joined: Sun Jan 01, 2006 5:00 pm
Posts: 72
For MLAT to work, we need at least 4 receiver sites (preferably more) receiving the same signal from a given aircraft at the same time. Additionally, each site must have MLAT-capable PiAware (or FlightFeeder) software running on it. With only 3 sites total in your area, we do not have enough coverage to do MLAT. When enough sites are available, MLAT calculations will start automatically.


Top
 Profile  
 
 Post subject: Re: Multilateration (MLAT) now available on PiAware!
PostPosted: Sat Dec 24, 2016 10:48 am 
Offline
FlightAware Member
PeterHR - FlightAware user avatar

Joined: Sat Jan 18, 2014 11:02 am
Posts: 695
Location: UK
On the map it looks like a sparsely populated area, the present three receivers are spread over 100 miles

The receivers for MLAT need to more or less surround the planes and must all receive mode S signals from the planes - with the 100 miles spread, they will all only see high altitude planes.

To see the low ones, you would need a receiver spacing of 5 - 30km and the four (or more) receivers.

PiAware raspberry pi based receivers would do the job, but getting hold of the bits to put them together can be torturous and expensive in SA ... then you need Internet availability to connect them up.

Could the planes be equipped with Flarm ( https://en.wikipedia.org/wiki/FLARM ) - this can work like a much lower cost ADSB with the planes transmitting thier location, so you'd just need a local reciever.


Top
 Profile  
 
 Post subject: Re: Multilateration (MLAT) now available on PiAware!
PostPosted: Mon Jan 16, 2017 1:58 am 
Offline
davidgoe - FlightAware user avatar

Joined: Thu Oct 15, 2015 8:53 pm
Posts: 18
I'm the Seattle area and have lots of MLAT syncs:

Feeder Type: PiAware (SD Card) 3.1.0
Multilateration (MLAT): Supported / Enabled (synchronized with 47 nearby receivers)

but I'm not seeing MLAT aircraft on the http://piaware:8080 map. This is in spite of seeing MLAT tracks (with lat/lon) for the missing aircraft (based on ICAO) looking at the output from port 12345 directly on the PI itself.

I haven't changed anything on my end. Has anything changed with the HTML rendering engine for the http://piaware:8080 page? ADS-B flights still shows up fine.

Thanks,

David


Top
 Profile  
 
 Post subject: Re: Multilateration (MLAT) now available on PiAware!
PostPosted: Mon Jan 16, 2017 5:19 am 
Offline
FlightAware Staff
obj - FlightAware user avatar

Joined: Tue Sep 30, 2014 7:14 pm
Posts: 3193
Uh, the piaware sdcard image does not produce output on port 12345. Are you running a modified image?


Top
 Profile  
 
 Post subject:
PostPosted: Mon Jan 16, 2017 6:05 am 
Offline
rosen85 - FlightAware user avatar

Joined: Wed Apr 06, 2016 8:40 am
Posts: 35
Location: Kozloduy
Obj is right. Mlat is on port 30105.


Top
 Profile  
 
 Post subject: Re: Multilateration (MLAT) now available on PiAware!
PostPosted: Sun Jan 22, 2017 5:29 pm 
Offline
davidgoe - FlightAware user avatar

Joined: Thu Oct 15, 2015 8:53 pm
Posts: 18
No, not running any kind of custom bits.

Going through post history I do now remember that I added an extra port for MLAT output:

obj wrote:
There is a piaware config option that lets you control how mlat results are returned to you.
By default they will be fed back via port 30104 to your local dump1090 for display, but you can configure extra ways of returning the data too.
For your purposes, probably a Basestation-format listener is what you need:
Code:
$ sudo piaware-config -mlatResultsFormat "beast,connect,localhost:30104 basestation,listen,12345"
$ sudo service piaware restart

Then you can connect to port 12345 (e.g. with socat or nc) and you'll get mlat results in the CSV-like Basestation format (the same format as dump1090 produces on port 30003).


However this never caused a problem with my http://piaware:8080 display before, but I guess now it does. A regression maybe?

David


Top
 Profile  
 
 Post subject: Re: Multilateration (MLAT) now available on PiAware!
PostPosted: Sun Jan 22, 2017 5:45 pm 
Offline
FlightAware Member
Skibox - FlightAware user avatar

Joined: Tue Nov 17, 2015 12:33 pm
Posts: 55
davidgoe wrote:
However this never caused a problem with my http://piaware:8080 display before, but I guess now it does. A regression maybe?


Maybe you have turned off the original connection for mlat results by mistake, then they would not get fed back into dump.

In Piaware 3 the syntax for mlat-results also changed, so the old syntax for changing the setting will not work any more.

ads-b-flight-tracking-f21/mlat-data-into-vrs-separate-feed-t38230-25.html?hilit=mlatresults

/M


Top
 Profile  
 
 Post subject: Re: Multilateration (MLAT) now available on PiAware!
PostPosted: Sun Jan 22, 2017 6:07 pm 
Offline
davidgoe - FlightAware user avatar

Joined: Thu Oct 15, 2015 8:53 pm
Posts: 18
I haven't made any configuration changes in a year since the post I quoted earlier.

In the past year since I made the configuration change http://piaware:8080 has been working fine, until just recently.

I know very well that running with anything but the default configuration is not officially supported, and I guess recent some code change somehow broke it. I do hope there is still a way to independently collect the MLAT data without breaking the http://piaware:8080 display.

The ability to access the MLAT data you help create is the main benefit of feeding to FlightAware instead of FlightRadar24 and is why I exclusively feed to FlightAware. I hope that's still possible.

Thanks,

David


Top
 Profile  
 
 Post subject: Re: Multilateration (MLAT) now available on PiAware!
PostPosted: Sun Jan 22, 2017 6:19 pm 
Offline
FlightAware Member
Skibox - FlightAware user avatar

Joined: Tue Nov 17, 2015 12:33 pm
Posts: 55
davidgoe wrote:
In the past year since I made the configuration change http://piaware:8080 has been working fine, until just recently.

I know very well that running with anything but the default configuration is not officially supported, and I guess recent some code change somehow broke it. I do hope there is still a way to independently collect the MLAT data without breaking the http://piaware:8080 display.


Something obviously changed. Did you let FA auto-upgrade piaware or not?

Check the current operating settings, Is there any connection between fa-mlat and dump on 30104, or not?

Just repeating "I didn't change anything" isn't going to help. There is nothing wrong with mlat-results in the new version, but, again

1. The syntax for setting the mlat-results destination has changed
2. The actual mlat messages has changed, they are now coded in a different message.

/M


Top
 Profile  
 
 Post subject: Re: Multilateration (MLAT) now available on PiAware!
PostPosted: Sun Jan 22, 2017 7:13 pm 
Offline
FlightAware Staff
obj - FlightAware user avatar

Joined: Tue Sep 30, 2014 7:14 pm
Posts: 3193
davidgoe wrote:
I haven't made any configuration changes in a year since the post I quoted earlier.

Well, if it's nothing immediately obvious, then you need to provide enough information to actually diagnose the problem: your piaware and dump1090 versions, your actual configuration (output of "piaware-config"), contents of /var/log/piaware.log. Without that info, I'd just be guessing.


Top
 Profile  
 
 Post subject: Re: Multilateration (MLAT) now available on PiAware!
PostPosted: Mon Jan 23, 2017 10:32 am 
Offline
davidgoe - FlightAware user avatar

Joined: Thu Oct 15, 2015 8:53 pm
Posts: 18
Thanks for taking a mental interrupt to think about this at all; I understand that since I did make a change to the configuration to add an MLAT output port I'm likely the only one experiencing this problem.

I have "Auto-update PiAware software" enabled so in theory should be running the latest and greatest. According to 'My ADS-B' I have "PiAware (SD Card) 3.1.0". I'm not actually going to be able to RemoteDesktop into the Pi until this coming weekend to gather more version and other details/logs.

I was planning to just flatten and rebuild the Pi with a new PiAware image, verify everything works, and then use the new command to add an addition MLAT output port. However if you guys are interested for your own reasons in understanding why my config change is interoperating with the new bits this way, I'm more than happy to provide whatever details/logs are needed to debug.

Let me know, and thanks again for the help.

David


Top
 Profile  
 
 Post subject: Re: Multilateration (MLAT) now available on PiAware!
PostPosted: Mon Jan 23, 2017 12:29 pm 
Offline
FlightAware Staff
obj - FlightAware user avatar

Joined: Tue Sep 30, 2014 7:14 pm
Posts: 3193
If you can provide the things I asked for above when you have a chance then I'm happy to take a look.


Top
 Profile  
 
 Post subject: Re: Multilateration (MLAT) now available on PiAware!
PostPosted: Sun Jan 29, 2017 3:01 pm 
Offline
mdebusschere - FlightAware user avatar

Joined: Wed Mar 28, 2007 11:00 pm
Posts: 5
Trying my best to trouble-shoot / understand why I don't see any MLAT being recorded.
I am running piaware & dump1090-fa from package builds I made on a debian VM
using a blue ProStick Plus. It appears to be working for ADBS as FA is recording those
records but still no MLAT received (or processed ).

Is there anything which reports there is not enough overlap or receiving bad data?
If understand the log below, it is sending UDP packets.
The lat and long set appear to be set correctly.

Note: I am aware the antenea has limitted view right now.

Here are recent logs.
Code:

Jan 29 01:17:15 debian piaware[2174]: piaware version 3.3.0 is running, process ID 2174
Jan 29 01:17:15 debian piaware[2174]: your system info is: Linux debian 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1 (2016-12-30) x86_64 GNU/Linux
Jan 29 01:17:16 debian piaware[2174]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Jan 29 01:17:16 debian piaware[2174]: Connection with adept server at piaware.flightaware.com/1200 established
Jan 29 01:17:17 debian piaware[2174]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Jan 29 01:17:17 debian piaware[2174]: FlightAware server certificate validated
Jan 29 01:17:17 debian piaware[2174]: encrypted session established with FlightAware
Jan 29 01:17:17 debian piaware[2174]: adept reported location: 37.xxxx, -122.xxxx, 720ft AMSL
Jan 29 01:17:17 debian piaware[2174]: Receiver location changed, restarting dump1090
Jan 29 01:17:17 debian piaware[2174]: attempting to restart dump1090..
Jan 29 01:17:17 debian piaware[2174]: attempting to restart dump1090-fa using 'systemctl --no-block try-restart dump1090-fa.service < /dev/null'...
Jan 29 01:17:17 debian piaware[2174]: dump1090 restart appears to have been successful
Jan 29 01:17:17 debian piaware[2174]: logged in to FlightAware as user mdebusschere
Jan 29 01:17:17 debian piaware[2174]: my feeder ID is 740599b3-d0a7-41a3-7aff-xxxx
Jan 29 01:17:17 debian piaware[2174]: site statistics URL: https://flightaware.com/adsb/stats/user/mdebusschere#stats-37304
Jan 29 01:17:17 debian piaware[2174]: multilateration data requested
Jan 29 01:17:17 debian piaware[2174]: no ADS-B data program is serving on port 30005, not starting multilateration client yet
Jan 29 01:17:18 debian piaware[2174]: no ADS-B data program seen listening on port 30005 for 3 seconds, next check in 60s
Jan 29 01:17:49 debian piaware[2174]: 0 msgs recv'd from dump1090; 0 msgs sent to FlightAware
Jan 29 01:18:17 debian piaware[2174]: Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --r
esults beast,connect,localhost:30104 --results beast,listen,30105 --results ext_basestation,listen,30106 --udp-transport 70.42.6.191:8433:2614718051
Jan 29 01:18:17 debian piaware[2174]: mlat-client(2255): fa-mlat-client 0.2.8 starting up
Jan 29 01:18:17 debian piaware[2174]: mlat-client(2255): Using UDP transport to 70.42.6.191 port 8433
Jan 29 01:18:17 debian piaware[2174]: mlat-client(2255): Listening for Beast-format results connection on port 30105
Jan 29 01:18:17 debian piaware[2174]: mlat-client(2255): Listening for Extended Basestation-format results connection on port 30106
Jan 29 01:18:17 debian piaware[2174]: mlat-client(2255): Input connected to localhost:30005
Jan 29 01:18:17 debian piaware[2174]: mlat-client(2255): Input format changed to BEAST, 12MHz clock


Jan 29 11:22:49 debian piaware[2174]: 18496 msgs recv'd from dump1090-fa (528 in last 5m); 18496 msgs sent to FlightAware
Jan 29 11:27:49 debian piaware[2174]: 19009 msgs recv'd from dump1090-fa (513 in last 5m); 19009 msgs sent to FlightAware
Jan 29 11:32:49 debian piaware[2174]: 19387 msgs recv'd from dump1090-fa (378 in last 5m); 19387 msgs sent to FlightAware
Jan 29 11:33:31 debian piaware[2174]: mlat-client(2255): Receiver status: connected
Jan 29 11:33:31 debian piaware[2174]: mlat-client(2255): Server status:   connected
Jan 29 11:33:31 debian piaware[2174]: mlat-client(2255): Receiver:  113.0 msg/s received       29.1 msg/s processed (26%)
Jan 29 11:33:31 debian piaware[2174]: mlat-client(2255): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.4kB/s UDP to server
Jan 29 11:33:31 debian piaware[2174]: mlat-client(2255): Aircraft: 6 of 14 Mode S, 5 of 5 ADS-B used
Jan 29 11:37:49 debian piaware[2174]: 19705 msgs recv'd from dump1090-fa (318 in last 5m); 19705 msgs sent to FlightAware



Top
 Profile  
 
 Post subject: Re: Multilateration (MLAT) now available on PiAware!
PostPosted: Sun Jan 29, 2017 3:21 pm 
Offline
FlightAware Staff
obj - FlightAware user avatar

Joined: Tue Sep 30, 2014 7:14 pm
Posts: 3193
mdebusschere wrote:
Trying my best to trouble-shoot / understand why I don't see any MLAT being recorded.
I am running piaware & dump1090-fa from package builds I made on a debian VM

Try it on bare metal. You are getting no synchronization at all, not even attempts at it, which usually means that your mlat timing is very badly wrong. Last time I saw this was with a VM that would drop around 10% of USB traffic.


Top
 Profile  
 
 Post subject: Re: Multilateration (MLAT) now available on PiAware!
PostPosted: Sun Jan 29, 2017 11:21 pm 
Offline
mdebusschere - FlightAware user avatar

Joined: Wed Mar 28, 2007 11:00 pm
Posts: 5
obj wrote:
mdebusschere wrote:
Trying my best to trouble-shoot / understand why I don't see any MLAT being recorded.
I am running piaware & dump1090-fa from package builds I made on a debian VM

Try it on bare metal. You are getting no synchronization at all, not even attempts at it, which usually means that your mlat timing is very badly wrong. Last time I saw this was with a VM that would drop around 10% of USB traffic.


Unfortunately, I don't have bare metal available. The VM and host CPU is running at around 1%-4%, i7 CPU (Virtual Box) windows host.
Is there anyway to determine if this is USB traffic issue and/or anything else which can impact MLAT time?
It doesn't make sense the USB traffic can be dropped without any record of this happening.

I just restarted everything and noticed this message in log
Jan 29 19:38:06 debian piaware[455]: mlat-client(835): Server status: not synchronized with any nearby receivers

So, is there a way to determine if the issue is related to bad / missing data on my side or not enough nearby receivers to make it work?
The status message "not synchronized with any .." is some what ambiguous.


Top
 Profile  
 
 Post subject: Re: Multilateration (MLAT) now available on PiAware!
PostPosted: Mon Jan 30, 2017 7:34 am 
Offline
FlightAware Staff
obj - FlightAware user avatar

Joined: Tue Sep 30, 2014 7:14 pm
Posts: 3193
Where you are, there are tons of receivers. Unless you've put your antenna inside a metal shed or something it should be synchronizing ;-)
It does not tell you that the timing data is bad because it is _so far_ wrong that it doesn't even look like wrong timing any more, it looks like you're receiving different messages entirely (if that makes sense..)

I know that "silently drops lots of USB traffic" doesn't make sense, but that's what I saw previously with a VM which had the same symptoms as yours.
I'd suggest picking up a Pi and trying piaware on that if you don't have convenient bare metal.


Top
 Profile  
 
 Post subject: Re: Multilateration (MLAT) now available on PiAware!
PostPosted: Tue Jan 31, 2017 2:20 am 
Offline
mdebusschere - FlightAware user avatar

Joined: Wed Mar 28, 2007 11:00 pm
Posts: 5
obj wrote:
Where you are, there are tons of receivers. Unless you've put your antenna inside a metal shed or something it should be synchronizing ;-)
It does not tell you that the timing data is bad because it is _so far_ wrong that it doesn't even look like wrong timing any more, it looks like you're receiving different messages entirely (if that makes sense..)

I know that "silently drops lots of USB traffic" doesn't make sense, but that's what I saw previously with a VM which had the same symptoms as yours.
I'd suggest picking up a Pi and trying piaware on that if you don't have convenient bare metal.

Follow-up: to test outside of possible VM/USB issue I loaded the windows version of dump1090 and
made sure that works. Then I configured the piaware running in the VM to use the windows instance.
It is now showing sync and recording MLAT. So I don't have any info to blame the VM-USB at this point,
maybe it's the linux RTL driver / VM clocking, I don't have time to debug that issue any more.

As much as I don't want to plug another device in, I will probaly resort to getting a Pi3..
Hopefully, I can power it from POE - it will at least let me put it close to the antenna later on.

Thanks for the input.


Top
 Profile  
 
 Post subject: Re: Multilateration (MLAT) now available on PiAware!
PostPosted: Sun Feb 05, 2017 9:27 am 
Offline
on4amg - FlightAware user avatar

Joined: Thu Jan 26, 2017 3:58 pm
Posts: 1
I started receiving the 'This feeder is not being used for multilateration because its timing information appears to be unreliable...' message when I switched booting from a micro SD card to a USB SSD drive (connected to a UUGEAR powered USB hub). I am using the standard FA image running on a Pi3 with a FA Prostick connected to the powered USB hub.
What exactly is causing this behavior is difficult to say, CPU use is max. 20% (nothing else running on the Pi, NTP is running correctly). Since I'll move the entire setup outside I feel more comfortable having the SSD in the equation compared to a micro SD card.
I shall try another USB to SATAIII cable and potentially also a smaller and less power hungry SSD to see if that changes anything (although the total power consumption - 300mA Prostick, 200mA Pi, 4mA USB Hub and 1000mA SSD, 1504mA in total is well within spec, even for the PoE standard).

Update:
Booting from a USB connected device requires a PI firmware.
Going through the syslog again, I noticed there were frequent dumps being produced and this was also apparent when I started monitoring the PI's green led which was active ever few minutes. I did two things:
1. Disabled wifi (I do not need it) -> No go
2. Add dtoverlay=mmc in /boot/config.txt -> the dumps disappeared and and so did the activation of the PI's green led

This seems to have worked since the 'This feeder is not being used for multilateration because its timing information appears to be unreliable...' message has not shown since.
Now happily running on what seems to be a stable setup booting from SSD.


Top
 Profile  
 
 Post subject: Re: Multilateration (MLAT) now available on PiAware!
PostPosted: Mon Feb 06, 2017 4:16 am 
Offline
davidgoe - FlightAware user avatar

Joined: Thu Oct 15, 2015 8:53 pm
Posts: 18
obj wrote:
davidgoe wrote:
I haven't made any configuration changes in a year since the post I quoted earlier.

Well, if it's nothing immediately obvious, then you need to provide enough information to actually diagnose the problem: your piaware and dump1090 versions, your actual configuration (output of "piaware-config"), contents of /var/log/piaware.log. Without that info, I'd just be guessing.


Hi Obj,

I finally got the requested info. I uploaded /var/log/piaware.log to: https://1drv.ms/u/s!AlUorSoxzp3ujSUQhsOxCR8N-yFs

The other data is inline here:

pi@piaware ~ $ sudo piaware-config
allow-auto-updates yes # value set at /boot/piaware-config.txt:5
allow-manual-updates yes # value set at /boot/piaware-config.txt:4
image-type piaware # value set at /boot/piaware-config.txt:6
mlat-results-format "beast,connect,localhost:30104 basestation,listen,12345" # value set at /boot/piaware-config.txt:7

pi@piaware /usr/bin $ piaware -v
3.1.0

pi@piaware /usr/bin $ dump1090 --help
-----------------------------------------------------------------------------
| dump1090 ModeS Receiver Ver : flightaware-1.2-3 |

Thanks!

David


Top
 Profile  
 
 Post subject: Re: Multilateration (MLAT) now available on PiAware!
PostPosted: Mon Feb 06, 2017 7:26 am 
Offline
FlightAware Staff
obj - FlightAware user avatar

Joined: Tue Sep 30, 2014 7:14 pm
Posts: 3193
That all looks correct and I don't see any connection errors in the piaware log.

However your dump1090 is somewhat old. I suspect that it is too old to understand DF18 TIS-B positions, which is now how mlat results are formatted. Can you try upgrading to the latest dump1090-fa?


Top
 Profile  
 
 Post subject: Re: Multilateration (MLAT) now available on PiAware!
PostPosted: Mon Feb 06, 2017 5:20 pm 
Offline
davidgoe - FlightAware user avatar

Joined: Thu Oct 15, 2015 8:53 pm
Posts: 18
obj wrote:
Can you try upgrading to the latest dump1090-fa?


I wasn't aware I had to manually update components when I had auto-update enabled. That's fine though. Is there a link you can point me too to make sure I do it correctly?

Also, Seattle had a snow storm (I'm on a rural Island near Vashon) and I'm on generators, but my Pi and WiFi repeater are at the top of a tower with a UPS that won't last for much longer, so I might not get to it right away.

David


Top
 Profile  
 
 Post subject: Re: Multilateration (MLAT) now available on PiAware!
PostPosted: Mon Feb 06, 2017 8:45 pm 
Offline
FlightAware Staff
obj - FlightAware user avatar

Joined: Tue Sep 30, 2014 7:14 pm
Posts: 3193
The mismatch is partly my fault - we pushed an autoupdate of piaware, but for non-sdcard installs or for installs that were originally on 2.1, that only does piaware and not dump1090-fa as well. I'll look at pushing a corresponding autoupdate for dump1090-fa (it was low priority since it shouldn't have affected anything, but I missed the mlat result thing)

In the meantime you can push an update to dump1090 via the "send command to device" option on your ADS-B stats page


Top
 Profile  
 
 Post subject: Re: Multilateration (MLAT) now available on PiAware!
PostPosted: Sat Feb 11, 2017 5:01 pm 
Offline
davidgoe - FlightAware user avatar

Joined: Thu Oct 15, 2015 8:53 pm
Posts: 18
obj wrote:
In the meantime you can push an update to dump1090 via the "send command to device" option on your ADS-B stats page


Sorry this is progressing at the rate of a 17th century letter exchange between Boston and San Francisco...

I tried this and it didn't seem to work:

Code:
[2017-02-11 13:36 PST] manual update (user-initiated via their flightaware control page) requested by adept server
[2017-02-11 13:36 PST] performing manual update, action: dump1090
[2017-02-11 13:36 PST] *** running command '/usr/lib/piaware/helpers/run-apt-get update' and logging output
[2017-02-11 13:36 PST] run-apt-get(24535): /etc/apt/trusted.gpg.d/flightaware-archive-keyring.gpg does not exist; installing it
[2017-02-11 13:36 PST] run-apt-get(24535): /etc/apt/sources.list.d/piaware.list does not exist; creating it
[2017-02-11 13:37 PST] run-apt-get(24535): Err http://archive.raspberrypi.org wheezy Release.gpg
[2017-02-11 13:37 PST] run-apt-get(24535): Something wicked happened resolving 'archive.raspberrypi.org:http' (-5 - No address associated with hostname)
[2017-02-11 13:37 PST] run-apt-get(24535): Err http://raspberrypi.collabora.com wheezy Release.gpg
[2017-02-11 13:37 PST] run-apt-get(24535): Something wicked happened resolving 'raspberrypi.collabora.com:http' (-5 - No address associated with hostname)
[2017-02-11 13:37 PST] run-apt-get(24535): Err http://flightaware.com wheezy Release.gpg
[2017-02-11 13:37 PST] run-apt-get(24535): Something wicked happened resolving 'flightaware.com:http' (-5 - No address associated with hostname)
[2017-02-11 13:37 PST] 32949 msgs recv'd from dump1090 (836 in last 5m); 32807 msgs sent to FlightAware
[2017-02-11 13:37 PST] run-apt-get(24535): Ign http://archive.raspberrypi.org wheezy Release
[2017-02-11 13:37 PST] run-apt-get(24535): Ign http://raspberrypi.collabora.com wheezy Release
[2017-02-11 13:37 PST] run-apt-get(24535): Err http://flightaware.com wheezy Release.gpg
[2017-02-11 13:37 PST] run-apt-get(24535): Something wicked happened resolving 'flightaware.com:http' (-5 - No address associated with hostname)
[2017-02-11 13:37 PST] run-apt-get(24535): Ign http://flightaware.com wheezy Release
[2017-02-11 13:38 PST] run-apt-get(24535): Ign http://flightaware.com wheezy Release


and indeed looking on the PI itself, the 1090 version is still at 1.2-3.

If there a way to manually update these bits?

Thanks,

David


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 376 posts ]  Go to page Previous  1 ... 12, 13, 14, 15, 16  Next

All times are UTC - 6 hours [ DST ]


Who is online

Users browsing this forum: david.baker, jluebbe, MrNuke, tdrane and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to: