NINA — Digital Instrument Cluster
ESP32-based digital dashboard for a 1990 Yugo 55, built on two custom PCBs and tested on the road.
- ESP32
- Embedded C++
- PlatformIO
- KiCad
- 4-layer PCB
Embedded systems · PCB design · Automotive electronics
I'm Simel Miftari. I design custom PCBs, write C/C++ firmware for ESP32 and STM32 and connect devices to the software around them. My hardware runs in a school, has been used daily in a workplace and is installed in a car. I hold a master's degree in Informatics, I'm working on a PhD, and I'm looking for a junior embedded, firmware or hardware role.
Selected work
Each project page covers requirements, hardware and firmware architecture, design decisions, testing and results. Status labels show which systems are deployed, which are prototypes and which are still in development.
ESP32-based digital dashboard for a 1990 Yugo 55, built on two custom PCBs and tested on the road.
RFID check-in/check-out terminal on a custom PCB, with its own backend and web dashboard, used daily at a workplace.
RTC-based bell controller that has run a real school's timetable for about five years.
ESP32-C3 desk device on a custom PCB that talks to the Clockify REST API over Wi-Fi.
Engine control unit built around the STM32G474: power, CAN, sensor conditioning and injector/ignition drivers. Ongoing.
Skills
Every area below links to a project where I used it.
Used inCheckpointNINA
Used inRepair case studies
Used inFull-stack work
Approach
Requirements come from where the device will live. In a car that means 12 V transients, ignition noise and senders that vary from one car to the next. In a school, it means years without anyone touching the device.
I use a scope or logic analyser to see the actual signal before writing a filter or swapping a part. NINA's RPM input rejects ignition ringing based on how fast an engine can physically change speed, not on a guessed filter constant.
Each input, output and service is a separate module with a small interface. Each part can be tested and replaced on its own, and the code is still readable a year later.
Bench tests come first, but a project counts as done only after it has worked in its real setting. Project pages state exactly how far each one has been validated.
Hiring for embedded or hardware roles?
I'm looking for junior embedded software, firmware, hardware or hardware-validation positions. The quickest way to reach me is by email.