filar

6 ms·

1. 1.▲
   by filar 6y ago

   I have been here a lot longer than that, and I do recognize some of these comments coming from long-time PJON users parttaking in the PJON gitter channel, asking for advice from other users, asking for new features, etc. What is wrong with
2. 2.▲
   by filar 6y ago

   I have used PJON, with the SWBB and DUDP strategies, for my home automation setup for at least 4 years. I do not need the kilometer range of SWBB, but have stretches of tens of meters running alongside 220V AC wires with no problems, in bot
3. 3.▲
   by filar 7y ago

   Small correction: Using CRC is not optional. Setting the crc flag makes it use CRC32 even for very small packets. The default is to use CRC8 for packets of a few bytes and then upgrade to CRC32 over a small size threshold. This is to minimi
4. 4.▲
   by filar 7y ago

   PJON is based on a concept of selectable "strategies" to support using the protocol with different physical media. Some of these, like the one named SoftwareBitBang which allows a bus on a wire connected directly to an I/O pi
5. 5.▲
   by filar 7y ago

   Although not using PJON addresses as IP addresses, PJON has a few strategies that allow a PJON bus to span a Ethernet+WiFi LAN and/or WAN. I use this in my PJON-based home automation system using clusters of SoftwareBitBang based devi
6. 6.▲
   by filar 7y ago

   Every user of Arduino and similar devices who do not know PJON should take a look. Especially the SoftwareBitBang strategy is genious, allowing lots of devices to communicate over a single wire (plus ground) over long distances on a bus, wi
7. 7.▲
   by filar 8y ago

   Also check out the related ModuleInterface library ( https://github.com/fredilarsen/ModuleInterface ) that lets devices declare their contracts for settings, outputs and inputs and a master that synchronizes these betwee