ModuleInterface

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 devices (a bus on a single wire plus ground), linking these clusters together and with the master with routers using the DualUDP strategy over my LAN. PJON is great for cases like this. It could easily cross the Internet as well but in that case I would recommend using site-to-site VPN commections for security as the PJON traffic is not encrypted (encryption is a little too heavy when running on limited devices like Arduino). I have shared my PJON-based automation library here for those interested: https://github.com/fredilarsen/ModuleInterface

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, without wasting money and space on communication shields. I use PJON as a basis for a library I created for my home automation, and it works flawlessly (https://github.com/fredilarsen/ModuleInterface).

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 between modules and to and from a web server / database. It does data logging and storage to a database for trending and/or analysis, as well as configuration in a web page. It uses PJON as transport, so it can run on one or multiple of the supported media, for example a SoftwareBitBang bus between worker devices, with a router that connects them via UDP to a master process on Linux. Or any other combination.

Ciao Shakna! I would say that calling PJON a serialization protocol is a little limitative. Thanks to Hackaday and Atmel blog publications, soon an year ago, the repository started having thousands of visits per month, it has been implemented in Python and C by other developers around the world, but is still not finished, or better it doesn't include all the features will have when finished. The first versions (in 2010) were almost totally unusable in the real world because a lot of bugs and inconsistencies, but it is almost 8 years I am linting, correcting and enhancing, before personally and in the last two years with the internet and github community. The protocol overhead depends on header configuration from 3 up to 19 bytes. If you want to see something real applied on top, take a look to this project: https://github.com/fredilarsen