1Jan

J2534 Driver Download

1 Jan 2000admin

Autel J2534 driver installation instruction: - used for Autel ms908p, maxisys Elite, J2534 box - download and install Maxisys j2534 Drivers and Printing Software The PC drivers for the Autel j2534 and PC Link for wireless printing are included in the MaxiSys software suite available for download at: English Spanish. Autel ms908p, ms908 Elite, J2534 box Maxisys j2534 Drivers and Printing Software; The PC drivers for the Autel j2534 and PC Link for wireless printing are included in the MaxiSys software suite available for download at.

I bought a cheap Chinese Mini VCI J2534 cable for diagnostics and auto settings.

Depending on what version of windows you are on, you may need to separately install the WinUSB driver (see next section).

Installation automatically happens for Windows 8 and Windows 10 because the pandafirmware contains the USB descriptors necessary to auto-install the WinUSB driver.

Windows 7 will not auto-install the WinUSB driver. You can use Zadig to installthe WinUSB driver. This software is not tested on anything before 7.

More details here:WinUSB (Winusb.sys) InstallationWCID DevicesZadig for installing libusb compatible driver

After installing the J2534 drivers for the panda, you can do.. nothing.You first need to get a J2534 client that can load the drivers and talk tothe panda for you.

A simple tool for testing J2534 drivers is DrewTech's 'J2534-1 Bus AnalysisTool' available in the 'Other Support Applications' section of theirDownload Page.

J2534 is an API that tries to provide a consistent way to send/receivemessages over the many different protocols supported by the OBD IIport. The place this is perhaps most obvious, is sending data overdifferent protocols (each using unique packetizing methods) using thesame data format.

For each PassThru Device that should be used with J2534 (in this case,the panda), a 'driver' has to be written that can be loaded by aclient application wanting to send/receive data.

A lot of J2534 has good ideas behind it, but the standard has some odd choices:

  • Platform Locked: Requires using the Windows Registry to find installed J2534 libraries/drivers. Drivers have to be DLLs.
  • Architecture Locked: So far there is only support for x86.
  • No device autodetect, and poor support for selecting from multiple devices.
  • Constant vague language about important behavior (small differences between vendors).
  • Most common differences become standard in later revisions.

J2534 is the only interface supported by most professional gradevehicle diagnostics systems (such as HDS). These tools are useful fordiagnosing vehicles, as well as reverse engineering some lesser knownfeatures.

  • J1850VPW(Outdated, and not physically supported by the panda)
  • J1850PWM(Outdated, and not physically supported by the panda)
  • CAN
  • ISO15765
  • ISO9141(This protocol could be implemented if 5 BAUD init support is added to the panda.)
  • ISO14230/KWP2000(Could be supported with FAST init, 5baud init if panda adds support for 5bps serial)

This project is developed with Visual Studio 2017, the Windows SDK,and the Windows Driver Kit (WDK).

The WDK is only required for creating the signed WinUSB inf file. TheWDK may also provide the headers for WinUSB.

To build all the projects required for the installer, in VisualStudio, select Build->Batch Build. In the project list select:

  • 'panda'Release x86
  • 'panda'Release x64
  • 'panda Driver Package' Debug x86 (Note this inf file works with x86/amd64).
  • 'pandaJ2534DLL'Release x86

The installer is generated with NullSoft NSIS.Use NSIS to run panda_install.nsi after building all the required projects.

Before generating the installer, you must go to copy vscruntimeinfo.nsh.sample tovscruntimeinfo.nsh and follow the instructions to bundle in the Visual Studio CRuntime required by your version of Visual Studio. Without this runtime, the pandacode will not work, so without this file, the installer will refuse to build.

  • Edit and merge pandaJ2534DLLJ2534register_x64.reg to register your development J2534 DLL.
  • Add your output directory (pandadriverswindowsDebug_x86) to your system PATH to avoid insanity.
  • Apply a style-guide and consistent naming convention for Classes/Functions/Variables.
  • Send multiple messages (each with a different address) from a given connection at the same time.
  • Implement ISO14230/KWP2000 FAST (LIN communication is already supported with the raw panda USB driver).
  • Find more documentation about SW_CAN_PS (Single Wire CAN, aka GMLAN).
  • Find example of client using a _PS version of a protocol (PS is pin select, and may support using different CAN buses).

  • ISO15765 Multi-frame TX: Hardware delays make transmission overshootSTMIN by several milliseconds. This does not violate the requirementsof STMIN, it just means it is a little slower than it could be.

  • All Tx messages from a single Connection are serialized. Ibm netvista 6269 drivers for mac. Rock guard for 1967 aloha 13'. This can berelaxed to allow serialization of messages based on their address(making multiple queues, effectively one queue per address).

troubleshooting:

  1. Install DrewTech J2534-1 Bus Analysis Toolhttp://www.drewtech.com/downloads/tools/Drew%20Technologies%20Tool%20for%20J2534-1%20API%20v1.07.msi
  2. Open DrewTech tool and make sure it shows 'panda' as a device listed (this means registry settings are correct)
  3. When DrewTech tool attempts to load the driver it will show an error if it fails
  4. To figure out why the driver fails to load install Process Monitor and filter by the appropriate process namehttps://docs.microsoft.com/en-us/sysinternals/downloads/procmon

Panda head ASCII art by dcau