Has anyone noticed that when you set the Min or Max for a parameter, the logic seems to be a < rather than a <=?

For instance, setting a max value for a temperature at 100 will cause the parameter to go invalid when the parameter is actually equal to 100.

Jerry

That could be caused by the resolution of the parameter.

For example, Fuel Level 1 has a resolution of 0.4 and it's maximum value is 100 but 0.4 is not expressed exaclty in binary so when it is multiplied by 250 (0xFA) it ends up being just a little more than 100 and it will make the gauge look invalid.

This is a known bug and it will be fixed in a future release but for now you can make the maximum value larger but by less than the resolution. We made Fuel Level's maximum value 100.1