GIgioscarab·Dec 16, 2019
More info here: https://github.com/gioblu/PJON/tree/master/src/strategies/An...
In How to use off-the-shelf LEDs as wireless or optic-fibre transceiversgioblu
PJON
C++2015–2022
gioblu / PJON
PJON
PJON (Padded Jittering Operative Network) is an experimental, arduino-compatible, multi-master, multi-media network protocol.
Systems & InfrastructureCreative & MediaHardware & EmbeddedRobotics & IoTNetworkingAutomation & Workflows
13Distinct people
105Mentions
0Explicit recommenders
2.8KGitHub stars
What to know before exploring
What it is
PJON (Padded Jittering Operative Network) is an experimental, arduino-compatible, multi-master, multi-media network protocol.
GitHub
Where it is used
No documented product use was verified in the last source check.
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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 4:00:59 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 year105 dated mentions
Observed mentions: 2015-08-07 02:16:44 UTC to 2022-12-20 15:15:32 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
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 6 | 4 | 2 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 12 | 11 | 1 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 14 | 9 | 5 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 7 | 5 | 2 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 29 | 13 | 16 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 24 | 5 | 19 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 11 | 1 | 10 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 2 | 0 | 2 |
What Hacker News says
29 sourcesMore info here: https://github.com/gioblu/PJON/tree/master/src/strategies/So...
In PJDL (Padded Jittering Data Link) – Free and Open-Source Alternative to 1-WirePJDL (Padded Jittering Data Link) – Free and Open-Source Alternative to 1-Wire
2 points · Open discussionMore info here: https://github.com/gioblu/PJON/tree/master/src/strategies/An...
In Off-the-shelf LEDs optical wireless communication with PJONPJDL (Padded Jittering Data Link) – Open alternative to 1-Wire
8 points · Open discussionThat needs connectivity via PJON: https://github.com/gioblu/PJON :)
In Off-Grid Cyberdeck: Raspberry Pi Recovery KitI'm applying the local-first methodology in PJON, a new networking open standard :
https://github.com/gioblu/PJON
In Local-first software: you own your data, in spite of the cloudWith PJON you can apply laser communication using AnalogSampling, see: https://github.com/gioblu/PJON/tree/master/src/strategies/An...
In Home-Made Optical P2P Data Link (2003)There's an optional 8-bit CRC and sequence number, with a single bit ACK.[1] This is even weaker than ARCnet, circa 1977, one of the earliest protocols for talking to low-end devices.
This is for talking to things like lightbulbs with some US$0.50 CPU inside. It's for really low end devices. It's best for idempotent operations that can be requested repeatedly without harm and are timeout-tolerant.
[1] https://github.com/gioblu/PJON/blob/master/specification/PJO...
In PJON 12.0 – Networking freedom for hackers, makers and experimentersAlthough stm32 is not the widest support, some strategies work with it, see the compatibility table here: https://github.com/gioblu/PJON/wiki
In PJON 12.0 – Networking freedom for hackers, makers and experimentersCiao gongoiler, the 32 bits address identify a group of devices that share the same bus id, so yes, many groups of devices (that may have the same 8 bits device id) can coexist without addressing collisions.
here: https://www.pjon.org/get-bus-id.php
we distribute bus ids for free, for everyone who could need it.
I have never thought about the bridging strategy you propose, yes effectively it may not be hugely complicated :) if you would like to share your idea with other users feel free to open an issue here: https://github.com/gioblu/PJON/issues
In PJON 12.0 – Networking freedom for hackers, makers and experimentersCiao gorgoiler, take a look to PJON's address space:
https://github.com/gioblu/PJON/blob/master/specification/PJO...
"The PJON protocol v3.1 in local mode supports connectivity for up to 254 devices, in shared mode supports connectivity for up to 4.294.967.295 buses (groups of devices) and up to 1.090.921.692.930 devices."
That means 32 bits for the bus id, and 8 bits for the device id.
Another interesting side-effect of the address-space scheme and the dynamic meta-data inclusion in the packet is the overhead:
"It supports interoperability between systems that use a different configuration and provides with high efficiency including only the protocol's features used and the overhead effectively required (5-22 bytes)"
In terms of minimum requirements PJON is uncomparable to IPv4 or IPV6 needing only in the most limited configuration: 1 IO
Read the rest
pin, 16MHz clock frequency, 4144 bytes of program memory and 46 bytes of RAM
PJON 12.0 – Networking freedom for hackers, makers and experimenters
186 points · Open discussionPJON, decentralized networking made simple
4 points · Open discussionShow HN: The PJON network protocol specification
1 points · Open discussionShowing the 15 most recent of 29 sources. Enable JavaScript to search and browse every indexed mention.