MASTER
Your tool connects to the CAN port of the Master device.
iProgK‑TAGPCMFlashLaunch X431
Direct CAN-to-CAN
Your vehicle's CAN bus.
Your vehicle's CAN bus.
Available remotely.
OBD‑LAN joins two physical CAN buses over the internet into one logical bus. Connect diagnostic and programming equipment as if the vehicle or ECU were right beside you.
Raw CANNo J2534 or virtual DLLs
2 × CAN FDIsolated channels
E2EEncrypted session
Live connection
● CHANNEL READYEngineer ↔ OBD‑LAN ↔ Vehicle
P2P · EncryptedBidirectional CAN frames
SLAVE
Connects to the vehicle's OBD‑II port or directly to an ECU on the bench.
OBD‑IIBenchCAN / CAN FD
Three steps to remote CAN access
No port forwarding or complex network setup. Both devices establish outbound connections automatically.
01
Connect Slave to the vehicle
The client connects Slave to OBD‑II or the ECU CAN pins, powers it on and receives a session code.
02
Enter the code on Master
The engineer enters the code. The server securely links both ends of the CAN bridge.
03
Start working
The diagnostic tool or programmer sees the remote CAN bus as a local physical connection.
One specialised mode
Raw CAN Bridge. Nothing extra.
Designed for equipment that communicates directly over CAN and does not require a virtual J2534 driver.
- Remote diagnostics with a physical tool
- ECU bench connection over CAN
- Coding and service functions
- Electronic control unit bench testing
- Two independent CAN / CAN FD channels
For Boot/Bench programming, power, IGN, BOOT and other signals are connected locally according to the ECU wiring diagram. OBD‑LAN carries CAN traffic and does not replace the correct bench cable.
iProgCAN functions and bench work
K‑TAGCAN bench scenarios
PCMFlashCompatible module operation
Launch X431Remote diagnostics
Bench ECUsDevelopment and testing
Other CAN toolsTransparent frame transfer
Ready to test OBD‑LAN?
Request early access to the Raw CAN Bridge system.