HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ESPARGOS
pyespargos
Python2025–2025
ESPARGOS / pyespargos

pyespargos

The python library for the ESPARGOS digital phased array

2Distinct people
2Mentions
0Explicit recommenders
1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The python library for the ESPARGOS digital phased array

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, 3:56:07 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 3-hour interval2 dated mentions

Observed mentions: 2025-02-16 20:09:16 UTC to 2025-02-18 06:40:55 UTC.

012025-02-16 18:00:00 UTC to 2025-02-16 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 16, 18:002025-02-16 21:00:00 UTC to 2025-02-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-17 00:00:00 UTC to 2025-02-17 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-17 03:00:00 UTC to 2025-02-17 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-17 06:00:00 UTC to 2025-02-17 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-17 09:00:00 UTC to 2025-02-17 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-17 12:00:00 UTC to 2025-02-17 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 17, 12:002025-02-17 15:00:00 UTC to 2025-02-17 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-17 18:00:00 UTC to 2025-02-17 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-17 21:00:00 UTC to 2025-02-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-18 00:00:00 UTC to 2025-02-18 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-18 03:00:00 UTC to 2025-02-18 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-18 06:00:00 UTC to 2025-02-18 09:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 18, 06:00

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.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 16, 18:002025-02-16 18:00:00 UTC2025-02-16 21:00:00 UTC101
Feb 16, 21:002025-02-16 21:00:00 UTC2025-02-17 00:00:00 UTC000
Feb 17, 00:002025-02-17 00:00:00 UTC2025-02-17 03:00:00 UTC000
Feb 17, 03:002025-02-17 03:00:00 UTC2025-02-17 06:00:00 UTC000
Feb 17, 06:002025-02-17 06:00:00 UTC2025-02-17 09:00:00 UTC000
Feb 17, 09:002025-02-17 09:00:00 UTC2025-02-17 12:00:00 UTC000
Feb 17, 12:002025-02-17 12:00:00 UTC2025-02-17 15:00:00 UTC000
Feb 17, 15:002025-02-17 15:00:00 UTC2025-02-17 18:00:00 UTC000
Feb 17, 18:002025-02-17 18:00:00 UTC2025-02-17 21:00:00 UTC000
Feb 17, 21:002025-02-17 21:00:00 UTC2025-02-18 00:00:00 UTC000
Feb 18, 00:002025-02-18 00:00:00 UTC2025-02-18 03:00:00 UTC000
Feb 18, 03:002025-02-18 03:00:00 UTC2025-02-18 06:00:00 UTC000
Feb 18, 06:002025-02-18 06:00:00 UTC2025-02-18 09:00:00 UTC101

What Hacker News says

2 sources
Every WiFi chip needs to be able to synchronize to the received signal down to a few I/Q samples (the remaining synchronization error is accounted for by the cyclic prefix of OFDM). For example, with 40MHz of bandwidth, there is an I/Q sample every 25 nanoseconds (the wave travels 7.5m during that time), so the level of synchronization will be on that order. The ESP32 reports the time of arrival, the code for extracting a nanosecond-precision timestamp is here: https://github.com/ESPARGOS/pyespargos/blob/main/espargos/po... Additionally, you can use the phase information in the estimated channel coefficients (CSI) to determine the more precise time of arrival. Very briefly, a time delay in time domain will be visible as a frequency(=subcarrier)-dependent phase shift in frequency(=subcarrier)-domain. Now synchronization is only limited by
Read the rest
impairments like thermal noise and phase noise. In practice in nice lab conditions, the time of arrival accuracy is on the level of <<1m. On top of phase differences between subcarriers (--> timing information), we also measure phase differences between antennas, which provides angle of arrival and, with multiple arrays, phase of arrival information. You can go even further by measuring phase differences between subsequent packets, which provides frequency offset and Doppler (--> velocity) information. I have some nice results on that, but that's a topic for the future ;)
In Espargos: ESP32-based WiFi sensing array

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.