Services

What I take on

Work that sits between the electronics and the software, where most prototypes stall.

• Firmware for motors, sensors and actuators, including closed-loop control
• Custom boards: motor drivers, sensor front-ends, and the firmware for them
• Getting microcontrollers and ROS 2 systems to talk to each other
• Taking an existing prototype from “moves on the bench” to “runs reliably”
• Sensor data pipelines, from the device through MQTT to a dashboard
• Technical lead on builds with several people working in parallel: architecture, task breakdown, and the interfaces between them

How a project usually runs

A short call or a couple of emails to understand the problem, then a written scope with a fixed price and a delivery date before any work starts. Most projects run a few weeks. I work remotely, and I’m in Vienna if the hardware needs hands on it.

Availability

My capacity is largely committed at the moment. Around a day a week is open for a new project, which suits a defined piece of work better than an open-ended engagement. More frees up later in the year. If your timing is tight, put that in your first mail and you will get a straight answer about whether it is realistic.

What I need from you to quote

What the machine has to do, what already exists, what the deadline is, and the constraint that matters most: cost, size, power, or how fast it has to be finished. Rough answers are fine.