The directory where the app installed includes a copy of the CAN_USB.dll file and the registry key for the CommTool app points to this version of the dll as shown in the attachment "enerdel_commtool_registry_pcan_usb_dll".
The app creation date is April 25, 2011 and the dll creation date is December 18, 2009. The app requires a version of .net Framework. My system has versions 2.0, 3.0, and 3.5 installed. During the app installation process, the installer said it would check for the appropriate version of .net framework and install it if necessary. The installer didn't appear to find issue with the versions I had installed already.
I've also run the Peak dll installer PeakPemDrv.exe besides copying the PCAN_USB.dll version 22.214.171.124 (the one from the app directory) to both the C:\Windows\System32 and C:\Windows\SysWOW64 directories.
I also tried the Windows compatibility tool to find out if I should run the app as if it was launching in an earlier version of Windows. The compatibility tool tried to set up for Windows 7, but the app still didn't find the CAN to USB device correctly and gave the same dll errors.
I'm out of ideas at this point. What am I missing?
(picture resized to 75% by Forum Admin)
- 2.JPG (98.38 KiB) Viewed 1626 times
- 1.JPG (209.1 KiB) Viewed 1626 times
download the PCAN-Light Package from here: PCAN-Ligh latest Version.
Now follow this rule / read this threads: Link1 and Link2
On a 64Bit OS please copy:
32bit DLLs > Windows\syswow64
64bit DLLs > Windows\system32
Yes it is true - the 32 Bit DLL need to be placed in the syswow64 Directory. (not our rules - ask MS)
This should solve your probblem - if not we need to get a copy of the Tool to check in our office what´s the problem.(we do not know or own this Software "Enerdel CommTool")
Technical Support Team
The first was the location and age of the dll. I followed your instructions first deleting every copy of pcan_usb.dll on the system.
The second problem was the app itself, which creates a shortcut during the installation process. When I tried to start the app from the shortcut, it tried to run the installation process again. It must have noticed that I deleted the ancient version of pcan_usb.dll from the installation directory. I didn't allow it to proceed and instead started the app directly from the install directory by double clicking the CommTool.exe file. At this point, the Peak USB to CAN bridge device led started blinking and no more dll complaints from the app. I was then able to connect to the CAN interface in my car and trace CAN traffic with the app.
I was also able to fix the shortcut eventually so that it doesn't try to launch the installer by creating a new shortcut for the app and then replacing the old with the new and renaming it so that it shows up in the installed programs menu.
thanks for your help!