Map and rpm limit bug

There appears to be a bug in correctly reading the RPM limit or MAP limit from the G4X ECU. This is using an XML I’ve written with those parameters in the can stream.
It acts like it’s capped.
So with the map limit you can start at zero in the ECU and raise the limit all the way to 255kpa which the dash reads perfectly at every step. Try going anything above that and it drops to 24.
The RPM limit behaves similarly although I ran out of time today to test at what point that stops reading correctly.

255 suggests that value is a single byte and overflows after that. Could that be the case?

That’s exactly what it was thankyou, all sorted and thanks for the swift reply.