udsxml2tex — Web UI

Generate UDS Specification

Mode

Single ECU (one ECU's DCM/CanTp/DEM → spec) Multi-ECU System (redundant pair / gateway-with-forwarder via system YAML → integration ZIP)

Built-in Samples click a button to load into the corresponding input below

Loading samples…

Input Files

Primary ARXML *

Choose file(s) or drag & drop
.arxml / .xml — multiple allowed

DEM ARXML (optional)

Choose file or drag & drop
.arxml / .xml

Options

ECU Name (override)

Output Format

Additional Input Files

LaTeX Class File (.cls) optional

Choose file or drag & drop
.cls

DID Implementation C Code optional

C/C++ source files containing DID read/write functions. Used to extract global variable references.

Choose files or drag & drop
.c / .cpp / .h / .hpp — multiple allowed

RID (Routine Control) Implementation C Code optional

C/C++ source files containing RID start/stop/result functions. Used to extract global variable references.

Choose files or drag & drop
.c / .cpp / .h / .hpp — multiple allowed

ECU1 — primary / gateway

ECU name

Role

Primary ARXML *

Choose file(s) or drag & drop
.arxml / .xml — multiple allowed

DEM ARXML (optional)

Choose file or drag & drop
.arxml / .xml

ECU2 — secondary / endpoint

ECU name

Role

Primary ARXML *

Choose file(s) or drag & drop
.arxml / .xml — multiple allowed

DEM ARXML (optional)

Choose file or drag & drop
.arxml / .xml

DID / RID Implementation C/C++ Sources (optional)

Upload C/C++ files containing each ECU's DID read/write or RID start/stop/result functions. The scanners populate DataElement.global_variables / Routine.global_variables in the spec output.

DID-C — ECU1

Choose files or drag & drop

DID-C — ECU2

Choose files or drag & drop

RID-C — ECU1

Choose files or drag & drop

RID-C — ECU2

Choose files or drag & drop

LaTeX Class File (optional, shared across ECUs)

Choose file or drag & drop
.cls — overrides the bundled udsspec.cls for every per-ECU spec and the system integration document

Options

Output Format

Infer routing rules from ARXML coverage gaps

Advanced — System YAML override (optional)

Upload an explicit system.yaml to define routing rules, topology, or non-default ECU naming. Without an override, a minimal config is synthesised from the per-ECU file slots above and routing inference does the rest. The bundled samples/system_redundant.yaml is the schema reference.

Chat with the parsed UDS Spec

Spec context

No spec loaded. Parse an ARXML on the Generate tab first.

Settings

Provider

Model

API key (optional — overrides server's environment)

Requires pip install udsxml2tex[llm] on the server. For Ollama, pick Ollama (local) — Base URL, model, and API key are filled in automatically. For other local servers (llama.cpp / vLLM / LM Studio), pick OpenAI-compatible and set the Base URL manually — your spec JSON never leaves your machine. The default Anthropic path uses prompt caching so repeat questions are cheap. Your API key, when supplied here, lives only in this browser tab.

Conversation

Try: “Which DIDs require security level 2?”, “List every NRC returned by SID 0x27.”, “Summarise the SecurityAccess configuration.”

About udsxml2tex

Overview

udsxml2tex converts AUTOSAR DCM / CanTp / DEM ARXML configuration files into professional UDS (ISO 14229) specification documents. It supports LaTeX, HTML, and PDF output formats.

Version: —

Features

Parse AUTOSAR DCM ARXML — sessions, security levels, services, DIDs, routines, DTCs
Optional DEM ARXML for full DTC event configuration
Output formats: LaTeX (ZIP), HTML (ZIP), PDF
Custom LaTeX class file (.cls) support
DID C code scanning — extract global variable references from DID read/write functions
RID C code scanning — extract global variable references from RID start/stop/result functions
Parse & Preview — inspect specification before generating
Works entirely in-browser — no data leaves your machine

Usage

Start the server with the CLI flag and access it in a browser:

udsxml2tex --serve

Optional web dependencies:

pip install udsxml2tex[web]