Wearable for patient tracking
What was the client’s initial situation? What challenges were they facing?
Nine months before certification and mass production, there was still no stable firmware in place. The team was going through internal changes, and key developers were missing.
The product was already in production, OTA updates were possible, and the battery charging and monitoring system (fuel gauge) was in place. The battery level algorithm lived in a separate IC, configured during manufacturing using a dedicated tool.
But after production started, the calibration changed – and there was no simple way to update it in the field.
How was the client handling the problem before we stepped in?
Before we got involved, the only option was a full device recall – updating each unit manually, one by one. It was costly, risky, and not scalable, especially knowing future changes might still be needed.
How did GoodByte solve the problem?
A dedicated team of four engineers joined the internal crew and helped push the project to MVP – ready for production.
The fuel gauge vendor didn’t offer any documentation on how to update calibration via firmware, so the team reverse-engineered the process. By analyzing how the configuration tool talked to the chip, they built a custom firmware module that could read the same config file and update the fuel gauge directly on the device.
Did this really require four additional engineers?
Of course not. There was still plenty of work to be done around unstable modules, such as OTA updates or database communication.
How did the changes help the client?
The customer avoided costly delays and potential penalties.
The new solution made it possible to update battery calibration remotely – no need to recall or physically access devices, which saved time, money, and a ton of operational hassle.
