There is distance counter in byte 5 and 6 in ca-bus frame and value goes to zero when it reach 30000.
If trust to information i found that 50 counts are 1 meter, so in every 600 meters it goes to zero.
I tested it and in my opinion it reaches 30000 much earlier, with few meters driving, so i maybe read wrong bytes or something, but that is other thing.
I use RealDash and i want that value, of course calculated right in future, to the text gauge.
What i want to know is how to avoid that overflow.
Or is there any simple way to store and save value to odometer display before it goes to zero when driving?
I read about overflow, but i think for example unsigned long may not be a good solution.