Ciao anfractuosity, Modbus have more "dedicated" and shorter (255 bytes) data frame and in my opinion is a little more narrow in its applications, its overhead

Ciao anfractuosity, Modbus have more "dedicated" and shorter (255 bytes) data frame and in my opinion is a little more narrow in its applications, its overhead if I am not mistaken is also high (11 bytes). PJON works with no additional hardware at the voltage level you prefer, totally software emulated, is a network protocol stack of 2 layers (data-link and protocol layer) can send packets of 255 or 655353 bytes, can support up to 255 devices connected on the same wire, or up to 1.090.921.692.930 devices in a bus network of up to 4.294.967.295 buses, it supports CRC8 or CRC32 at users choice and have an overhead added to information varying from 3 up to 19 bytes (thanks to a header configuration driven packet format). PJON also supports 2 different types of acknowledgment (sync and async). Being the data link level handled "agnostically" PJON protocol layer is able to run over Serial, RS485, TCP and UDP (with the necessary hardware additions). PJDL (Padded Jittering Data Link) https://github.com/gioblu/PJON/blob/master/strategies/SoftwareBitBang/specification/PJDL-specification-v1.0.md https://github.com/gioblu/PJON/blob/master/strategies/Softwa..., that is the default data-link we propose for PJON procedure, it is generally tested with 50 meters cable, working fine. We actually still haven't find a range limit, and maximum devices limit.