HackRF One error

asu.plt.lab.az · November 21, 2025, 10:32pm

I am trying to set up a ground station using Satnogs and the HackRF One SDR. This is my first experience with ground stations, and as a novice it has been a bit of a learning curve. I am to the point where we are scheduling our first test observations and have cleared other errors (like getting the HackRF visible in Docker), but we are stuck on this last issue (below) to get our first waterfalls. Here is the readout for the last pass. All the passes now have this same error. The failure is connecting to 127.0.0.1.

rig_init: rig does not have rx_range!!
network_open: hoststr=127.0.0.1, portstr=4532
connect to 127.0.0.1:4532 failed, (trying next interface): Network error 111: Connection refused
network_open: failed to connect to 127.0.0.1:4532

rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c ( REPEAT MULTIPAL TIMES)

[INFO] Opening HackRF One #0 a06063c8256c525f…
[ERROR] ./lib/tcp_rigctl_msg_source_impl.cc:147: Could not connect at rigctl server 127.0.0.1

rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c ( REPEAT MULTIPAL TIMES)
ERROR satnogsclient.observer.observer Waterfall data array is invalid

Any guidance is greatly appreciated.

We have a stationary dish pointed straight up and try to capture data from passes as they go overhead.

PE0SAT · November 22, 2025, 5:37am

Welcome and please follow Troubleshooting - SatNOGS Wiki and share log information otherwise it will be impossible to point you in the right way,

Jan | PE0SAT

asu.plt.lab.az · November 24, 2025, 6:44pm

Here is the Info -

------------[ copy here ]------------
{
“versions”: {
“satnogs-client”: “unknown”,
“satnogs-ansible”: “unknown”,
“satnogs-flowgraphs”: “unknown”,
“gr-satnogs”: “unknown”,
“gr-soapy”: “unknown”,
“gnuradio”: “unknown”,
“satnogs-config”: “1.1”
},
“state”: {
“is-applied”: false,
“pending-tags”: null
},
“system”: {
“date”: “2025-11-24T17:49:45.545657+00:00”,
“platform”: {
“system”: “Linux”,
“node”: “satnogs-config”,
“release”: “6.12.47+rpt-rpi-v8”,
“version”: “#1 SMP PREEMPT Debian 1:6.12.47-1+rpt1~bookworm (2025-09-16)”,
“machine”: “aarch64”,
“processor”: “”
},
“memory”: {
“total”: 8200753152,
“available”: 4113620992,
“percent”: 49.8,
“used”: 3596025856,
“free”: 1490612224,
“active”: 4248104960,
“inactive”: 1745571840,
“buffers”: 315412480,
“cached”: 2798702592,
“shared”: 311058432,
“slab”: 371277824
},
“disk”: {
“total”: 30603280384,
“used”: 12614238208,
“free”: 16413573120,
“percent”: 43.5
}
},
“configuration”: {
“satnogs_antenna”: “TX/RX”,
“satnogs_api_token”: “[redacted]”,
“satnogs_rf_gain”: “30”,
“satnogs_rig_ip”: “rigctld-host”,
“satnogs_rx_samp_rate”: “3e6”,
“satnogs_soapy_rx_device”: “driver=hackrf”,
“satnogs_station_elev”: “356”,
“satnogs_station_id”: “4440”,
“satnogs_station_lat”: “33.417472”,
“satnogs_station_lon”: “-111.933111”
}
}
------------[ copy end ]-------------

and the last 3 observation attempt 2 on Friday and 1 on Monday. Window was open over weekend which I believe is why there were communication errors in between the Friday and Monday attempts (normal?)
rig_init: rig does not have rx_range!!
network_open: hoststr=127.0.0.1, portstr=4532
connect to 127.0.0.1:4532 failed, (trying next interface): Network error 111: Connection refused
network_open: failed to connect to 127.0.0.1:4532
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
[INFO] Opening HackRF One #0 a06063c8256c525f…
[ERROR] ./lib/tcp_rigctl_msg_source_impl.cc:147: Could not connect at rigctl server 127.0.0.1
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80001020, vfo=0x7f967fa38c
ERROR satnogsclient.observer.observer Waterfall data array is invalid
ERROR satnogsclient.scheduler.tasks HTTPSConnectionPool(host=‘network.satnogs.org’, port=443): Max retries exceeded with url: /api/jobs/?ground_station=4440&lat=33.417472&lon=-111.933111&alt=356 (Caused by NewConnectionError(‘<urllib3.connection.HTTPSConnection object at 0x7f9cd87af0>: Failed to establish a new connection: [Errno 101] Network is unreachable’))
ERROR satnogsclient.scheduler.tasks Fetching jobs from network failed.
ERROR satnogsclient.scheduler.tasks HTTPSConnectionPool(host=‘network.satnogs.org’, port=443): Read timed out. (read timeout=45)
ERROR satnogsclient.scheduler.tasks Fetching jobs from network failed.
ERROR satnogsclient.scheduler.tasks HTTPSConnectionPool(host=‘network.satnogs.org’, port=443): Read timed out. (read timeout=45)
ERROR satnogsclient.scheduler.tasks Fetching jobs from network failed.
ERROR satnogsclient.scheduler.tasks HTTPSConnectionPool(host=‘network.satnogs.org’, port=443): Read timed out. (read timeout=45)
ERROR satnogsclient.scheduler.tasks Fetching jobs from network failed.
ERROR satnogsclient.scheduler.tasks HTTPSConnectionPool(host=‘network.satnogs.org’, port=443): Read timed out. (read timeout=45)
ERROR satnogsclient.scheduler.tasks Fetching jobs from network failed.
ERROR satnogsclient.scheduler.tasks HTTPSConnectionPool(host=‘network.satnogs.org’, port=443): Read timed out. (read timeout=45)
ERROR satnogsclient.scheduler.tasks Fetching jobs from network failed.
ERROR satnogsclient.scheduler.tasks HTTPSConnectionPool(host=‘network.satnogs.org’, port=443): Read timed out. (read timeout=45)
ERROR satnogsclient.scheduler.tasks Fetching jobs from network failed.
ERROR satnogsclient.scheduler.tasks HTTPSConnectionPool(host=‘network.satnogs.org’, port=443): Read timed out. (read timeout=45)
ERROR satnogsclient.scheduler.tasks Fetching jobs from network failed.
ERROR satnogsclient.scheduler.tasks HTTPSConnectionPool(host=‘network.satnogs.org’, port=443): Max retries exceeded with url: /api/jobs/?ground_station=4440&lat=33.417472&lon=-111.933111&alt=356 (Caused by NewConnectionError(‘<urllib3.connection.HTTPSConnection object at 0x7fa76cdb20>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution’))
ERROR satnogsclient.scheduler.tasks Fetching jobs from network failed.
rig_init: rig does not have rx_range!!
network_open: hoststr=127.0.0.1, portstr=4532
connect to 127.0.0.1:4532 failed, (trying next interface): Network error 111: Connection refused
network_open: failed to connect to 127.0.0.1:4532
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
[INFO] Opening HackRF One #0 a06063c8256c525f…
[ERROR] ./lib/tcp_rigctl_msg_source_impl.cc:147: Could not connect at rigctl server 127.0.0.1
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
rig_get_vfo: no rig and/or vfo? rig=0x7f80000ff0, vfo=0x7f967fa38c
ERROR satnogsclient.observer.observer Waterfall data array is invalid

asu.plt.lab.az · November 24, 2025, 7:01pm

PE0SAT · November 24, 2025, 7:39pm

Well looking at the log file the client is unable to connect to the doppler correction service.

There one should use the rigctl service name and if I am correct that should be satnogs_rigctld and not rigctld-host

docker container list should give the name if in doubt.

Jan | PE0SAT

asu.plt.lab.az · November 25, 2025, 12:49am

Thanks!! I have changed. I tried to double-check using “docker container list” but was getting a permissions error - will try again later.

Could you also check these below, please, and see if anything else sticks out. (Someone “borrowed” my antenna, so I have to wait till tomorrow to schedule new passes anyway)

PE0SAT · November 25, 2025, 7:55am

Regarding the permission denied you can add sudo to the command this should allow you to run it.

Other default settings should be fine.

asu.plt.lab.az · November 26, 2025, 2:01am

Thanks you. I will try to run new observation tonight using satnogs_rigctld instead of rigctld-host. I have changed it. I also ran the “sudo docker container list” and got this. Not sure if that is good or not.

asu.plt.lab.az · November 26, 2025, 2:35am

First two observations ran and failed. Here is what the logs looked like - Both look same. Suggestions?

PE0SAT · November 26, 2025, 5:54am

The container names look oke I only doubt if the versions are correct, hamlib 4.5.4 and satnogs 1.9.3 at the same time shouldn’t be an available setup. I get the impression a lot of manual changes are tried that are now causing other new challenges.

Can you run curl -sfL https://satno.gs/install | sh -s -- this should check and update the SatNOGS-client version.

Jan | PE0SAT

asu.plt.lab.az · November 26, 2025, 4:10pm

Yes—I would agree with your assessment. I think I am the second or third person trying to get an S-band to work here using this HackRF One SDR. I am a student like all the others here, but… a 64-year-old student who just took an early retirement and decided to come back to school to finish my BA and possibly work in the space industry.

The HackRF One module could also be suspect, as it was lost in the lab for at least a year before I stumbled upon it. No box or instructions—but it looks newish. I have not looked into what updates it might need. I was first focused on just learning SatNOGS and basic items, being a novice to this environment.

Thank you for your patience and assistance. I will try the above curl command.

asu.plt.lab.az · November 26, 2025, 7:16pm

Everything seemed to run as expected with the curl command - it updated and the client popped up, so I exited, and it saved/updated with the exit command. (I assume)

I scheduled 4 passes and it looks like the same error as before, which seems to center on failing to connect. However…….I see a possible discrepancy. It says 127.0.0.1:4532

This one below has some more verbiage, but 2 after this one are the same as the one above.

However on this page in the client, it says a different port - I know it says GPSd and false but is there any other page or place this comes into play? Could all the manual tinkering have broken something else somewhere else, related to the port?

asu.plt.lab.az · December 17, 2025, 7:29pm

Well, I gave up for the last month on setting up an S-band receiver dish with a HackRF One on SatNOGS for my university school project. I couldn’t get any support or help, and being a complete novice did not help, I’m sure. I even made a few inquiries about hiring a tutor, to no avail (so if anyone knows is or knows one, please email me).

However, there was an existing Pi here with an RTL-SDR, so I used that unit, got it working, and pieced it together with another antenna and some additional equipment. I was able to put a decent ground station together and at least learn some of the processes—such as scheduling passes, getting good waterfall data, messing around with different filters and LNA’s ect….and several other things that people often take for granted because they’ve been doing this for years.

For me, it was one big learning curve, especially coming from a non-engineering background.

Anyway, I am going to start again from square one—this time downloading the SatNOGS image myself. Someone else helped me originally and set up the initial image, but using the PRETTY_NAME command I just discovered that it was not the SatNOGS image I was told it was. I am now fairly certain that this was the root cause of many of the issues.

asu.plt.lab.az · January 30, 2026, 12:04am

PEOSAT said it was correct. There were so many attempts to fix what may have initially been minor issues that the system became so jacked up it was far easier to scrap that particular SD card and start from scratch with a new image that I could verify was the actual SatNOGS Pi image.

The first two observation attempts resulted in “failed” observations, but I recognized some simple errors in the Metadata, fixed those, and on the third attempt, it finally came up and we go our first waterfalls . We then got brave and decided to install GQRX on the Pi, which immediately crashed it again and caused nothing to work. Some thing about GQRX overwriting Satnog files.

So we reloaded a third, brand-new SD card with the correct image AGAIN… it was producing waterfall right away. We’re not touching anything right now other than running SatNOGS, (No Desk top enviroment etc….) and we haven’t had a single failure. Most passed have not been successful, but there have been no failures, and we’re starting to get a few that have good waterfalls and couple with data files that’s at least worth looking at.

So that’s my rookie suggestion: when in doubt, and when the system gets wrapped around the axle, throw away the axle. Start fresh with a new image.

PE0SAT · January 30, 2026, 1:03pm

Thanks for the update and good to see you are finally able to get some observations.

What SatNOGS ID are you using, so I can have a look at the obs and meta data?

Jan | PE0SAT

asu.plt.lab.az · January 30, 2026, 5:42pm

Thanks. Still getting the hang of it, but making progress.

That station is: **4561 - S-band 2026B

Owner : ii-laboratory
**
We are the Interplanetary Initiative Lab on the Arizona State University (ASU) campus in Tempe Arizona, USA

PE0SAT · January 30, 2026, 8:29pm

Have a look at this observation and compare with your configuration. (This station has a LNA in combination with the HackRF)

gain-mode: "Settings Field" in combination with other-settings: "AMP=14,LNA=40,VGA=26" opens the option to be more granular in your gain settings.

lo-offset: "200000" can be used to move the HackRF DC spike out of the reception area.

Jan | PE0SAT