Really?
You’re not even trying 
(plus you’ll need to use the dev branch)
The simplest solution by far.
You aren’t really showing the error, please show this, it will really show the error.
sudo journalctl --no-pager -u dump978-fa
.
No, this one 
is simplest 
Thinking of ordering a Pi Zero W. Is there any difference preparing the SD card with Piaware 3.7.1 image for it? Can I switch cards between a Pi 3B and a Pi Zero W?
As long as the software version is new enough for the device in question, you can switch as much as you want.
I could even run my upgraded Stretch card on a RPi4 now that it’s updated.
Personally i dislike the zero because it’s missing a proper USB port and you need a cable to attach the dongle.
Also not sure how the power situation is with the zero.
But they probably tweaked it to a point where the port gives enough current to the dongle.
Thank you for reminding me of this important ‘detail’, as I had completely forgot. Never mind the Pi Zero W then.
I was shopping around and with all the cabling the price wasn’t nearly low enough to use it instead of the 3B+.
The processor is also really slow, it’s just too dated by now.
I am using this low-cost one since 2016:
.
IMPORTANT NOTE: No on-board WiFi
OS Image: Armbian (Currently Buster and Bionic)
Orange Pi PC – Armbian
I remember that suggestion, but Wi-Fi is a ‘must’ here.
pi@PI978:~ $ sudo journalctl --no-pager -u dump978-fa
– Logs begin at Wed 2019-07-31 08:36:11 CDT, end at Wed 2019-07-31 23:01:57 CDT. –
Jul 31 08:36:32 PI978 systemd[1]: dump978-fa.service: Service RestartSec=30s expired, scheduling restart.
Jul 31 08:36:32 PI978 systemd[1]: dump978-fa.service: Scheduled restart job, restart counter is at 1255.
Jul 31 08:36:32 PI978 systemd[1]: Stopped dump978 ADS-B UAT receiver.
Jul 31 08:36:32 PI978 systemd[1]: Started dump978 ADS-B UAT receiver.
Jul 31 08:36:32 PI978 systemd[1]: dump978-fa.service: Main process exited, code=killed, status=4/ILL
Jul 31 08:36:32 PI978 systemd[1]: dump978-fa.service: Failed with result ‘signal’.
Now that didn’t say much, let’s try this and see if it turns up an actual error:
sudo systemctl stop dump978-fa
sudo /usr/share/dump978-fa/start-dump978-fa
Yeah i’d recommend using stretch or building dump978-fa yourself.
This requires using the dev branch of the git repository and installing the required build dependencies. If you don’t know how to that, it’s back to using Stretch.
This Set has on-board WiFi.
All this for US $32.50 :
- Computer Board
- DC 5V Power Supply
- Plastic Case
Piaware SD Card image 3.8.0 released yesterday 03 -January-2020.
I have changed the title of this thread from 3.7.1 to 3.8.0
@obj : As I cannot edit the first post of this thread, can you please arrange to update following paragraph of first post? Thanks
Why change the title rather than create a new thread.
The title refers to the 352 post in the thread.
S
2 Likes
I am lazy 
1 Like
Upgraded with fresh SD card image installed.
Thanks again, man! Just got the familiar green-orange-green-green-green. Now I gotta install this at the airport and order another 978 thumb.
Unfortunately, I followed this guide to the letter to upgrade my PiAware at the house to dual-band.
I charged through and followed the guide on serializing the dongles but I’m using a nooElec 978 nano and the FA Orange Pro Stick.
At the step of serializing the 1090 receiver, the FA Orange threw a bunch of “access denied” sort of messages and now I can’t see or initialize it. My home station is now using a pair of nooelec receivers and the range has been cut by about 200 nautical miles.
Any advice on how to recover the pro stick, or am I out of luck?
Unplug both the dongles. Replug both the dongles after 30 seconds or more. Reboot Pi.
Now test:
rtl_test -t
Do you see both the dongles listed?
No. The only one that shows up is the Nooelec 978 with serial 00000978. There’s no device 1 at all.
This persists over several reboots and swaps of dongles. The orange can be seen by windows, as an RTL something-or-other FA but the pi fails to initialize the device every time, even on a fresh SD card and fresh buster image with no other dongles or config modifications (except ssh and the wifi info, of course).
I know it might have been a bonehead move, but perhaps the post needs a warning not to do that to the FA branded receivers?
FA branded rtl-sdr receiver normally have no problem with changing the serial.
The chip actual sdr chip used is no different than other rtl_sdr compatible sdrs.
The difference is mostly the quality of components and LNA and/or filter.
Remove the Nooelec and check only the FA stick.
You could also try using rtl_eeprom in windows:
https://ftp.osmocom.org/binaries/windows/rtl-sdr/
Download the current 32bit or 64bit binary zip, extract it and use rtl_eeprom on the command line just as you would on Raspbian.
Maybe someone else can give you a more detailed guide, i don’t normally use Windows.