>> ... in real world use you are going to sync in some manner.

> This is rarely the problem you make it out to be.

Pardonez moi?
I think I thought I just asked a question with a series of example
solutions escalating in complexity.

However, for a lack of problem ...

> =A0Almost always, I send commands starting with a opcode byte and followe=
d by data bytes dependent on
> the opcode.

> Usually you test
> each command and response

> Very simple
> things you can do is to make 0 and 255 unused opcodes or specifically def=
ine
> them as NULL opcodes.

> Sometimes I have deliberately used this to sync on startup.

> Another trick that I have used occasionally is to add a timeout.

> In a few cases I did have to implement a packet protocol with checksums,
> ACK, etc,

you seem to have done an excellent job of suggesting various ways of
varying complexity of meeting the requirement.
So, thanks, that seems to have well addressed the problems I
apparently don't  have :-).

Others may also have different interesting and/or useful ad hoc ways
of achieving this.



         R

--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.