No problem. Contained in the header of every message, there are flags which specify if there is error protection, and if an acknowledgment receipt is required. This works in either direction.GartnerProspect wrote:
One: I want data integrity for all writes to the hardware.
This is a bit tricky. Either the protocol needs to be watered down or it needs to operate in duel modes, with the ability to switch it mid-stream if necessary (if the user unplugs their digital gauge thingy, and plugs their laptop in for example). This is a bit harder with a serial interface, where there is no logon,logoff.Two: I want an easy way to get data out of the hardware for add-on modules.
I have broken my protocol proposal in two parts. The low-level layer takes care of the nuts-n-bolts of the communication, leaving the programmer with the decision what to send, rather than how. All it requires, is somone to port the protocol to each platform. I am happy to write some sample code in Java or C#.