thank you for helping me here. Below is the output for the file:-
allow-auto-updates yes # value set at /boot/firmware/piaware-config.txt:67
allow-manual-updates yes # value set at /boot/firmware/piaware-config.txt:71
allow-mlat yes # value set at /boot/firmware/piaware-config.txt:75
allow-modeac yes # value set at /boot/firmware/piaware-config.txt:79
feeder-id xxxxxxxxxxxxxxxx # value set at /boot/firmware/piaware-config.txt:81
image-type piaware # value set at /usr/share/piaware-support/piaware-image-config.txt:5
manage-config yes # value set at /usr/share/piaware-support/piaware-image-config.txt:4
rtlsdr-gain max # value set at /boot/firmware/piaware-config.txt:60
wired-network yes # value set at /boot/firmware/piaware-config.txt:27
wireless-network yes # value set at /boot/firmware/piaware-config.txt:33
wireless-password # value set at /boot/firmware/piaware-config.txt:49
wireless-ssid MyWifiNetwork # value set at /boot/firmware/piaware-config.txt:48
I havenât heard of the ADSB image, ill go do some checking as a backup.
thank you for checking, this might help other users moving over to Airspy on the new SD card
Edit: install didnât work due to piaware-config.txt being in different folder on newer raspbian.
Should be fixed just rerun the install in 5 minutes. github sometimes needs a moment to update it.
Airspy Mini or Airspy R2. Iâve either sat here on my bench gathering dust. Along with some various LNAâs, Uptronics Nooelec, RTL triple ADSB, random Amazon one.
I donât think youâll see much difference between the two which means I would choose to use the mini for ads-b and keep the R2 available for other stuff where its better bandwidth might be more useful. Iâve been using a mini for over 5 years now and itâs given excellent performance.
Recently got an Airspy mini. Installed the Airspy_adsb software using wiedehopf automatic script in Post 1. All went well on the install (aside from a few operator errors), and it is running now on an RPI 4B. I also installed graphs1090. Thanks to wiedehopf.
A few questions/comments. Granted I havenât read all 4525 posts herein, so some of this might have been covered earlier.
When I first started running Airspy_adsb the ADS-B CPU Utilization graph showed more than 100% utilization. This is with SAMPLE_RATE= 12 and all other OPTIONS set at default values. Then looked at the clock frequency of the RPI vcgencmd measure_clock arm and it was 900 MHz. Edited /boot/firmware/config.txt to add: force_turbo=1 arm_freq=1200
This brought the CPU utilization down to about 85%, and I can bring it down to 50% by increasing the arm_freq to 1600 MHz. But why should I have to do this? Shouldnât the RPI adjust CPU freq on its own due to load? The RPI is not over temperature (temp = 47 C). Possibly this is a problem with the RPI itself?
What is the relationship of the Airspy RSSI shown in graphs1090 to the RSSI in Skyaware ?
Airspy RSSI is in the range of 30 to 70 dB. Skyaware shows approximately 0 to -35 dB.
The option -p packs I/Q data in 3-bytes (24 bits) vs not using the option where I/Q uses 4-bytes (32 bits). This reduces the USB data rate 25%. So why wouldnât it always be used? Whatâs the downside to using this option? Granted if the -p option is used, the RPI needs to unpack the data, but that shouldnât be much of a load.
Ok, but is there a summary user documentation for airspy use on Linux? Having to comb through 4500+ posts over 6 years looking for a given subject is like trying to find a needle in a haystack. The reason I thought that more than100% load was a problem was that I was looking at very old posts.
Thanks.
Thatâs good and I saw that in /etc/default/airspy_adsb file also.
Have you ever seen a block diagram of the Airspy mini ?
On the Airspy mini page it says I/Q output has no DC offset, or I/Q imbalance. How do they generate I/Q ? Also, when the sample rate is say 12 MSPS, assume thatâs 6 MSPS I and 6 MSPS Q.
My understanding is that is exactly what is done.
Raw samples from the ADC and the DSP generating I/Q in the computer.
It is referenced on the Airspy about page:
Ok, I was interpreting the write-up for the Airspy dongle to say that I/Q data was provided as an output. But I guess you could also say that âAirspyâ refers to the dongle + the software on the PC (Airspy_adsb). That would say that the sample rate from the dongle is always 20 MSPS and the rate reduction to 12 MSPS is done in Airspy_adsb software.
Their method of generating I/Q data is interesting: itâs not the classical approach of taking the samples from the A/D and mixing (i.e. multiplying) with sin and cos at the IF freq ( 5 MHz ) and then lowpass filtering the I and Q legs. I think their approach uses a Hilbert Transform, though Iâm not sure. Also there is a trick you can do in the mixer if the sample rate (20 MHz) is 4x the IF ( 5 MHz) : the multiplies are just by +1 and -1.
The fact that the I/Q formation is performed digitally rather than in the analog domain means that you have perfect quadrature (90 deg) and no I vs Q amplitude differences that you would have with the analog approach. However, I think the RTL-SDR dongle uses digital I/Q mixing as well. So, no advantage there for the Airspy. I think the Airspy advantage is 12-bit A/D (and higher sample rate of 20 MSPS) vs 8-bit A/D and 2.4 MSPS in the RTL-SDR dongle.
Also, see the block diagram that @LawrenceHill posted above.
But it could be that the I/Q formation process was later moved from the PC to the Airspy itself as I mentioned above. The Airspy has lots of computing power with the LPC4370 chip.