CANsole ECUconnect
Firmware that turns an ECUconnect adapter into a remote-controlled diagnostic node.
ECUconnect is CANsole at its smallest and most networked. A small adapter sits in the vehicle, on the bench, or in a CI rig — running the same runtime as Studio and Touch, just without a display.
A runtime node, not just an adapter.
Many adapters are pass-through tunnels — bytes in, bytes out. ECUconnect is something bigger: it can hold simulated ECUs, run scenarios, expose protocol services, and identify itself stably over time.
Headless ECU simulation
Drop a preset onto the adapter, and it speaks like an ECU on the bus. Useful for restbus simulation, gateway emulation, or unattended bench setups.
Remote diagnostic bridge
Expose the bus over TCP/UDP services. A diagnostic client far away from the vehicle can drive the same workflows as if it were plugged in.
Stable adapter identity
Every node carries a stable identity for automation. You can address the same bench rig from CI runs across days and weeks without reconfiguration.
Reproducible automation
Pair an adapter with a preset, and you have a test fixture. Run the same diagnostic sequence on every commit and watch for regressions.
Compact form factor
Small enough to live behind the dash of a vehicle or zip-tied to a test rig. No display, no input, no excess — just the node and the wire.
Studio-driven
Configure presets, monitor traffic and pull logs from Studio over the network. The adapter doesn’t need a UI — Studio is the UI.
In the vehicle. On the rig. In CI.
In the vehicle
Plug into OBD-II and tunnel diagnostics over Wi-Fi to a developer somewhere else. Or run a simulated module on the parallel bus to test gateway behavior.
On the bench
Provide a stable, identifiable diagnostic node next to the unit-under-test. Multiple ECUconnect nodes can share a bench setup with deterministic addressing.
In CI
Hardware-in-the-loop done right. The runtime is the same as on the desktop — so passing a CI test on ECUconnect means something for production.