Spurious firmware version numbers from an FTC MK1 #3
Description
Our FTC team (Robovines 6955 -- I'm a programming mentor) has been using the FTC MK1 octoquad since last season. We specifically are using it with 3 gobilda odopods. We got occasional spurious values (seemingly bit flips) through the i2c bus, and had added our own code to detect when the values were clearly wrong and ignore them (this mostly worked but occasionally we would take a modestly wrong value).
We just upgraded to the V3 firmware and are using the code provided from this library. The isDataValid() method works as desired -- when that check passes, all of our data looks good.
Fairly often, however, the driver control hub prints a warning about an incompatible firmware version (the "OctoQuad is running a different major firmware version than this driver was built for ..." message or the "OctoQuad does not report correct CHIP_ID value" message). Printing the firmware version string, we see that it often has bad values (often 3.0.10 as we'd expect but sometimes 131.0.10 and sometimes 127.255.255). We get the same results regardless of which rev hub or expansion hub and which i2c port we plug into. This happens even when we aren't operating motors. Other i2c devices are plugged in to other i2c ports.
Have you seen this before? It isn't causing any functional issue, because we guard the actual reads with the isDataValid method. We can obviously suppress the warning messages, but we'd rather have less spurious values.
Thank you.