ANCIT's intelligent UDS Stack Configuration Tool that bridges the gap between AUTOSAR and non-AUTOSAR ECU development. Generate fully compliant UDS stacks in ARXML and C/H source code formats — without writing a single line of code.
VxDiag is ANCIT's intelligent UDS Stack Configuration Tool that bridges the gap between AUTOSAR and non-AUTOSAR ECU development. It empowers engineers, researchers, and educators to generate fully compliant UDS (Unified Diagnostic Services) stacks in both ARXML and C/.H source code formats - without writing a single line of code.
Define ECU parameters, diagnostic sessions, and service behavior through a clean GUI — then click Generate to produce a complete, compilable UDS stack.
Perfect for teaching, prototyping, and production deployment!
Generate Service and Diagnostic ARXMLs ready for RTE integration
Generate C/H code-based UDS Stack for direct deployment on microcontrollers
Build UDS configurations for both AUTOSAR and Non-AUTOSAR ECUs from a single tool.
Define parameters through GUI and generate complete, compilable UDS stacks instantly.
All diagnostic services generated in accordance with ISO standards for reliability.
Choose, edit, or assign Negative Response Codes for each UDS service easily.
Generated code compiles directly on automotive-grade MCU platforms.
Set ECU addresses, timing parameters, DIDs, and security levels through intuitive UI.
Integrate effortlessly with ANCIT's SmartWheels UDS Simulator to test your stack before deployment. Validate diagnostic services, test NRC responses, and ensure complete functionality in a safe simulation environment.
Native support for all SmartWheels ECU variants with optimized code generation.
Full support for NXP S32K automotive MCU family with validated drivers.
Compatible with Texas Instruments TMS570 safety MCUs for critical applications.
ISO 14229 defines 26+ UDS services. Each stack implements only the subset it actually needs — nothing more, nothing less.
VxBoot exposes only the flash pipeline — fewer services means fewer entry points at the most security-critical ECU operation. Bundling VxDiag would expose flash-programming capability at the diagnostic layer. That’s a security hole, not a feature.
Each stack is tested and updated on its own cycle. VxBoot doesn’t break when VxDiag’s DID list evolves. ROM footprint stays predictable — bootloaders live in reserved flash, so keeping them isolated keeps them tight and portable across ECU variants.
VxDiag is a scalpel for field diagnostics — precise, focused, no flash access. VxBoot is a scalpel for programming sessions — no DTC context, no calibration. Giving you both in one binary would be like handing every nurse a surgeon’s kit. Separation is by design.
Mixed stacks blur ownership and complicate safety cases. Separate stacks map directly to ISO 26262 decomposition — each has a clear ASIL level, a clear memory region, and a clear integration boundary. No ambiguous handoffs between diagnostic and bootloader sessions.
Same standard, different purpose. ISO 14229 defines the full UDS vocabulary — 26+ services. VxDiag uses the diagnostic subset: DTC management, calibration, I/O control. VxBoot uses the flash programming subset: download session, data transfer, memory erase.
They share only 4 services out of the full spec. Bundling them would mean every ECU ships with flash-programming capability exposed at the diagnostic layer — that’s a security vulnerability, not a feature.
No — and that separation is intentional, not a sales tactic. Think scalpel, not Swiss Army knife. VxDiag is purpose-built for field diagnostics — no flash memory access. VxBoot is purpose-built for programming sessions — no DTC or calibration context at all.
Giving you both in one binary would be like a hospital handing every nurse a surgeon’s kit. That said, we do offer a bundled license for teams that need both — contact us for details.
VxBoot. OTA firmware updates use the ISO 14229 flash programming sequence — RequestDownload (0x34), TransferData (0x36), RequestTransferExit (0x37) — which is exactly what VxBoot implements. VxDiag has no download pipeline.
If you also need diagnostic access post-update (reading DTCs, calibration), you’ll want both stacks on the same ECU in separate memory regions.