CASE STUDIES

Case studies.
Your design stays yours.

You will not find customer projects on this page, and that is deliberate. Every design I work on belongs to my client: the schematics, layouts, firmware and test results, and often the fact that the product exists at all. Protecting that intellectual property is the foundation of the trust my clients place in me, so I do not show case studies at any level.

What I can show is how I work. Over a long period I developed and used a set of standard building blocks to prove automotive concepts quickly, before any dedicated hardware was designed.

No customer design is shown

Schematics, layouts, firmware and test data stay confidential, during the project and after it.

No case studies at any level

Not even anonymised: one familiar detail can be enough to identify a product or a client.

IP and trust come first

Your intellectual property, and the trust you place in me, are the most valuable things I work with.

PROOF OF CONCEPT

Standard building blocks.
Software from day one.

Each building block is a proven hardware module for one general function. Combined, the blocks form a working electronic control unit (ECU) on the bench long before dedicated hardware exists.

Because the blocks come with a standard software library, which I also developed, firmware development could start almost at once: in parallel with the concept work, not after the first prototype boards.

The blocks were used to prove concepts for automotive ECUs of many kinds, including multi-function units, working together with other control units in the vehicle. Only when a concept was proven did the project move on to dedicated hardware design.

Standard hardware building blocks

  • Supply and protection
  • Microcontroller core
  • Vehicle network interfaces
  • Inputs
  • Outputs and drivers
  • Sensor interfaces
Standard software library runs on every block from day one
On the benchProof-of-concept ECUSingle or multi-function, built from the blocks
Other vehicle control unitsTested together in the real system
Dedicated hardware designStarted once the concept is proven, then on to start of production
From standard blocks to a proven concept, then to dedicated hardware. Block names show the general functions.
01

Software starts at once

With the standard library, firmware work begins with the concept, not after the first boards.

02

Proven hardware, lower risk

Each block was reused over a long period, so a new concept is tested on hardware that is already known to work.

03

Tested with the real system

Concepts are proven together with other automotive control units, so integration issues appear early.

04

Faster to market

Building on standard modules has been of very high value for a fast route to market.

Conventional route

Dedicated hardware designFirst boardsSoftware developmentConcept proven

Building-block route

Blocks assembledSoftware from day one, concept proven on the benchDedicated hardware, already de-risked
Where software starts on each route. Illustrative, not to scale.

The same principle guides my consulting work today: reuse what is proven, start the software early and design dedicated hardware once the concept is clear.

CONTACT

Tell me about your concept.
I read every message myself.

A new product to develop from scratch, a design that needs a second look, or a prototype that does not work yet: a few lines are enough to start.

  • A personal reply within one working day
  • No cost and no commitment up front: you only pay for work you approve
  • Your idea stays confidential, NDA on request (how I keep your project confidential)
Henrik Andersen at his desk, ready to talk about your product
Henrik AndersenElectronic engineering consultant

Write to me

info@siliconmeetscode.com
Write an email

Helpful to mention: what the product does, where it is today, and your timeline. The email opens with these questions ready to fill in.

Working from Belgium and Germany with clients across Europe and Asia