2008/12/12, Eur van Andel <[email protected]>: > >> There are a lot. Wbus is one of them, used to communicate the wisp >> programmer. > Mine is close to the wisp programmer: the PC program is an extension of > wisp.py I don't like the break char used by wbus. Avoid this if you can.
>check >check >check >check We seem to agree on this topic ;) > On top of this you could: > - add a data lenght field in the frame. > frame is fixed length of four bytes You should have made it 5: one byte length field. In the early nineties I was involved in a protocol for parking systems. It had a frame-type field and each frame type had a corresponding length. This was a big mistake and the guy who supports the current systems still carries the burden. All systems must know all frame types until the last component is upgraded to the new protocol... > On top of this: my protocol works with a bootloader too. Neat! Joep --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
