FlightAware Discussions

Announcing PiAware 4.0!

Me too. The scroll bar is missing. Cleared the cache etc.
I can get to the stuff at the top of the list by zooming the page out to 50%.
Firefox 81.0.1 (64-bit)

My list all works nothing missing
using google chromeeeee

It may be a screen resolution issue. A scroll bar would be a nice addition.

I am using Chrome.

Hello all.

I just recently built a PiAware 4.0 from SD Card Image and now added a few more options like VRS and feeding other services such as ADSB Exchange, FR24 and PF.

Any way to “upgrade” to the Touch Screen Version without re-building?

Thank you!!

Everything works great, but I used to have a nice status message on my tiny pi screen and now I have nothing. All white. Do I need to go back to 3.8?

I’m unable to access any of the dump1090 or PiAware upgrade servers. My internet access is otherwise fine. Could you please advise? Here are the messages I received:

dump1090:
Could not resolve ‘raspberrypi.collabora.com
Err http://raspberrypi.collabora.com wheezy Release.gpg
Get:1 http://archive.raspberrypi.org wheezy Release.gpg [488 B]
Ign http://flightaware.com wheezy Release
Hit http://flightaware.com wheezy Release
Get:3 http://archive.raspberrypi.org wheezy/main armhf Packages [144 kB]
Hit http://flightaware.com wheezy/piaware armhf Packages
Ign http://archive.raspberrypi.org wheezy/main Translation-en
Err http://flightaware.com wheezy/main armhf Packages
404 Not Found
Err http://flightaware.com wheezy/contrib armhf Packages
404 Not Found
404 Not Found
Err http://flightaware.com wheezy/non-free armhf Packages
Err http://flightaware.com wheezy/rpi armhf Packages
Ign http://flightaware.com wheezy/main Translation-en
Ign http://flightaware.com wheezy/contrib Translation-en
Ign http://flightaware.com wheezy/non-free Translation-en
Ign http://flightaware.com wheezy/piaware Translation-en
W: Failed to fetch http://flightaware.com/mirror/raspbian/raspbian/dists/wheezy/contrib/binary-armhf/Packages 404 Not Found
Reading package lists…
W: Failed to fetch http://flightaware.com/mirror/raspbian/raspbian/dists/wheezy/non-free/binary-armhf/Packages 404 Not Found
W: Failed to fetch http://flightaware.com/mirror/raspbian/raspbian/dists/wheezy/rpi/binary-armhf/Packages 404 Not Found

PiAware:
*** running command ‘/usr/lib/piaware/helpers/run-apt-get update’ and logging output
performing manual update, action: piaware
Could not resolve ‘raspberrypi.collabora.com
Hit http://archive.raspberrypi.org wheezy Release.gpg
Hit http://flightaware.com wheezy Release.gpg
Hit http://archive.raspberrypi.org wheezy/main armhf Packages
Hit http://flightaware.com wheezy/piaware armhf Packages
Ign http://archive.raspberrypi.org wheezy/main Translation-en
Err http://flightaware.com wheezy/contrib armhf Packages
404 Not Found
Ign http://flightaware.com wheezy/non-free Translation-en
Err http://flightaware.com wheezy/rpi armhf Packages
Err http://flightaware.com wheezy/non-free armhf Packages
404 Not Found
Ign http://flightaware.com wheezy/main Translation-en
Ign http://flightaware.com wheezy/piaware Translation-en
W: Failed to fetch http://flightaware.com/mirror/raspbian/raspbian/dists/wheezy/main/binary-armhf/Packages 404 Not Found
W: Some index files failed to download. They have been ignored, or old ones used instead.
*** running command ‘/usr/lib/piaware/helpers/run-apt-get upgrade-package piaware’ and logging output
Reading package lists…
W: Failed to fetch http://flightaware.com/mirror/raspbian/raspbian/dists/wheezy/rpi/binary-armhf/Packages 404 Not Found
Building dependency tree…
Reading state information…
0 upgraded, 0 newly installed, 0 to remove and 211 not upgraded.

Wheezy is unsupported (by FlightAware, the Pi Foundation, and upstream Debian). Please reimage with a recent sdcard image.

Seamless upgrade via the console, great job team :smiley: :love_you_gesture:

An interesting effect. On every reboot, the serial port number changes. Initially, my GPS receiver is connected as /dev/ttyACM0. Reboot - /dev/ttyACM1 Reboot - /dev/ttyACM0 …ACM1,ACM0,ACM1,ACM0,.etc. How to permanently assign only ttyACM0 to this USB-device?

You can create a symlink automatically…

Example:

If your device has a unique serial number you can use the following rule:
/etc/udev/rules.d/50-gps.rules:

SUBSYSTEM=="usb", ATTRS{serial}=="UBLOX001", MODE="0666"
SUBSYSTEM=="tty", ATTRS{serial}=="UBLOX001", SYMLINK+="ttyGPS1"

That automatically creates symlink /dev/ttyGPS1 which points to whatever ttyACM device got assigned by the kernel whenever a device with serial number “UBLOX001” is connected. It also gives everyone read/write access to it. Substitute your correct serial number of course.

If your device doesn’t have a unique serial number but you have only one with the same vendor and product id, you can use the following rule.
/etc/udev/rules.d/50-gps.rules:

SUBSYSTEM=="usb", ATTRS{idVendor}=="1546", ATTRS{idProduct}=="01a9", MODE="0666"
SUBSYSTEM=="tty", ATTRS{idVendor}=="1546", ATTRS{idProduct}=="01a9", SYMLINK+="ttyGPS"

That automatically creates symlink /dev/ttyGPS which points to whatever ttyACM device got assigned by the kernel whenever a device with vendor id 1546 and product id 01a9 is connected. Of course this doesn’t work so well if you have more than 1 of the same type of device.

Either way, you can use the predictable symlink names instead of the unpredictable ttyACMx names.

Oh, there are commands to reload the rules without rebooting but reboot to be safe.

3 Likes

Since installing 4.0 everything has basically ground to a halt on the desktop. I keep getting an error bottom left of page " Problem fetching data from dump1090.
AJAX call failed (timeout: timeout). Maybe dump1090 is no longer running?
The displayed map data will be out of date."
I tried all the site configuration options in device commands and still the error poops up about once every 10 seconds or so. I haven’t altered anything just followed the upgrade instructions and now takes forever to refresh.

Worked for me too, thanks

I’ve been running the update since release and have seen a noticeable drop in CPU usage. Nice work, team!

2 Likes

Hi. I have just upgraded from a Pi Zero running PiAware 3.8.1, to a Pi3+ running PiAware 4.
I have now started to receive signals from 250+ miles. Is this down to version 4 software, or now using a Raspberry Pi3+?
Nothing else has changed. Just curious really. :nerd_face:
Nigel

What did you achieve before?

I had a very small improvement by moving from a Pi3 to a Pi4, but i would rate this more as default deviation.

Hi foxhunter. I was getting less that 30ish hits on the 200-250 miles limit. I’ve never had any hits on the 250+ limits. the only thing that has changed is the PiAware software, and changed to a Pi3+ from a Pi Zero W. Not sure what is the cause of my greater range. :thinking:

Hi @eric1tran - sorry for the late reply - yes it solved the problem for me too :slight_smile:
For what it’s worth, I also restored a slight enhancement to my script.js to allow a few extra colors, since I have more than one range ring. This is my approach:

			    var ringStyle = new ol.style.Style({
                        fill: null,
                        stroke: new ol.style.Stroke({
                                color: '#ffff00',
                                width: 1
                        })
                });

                var ringStyle2 = new ol.style.Style({
                        fill: null,
                        stroke: new ol.style.Stroke({
                                color: '#40ff00',
                                width: 2
                        })
                });

                var ringStyle3 = new ol.style.Style({
                        fill: null,
                        stroke: new ol.style.Stroke({
                                color: '#ff00ff',
                                width: 1
                        })
                });

Then, a simple change further down where the style is set…

			feature.setStyle( i == 0 ? ringStyle2 : ( i == 1 ? ringStyle3 : ringStyle ) );

Thanks again!

2 Likes

Awesome. I made the same adjustments on mine as well :smiley: I’ll probably add it as a SkyAware feature since the rings are sometimes hard to see, especially with the new dark maps

1 Like

@hphillip

Great! :+1:
Having each ring in a different color makes it easy to judge the distance at a glance.

 

Couple of years ago I have done this, but in slight different way i.e. as follows

Colored Range Circles Alternating Red/Blue (like VRS)
and
Made Circles dashed line instead of solid line

 

 

1 Like

Pi Zero needing cable/adaptor (with losses) to attach the dongle whereas Pi3+ has direct USB plug in??
Just a thought?