2 ms·
Why would someone write a protocol in 2019? Don't we already have formats? (EDIT: Like CAN or I2C?)
by robertAngst 8y ago
Why would someone write a protocol in 2019?
Don't we already have formats? (EDIT: Like CAN or I2C?)
- bsder 8y agoDon't know why you got downvoted, it's a good question. A "protocol" sits on top of things like I2C, SPI, and CAN. Protcols answer things like: "How do I send more bytes than the underlying transport can take in a single transaction?" "How do I exchange data when hardware has different characteristics." "How do I minimize the power or time needed to exchange data?" Different protocols have different strengths and weaknesses. Remember: part of my complaint about this "protocol" is its "verbosity". If you are on a battery or are bandwidth constrained (Narrowband-IoT, LoRA, ANT, etc.), you want a protocol that exchanges short messages. Time is certainly something that you don't want to require lengthy messages when you are trying to set up. Too many people think "embedded" means "runs a Linux installation larger than the average computer in 1996".