Should be ignoring high bit of CAN frames in MTI decode

[bobjacobsen]

OpenMRN is apparently checking the top 0x1,0000,0000 bit of CAN frames for a 1. That bit is “send as 1, don’t check on receipt” so the zero should be valid.

For example the Fast Clock replies to a VerifyNodeAddressed when a 1 is there and doesn’t with a zero there.

See Frame Standard section 4 and TN section 2.4.