1 digit readout issue on dash for Lambda

[B17overhead]

Always had 2 digits on the dash (like 1.60 or 0.92 Lambda) but now something has changed and only get a 1 or a 2 or no digits if the LCU-One isn't on. Now, downloading after an event to my PC, all the 2 significant figure data is actually there and it all looks fine.

Going into config of LCU-One, it, looks fine.
Dash config looks fine.
Only clue that it might be something I can't fix with a config reload or change to config is that my EVO4S board was replaced at AIM at the Lake.
Ideas, anyone?

[romoman]

Always had 2 digits on the dash (like 1.60 or 0.92 Lambda) but now something has changed and only get a 1 or a 2 or no digits if the LCU-One isn't on. Now, downloading after an event to my PC, all the 2 significant figure data is actually there and it all looks fine.

Going into config of LCU-One, it, looks fine.
Dash config looks fine.
Only clue that it might be something I can't fix with a config reload or change to config is that my EVO4S board was replaced at AIM at the Lake.
Ideas, anyone?

Is the FW up to date? There was a version a (longish) while ago that did something similar.

[B17overhead]

Thanks for the idea. I'll be checking

[Steve Davis]

It's been a WHILE since I used an AIM system, but pretty sure there is a SETTING in Config that allows you to select how many DIGITS you want to see. Don't know how it might have gotten changed without YOUR input, but you might want to check that first. Trying to visualize the config screen, but can't quite remember... seems like it was the last tab on the right .. but maybe not? That's the AIM config.. not the LCU.
Steve, FV80