Services
AI & Software
Solutions
Training
Tools
Insights
References
Contact
Free initial consultation Ask a first question by email
About Deutsch
← AI & Software

Reverse engineering: machines, controllers, software

Understand unknown technology: capture protocols, decode data formats, document behaviour and rebuild interfaces, all within the legal limits.

How I work: with source

The controller runs, but nobody knows what it speaks. The vendor of the machine software is gone, and the documentation is an installation guide. The database has tables without descriptions, the interface is a binary protocol. Anyone who wants to extend here needs understanding first.

How I work: with source · with approval · in your system.

Starting point

Three cases are typical. A machine or device should connect to a new system, but the protocol is unknown. An old domain application should be replaced, but nobody can say which rules live inside it. Or a spare part is missing and the design data no longer exists.

What I do

I observe first instead of guessing: capture network traffic, address devices in a controlled way, read databases, evaluate logs. The result is a description of behaviour, not just a list of fields.

With software, reading code, data and documentation comes on top. AI tools speed this up for large estates but do not replace verification against the running system. Every assumption is checked against an observation.

Depending on the job, the outcome is a report, an interface specification or a working adapter. Where a rebuild makes sense, I build it so that the next vendor update does not silently change its behaviour.

Result

A reverse-engineering report with behaviour, data model and protocols, an interface specification and, on request, an adapter or a first replacement. The documents are the basis for migration, integration or a printed spare part.

Example

I analysed the API of a home automation system: control types, states and the limits of remote control, documented for a custom interface (my own project). On the software side there is the app and protocol analysis of a point-of-sale system, including its data storage, read-only and without contacting the vendor’s services. Where no interface documentation existed, I extracted it from manuals, logs and databases. The work runs on my own analysis toolkit for binaries, protocols and databases; AI helps with reading large code estates, but every finding is checked against the running system. I have not yet had a case of old machine software; there I work with the same method and say up front what I need to check on the existing system.

Possible ground is plant and building technology, measuring devices, point-of-sale systems or domain software without vendor support. Whether a case is viable is decided by a first look at the estate, not by the category.

Limit

Decompiling third-party software is permitted only to achieve interoperability under § 69e UrhG or with the rights holder’s permission. Copy protection must not be circumvented (§ 95a UrhG). For devices, analysing lawfully acquired products is generally permitted (§ 3(1) no. 2 GeschGehG) unless the purchase contract says otherwise. The client checks this first; I start once the basis is clear.

Your effort: access to the estate, a contact person who can explain exceptions, and the legal clarification. If one of the three is missing, the analysis starts later.

How it runs

  1. Clarify the goal and the limit: what should be possible afterwards, what is legally allowed
  2. Observe and measure without changing the system
  3. Document behaviour and data model, mark open points
  4. Specify the interface and, if wanted, build an adapter
  5. Hand over with test cases and operating notes

Common questions

When is an adapter better than a replacement?

When the existing system runs reliably and only a connection is missing. A replacement makes sense when the vendor is gone or the data model no longer carries the requirements.

How long does an analysis take?

A single interface often takes one to two weeks. An unknown device with several operating states can take much longer because each state must be checked.

Who owns the findings?

The client. I document so that another developer can continue without asking me.

Do you work on safety-critical systems?

Only within applicable rules and with the operator’s approval. Safety-related controllers are not an experimental field.

The next step costs nothing.

30 to 60 minutes, no strings attached: where is the biggest friction, what is the most effective lever, and is a collaboration a fit?