The old computer processing adage is “garbage in, garbage out.” What it means is that unless your data is good, don’t expect to see good results. So what can be done to ensure that the data is good? A checksum, that’s what.
\n
\nWhenever data is input, stored, or transmitted, good programming practice is to perform some type of check to confirm that the data desired is what’s input. You may perform such checks in your code already.<\/p>\n
For example, if a value is requested, the code confirms that the text input appears to be some form of value and not random characters.<\/p>\n
Back in the old days, computer code appeared in books or magazines. The user would type in the data one line at a time.<\/p>\n
Don’t laugh: I did this type of typing exercise frequently. A lot of early hobbyists did.<\/p>\n
To confirm that you typed in the correct values, a checksum was included. The checksum was often a two-digit value that appeared at the end of a line of text. When the program processed the input, it calculated a checksum. If the value calculated matched what you typed, the assumption was that the data was good. Otherwise the line was flagged for input a second time.<\/p>\n
The following code presents three sample strings, The checksum()<\/em> function at Line 3 chomps through the string one character at a time. Each character is converted to a value, with hex digits A through F translated to 10 through 15. The value of each digit is added to variable In Line 15, the logical AND operator lops off all the but final two digits of the cumulative sum, returning a truncated value. That value is the checkum.<\/p>\n Here’s the output:<\/p>\n The string appears, followed by the checksum.<\/p>\n Both The Internet uses a more sophisticated form of error-checking for its information packets. That value is sent as part of the packet transmitted. When the receiving computer examines the data, it performs a complex calculation as a checksum. If the values are off, the packet is requested as second time.<\/p>\n","protected":false},"excerpt":{"rendered":" Calculate a checksum to ensure the quality of data. Continue reading packet_a<\/code>, packet_b<\/code>, and packet_c<\/code>. Each string is displayed, followed by a simple checksum calculation, which the checksum()<\/em> function calculates.<\/p>\n\r\n#include <stdio.h>\r\n\r\nint checksum(char *line)\r\n{\r\n int c = 0;\r\n\r\n while(*line)\r\n {\r\n if( *line >= 'A' && *line <= 'F')\r\n c += *line - 'A';\r\n else\r\n c += *line - '0';\r\n line++;\r\n }\r\n return( c & 0xFF);\r\n}\r\n\r\nint main()\r\n{\r\n char *packet_a = \"F6A4C8D4EF44D4AA91165C8E\";\r\n char *packet_b = \"E6A4C8D4EF44D4AA91165C8E\";\r\n char *packet_c = \"6EA4C8D4EF44D4AA91165C8E\";\r\n\r\n printf(\"%-24s %s\\n\",\"Packet\",\"Checksum\");\r\n printf(\"%24s %X\\n\",packet_a,checksum(packet_a));\r\n printf(\"%24s %X\\n\",packet_b,checksum(packet_b));\r\n printf(\"%24s %X\\n\",packet_c,checksum(packet_c));\r\n\r\n return(0);\r\n}<\/pre>\nc<\/code>, creating a cumulative sum.<\/p>\nPacket Checksum\r\nF6A4C8D4EF44D4AA91165C8E 5C\r\nE6A4C8D4EF44D4AA91165C8E 5B\r\n6EA4C8D4EF44D4AA91165C8E 5B<\/code><\/pre>\npacket_c<\/code> and packet_b<\/code> share the same the checksum value. That shouldn’t pose a problem, but it points out a weakness of the simple checksum calculation. If you accidentally swap values in the string, the checksum result is the same.<\/p>\n