I seem to be having a problem with the formatting of 16-bit checksums from StreamDevice 2.8.25. When I use a string that ends with “%+<sum16>” in the protocol file, I get the correct checksum in ascii characters as expected, but I have
an extra leading 0 (5 characters instead of 4). A checksum that should be “0389” is written as “00389” A similar problem seems to be happening when reading (seems to be expecting an extra leading zero). I can work around this because I know what will
be sent and can ignore the checksum on reads,. Has anyone else had this problem? If this is working correctly for you, what version of StreamDevice are you using?
