logger_tested_devices
Tested J2534 devices
| Device | Comment | Muxer Parallel HW | Muxer Parallel SW |
|---|---|---|---|
| Tactrix OpenPort 2.0 | Full speed, needs Tactrix J2534 Drivers | Not supported | Stable |
| MongoosePro 1/2/JLR | Full speed | Unknown | Unknown |
| Autel MaxiFlash | Full speed | Unknown | Unknown |
| EVC UCM100 | Full speed, use latest version!, enables tracing in WinOLS | Stable, slow | Not supported |
| PeaK PCAN-USB | Very high CPU usage, no K-Line (use through Muxer) | Stable, high CPU | Stable |
| Scanmatik 2 Pro | Full speed | Stable | Stable |
| Setek VIDA DiCE | Full speed | Unknown | Unknown |
| Kvaser J2534 | Not working, buggy J2534 DLL | Not supported | Not supported |
| Chipsoft J2534 Pro | Full speed, some issues with K-Line. VAG C167 protocol not possible on older ECU's | Not supported | Stable, slow |
| Dialink J2534 | Full speed | Stable | Not supported |
| Godiag GD101 | Not working - connection only through Muxer (see below) | Not supported | Unknown |
It is recommended to use a Parallel capable device if you wish to log multiple ECU's simultaneously using the Muxer.
If you have an unlisted interface and it does not seem to establish a reliable connection on CAN, you can try to use the Muxer in “Parallel SW” mode. This way the the ISO-TP stack runs in the Muxer, and the device only has to handle the transmission and reception of raw CAN frames. It has worked for certain Chinese no-name devices.