Skip to content

DriverBridge ​

DriverBridge is a companion application for 32-bit J2534 drivers, including use from 64-bit Protohaund. It is included in the J2534 package and supports CAN adapter connections in CANopen and VAG modules. It is not needed for a normal Modbus RTU serial connection.

Setup ​

  1. Install the adapter manufacturer's J2534 driver.
  2. Install J2534 in Settings → Packages and restart when prompted.
  3. Open Settings → Connections → Driver Bridge.
  4. Click Start, then Refresh if needed. Check the Adapters list.
  5. In Connections → Transport, select J2534, the adapter and CAN speed.

The Driver Bridge page appears when the component is available. The adapter list shows the device, library, driver state, and physical and logical connection states. An empty list means the bridge reported no available 32-bit adapters. A running bridge alone does not confirm that the physical device is connected.

Supported modes and observation limits are described under J2534.

Bridge controls ​

ControlPurpose
StartStart the bridge
RestartRestart the bridge
StopStop the bridge and disable its automatic startup setting
RefreshRefresh status and adapter information
StateCurrent bridge state
PID / Track IDIdentify the process and correlate technical logs

Stopping or restarting affects connections through the bridge. Finish using the adapter before these actions.

Startup options ​

OptionBehavior
Start automaticallyStart with the application if the bridge was used in the previous session
Restart policyRestart on failure permits recovery after an unexpected exit; Disabled disables it
Runtime modeInteractive opens a window; Headless runs without a window
Use legacy presence probeOpen and close a device to detect its presence when the driver cannot enumerate devices

Use legacy presence probe calls the driver. If discovery is slow or problematic for an adapter, disable it and check again. No window does not mean the bridge has stopped: use State to check its status.

Protohaund is independent software and is not affiliated with, endorsed by, sponsored by, or certified by any third-party organization referenced in the application.Third-party names, trademarks, product names, device names, protocol names, and standards are referenced solely to identify vehicle applicability, supported products, technologies, protocols, formats, or compatibility.All third-party trademarks and other marks are the property of their respective owners. Their use does not imply any affiliation with, endorsement of, certification of, or approval of Protohaund by their respective owners.Compatibility is limited to the features, devices, protocols, standards, and versions explicitly documented by Protohaund.