Sorry, my mistake. I missed the command git fetch --all immediately after cd to folders dump1090 and piaware_ builder.
Thanks to @obj for pointing it out. I have now corrected that post.
1 Like
It is in liblimesuite-dev. I guess you just needed a newer version. My x86 test machine is also on 18.04 but I have recent myriadrf packages installed.
If you don’t actually need the support for other SDRs, it’s possible to build the dump1090-fa package with a subset of SDR support, e.g. --build-profiles=custom,rtlsdr will build with rtlsdr support only (see the README for more details)
2 Likes
More than a year of feeding with lots of readings in the discussions, but still things to learn.
Thanks. I’ve tried it on my both feeders and worked without issues.
2 Likes
Two new dependencies for v4.0 (in addition to those for ver 3.8.1)
1 Like
Updated RPi4b and built and installed the updated packages for my RockPi.
All good.
Good clean update!
1 Like
Thankyou soo much
all sorted working 4.0 model
1 Like
I updated my installation on x86 Ubuntu 20.04.1 LTS, using your instructions, by simply replacing in your instructions arm64 with amd64
Thank you!
2 Likes
We will look into this
Now finally it added support for a screen, and then it doesn’t even work. Screen is just white. Got excited for nothing.
What LCD hardware do you have, and what image did you try?
Hi. I assume I have missed something. I am currently running a Pi Zero with WiFi. Image version 3.8.1 on the SD Card. Thought I would go the hog and use a Pi 3+ with the LCD screen. Downloaded the 4.0 LCD image and installed to new SD card. After booting in the Pi 3+, it configures itself and after I connect the antenna I get Aircraft on the screen. Unfortunately, the MLAT is no going active. After reader some of the posts here it apparently has something to do with generating a new Unique Identifier. So, my question is, how do I get my original UI, from the Pi Zero installation, onto the new installation for the Pi 3+.
Thanks in advance.
Hey folks, I was interested in the Mode A/C hit count referenced above and found the following lines in my aircraft.json file. Am I correct that these “category”:“A3” entries are those?
{"hex":"c0480f","category":"A3","version":2,"sil_type":"perhour","mlat":[],"tisb":[],"messages":3657,"seen":81.0,"rssi":-24.1},
{"hex":"c08081","category":"A3","version":2,"sil_type":"perhour","mlat":[],"tisb":[],"messages":5150,"seen":295.0,"rssi":-23.7}
You will need to manually add the feeder-id to piaware-config.txt file to claim your existing feeder-id. Insert the SD card into a computer, open that file, and at the end of the file add the line:
feeder-id XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
where XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX is the feeder-id of your Pi Zero.
Sorry for the hassle, the next release will make it more convienent to do this via the LCD screen itself.
I tried the image, that supports LCD Displays (or so i thought atleast), With the name of “piaware-sd-lcd-card-4.0.img”.
The LCD display i have looks as same as the display used in your pictures, however, it just stays White, without showing anything.
1 Like
Check what model & manufacturer. There are many similar-looking LCD screens that are mutually incompatible. The sdcard image supports only specifically the Waveshare 3.5" model linked in the top post. A white screen indicates that the framebuffer is not initializing correctly, which usually means the sdcard configuration does not match the LCD model (either that or hardware damage)
1 Like
No, A3 is the ADS-B emitter category. The new fields are modea and modec. They only appear if true. You will only see them if you have mode A/C decoding enabled, obviously.
(Also the changelog wording is a bit inaccurate - it’s a true/false flag, not a count)
Thank you for your support.
I’ve done a fresh install in another RPi using the latest Piaware image, then a fresh install of Raspberry OS lite and still couldn’t add the "terrain limit rings.
Then I’ve done a fresh install of Piaware_3.7.2 and after having the file upintheair.json in /usr/share/dump1090-fa/html/upintheair.json I got the “terrain limit rings”.
In all excitement, I see upgraded sites with altered site ID. Remember to set feeder-id. The most future-proof way is to add a line
feeder-id 1234abcd-5678efgh-XXXX
to /boot/piaware-config.txt. Use the feeder-id when you first registered. (You can find that in your feeder page by selecting the old site.) I had this issue a when I first came up and had to make a new image. (Search led me to an old topic in this forum. But this probably belong to an FAQ and perhaps include in each release notes.)
3 Likes
@pretoescuro @hphillip @grsham Turns out OpenLayers6 Geometry constructors now require a coordinate array even if it’s empty. I’ll commit a fix in the next release.
For a quick fix, edit line 947 in /usr/share/dump1090-fa/html/script.js and add an empty array.
var geom = new ol.geom.LineString([]);
Let me know if this fixes your issues.
5 Likes
Problem solved, thank you.