Skip to main content
Automotive software · Embedded systems · Bavaria

Software made
for the vehicle.

ATMAN develops automotive software for suppliers, vehicle developers, and fleet operators, from embedded firmware and CAN Bus diagnostics to telematics cloud systems. We work across Bavaria and beyond.

Automotive capabilities

From the ECU to the cloud, we build the software layers used in modern vehicles, test systems, and vehicle-development programmes.

Embedded & ECU software

Bare-metal and RTOS firmware for ECUs and microcontrollers. We work in C and C++ with MISRA guidelines, develop drivers, integrate board-support packages, and implement FOTA mechanisms.

CAN Bus & vehicle protocols

Application and driver software for CAN Classic, CAN FD, LIN Bus, and Automotive Ethernet. We implement UDS, J1939, SOME/IP, and DoIP for ECU communication and diagnostics.

OBD-II & diagnostic software

Desktop diagnostic applications for workshops, test benches, and vehicle development. Work includes UDS sequences, flashing, trouble-code handling, and custom interfaces through CAN adapters or DoIP.

Telematics & connectivity

Telematics control units for vehicles and machines, including GPS capture, 4G/LTE connectivity, MQTT streaming, and cloud integration for fleet data and remote diagnostics.

Test bench & validation software

Hardware-in-the-loop automation, test-bench control, and analysis software. We build automated sequences for ECU validation, regression testing, and end-of-line production tests.

Automotive cloud & data

Backend systems for vehicle-data ingestion, storage, and analysis. We build fleet dashboards, OTA update infrastructure, and interfaces to existing ERP and MES systems.

Reference flow: from vehicle bus to usable system The layers separate low-level communication, diagnostics, transport, and operation. This makes the architecture legible across test benches, development vehicles, and fleets.
  1. ECUs & sensorsControl units, measurements, states, and diagnostic memory
  2. Vehicle networkCAN Classic, CAN FD, LIN, or Automotive Ethernet
  3. Diagnostic gatewayUDS, OBD-II, J1939, SOME/IP, or DoIP
  4. Backend & cloudTelemetry ingestion, storage, and interfaces
  5. Test bench & fleetTesting, diagnostics, analysis, and operations
Bus layer
Messages, timing, states, and failure cases
Diagnostic layer
Sequences, responses, and result records
Operating layer
Measurements, vehicle state, and update status

Automotive software in practice

Systems we build for vehicle developers, Tier 2 and Tier 3 suppliers, and fleet operators in Bavaria's automotive cluster.

01

ECU diagnostics & flash tools

Custom applications communicate with ECUs through CAN or DoIP. UDS implementation, diagnostic trouble codes, parameterisation, and flash programming support development, workshops, and production lines.

02

Vehicle telematics for suppliers

Telematics units capture CAN, OBD-II, and GPS data and transmit it to cloud backends. Suppliers can provide OEM customers with live diagnostics or fleet-usage data through a dedicated portal.

03

Test-bench automation

Software controls and analyses functional and endurance test benches. Automated sequences, measurement capture, threshold checks, and reporting support ECU, motor, and component validation.

More use cases
04

Fleet-management software

Web-based systems combine GPS tracking, trip records, maintenance intervals, and consumption analysis for commercial fleets, municipal vehicle pools, and mobility providers.

05

FOTA & remote updates

Firmware-over-the-air infrastructure manages packaging, signing, rollout control, and rollback for connected vehicles and machines.

06

Production line & end-of-line tests

Automated systems flash and test ECUs or components, record results, and connect to MES platforms for traceable production documentation.

From brief to working software

Automotive projects have tight schedules and explicit quality requirements. Our process keeps technical decisions visible and tests integration early.

  1. Technical analysis

    We analyse the vehicle or system architecture, existing protocols, and interfaces before preparing a proposal.

  2. Architecture & protocol design

    Software layers, protocol behaviour, data models, and interfaces are defined and reviewed before implementation begins.

  3. Development & integration

    Iterative development starts integrating with target hardware early. Each increment is tested on the real system where possible.

  4. Validation & testing

    Tests cover target hardware, expected behaviour, boundaries, communication, and relevant failure scenarios in the project environment.

  5. Handover & support

    We provide documentation, source-code handover, and onboarding. Optional support covers maintenance, extensions, and follow-on work.

Our automotive stack

Standard protocols and field-tested tools, selected for the project instead of hidden behind proprietary black boxes.

C / C++ Rust Python CAN Bus / CAN FD OBD-II UDS (ISO 14229) J1939 LIN Bus
More technologies
SOME/IP DoIP MQTT FreeRTOS Linux (Embedded) QNX MISRA C/C++ PEAK CAN Vector CANalyzer STM32 NXP S32 Raspberry Pi CM Qt (HMI) AWS IoT Azure IoT Hub InfluxDB Grafana

What clients ask us

Which protocols does ATMAN support?

CAN Classic, CAN FD, OBD-II, UDS, J1939, LIN Bus, SOME/IP, and DoIP. For cloud connectivity, we work with MQTT and project-specific telematics protocols.

Do you develop MISRA-compliant code?

We use MISRA guidelines for C and C++ and can review existing code for conformance. For safety-related ECU work under ISO 26262, we agree the appropriate quality framework first.

Can you build diagnostics for our test bench?

Yes. Our desktop tools can communicate with ECUs through PEAK or Vector CAN interfaces or DoIP, including UDS sequences, flashing, trouble-code handling, and custom test-bench interfaces.

Does ATMAN work with Tier 2 and Tier 3 suppliers?

Yes. We focus on suppliers across Bavaria's automotive cluster, including Regensburg, Ingolstadt, Munich, and Landshut, and build for real development and production environments.

“ATMAN's team took our requirements and legacy infrastructure and rebuilt it into a modern platform in under six months. The quality of engineering is exceptional.”
J.M.CEO, SüdOstSpreng · Engineering

Planning an automotive project?
Let's talk.

Tell us about the vehicle system, protocol, or constraint. We will respond within 24 hours with an initial technical assessment.

Automotive software by proposal  ·  Straubing, Bavaria  ·  Remote or on site
The vehicle system, protocol, goal, and main constraints are enough.

We use your details only to respond to this enquiry. Marketing consent is not required. Read our privacy policy (German).

No spam  ·  Free and non-binding  ·  Response within 24 hours