Airspy instead of HackRF? about gr-iridium

[coddingtonbear]

I can't speak to whether this will work for an Airspy, but just glancing at this, it looks like maybe you're not running this from the root of where you've cloned this. The error it's raising is that it didn't find the section it's looking for in your config, which is what will happen if examples/hackrf.conf isn't actually the path to the configuration file.

[dsound-zz]

Deleted

[coddingtonbear]

@dsound -- this isn't my project, but I still really recommend posting each problem you're running into as a separate issue. The first problem you posted is easily solved by making sure you're typing in the path to hackrf.conf properly; you don't need to re-install. I'm not clear on what message you're trying to highlight in your second comment, but everything seems fine there.

[dsound-zz]

Sorry, I thought some of that was error but apparently not. So for the first issue, I need to run iridium-extractor -D 4 examples/hackrf.conf | grep "A:OK" > output.bits in the folder containing the .conf file?

[coddingtonbear]

You need to make sure that examples/hackrf.conf is the path to the configuration file, yes. If you are in the same folder as hackrf.conf you'd run iridium-extractor -D 4 hackrf.conf | grep "A:OK" > output.bits. If you're somewhere else, you'd run iridium-extractor -D 4 /whatever/the/path/to/the/configuration/file/is | grep "A:OK" > output.bits.

[dsound-zz]

Just got my HackRF and am trying in directory with the .conf file. Have the HackRF running through a filter and into an antenna built for Iridium sitting on a pizza pan 15 stories high by the window. Does this mean it's recording Iridium data?

gr-osmosdr 0.1.4 (0.1.4) gnuradio 3.7.9 built-in source types: file osmosdr fcd rtl rtl_tcp uhd miri hackrf bladerf rfspace airspy redpitaya Using HackRF One with firmware 2014.08.1 (RF) Gain: 14.0 (Requested 20) IF Gain: 40.0 (Requested 40) BB Gain: 20.0 (Requested 20) Bandwidth: 10000000.0 (Requested 10000000) OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO1462216233 | i: 0/s | i_avg: 0/s | q: 0 | q_max: 0 | o: 0/s | ok: 0% | ok: 0/s | ok_avg: 0% | ok: 0 | ok_avg: 0/s | d: 0 ODetector in burst squelch at 49.206612 1462216293 | i: 0/s | i_avg: 0/s | q: 0 | q_max: 12 | o: 0/s | ok: 22% | ok: 0/s | ok_avg: 22% | ok: 6 | ok_avg: 0/s | d: 0 1462216353 | i: 0/s | i_avg: 0/s | q: 0 | q_max: 1 | o: 0/s | ok: 0% | ok: 0/s | ok_avg: 20% | ok: 6 | ok_avg: 0/s | d: 0 1462216413 | i: 1/s | i_avg: 0/s | q: 0 | q_max: 64 | o: 1/s | ok: 0% | ok: 0/s | ok_avg: 5% | ok: 6 | ok_avg: 0/s | d: 0

[schneider42]

iridium-extractor actually emits ConfigParser.NoSectionError: No section: 'osmosdr-source' if the file can not be found, so @coddingtonbear is correct.

I just fixed this in 69d69cb.

Regarding the Airspy that @dsound wants to use:
The default hackrf.conf uses a 12 MSPS sample rate. The Airspy only suports 10 MSPS with 9 MHz bandwidth.

I've just pushed some more example configurations. One which I think should work for the Airspy (I don't have one), and one which uses the HackRF with a smaller sample rate (54f125c).

[schneider42]

@dsound: Yes it is receiving some iridium, very poorly though.

Among other things, it runs into a burst squelch. You should check with fosphor, sdrangelove or inspectrum if your spectrum is clean.

[dsound-zz]

Ok good to know. Maybe things will improve when I get the second filter and LNA4ALL to add in series. I live in a very dense RF area (Brooklyn, NY) so filtering will be a must.