UniBo Motorsport HY | Matteo Di Iorio

At a glance

What matters first

What it is: Electronics leadership and embedded work for UniBo Motorsport Formula SAE Hybrid.
My role: Electronics Division Manager from September 2024 to June 2025, with embedded work from March 2024 to March 2026.
Core stack: STM32L496, FreeRTOS, CAN communication, BMS firmware, telemetry, OpenProject.
Best evidence: Electronics responsibility map showing the systems and coordination work around the HY cycle.

HY Electronics Division Manager Role

I served as Electronics Division Manager for UniBo Motorsport Formula SAE Hybrid from September 2024 to June 2025, while also contributing as an Embedded Software Engineer from March 2024 to March 2026. The role combined task planning, integration follow-up, and hands-on vehicle electronics work.

Systems I Coordinated

The electronics scope touched BMS firmware, CAN communication, telemetry and logging, ECU-side integration work, LV wiring, validation, and cross-team coordination. OpenProject helped keep electronics tasks, owners, and bring-up status visible across the HY cycle.

Leadership map

Electronics responsibility map

Sept 2024 to June 2025 Electronics Division Manager Formula SAE Hybrid electronics leadership

STM32 + FreeRTOS

BMS firmware

State management, sampling paths, CAN communication, balancing tasks, and fault handling.

vehicle network

CAN integration

Bus behavior, sender and receiver expectations, communication checks, and bring-up notes.

vehicle integration

LV wiring

Low-voltage wiring design and manufacturing work tied to sensors, electronics, and serviceability.

debug visibility

Telemetry

Logging and telemetry paths used to inspect system behavior during bench and vehicle work.

bench to vehicle

Validation

ST-LINK, oscilloscope, CAN analysis tools, and recorded follow-up during integration.

OpenProject

Coordination

Electronics task planning, ownership tracking, and cross-team alignment for the HY cycle.

Technical Work

My embedded work centered on C/C++ BMS firmware for STM32L496 with static FreeRTOS allocation, LTC6812/SPI acquisition paths, bxCAN communication, cell-balancing tasks, and fault-handling behavior. I also worked on vehicle bring-up tasks including CAN validation, APPS sensor linearization, and bench debugging.

Evidence

Responsibility ledger

Firmware

BMS path

STM32L496 firmware work covered sampling, CAN communication, balancing tasks, and fault-handling behavior.

public scope

Integration

Vehicle bring-up

CAN validation, APPS sensor linearization, LV wiring, and bench debugging kept software tied to physical checks.

field loop

Coordination

Task ownership

OpenProject made electronics responsibilities, follow-ups, and validation status visible during the HY cycle.

leadership

Validation and Debugging

The practical loop was direct: implement firmware or wiring changes, bring them to bench or vehicle checks, inspect CAN behavior with analysis tools, record what changed, and assign the next action. That workflow made debugging traceable across software, electronics, and vehicle integration work.

Lessons From Vehicle Engineering

Formula SAE Hybrid work made leadership concrete, by keeping firmware, bus behavior, wiring, validation, and people aligned while the vehicle moved from plan to integration.