You’re welcome
m
You’re welcome
m
Anybody with the 1.39 Version for the Pi ?
I don’t know what version I have. The airspy_adsb-linux-arm.tgz was written on my system on May24 2018
You can tell the version by running airspy_adsb -h
Well, I’m out of the testing game. All out of ideas, and without the proper hardware. I thought I had a bias-t inserter, but what i have is a ZAP-##-### thing that has one port facing amp/antenna and two ports facing back to receivers – one of the ports allows the passing of power (so you’d run a dongle or Airspy on it with bias T enabled) and the other you would run another dongle or Airspy without bias T turned on. That’s not what I was thinking it was. So I really can’t do a good test in my situation.
Mike
I have just measured the voltage on my N2 as follows with the Airspy R2 running at m20 - N2 powered by 12V psu that came with it and USB tester showed 5.00v off load and the following whilst running:
4.96V - 0.325A - 1.62W - All steady with no fluctuation.
Just waiting until the next Armbian update comes out which hopefully will have the later kernel which they say (Odroid forum) has cured usb problems!
There has been so much discussion and excitement about AirSpy lately, I am temted to buy (AirSpy+Pi4+psu+case+cooling fan). How much my wallet will loose weight?
There has been lot of excitement and enthusiasm about Odroid as well. What is so special about Odroid compared to RPi?
The Airspy is a really good radio - somewhat overkill for just ADSB, but you would see an improvement over an rtl-sdr. You’d be out about $170 for the R2 or $99 for the Mini plus the shipping. I personally use the mini, currently running at 20Mhz without a hitch on a Pi4. I never knew until the other day (reading this thread actually) that the mini would run > 12Mhz. I’ll probably grab an R2 as well for other uses, but closed source code is a serious pisser and it’s kept me from grabbing one so far.
So far as Odroid, the N2 hardware is superior to the Pi3/B and the driving force behind many sucking those up, but now that since the Pi4 has been introduced, that’s no longer the case. There have always been issues with their kernel support which can be hit and miss, but overall, they make some solid SBC’s. There are still many issues with the Pi4 as well, but one can venture to guess it will come around sooner than later based on history. With the latest EEPROM update, you can run a Pi4 all day long at 2Ghz so long as you have some sort of cooling. Really don’t need > 1GB ram either unless you plan on tinkering with Windows IOT - I can’t think of what else requires that much ram to run outside of Winblows.
Here is the case I prefer for the Pi4 - acts as a passive heatsink and works very well:
https://www.amazon.com/Flirc-Raspberry-Pi-Case-Kodi/dp/B07WG4DZR6
It will also house the LoveRPi POE hat (with some grinding):
https://www.amazon.com/LoveRPi-Power-Over-Ethernet-PoE-Raspberry-Model/dp/B07WD7HXSQ
You’re not even using the rtl-sdr LNA with the FA antenna
The Airspy is of most benefit for users wanting to maximize numbers mostly.
It’s suited to deal with the high message rates happening in Europe or dealing with trees in the way because it can pick up signals out of the noise a little better.
In your location and with what you are doing i don’t see any justification for the money spent.
Especially because you can easily setup a long range station with high gain (rtl-sdr LNA + FA antenna) and then a lower gain station with literally any antenna where you keep the strong messages low.
That is one of the advantages of the Airspy, the dynamic range. You don’t have to choose between local planes and long range.
But with two stations, you can get that advantage as well.
The Rpi4 on the other hand, i can see that being useful to you with all the compiling you do
It’ll be a lot quicker with that.
(I have managed to make the Airspy Mini work on 20 MHz using the Rpi3B+, but i get the impression that almost requires an adjustable power supply so you can feed the 3B+ 5.2 V
Anyway if you buy an RPi for use with the Airspy anyway, there is no reason not to use the Rpi4.)
I suppose if you want to listen to Airband or other audio, the Airspy will provide better quality than an rtl-sdr dongle.
But for occasionally doing that, that’s a lot of money as well.
I miss communicate. The file in that location is older, not identical with the one in use now, because I have switched from one way to launch it (via rc.local) to another (as a service) and the old tar file remained there.
There is no way to know the version of that file?
./airspy_adsb -h
That will use the local version in that folder versus the system version.
I agree with wiedehopf. If you think you need higher dynamic, then get the Airspy mini, it’s great for that. I have two close-by airports and an air traffic “lane” almost above me that create strong signals. I wanted to improve the reception of the far away ones with the same Pi. Well… it did indeed improve it, but not in the proportion of cost ($99), just like 25% better. Mainly because I still have the Pi3 that can’t make use of 20MHz option.
As for the Pi4, since I think you are still using a 2… that would be a nice step up. But again, that depends of how much is this hobby meaning to you. I was tempted too, but the whole thing (with 1GB RAM) is like $60. Add $10 for the 2GB version. And not being 100% compatible kept me from upgrading.
-bash: ./airspy_adsb: No such file or directory
Ah, I needed “cd airspy” before that…
The old file it’s version 1.37
The one that I am running is 1.40
FYI, somebody on Odroid forums (looks to be an Odroid person) indicated that each USB 3.0 port will provide up to 900 ma of power. I think the Airspy advertises that it uses max 500 ma (I’m not sure if that includes any power it might require to power an amp over bias tee or not).
And since it’s a 4-port USB hub, you should never have a problem with speed with just one port in use but might have a problem with combined speeds if you have multiple devices attached (I only have one).
So I’m thinking there should be enough power.
The preamp that I’m using says it only requires 56 ma for power.
So the issue some of us are having running 20/24 Mhz with an Airspy R2 on an Odroid N2 shouldn’t have to do with power availability.
mike
Yeah, grasping at straws.
To be honest i have no clue what the problem is.
Maybe there are just driver/kernel problems that somehow corrupt the data or reorder USB transfers or something strange.
MLAT is quite sensitive, just getting the required MSPS over USB is not enough.
So let’s hope that it improves.
In the meantime the RPi4 seems to be the device of choice for the task.
(Even if one user reports problems, he hasn’t yet responded to the suggestions)
@mtindor - I just happened to be bouncing through the Odroid N2 hardware specs again and there is just no way that board shouldn’t handle this without breaking a sweat unless it’s borked at the driver level.
Something else simple and easy to try is swapping USB cables. They are NOT created equal by any means and have personally pulled every last hair out in multiple projects only to find out that I was working with sub-par USB cables causing strange errors. Forgive me if you’ve already tried this, but it’s often overlooked during troubleshooting.
The USB cable is supplied with the Airspy R2 and should be of sufficient quality.
Why not try one of the old HardKernel images with 3.10.x ?
Because I don’t know what the hell I’m doing with Debian-based systems and don’t want to have to redo everything from scratch if I can’t get the remote device to reboot afterwards
m