Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected behaviour with crc8 dvb-s2 #3

Open
kaufmo opened this issue Jan 23, 2023 · 0 comments
Open

Unexpected behaviour with crc8 dvb-s2 #3

kaufmo opened this issue Jan 23, 2023 · 0 comments

Comments

@kaufmo
Copy link

kaufmo commented Jan 23, 2023

Hi @Fabio286,

I've a very specific use case which I need to implement for an external service. I create an unique ID with crc32 & crc8-dvbs2 and there seems to be a problem. The Service has an example which works fine with you algorithms see example below. But when I'm using a new one I ran into an unexpected behaviour maybe you could explain to me what is wrong.

Example:

MessageId = AT999999201812312359598880000000001
CRC-32(MessageId) = 0x45 0xA2 0xDF 0xF1
CRC-8(0x45 0xA2 0xDF 0xF1) = 0xF6
BASE-32(0x45 0xA2 0xDF 0xF1 0xF6) = IWRN74PW

New Message:

MessageId = RC100378202301201049399550000007026
CRC-32(MessageId) = 0x90 0x12 0xE7 0xCC
CRC-8(0x90 0x12 0xE7 0xCC) = 0 // but this should be 0x0A see https://crccalc.com/?crc=9012e7cc&method=crc8&datatype=hex&outtype=0
BASE-32(0x90 0x12 0xE7 0xCC 0x0A) = SAJOPTA= // but this should be SAJOPTAK

Can you pls help me?

@kaufmo kaufmo changed the title Unexpected behavior with crc8 dvb-s2 Unexpected behaviour with crc8 dvb-s2 Jan 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant