Oxeltech
Menu
A leading German Battery manufacturer required a working BMS master software for a battery variant. They wanted us to adapt existing software from another battery and add product specific features.
We adapted the existing software to make it work with the new hardware configuration. This required modification of various state machines, adding CAN communication with vehicle, interfacing an on-board charger (OBC), adding bootloader, solving various bugs in the existing firmware, interfacing isolation monitor, error reporting etc.
All the given requirements were satisfied with a stable firmware behavior and now the customer can use the new battery in the vehicle.
Eclipse, VS Code, PCAN Explorer, PCAN View, STM32CubeMX
Oxeltech GmbH embarked on a significant project to develop custom BMS software for a new battery variant in collaboration with a leading German Battery manufacturer. Our task involved integrating the software seamlessly with the low-power STM32 processor. We meticulously adjusted state machines, implemented CANOpen communication protocols for diagnostics, PDOs/SDOs, and other critical features. Additionally, we successfully interfaced an on-board charger (OBC) and integrated a UDS bootloader to ensure secure firmware updates. Throughout development, we prioritized identifying and resolving firmware bugs while implementing robust error handling mechanisms. The outcome is a stable, high-performance firmware solution tailored to meet the precise requirements of the customer’s innovative battery technology.
Our partnership with the customer underscores our dedication to delivering customized solutions that seamlessly integrate with advanced hardware platforms. Leveraging our expertise in embedded systems and proficiency with STM32 series processors, we enhanced the BMS software’s functionality.
Eclipse, VS Code, Altium, Ozone, PCAN Explorer, PCAN View, STM32CubeMX
The microcontroller our customer used for their engine controller was discontinued. This was a serious problem for them as they would be unable to sell those products in the future without changing the hardware. They required experienced firmware developers to port the firmware to STM32 hardware they were developing in-house.
We ported the previous bare-metal application to STM32 application running on FreeRTOS. Separate RTOS tasks were created for CAN, Display, Memory and the main control application, while keeping all the existing functionality intact. Customer can now continue selling their popular product to new and existing end users.
STM32CubeIDE, FreeRTOS
