Daniel Estévez
destevez.net · Personal blog · on HN since 2016
Daniel Estévez is an amateur radio operator and engineer who decodes signals from spacecraft and satellites using GNU Radio and software-defined radio.
What HN saysCommenters recommend his work as fascinating and excellent, especially the Voyager 1 decoding series and his 802.11ah decoding post.
40HN people shared it
13linked it in comments
123stories submitted
2.4Kstory points
6 months agolast shared
2016people per year2026
Most-shared posts
- 1Decoding Voyager 18 people · 59 points · first shared 2021 · 4 comments on HN
- 2Decoding James Webb Space Telescope3 people · 290 points · first shared 2021 · 93 comments on HN
- 3Voyager 1 and Reed-Solomon3 people · 53 points · first shared 2021 · 1 comments on HN
- 4Decoding the Artemis I Orion vehicle3 people · 7 points · first shared 2022 · discussion on HN
- 5Investigating the Galileo Satellite Navigation System Outage with a LimeSDR2 people · 152 points · first shared 2019 · 41 comments on HN
- 6JWST Sequential Ranging2 people · 71 points · first shared 2021 · 2 comments on HN
- 7Scientific and Technical Amateur Radio2 people · 57 points · first shared 2022 · 6 comments on HN
- 8A Rust Implementation of Galileo Osnma2 people · 21 points · first shared 2022 · discussion on HN
- 9LTE Downlink: Synchronization Signals2 people · 18 points · first shared 2022 · discussion on HN
- 10Timing SDR Recordings with GPS2 people · 15 points · first shared 2022 · discussion on HN
- 11Voyager-1 single dish detection at Allen Telescope Array2 people · 2 points · first shared 2021 · discussion on HN
- 12Not-LoRa GRCon24 CTF Challenge2 people · 2 points · first shared 2024 · discussion on HN
- 13Gr-satellites – A collection of GNUradio decoders for satellite telemetry1 people · 170 points · first shared 2016 · 15 comments on HN
- 14Imaging Cygnus a at 8.45 GHz with ATA1 people · 166 points · first shared 2021 · 31 comments on HN
- 15A look at Chang’e 5 telemetry1 people · 154 points · first shared 2020 · 31 comments on HN
What HN people wrote when they linked it
X-Cubed · 2022-07-24
Daniel Estévez (https://destevez.net/) has lots of interesting blog posts on using tools like GNU Radio and Jupiter to decode transmissions from various objects in space. He's recently also been looking at LTE.
I would also recommend CuriousMarc who has done a lot of work with his friends on restoring some radio equipment from the Apollo missions: https://www.youtube.com/watch?v=v49ucdZcx9s&list=PL-_93BVApb58SXL-…
There are lots of good explanations of the how and why in those videos.
vmilner · 2026-03-30
The estimable (inestimable?) Daniel Estevez wrote excellent blogs on the Voyager comms protocols.
https://destevez.net/2021/09/decoding-voyager-1/
CamperBob2 · 2025-10-17
Not necessarily leading-edge stuff, but the work he did on Voyager 1 decoding with GNU Radio was fascinating (e.g. https://destevez.net/2021/09/decoding-voyager-1/ ). Same with 802.11ah ( https://destevez.net/2025/01/decoding-ieee-802-11ah/ ). The fact that he puts so much care and attention into describing the methodology as well as the results makes his blog a great educational resource for GNU Radio and communications DSP in general.
Estevez pretty much does for DSP what Karpathy does for ML, sans the latter's videos.
I also just noticed a post on the Remez algorithm for FIR filter design, where he ran into some of the same problems with 1970s-era legacy code that I have and (unlike me) actually addressed them. That one, I'm going to have to bookmark for sure.
kayodelycaon · 2024-03-14
Great question! Voyager 1 does appear to be using ASCII. :D
https://destevez.net/2021/09/decoding-voyager-1/
strangattractor · 2024-01-26
Another interesting possibility is to use GPS for a clock. [1] Apparently 1 microsecond accuracy. Maybe useful if you want to make the distance really far. Someone has an article [2] Would be cool if you could pool the resources of multiple amateur rigs over a great distance in ad hoc antenna arrays.
[1] https://digitaldisplay.com/network-clock/master-clock/gps-vs-ntp-maste…
[2]https://destevez.net/2022/03/timing-sdr-recordings-with-gps/
mendigou · 2021-09-15
There are normally at least two radio links: telemetry and telecommand. Some spacecraft have multiple of each, with at least one channel of each being some sort of emergency channel where you can only do the most basic ops or get the most basic data.
As the sibling comment mentions, command signals are normally at least signed, and many times also encrypted.
Telemetry is way less sensitive, so it is usually not encrypted in scientific missions. There are well known protocols for space communications (e.g. CCSDS, PUS), so once you figure out a few fields you can make educated guesses of what each byte is. A previous post of the linked blog discusses it in detail: https://destevez.net/2020/08/tianwen-1-telemetry-framing-and-data/
Even without the actual telemetry, there are many things you can guess about the satellite attitude from just observing the radio signal. Many satellite and radio amateurs love doing that!
ElectRabbit · 2024-12-20
Have a look at Daniel Estevez blog. He's a regular user of bigger telescopes (like ATA) and managed to receive and decode Voyager 1. He wrote a GNURadio decoder for it.
https://destevez.net/2021/09/decoding-voyager-1/
magicalhippo · 2024-06-03
One thing that seems missing to me is that while the probe might send 160 bits/sec of useful data, those bits are not sent directly as such[1]:
The TMU encodes the high rate data stream with a convolutional code having constraint length of 7 and a symbol rate equal to twice the bit rate (k=7, r=1/2).
So the effective symbol rate is 320 baud[2], and thus a factor of two should be included in the calculations from what I can gather.
Note that the error correction was changed after Jupiter to use Reed-Solomon[3] (255,223) to lower the effective bit error rate, so effectively I guess the data rate is more like 140 bps.
[1]: https://web.archive.org/web/20130215195832/http://descanso.jpl.nasa.go…
[2]: https://destevez.net/2021/09/decoding-voyager-1/
[3]: https://destevez.net/2021/12/voyager-1-and-reed-solomon/
guenthert · 2023-12-15
> even though there was no computer on Earth at the time fast enough to decode it
I'm not sure what is meant by that. Not fast enough to decode in real time? There is/was no need to do that. The transmissions would have gone to tape in any case.
Here is a link describing how to decode such a tape: https://destevez.net/2021/09/decoding-voyager-1/
onetwentythree · 2023-08-06
Not sure about a mission as old as voyager, but most modern missions use CCSDS protocols, which are open and available online.
But just because you know the protocol dues not mean you have enough information to send a valid command. The commands are wrapped in a common protocol, but the commands themselves are typically mission-specific and definitely not made public.
Here’s an example of someone unaffiliated with the mission decoding JWST telemetry. While they were able to identify the packets defined per CCSDS protocols, they do not know the actual content of the packets, which are mission specific.
https://destevez.net/2021/12/decoding-james-webb-space-telescope/
And as someone else mentioned, the biggest hurdle with getting a command to voyager is access to a 70 m dish. Not many of those floating around…
belter · 2022-08-31
argvargc · 2021-02-28
Yourself and others interested in detail, may appreciate Daniel Estévez's recent post on his use of GNU Radio and the Allen Telescope Array to detect Voyager 1 transmissions:
https://destevez.net/2021/02/voyager-1-single-dish-detection-at-allen-…
Also this JPL document on both Voyagers is packed. Check out the chart on page 44, regarding diminishing bitrates over the coming years:
https://descanso.jpl.nasa.gov/monograph/series13/DeepCommo_Chapter3--1…
drmpeg · 2020-03-28
Even satellites built in 1967 were digital.
https://destevez.net/2020/03/decoding-les-5/