Last week I ran into this interesting CRC Reverse Engineering challenge at Stackoverflow . I immediately felt this is something I should be able to figure out using our Docklight Scripting tool , and indeed I managed to find the correct CRC within two hours. (Update 2016 - the Docklight CRC Finder also found the answer for this second CRC puzzle .) Now here are my personal sentiments about CRC: The fact that the most frequently cited reference is called A Painless Guide to CRC Error Detection Algorithms only proves - it's painful. It really is. So if you are with CRC aches, too, here is my personal list of painkillers on the subject: Sven Reifegerte's great Online CRC Calculator and his related C sample implementations . A somewhat comforting article about CRC Implementation Code in C . This article was originally called "Easier said than done (Michael Barr) - A guide to CRC calculation", and I much respect the honesty. The Boost CRC ...
How to make a PC talk industrial serial or fieldbus protocols via RS232/RS485/TCP/MODBUS/CAN/CANopen and the likes. Every now and then you come across this tiny annoying piece of functionality, where Google or Microsoft don't really help out and make you think: "How come no one ever published a small piece of code or some cookbook advice?" So I am happy to share some insight and code.