Toolkit

Programming languages

• C
• Python
• JavaScript
• HTML
• CSS
• SQL
• PHP

C is where I have lived for sixteen years: bare metalbare metalCode that runs straight on the microcontroller, with no operating system underneath it., no operating system, on parts where a kilobyte is a real constraint. Python is the working language for everything around the product: test benches, data analysis, and plant modeling. The web stack is genuine but occasional, and it comes from a side project.

Microcontrollers

• Renesas RA / RX / RL78
• Infineon PSoC
• ST STM32 (F4, F7, H7)
• Freescale S08
• Microchip PIC
• 8051-core MCUs (Silicon Labs, Atmel)

Nine vendors over sixteen years, from 8-bit parts written partly in assembler to Cortex-M7 driving a graphical framework. What carries across is never the family, it is the habits: read the errata before the datasheet, respect the peripheral mapping constraints when you fix the pinout, and assume the part will be second-sourced.

Communications

• UART
• SPI
• I2C
• QSPI
• SDRAM
• BLE
• Wi-Fi
• MQTT
• DALI
• DMX
• field buses

Most of my work is boards talking to each other inside a single appliance, which is where the proprietary buses live, and displays talking to a microcontroller, which is where the bandwidth goes. The wireless side is newer and mostly serves connectivity modules and remote test benches, which is where MQTT earns its place.

Control

• PID / PI loops
• on-off control
• FOPDT plant modeling

Thermal plants, mostly: slow, with real dead time, and with a response that changes with the operating mode and the size of the cavity. I model the plant before tuning the loop, because tuning on the real appliance costs hours per attempt and gives an answer that only holds for one configuration. How that actually works.

Safety and standards

• Class B (IEC 60730, IEC 60335)
• VDE
• UL
• CB Scheme
• risk analysis
• MISRA
• Polyspace

The hardest part of this inventory to acquire and to fake, because it is learned by defending a concept in front of a certifier rather than by reading the standard. MISRA and static analysis are what make the software side provable: in a certification, evidence and correctness are not the same claim.

Process and tools

• V-Model
• Polarion
• Git
• Jira
• Altium Designer
• LTspice

The V-ModelV-ModelA development process that pairs every specification step with the test that proves it. is how I think about a project rather than a box I tick: requirement, specification, design, and the test that proves each one. Altium and LTspice are here because I read and modify hardware and simulate the changes, not because I am the hardware designer.

Spoken languages

• Spanish, native.
• Catalan, native.
• English, working proficiency (CEFR B2/C1). Daily technical liaison with appliance manufacturers across Europe, Asia, and the Americas: meetings, specifications, counter-proposals, and field support.