cc1xxx CRC ok != packet is not corrupted. Any light weight solutions? FEC is too heavy

z mz

Hi all,

Anyone has this question? In my test environments it happens quite often that CRC is ok but packet is corrupted.

While cc2xxx (2.4GHz) chips do not have this problem.

How shall I solve it? Does an additional CRC/checksum for my data packets solve this problem? What kind of checksum/crc algorithm shall I use? Thank you very much.

I just want to make sure part of my packet (which contains important data) is correct with very high probability before I use them.

Thank you very much.

over 16 years ago

0 Denis Kuzmenko over 16 years ago

Intellectual 540 points

CRC16 gives very high probability. Try to find error anywhere else.

FEC helps?

0 ronnym over 16 years ago

Expert 1835 points

I guess the easiest way to add a data checksum is to add the value of all the bytes in the string you send, and the sum with 0xFF. Then send it out at the end of the string. Do the same on the received packet, and see if it matches the last byte. The CRC16 should really be all you need most of the time as previously replied.

Ron.

Other wireless

Other wireless technologies forum

cc1xxx CRC ok != packet is not corrupted. Any light weight solutions? FEC is too heavy