Hi,
Upgraded to PiAware v3 SD card Img, all works, but:
Thank you in advance.
I think port 8080 just forwards to port 80. I can access mine using the default port 80. Lighttp is used as the webserver in V3.
Thank you,
changing
sudo nano /etc/lighttpd/lighttpd.conf
and restarting
sudo systemctl restart lighttpd
is working and now, I have it running on specific port.
Looking in
sudo nano /etc/default/dump1090-fa
the file is controlled by “fa_config_generator”
DECODER_OPTIONS=“–max-range 360”
NET_OPTIONS=“–net --net-heartbeat 60 --net-ro-size 1000 --net-ro-interval 1 --net-http-port 0 --net-ri-port 0 --net-ro-port 30002 --net-sbs-port 30003 --net-bi-port 30004,30104”
JSON_OPTIONS=“–json-location-accuracy 2”
RECEIVER_OPTIONS=“–device-index 0 --gain -10 --ppm 0 --net-bo-port 30005 --fix”
but I am not sure, where to find it … can anyone help?
I just want to add --modeac option.
Anyone over here knows how to get rid off X11 / X Server and have it headless?
On “piaware-sd-card-3.1.0.img”:
pi@piaware:~$ sudo /opt/vc/bin/tvservice -o
Powering off HDMI
pi@piaware:~$
If you want an image that’s more closely tailored to your particular setup then you may want to start from a regular Raspbian or Raspbian-lite image and install piaware/dump1090 onto that.
3.2.0 (to be released shortly) has support for configuring mode A/C support via piaware-config.
This is exactly what I do.
However I have few spare microSD cards, and whenever a new version of “piaware.img” is released, I write it on one of the spare card, slip the card into one of the Pis, run for few days and perform configurations and tweaks to see how it feels and performs. After I am done with, I remove the spare card and slip in the original microSD card.
3.2.0 (to be released shortly) has support for configuring mode A/C support via piaware-config.
Thanks. This will be great.
Sorry port 8080 doesn’t forward to port 80. Port 8080 is port like any other port in a Unix OS, yes Linux is Unix. The port for the Dump web page is set in one of the Dump config files but don’t remember the file name or path, it’s been a while. Best I recall, it’s off of /etc.
Just upgraded to 3.3.0 with new clean install, enabled in /boot/piaware-config.txt option “allow-modeac yes”, but do not see any Mode AC
sudo tail -f /var/log/piaware.log
Mar 17 19:32:14 RaspberryPi-2B-1GB-piaware piaware[494]: 49548 msgs recv’d from dump1090-fa (370 in last 5m); 49399 msgs sent to FlightAware
Mar 17 19:37:14 RaspberryPi-2B-1GB-piaware piaware[494]: 49932 msgs recv’d from dump1090-fa (384 in last 5m); 49783 msgs sent to FlightAware
Mar 17 19:38:01 RaspberryPi-2B-1GB-piaware piaware[494]: mlat-client(1006): Receiver status: connected
Mar 17 19:38:01 RaspberryPi-2B-1GB-piaware piaware[494]: mlat-client(1006): Server status: synchronized with 127 nearby receivers
Mar 17 19:38:01 RaspberryPi-2B-1GB-piaware piaware[494]: mlat-client(1006): Receiver: 221.4 msg/s received 36.8 msg/s processed (17%)
Mar 17 19:38:01 RaspberryPi-2B-1GB-piaware piaware[494]: mlat-client(1006): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.6kB/s UDP to server
Mar 17 19:38:01 RaspberryPi-2B-1GB-piaware piaware[494]: mlat-client(1006): Results: 12.9 positions/minute
Mar 17 19:38:01 RaspberryPi-2B-1GB-piaware piaware[494]: mlat-client(1006): Aircraft: 4 of 8 Mode S, 11 of 15 ADS-B used
Mar 17 19:42:14 RaspberryPi-2B-1GB-piaware piaware[494]: 50364 msgs recv’d from dump1090-fa (432 in last 5m); 50215 msgs sent to FlightAware
Mar 17 19:47:14 RaspberryPi-2B-1GB-piaware piaware[494]: 50823 msgs recv’d from dump1090-fa (459 in last 5m); 50674 msgs sent to FlightAware
There is no display mechanism for mode A/C on the webmap (there’s nothing useful to show, really)
If you have a client that can make use of A/C data, it can request it via the usual Beast command to enable A/C on port 30005; is it sending that command?