Click here to Skip to main content
65,938 articles
CodeProject is changing. Read more.
Articles
(untagged)

CRC Encoding

0.00/5 (No votes)
6 Dec 2003 1  
An article on using CRCxxx checksum calculations in C#, combined with the serialstreamreader example found on this site.

Introduction

A lot of medical devices use the RS232 port to communicate and they all use a kind of CRC algorithm. Since a few months I tried to migrate to .NET and C#. However a lot of the old things just don't exist in C#. So you have to write or port them yourself.

This code can generate any CRCXX calculation, as long as XX is 8, 16, 32. The CCITT is just 16 but with a different polynomial. The project also uses the serialstream sample on this site. I used the demo project to communicate with an existing device.

Background

In this section I won't explain the CRC checksum calculation. A lot of the stuff can be found on the web. Especially on the site of Rocksoft, the original designers.

Just to introduce it:

Cycle Redundancy Check is added to a communication protocol to make sure no data is lost or has been changed. It is a far more advanced version of the parity check in the basic RS232 communication protocol. It uses a polynomial to create a unique checksum, so if somewhere a bit is changed, the total checksum is also changed.

Using the code

To use the code, just add the CRCTool.cs class to your C# project and add the namespace to your class:

        using Communication.IO.Tools

Add the CRCTool to the class in which you'll be using it.

class Class1
    {
        /// <SUMMARY>

        /// The main entry point for the application.

        /// </SUMMARY>

        /// 


        .......
        // Crc Computation Class

        private static CRCTool compCRC = new CRCTool();
}

Tell the class which kind of CRC you'll be using. Most functions are generic for all kinds of CRC encoding. The Init function is used to specify to start values for each kind of encoding: CRC16, CRC_ITT, CRC32. It also creates the encoding tables needed for the fastest encoding algorithm!

When you want to change the type of CRC, call Init again.

        // use of these values,

        // enum CRCCode{CRC_CCITT, CRC16, CRC32};

        // if the protocol you need is not here

        // you can add it to this enum and change the relevant parameters

        // in the Init function.       

        compCRC.Init(CRCTool.CRCCode.CRC_CCITT);

There are four ways to calculate the CRC checksum value and a fifth one to show you another way. The difference it the speed of calculation, with the crctablefast begin the fastest and the crcbitbybit the slowest.

However there are situations in which one could be preferred for the other. Keep, for example, in mind that the calculation of the lookup table also takes time. So for one time calculation this would be slower.

     //Four function with a little different algoritm but the same endresult.

     public ulong crcbitbybit(byte[] p); 
     public ulong crcbitbybitfast(byte[] p); 
     public ulong crctable(byte[] p); 
     public ulong crctablefast (byte[] p);
         
     // Not a generic but an example of how to do everything in one function 

     public ushort CalcCRCITT(byte[] p);
        

I have added it to the serialstream example and now the command writing code is changed to this. I use the CRCITT 16 bits encoding. The device I talk to needed a ! in front of the message and a |XXXX\r as end of the message with XXXX being the CRCITT value.

         // Write command to port

         byte[] rawBytes = System.Text.ASCIIEncoding.ASCII.GetBytes(command);
              
         compCRC.Init(CRCTool.CRCCode.CRC_CCITT);
         ushort usCrc16 = (ushort)compCRC.crctablefast(rawBytes);

         // The following is equal to 

         // sprintf( message,"!%s|%04X\r", buf, crc );

         string sMessageString = 
            String.Format("!{0}|{1:X4}\r",command,usCrc16);
         sw.WriteLine(sMessageString );
         sw.Flush();
        

I have tested it with CRC16, CRCITT, CRC32, and all algorithms worked fine.

Points of Interest

Nothing of interest yet. It depends on how you take the article! Please keep me informed about your experiences!

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here