HERDER ELEKTRONISCHE SYSTEMEN

Service 01 / Embedded systems

Embedded controls
that behave.

We design firmware around real hardware—connecting sensors, actuators, communications and control logic into a system you can test and understand.

This work is useful when a prototype needs clearer states, more predictable timing, better fault handling or a cleaner path from firmware changes to measured results.

Start a technical discussion →
01Capabilities

From first state
to full system.

Firmware and control

  • C and C++ for MCU systems
  • Firmware architecture, state machines, interrupts and timers
  • PWM, ADC acquisition, encoder interfaces and real-time control
  • Motor and actuator control integration
  • Fault handling and explicit operating states

Platforms and interfaces

  • TI C2000 and ESP32
  • Arduino and STM32-class systems where the project calls for them
  • CAN, SPI, I2C and UART interfaces where required
  • Hardware and firmware bring-up
  • MATLAB and Simulink integration where it helps answer the control question
02Tools and platforms

A practical
working set.

LanguagesC / C++Python
EmbeddedTI C2000ESP32MCU-class systems
InterfacesUART / SPI / I2CCAN where applicable
ControlMATLAB / SimulinkPWM / ADC / encoders
DocumentationGit repositoriesInterface notes
03Typical deliverables

Useful work for
the next decision.

  • Architecture and interface notes
  • Firmware source or prototype code
  • State and fault-handling documentation
  • Integration and test procedures
  • Validation observations, plots or handoff notes

The deliverables depend on the project stage, the available hardware and the scope we agree together.

04Representative work

Public technical
evidence.

Public educational reconstruction

ESP32 Robotics Control Platform

BNO08x sensing, PS4 Bluetooth input, H-bridge PWM motor control, quadrature encoder feedback, servo actuation and self-balancing PID control.

View public repository ↗
Hardware-backed demonstrator

TI C2000 Actuator Controller

F28069M control with SCI/UART commands, an explicit state machine, ePWM output, setpoint validation, fault latching and safe-low behavior.

View public repository ↗
Public university research

TI Piccolo PMSM dynamometer

Dual-motor work covering F28069M field-oriented control, QEP encoder feedback, SCI-to-CAN migration, real-time testing and validation.

View public MTU repository ↗

These are public technical projects, not presented as completed client contracts.

05Engagement process

Build a clear
technical path.

Technical discussion → Evidence and requirements review → Architecture or recovery plan → Implementation → Integration and validation → Documentation and handoff

The order changes with the project. We use the first discussion to identify what should happen next.

06Good fit

Bring the
hard part.

  • Prototype firmware or control-system integration
  • Communications and hardware/firmware debugging
  • Motor or actuator control development
  • A testable embedded prototype and a clear handoff

Not a fit: unsafe or unlawful work, certification requests outside this practice, mass-production commitments, or projects without reasonable access to hardware, documentation or test evidence.

Start a technical discussion

Let’s make it
real.

Tell us where the project stands, what you want it to do, when you need it and what technical material is available. Please describe the project first; secure file exchange can follow.

Start a technical discussion →

Or write directly: [email protected]