jks-prv

Beagle_SDR_GPS

C++2019–2023

jks-prv / Beagle_SDR_GPS · Archived

Beagle_SDR_GPS

KiwiSDR: BeagleBone web-accessible shortwave receiver and software-defined GPS (archived)

Explore on GitHub Read Hacker News discussions

5Distinct people

5Mentions

0Explicit recommenders

523GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

KiwiSDR: BeagleBone web-accessible shortwave receiver and software-defined GPS (archived)

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year5 dated mentions

Observed mentions: 2019-03-30 15:32:58 UTC to 2023-08-17 21:00:08 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	2	2
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	0	0
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	2	2
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	0	0
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	1	1

What Hacker News says

5 sources

gregsadetsky·Aug 17, 2023

Amazing, exactly what I was looking for! I've had luck on http://carinthia.proxy.kiwisdr.com:8073/ (the link you posted seems busy right now) I was able to use the FSK decoder, it worked really well. For those curious, the C-based decoder extensions are here [0] [0] https://github.com/jks-prv/Beagle_SDR_GPS/tree/master/extens...

In Casio G-Shock time sync radio

belter·Aug 3, 2021

https://github.com/jks-prv/Beagle_SDR_GPS/commit/0edf5fcfb99...

In Post seems to imply KiwiSDR author has remote access to all KiwiSDRs

gregmac·Jul 15, 2021

I wanted to see what the history of this was, and found many more. The code in question was removed yesterday [1] with the commit message "v1.461: bug fixes". The password sha256 hash was df05611250593c4299da8b3216751552b5a690e44b7e1b63f419e64b5e14ed9c. There's been at least 5 different values, though some are short-lived: * First added Jul 6, 2017 [2] commit message "for cases when src ip address is not preserved" and hash cc9b1457655eecfcb5f1beb6986bb9d27adfca2377ed32a4120014852fa415e6 * Changed later that day [3] with commit message "proper way to cleanup" to hash 7cdd62b9f85bb7a8f9d85595c4e488d8090c435cf71f8dd41ff7177ea6735189 * Nov 6, 2017 [4] commit message "first cut at GPS_ONLY_BUILD support" added a second hash: 974706effe52b397714f8ee22bf137e7cbfb46f3e88c7972defa3bbc55883048 * ..which was then removed on Nov 7, 2017 [5] with com

Read the rest

mit message "remove admin console bypass hack" * Changed Oct 24, 2018 [6] with commit message "v1.243: security improvements" to hash 34ac320e522bdd9c8e5f8b9e5aa264e732473b0621a8b899ddf2c708d80b442c * Changed Feb 13, 2020 [7] with commit message "lint" to hash df05611250593c4299da8b3216751552b5a690e44b7e1b63f419e64b5e14ed9c [1]: https://github.com/jks-prv/Beagle_SDR_GPS/commit/fef90929ed8... [2] https://github.com/jks-prv/Beagle_SDR_GPS/commit/6bdde32e603... [3] https://github.com/jks-prv/Beagle_SDR_GPS/commit/c0178bd2206... [4] https://github.com/jks-prv/Beagle_SDR_GPS/commit/d6ea8061c8f... [5] https://github.com/jks-prv/Beagle_SDR_GPS/commit/e66e67a20bc... [6] https://github.com/jks-prv/Beagle_SDR_GPS/commit/30024d542f3... [7] https://github.com/jks-prv/Beagle_SDR_GPS/commit/20b3859bbbc...

In A backdoor giving root access has lurked for years in popular KiwiSDR

VLM·May 1, 2019

Speaking of state of the art CPUs, I own a couple years old "KiwiSDR" web-ui receiver which devotes some CPU cycles to implementing a GPS rx and it uses the GPS lock to discipline the internal oscillators such that the radio is driftless and perfect frequency accuracy. It works pretty well. My receiver is somewhat more frequency stable than some local AM broadcasters, which is weird to see in the waterfall display; many local broadcasters do GPS discipline, of course. Pretty sure the code is at https://github.com/jks-prv/Beagle_SDR_GPS Note that the hardware Skyworks SE4150L chip is an RF front-end, all the math is done in software, the chip merely attaches to the GPS antenna and squirts out a very raw digital bit-stream of data, its hardly a full GPS squirting out NMEA RS232 serial data. I am aware of SDR hardware that does the RF wor

Read the rest

k in software, which is a slight step beyond the KiwiSDR. Technology is not distributed smoothly and software defined GPS is cheap enough that everyone except cheap consumer gear can implement it. Someday, presumably, computing power will be cheap enough that your microwave oven and clothes washer will not bother with expensive hardware to have a semi-accurate timer, they'll just use cheap SDR code in a FPGA to listen to GPS to time your microwave popcorn and clothes spin cycle. That's the fundamental problem with regulations like this, they don't slow down "state actors" they just stand in the way of (taxable, profitable) commercial exploitation. Post 2000, post 2010 at worst, no serious missile program will ever lack an unlimited GPS, but post regulation, the technology will be crippled from entering consumer goods. Now what is interesting to speculate is it would be destabilizing if we know that they know how to crack the military P(Y) code or the newer M code for higher resolution positioning. I'm not sure that would help with missiles but if our secret squirrels are freaking out about the generic topic of software GPS, that would imply some state level actor (or lower?) has a crack or exploit for the math behind P(Y) code or M code streams, which has interesting implications for other crypto systems.

In Review of Controls for Certain Emerging Technologies (2018)

elfchief·Mar 30, 2019

If you want this straight from the spec, grab a copy of IS-GPS-200J (it's free, just google it), look at section 3.3.1.1, which talks about the carrier frequencies of the various signals. From that: "The carrier frequencies for the L1 and L2 signals shall be coherently derived from a common frequency source within the SV. The nominal frequency of this source -- as it appears to an observer on the ground -- is 10.23 MHz. The SV carrier frequency and clock rates -- as they would appear to an observer located in the SV -- are offset to compensate for relativistic effects. The clock rates are offset by (delta f)/f = -4.4647E-10, equivalent to a change in the P-code chipping rate of 10.23 MHz offset by (delta)f = -4.5674E-3 Hz. This is equal to 10.2299999954326 MHz. The nominal carrier frequencies (f0) shall be 1575.42 MHz, and 1227.6 MHz for

Read the rest

L1 and L2, respectively." In this context, "SV" is "Space Vehicle", a.k.a. a GPS satellite. You also have to make a relativistic adjustment in the user segment (aka "your GPS"). You can see an example of doing this correction in open-source software GPS receivers, for example https://github.com/jks-prv/Beagle_SDR_GPS/blob/de895035e93ba... . This adjustment is documented in the above spec, in section 20.3.3.3.3.1 (which you'll see is almost verbatim copied into the the code linked above)

In GPS Flaw: Security Expert Says He Won't Fly April 6