I think I cloned the Git repository on the v2.1.0 image using a sudo command which may be causing your sudo issues…
Anyways v2.2.0 has gone through it’s debug/testing phase and an image will be released tonight.
There is a bug fix in v2.2.0 which fixes an issue noticed when PiAware v3.0.5 was released this morning which is causing an issue when installing the PiAware package using v2.1.0. Due to severity of this issue I will be removing the v2.1.0 image from GitHub. I would not recommend anyone using the v2.1.0 release and instead wait for the v2.2.0 image to be released later on tonight.
BTW the v2.2.0 branch containing a fix for the PiAware issue as well as other features and fixes has been merged into the master branch in the GitHub repository. If you are currently running v2.1.0 you can give v2.2.0 a shot using the upgrade instructions found in the README.md file which are that same instructions as in the past.
Hi Joe!
Thanks for the update.
Right now I am not at home, will try 2.2.0 fresh install tonight (1st attempt, 2.2.0 img, 2nd attempt Jessie Lt img + cloning: git clone github.com/jprochazka/adsb-receiver.git ).
The v2.2.0 image is up on GitHub. I would have made a more detailed announcement here but I just got done fighting with my new receiver hardware. Come to find out a brand new powered hub is apparently bad… Anyways site 30000 is now up and running using v2.2.0. It is getting late and I have grown weary of typing for the night. A more detailed announcement will be made in the morning.
Well stop the presses. the spinning wheel map and no graphs may be a chrome issue. Swapped over viewing to IE11 and its all there. Any suggestions why chrome wont work??
Downloaded 2.2.0 img https://github.com/jprochazka/adsb-receiver/releases/download/v2.2.0/adsb-receiver_2.2.0_raspbian-jessie-lite.zip
unzipped, burned img on formatted microSD card, inserted in RPi, powered up.
sudo raspi-config #expanded file system, set time zone, changed password
cd ~/asdb-receiver
./install.sh #configured dump1090
](http://)/install #configured portal
./install.sh #installed and configured data feeders (piaware, pfclient, fr24, adsbexchage, adsbexchange mlat client)
Finished install
All data feeders working OK
All Graphs displaying & Populating OK
Map with planes showing OK
adsbexchage MLAT working OK
pi@raspberrypi:~/adsb-receiver $ Thu Sep 1 05:06:54 2016 mlat-client 0.2.6 starting up
Thu Sep 1 05:06:55 2016 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking
Thu Sep 1 05:06:55 2016 Server says:
In-development v2 server. Expect odd behaviour.
The multilateration server source code is available under
the terms of the Affero GPL (v3 or later). You may obtain
a copy of this server's source code at the following
location: [github.com/mutability/mlat-server](https://github.com/mutability/mlat-server)
@abcd
Lots of questions now that I have it working. Do you loose performance by feeding 2 services off the one dongle?? Can you still go in to adjust gain? Just ones to hand quickly, I thought my detection rate appeared down using this when compared to a naked FA setup but the jury is still sitting on that. Apart from the new receiver setup, the only difference now for me is that I am also sending to ADSB xch at the same time.
cd ~
sudo nano /etc/default/dump1090-mutability
#ctrl+w then type keyword GAIN= and press Enter button
#The cursor will jump to line GAIN="max"
#Replace max by the gain value you want (I use 44.5 with FA Antenna+Filter+ProStick)
# save ctrl+o and close nano ctrl+x
#restart dump1090-mutability
sudo systemctl restart dump1090-mutability
Note: when dump1090-mutability is restarted, adsbexchange-mlat client reports disconnection, then reconnection as shown below:
sudo systemctl restart dump1090-mutability
Thu Sep 1 06:38:31 2016 Lost connection to 127.0.0.1:30005
Thu Sep 1 06:38:31 2016 Reconnecting in 30.0 seconds
Thu Sep 1 06:38:31 2016 Beast-format results connection with 127.0.0.1:30104: connection lost
pi@raspberrypi:~ $ Thu Sep 1 06:39:01 2016 Input connected to 127.0.0.1:30005
Thu Sep 1 06:39:01 2016 Input format changed to BEAST, 12MHz clock
Thu Sep 1 06:39:01 2016 Beast-format results connection with 127.0.0.1:30104: connection established
Now check that the new gain value has taken affect
pi@raspberrypi:~ $ sudo systemctl status dump1090-mutability -l
How are you on Chrome??? I don’t know why but when I did the clone method and jp’s img file, neither would show the map or graphs in Chrome, swap over to IE bingo!!!
I left my PuTTy’s terminal connected to RPI, but idle.
After a while I found the adsbexchange MLAt client is outputing status to the SSH terminal every 15 minutes.
This is ok if the terminal is idle, but if one is using it, this sudden input will create confusion, and will be a nuisance.
pi@raspberrypi:~ $ Thu Sep 1 06:51:56 2016 Receiver status: connected
Thu Sep 1 06:51:56 2016 Server status: ready
Thu Sep 1 06:51:56 2016 Receiver: 607.4 msg/s received 114.6 msg/s processed (19%)
Thu Sep 1 06:51:56 2016 Server: 0.0 kB/s from server 1.1kB/s TCP to server 0.0kB/s UDP to server
Thu Sep 1 06:51:56 2016 Results: 18.4 positions/minute
Thu Sep 1 06:51:56 2016 Aircraft: 8 of 110 Mode S, 15 of 41 ADS-B used
pi@raspberrypi:~ $ Thu Sep 1 07:06:56 2016 Receiver status: connected
Thu Sep 1 07:06:56 2016 Server status: ready
Thu Sep 1 07:06:56 2016 Receiver: 782.9 msg/s received 135.8 msg/s processed (17%)
Thu Sep 1 07:06:56 2016 Server: 0.0 kB/s from server 1.2kB/s TCP to server 0.0kB/s UDP to server
Thu Sep 1 07:06:56 2016 Results: 20.3 positions/minute
Thu Sep 1 07:06:56 2016 Aircraft: 15 of 122 Mode S, 10 of 46 ADS-B used
pi@raspberrypi:~ $
I see your name on a few antenna posts, I will run this pass you. Have a FA USB Pro stick, currently with the FA 1090 filter attached ( a bit better noise figures) going into a DPD productions 9db ADS-B outside antenna, RG213 cable. I have got a inline matchmaster masthead amplifier (matchmaster 10mm-SA18) 950 - 2400 mhz range, quoted 20db gain, which was used on my previous antenna setup ( small collinear whip antenna outside).
Do you think this will improve things as well if it is put back in the line??
How long is your coax run? RG213 sucks at 1.1Ghz (around 9db/100ft and poor shielding) without an amp. A mast head amp would fix this issue.
You may need to reduce the dongle gain considerably. I had a similar setup(FA 1.0 dongle, better filter, 35 ft LMR400UF and DPD antenna, no amp) and had to reduce the gain to 38db for best results.
The ADS-B Exchange script now sets up mlat-client to connect to their mlat-server.
Added the ability to display either the dump1090-fa or dump1090-mutability map.
Changed the bash function which retrieves config file variables so it works properly.
Fixed issue causing a package installation error when PiAware versions change.
–installed and configured dump1090, data feeders (piaware, pfclient, fr24, adsbexchage, adsbexchange mlat client) and web portal.
–mac address issue: spoofed mac address by adding below Wired adapter #1, line “hwaddress ether xx:xx:xx:xx:xx:xx” in file /etc/network/interfaces.
–dump1090 issue: edited /etc/modprobe.d/rtl-sdr-blacklist.conf and added following two lines
blacklist dvb_usb_rtl2832u
blacklist dvb_usb
–temprature graph issue: edited nano /home/pi/adsb-receiver/build/portal/graphs/make-collectd-graphs.sh
in function temp_graph_imperial() and function temp_graph_metric(), went to line line “CDEF:tfin=traw,1000,/” , and changed 1000 to 1
All data feeders working OK
All graphs displaying & populating OK
Map with planes showing OK
adsbexchage MLAT working OK
@JP @Obj
With two sites (Flightaware & Adsbexchange) calculating & feeding MLAT data back to my receiver, how I can distinguish which plane on my gmap.html is plotted by data fed back by Flightaware and which one plotted by data fed back by adsbexchange?
Maybe I will see same plane plotted twice, slightly away from each other, one plotted by flightaware date, other by Adsbexchange data ( I have seen this happening several times on Rdarbox24 web site, one plane plotted twice at short distance with each other, one by data from feeder and other by data from civil aviation)
That is something that you will need to work out yourself. I think VRS can distinguish data from different datafeeds. dump1090 does not have this ability.
Also, probably best to keep the adsbexchange questions elsewhere, not here.
( I have seen this happening several times on Rdarbox24 web site, one plane plotted twice at short distance with each other, one by data from feeder and other by data from civil aviation)