Dean Roddey
Senior Member
I've been working on a document that provides guidance to companies looking to create controllable hardware on how to create good control protocols. This is not intended to be super-technical, but mostly for the guy at the company who may be a programmer already but hasn't really gotten into control protocols and now needs to, or for the technical manager to get an overview and so forth.
Anyway, if you are interested here is what I have so far. Comments are welcome to improve it:
Protocol Design Guide
There's a section at the end yet to be done where I dissect some real world protocols and discuss the good and bad. Feel free to forward the link to anyone you think might benefit, but send them the link, not the document, so that they will see updates to the original in the future.
Anyway, if you are interested here is what I have so far. Comments are welcome to improve it:
Protocol Design Guide
There's a section at the end yet to be done where I dissect some real world protocols and discuss the good and bad. Feel free to forward the link to anyone you think might benefit, but send them the link, not the document, so that they will see updates to the original in the future.
