Open Source · Apache-2.0 · v0.1.0
Signal-to-SWC ToolExplicit mapping. Deterministic ARXML. A Python CLI that converts CAN DBC networks into AUTOSAR ARXML only when every governed relationship is explicitly mapped and validated. Missing, conflicting, or out-of-scope data stops the run before output is replaced.
DBC network
Frames and signals
→ Explicit mapping
Signals → SWCs and ports
→ SWC model
Components and runnables
→ Strict validation
Complete or stop
→ AUTOSAR ARXML
Plus assumptions and parity
Supported inputs DBC: CAN frames, signals, senders, and receivers.SWC model JSON: software components, ports, interfaces, and runnables.Mapping YAML: exact signal ownership and port relationships.Optional profile and golden: governed scope, expected counts, and parity baseline.Generated outputs AUTOSAR ARXML: deterministic software-component and communication definitions.Assumptions report: human-readable conversion decisions.Strict parity report: exact mapped and unmapped coverage.Atomic publication: invalid runs leave existing output untouched.Quick start Run the repository's fully synthetic example. No production network data is included.
git clone https://github.com/Taktflow-Systems/signal-swc-tool.git
cd signal-swc-tool
python -m pip install .
signal-swc run \
--dbc examples/demo.dbc \
--model examples/swc_model.json \
--mapping examples/mapping.yaml \
--profile examples/strict-profile.json \
--system-name DemoSystem \
--output-name DemoSystem.arxml \
--golden examples/strict-parity.golden.json \
--output-dir outputStrict by design There is no legacy mode, heuristic ownership, name-derived mapping, or silent fallback. Explicit inputs are the authority.
Current limits It is a conversion and validation CLI, not an AUTOSAR authoring environment. It does not infer missing Signal-to-SWC relationships. It does not replace system-level review or vendor tool qualification.