Tools for control units — software and hardware.

We build logging and flashing tools— as PC software, as a standalone device or both. Tools to read, record and safely apply software versions, for development, test bench and service. What gets written with them is the user’s decision — we do not supply the payload.

DEPTH OF SERVICE
Tool software (PC)in-house
Device firmwarein-house
Schematic & layoutin-house
Prototype & small seriesin-house
PCB fabrication & assemblyvia manufacturer
Modification / tuning filesnot offered

We build the tool, not the content: application software in customer ECUs and homologation are not part of our scope.

CORE FOCUS

Logging and flashing tools — software and hardware from one source

Tools for development, test bench, end-of-line programming and service. Built for continuous use, not lab improvisation.

Logging tools

AX-LOG
HARDWARE
CAN and CAN-FD interfacesMass storage & precise time baseTrigger inputs, galvanic isolationIn-vehicle supply, quiescent current design
SOFTWARE
Recording of bus communicationRecordings stored as CSVPC software for plotting the data
Typical use: development, test bench, endurance runs and service — record and prove, not intervene.

Flashing tools

AX-FLS
HARDWARE
Programming adapters and level shiftingStabilised supply during programmingProtection against abort and undervoltageTest setups prepared for production
SOFTWARE
UDS flash sequences, bootloader protocolsChecksum correction and versioningRecovery after a failed attemptLogging and series programming
Typical use: apply software versions safely and traceably. What gets written is supplied by the client.
THE TOOL — NOT THE PAYLOAD

We build the tool, not what gets written with it.

Our tools work generically and content-neutrally. What is written to a control unit is the client’s decision and responsibility; we do not supply modification files or calibrations. We work only with the rights holder’s authorisation. Legal admissibility is clarified per project and recorded in writing before the project starts.

Read, record and decode
Write and correct checksums
Recovery after abort, logging
No built-in manipulation functions (e.g. DPF, EGR, speed limiter)
No changes to emission, safety or mileage data
No ready-made modification files or third-party calibrations
No circumvention of signature or access protection as a feature

FURTHER SERVICES · A1–A5

A1Tool software & firmware — PC application, standalone device or both
A2Bus systems & protocols — CAN, CAN-FD, UDS
A3Hardware — breakout prototype, own board in KiCad, fabrication and assembly ordered
A4Prototypes & bring-up — every delivered board checked in our own lab
A5Requirements & documentation — written and traceable

Depth: tool software, device firmware, schematic, layout, prototype and small series in-house; series production of our own boards via partners.

CLEAN ROOM · LEGACY SYSTEMS

Reverse engineering ends at interoperability

We analyse a legacy system only as far as interoperability requires — that is where the statutory permission ends, and we do not go beyond it. The deliverable is a functional specification, never derived code. That is where our work ends; implementation happens separately, by your team, a third party or an implementation partner without access to the analysis material.

Before a project starts we check licence and confidentiality terms and record the authorisation in writing. The released specification is frozen and dated; analysis material stays in a separate, access-restricted area.

Deliverable: specificationImplementation kept separateFull audit trail

Need a tool? Send us the requirements.

For development, test bench, service or motorsport — we reply with an initial technical assessment.

Contact →