PMAXKBI is what is contained in that byte and loaded by the Mbox firmware.

It’s sent out once more in another ID very near.

This has nothing remotely to do with error reporting for the reed sensor. Yet it throws the reed sensor fault in the cluster. I would argue that given the difference in years this would be an acceptable method to rid this error instead of having to switch to another firmware which doesn’t report that byte anyways.

Always open to debate, I just don’t see how that error isn’t a false positive with how the cluster is interpreting the data from that specific CAN message.

Yes, that also does work. I was just trying to preserve the usage of it elsewhere which is why I opted for only that change in code. Thanks for your input!