Which microcontrollers and interfaces do you support?

My focus is on ESP32 and Arduino-compatible platforms. Other platforms, bus systems or protocols are assessed case by case – I will tell you openly if something is outside my experience.

I only have an idea, no schematic. Is that a problem?

No. We start with the purpose and requirements; from there, a test setup and then a robust solution are developed step by step.

Microcontrollers and embedded systems

When software meets hardware, programming skills alone are not enough. You need to understand how signals are generated, how components behave and what happens when something fails. I develop solutions from the firmware to the working setup.

Services

Firmware development and microcontroller programming
Sensor integration: capturing, filtering and evaluating measurements
Control and monitoring systems
Communication between hardware components and with applications
Serial interfaces and bus systems – depending on the project and feasibility
Evaluating contacts, switching signals and relays
Diagnostics at hardware and software level
Test setups and prototypes
Integration into existing systems, documentation and maintenance

Evaluating signals, automating processes

Many devices already provide a signal – such as a switching contact or a status message. It can trigger defined actions: lights, displays, notifications or forwarding to other systems.

Where reliability matters, defined failure states, safe restart behaviour, traceable logging and tests under realistic conditions are part of the job.

Productive, safety-critical systems require appropriate validation and, where applicable, professional review or approval. Automation complements alerting – it does not replace it.

Enclosures and mounts from the 3D printer

So that a setup does not lie loose on the desk, I design and print matching enclosures, mounts and fixtures where needed. Printed parts are generally not suitable for safety-relevant or heavily loaded components.

Approach

First we clarify what the solution should do and under which conditions it runs: power supply, environment, reliability, maintenance. Then a test setup is built to check assumptions quickly. Only when that works does the permanent implementation follow – documented, so it remains understandable later on.

Honest limits

Not every platform and protocol is part of my daily work. Before I commit, I check technical feasibility and tell you openly where I have experience and where a project requires familiarisation.