UniGo Firmware 1.05.022

We haven't released a new firmware in a while, so this "Winter refresh" has a little more stuff than usual:

• You can't have GPS splits anymore that are closer together than 3 seconds. We did this because 3 second GPS splits are never accurate anyways, and OCD does not let you configure a split point like that.
• There were some typos in the Spanish translation. They are now fixed.
• We are working on a change in OCD that lets you take the UniBox default configuration, make a copy of it, and then change it. That's easier than starting from a new configuration. This is a change for both the UniGo and OCD, and this firmware contains the UniGo part. When we release the new version of OCD, you can try this yourself!
• The UniGo writes log messages into the /Logs folder. This helps figuring out what's wrong when something is wrong. This has been there for a long time, but we made some changes to it:
  • We made sure that writing logs can never interfere with data logging. The data is always the most important thing!
  • We made sure that a GPS signal that sometimes drops and then comes back doesn't write 100s of messages.
  • There was always one error message in the logs during startup that means nothing. We removed it.
• We made a lot of fixes for what happens when the UniGo runs out of space:
  • The UniGo now prints a warning when it's almost out of space.
  • Further, when the UniGo is almost out of space, it doesn't try to update itself anymore. Updating needs space too, so we skip the update if we already know it will fail anyways.
  • While testing this, we found a way to fill up the space on the UniGo so it doesn't start anymore. Now it always starts...
  • ... except when it doesn't even have enough space left to boot up properly. In that case, it prints a warning and and explanation for how to fix it. You can then plug in a USB cable and delete files using the PC or Mac.
• Under some circumstances, using the UniKey could freeze the UniGo. That's now fixed.
• During testing, we found a specific way to configure the LEDs that crashes when logging starts.
• The UniGo turns itself off when it sees less than 4.5V during startup. This is to protect the LiPo battery. 4.5V is still really low for a LiPo battery, and it might be too late at that point. We recommend configuring a battery warning voltage that is much higher, for example 7V.
• In some rare cases, the time for the first split/lap might be shown incorrectly in the display while driving.
• Matt found a way to make the code much smaller. We will probably use that space later for new features :-)

I'm happy to say that a lot of these problems were actually never found on the track. We changed some things about how we test the UniGo internally, before we send it to customers. We hope that this way we can do a better job catching these problems early, before they bother anyone but us.

As always, for thoughts and comments, please get in touch with us at , or by simply replying to this email.

Cheers!