Diverging CRC16 results

[ClaesClaes]

Diverging CRC16 results

[RobTillaart]

Not much time this week to dive into this.

Things I would check

• line endians "\n \r" or single versions.
• UTF encoding?
• special characters?

Would start with a simple test - just a single char "a", extend it and see when it breaks.

[ClaesClaes]

No worries,
thanks for the tip. Integers fitting in one byte produce the same crc results. So good first step. I have no special characters in the files (json) but could be something with the UTF encoding. I'll look in that direction. Thanks again.

[ClaesClaes]

Well, turns out both libraries spits out the exact same crc...
It was my mistake. In the iOS application I add the crc number to the json file at the time of transmission to the ESP32 (my first verification architecture approach) but not the copy stored in iOS. So the two files could never be the same and obviously with different crc outcomes. Apologies for taking up your time.

[RobTillaart]

No problem, on contrary. It is good to have another real live test that the lib is working and doing what it supposed to do.
Thanks