Thanks for confirming.
I had grabbed the python sample code and it had a big comment about possible CR/LF's in the checksum, and then I read the spec 5 times and kept coming to the same (incorrect) conclusion as the comment.
Search found 3 matches
- Mon Jun 03, 2013 12:36 pm
- Forum: EnvisaLink ( IP100D, IP170D, 2DS, 3, 4)
- Topic: TPI Checksum and CR/LF
- Replies: 3
- Views: 4870
- Mon Jun 03, 2013 3:17 am
- Forum: EnvisaLink ( IP100D, IP170D, 2DS, 3, 4)
- Topic: TPI Checksum and CR/LF
- Replies: 3
- Views: 4870
Re: TPI Checksum and CR/LF
Ok.. Definitely time to go to bed. I think the hex code representing the checksum IS sent literally as ascii characters A-F0-9.
- Mon Jun 03, 2013 3:13 am
- Forum: EnvisaLink ( IP100D, IP170D, 2DS, 3, 4)
- Topic: TPI Checksum and CR/LF
- Replies: 3
- Views: 4870
TPI Checksum and CR/LF
I'm still trying to understand the spec, but it seems like the checksum could theoretically have a CR/LF encoded in it since CR and LF are in the lower nibble of the ascii range. This makes the protocol a little unpredictable, especially if the data lengths aren't fixed as well. No? (ok, the maybe ...