Reusable diagnostic model
Extend DID, DTC, Routine, session, and security definitions across product lines and ECU variants instead of rebuilding them for every program.
Back to / Embedded Systems
ECU-Side UDS Diagnostic Middleware
KopherUDS
Released Version 0.1.0
Build a reusable ECU diagnostic core with one diagnostic model from service configuration and application integration through test validation.
KopherUDS UDS Software Architecture
Overview
Turn project-specific diagnostics into a reusable ECU capability
KopherUDS provides configurable automotive UDS diagnostic middleware for integrating Diagnostic Session, DID, DTC, Routine, SecurityAccess, memory, and programming services into an ECU. DCM, DEM, NM, and DoCAN / DoIP handle service flow, fault events, network state, and transport, while engineering teams connect their actual data sources, I/O, Routines, and platform services for each ECU program.
ID · ko-uds
ODX Import and Code Generation
KopherUDS
Configurable service scope
Select diagnostics, fault management, communication control, memory, and programming services for each ECU profile while retaining room for OEM extensions.
Algorithm-neutral security
GetSeed / CompareKey callbacks separate UDS 0x27 from OEM algorithms, HMAC, and HSM / SHE key services.
Connected configuration and validation
Kopher Config generates ECU configuration while KITE UDS Tester validates services, trace, and reports in one engineering workflow.
Product Highlights
Covers common session, reset, DTC, DID, memory, SecurityAccess, communication, Routine, download / upload / transfer, and TesterPresent workflows.
Connects DID, DTC, Routine, I/O, memory, and flash behavior to the existing ECU application and platform services through callbacks.
Links one diagnostic model to Kopher Config configuration and code generation plus KITE UDS Tester validation and reporting.
Core Capabilities
DCM service runtime
Handles request routing, positive / negative responses, and pending flows from session, security level, service table, and P2 / P2* timing configuration.
DID, memory, and Routine
Supports DID lists / ranges, multiple DIDs, sync / async client-server, sender / receiver, optional NvM, and project memory or Routine callbacks.
DEM diagnostic event management
Connects events, debounce, snapshots, extended data, DTC state, and clear / report / ControlDTCSetting workflows.
SecurityAccess integration
GetSeed / CompareKey callbacks support pending, attempt counters, delay timers, and NRC policy before connecting to customer algorithms or hardware-backed key services.
DoCAN and DoIP transport
Carries diagnostics over CAN / ISO-TP and Ethernet / DoIP paths through PduR, ComM, NM, and lower-level driver integration.
Programming service hooks
Provides RequestDownload, RequestUpload, TransferData, RequestTransferExit, and memory callbacks while KopherBoot or the project owns the final flash policy.
From diagnostic definition to ECU acceptance evidence
The same DID, DTC, Routine, session, and security definitions flow through configuration, ECU runtime, PC validation, and delivery review.
1
Define diagnostics
Capture DID, DTC, Routine, session, SecurityAccess, timing, and transport profiles.
2
Generate with Kopher Config
Validate project rules and generate the ECU configuration plus callback boundaries required by KopherUDS.
3
Integrate the ECU runtime
Connect DCM, DEM, NM, transport, and application / boot hooks to the target MCU and vehicle network.
4
Validate and accept
Use KITE UDS Tester for interactive diagnostics, automation, trace, and reports, then complete acceptance with on-target results.
Where KopherUDS fits
KopherUDS fits automotive controller programs that need diagnostic requirements implemented in ECU BSW with PC validation and delivery evidence.
ECU diagnostic BSW integration
Implement sessions, DID, DTC, Routine, SecurityAccess, and transport, then connect MCU, NvM, flash, and application callbacks.
Shared diagnostics across ECUs
Reuse the DCM foundation and service model while each ECU keeps its own data, callback, and network profile differences.
Consistent development and acceptance
Keep Kopher Config, KopherUDS, and KITE UDS Tester on the same diagnostic definition to reduce duplicated ECU and PC maintenance.
Supported Formats & Standards
AUTOSAR CP DCM ISO 14229 UDS ISO 15765-2 / DoCAN DoIP / TCP-IP DCM / DEM / NM Kopher Config KITE UDS Tester