Generate UDS Specification

Load BSW Repository (one-click — server scans every ARXML / C file, picks the Dcm / CanTp / Dem modules, auto-detects single vs multi-ECU)
No repository selected. Pick a folder to upload, or click Load sample bundle to materialise the bundled demo repo + two compliance-matrix CSVs server-side and run the full repo → compliance-matrix → tex → pdf flow without any local files.
Compliance Matrices (optional) DOORS-style CSV exports — each row is matched against the parsed ARXML; a "Requirement Traceability" chapter is appended to the output with \cite{} references in LaTeX.
No compliance matrices selected. The "Load sample bundle" button above auto-fills two demo CSVs + a sources YAML.
Options
Additional Input Files DID / RID C sources are picked up automatically from the repository; only the LaTeX class file remains manual.
Choose file or drag & drop
.cls

Parsed Summary

No spec parsed yet. Run Parse & Preview first.

Chat with the parsed UDS Spec

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

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.”

ECU Hardware Test

CAN Interface
ARXML Input
Browse or drop DCM .arxml here
Test Categories
Options
Note

ECU testing requires pip install udsxml2tex[ecu-test] and a physical CAN interface connected to the target ECU. The web UI submits a test request to the local server (udsxml2tex --serve); the server runs the test and streams back the result. For offline report generation, use the CLI directly: 

udsxml2tex --ecu-test --ecu-interface vector --ecu-coverage input.arxml

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]
Ready
Step 1 of 6