| ??? 08/10/11 08:27 Read: times |
#183282 - Error detecting codes over RS232 |
I've knocked out a command set for a project that contains just 37 commands (at the moment). I've each command as a single byte, and I've chosen from only the ASCII printable bytes. This means that all commands are atomic, and I can exercise my target from a terminal program without having to write a test app that understands the protocol. My client has now asked whether I can add error detection to the protocol to reject comms glitches. I will change the RS232 frames from no parity to even parity to give the most basic checking, but I was wondering if I can do better.
Can someone tell me if I can increase the error detection capability by chosing different command bytes, but still retain the ability to type them into a termianl program? |
| Topic | Author | Date |
| Error detecting codes over RS232 | 01/01/70 00:00 | |
| RE: increase the error detection capability | 01/01/70 00:00 | |
| How complex? | 01/01/70 00:00 | |
| Hamming distance | 01/01/70 00:00 | |
| Hamming distance really not a good choice | 01/01/70 00:00 | |
| KISS | 01/01/70 00:00 | |
| Transfer size? | 01/01/70 00:00 | |
| Transfer Size --- | 01/01/70 00:00 | |
| Parameter free | 01/01/70 00:00 | |
Transfer Size --- | 01/01/70 00:00 | |
| double command and CR | 01/01/70 00:00 | |
| a bit more involved and better | 01/01/70 00:00 | |
| Double Characters... | 01/01/70 00:00 |