Problem:
I managed to resolve an annoying communication error (99.58642.0) that I have been experiencing for a while when trying to scan certain vehicle models using XENTRY Pass Thru 23.6.3 with my Tactrix Openport 2.0 and GODIAG GD101 PassThru devices. E.g. my A45 AMG W176 would always throw Communication Error 99.58642.0 when trying to scan it.
If you have DTS9 installed on the same machine as XENTRY Pass Thru and
have also imported the 'PassThruSupport' regkeys that have been provided
on mhhauto and elsewhere so that DTS9 can recognise your PassThru VCI,
then that is the cause of the this XENTRY Pass Thru communication error.
The DTS9 PassThru VCI regkeys floating around on here and elsewhere are
basically just
exports from "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\PassThruSupport.04.04"
and then re-imported
to "HKEY_LOCAL_MACHINE\SOFTWARE\PassThruSupport.04.04" which allows DTS9
to recognise the PassThru VCI so it can be added as a VCI within the
DTS9 settings.
The problem with these copied keys is that they seem to conflict with
each other due to having the same key names (for some weird reason),
regardless of them being in different registry locations.
Solution:
They were the cause of my XENTRY Pass Thru Communication Error 99.58642.0, and here is what I did to fix it:
1. Open Regedit and navigate
to "HKEY_LOCAL_MACHINE\SOFTWARE\PassThruSupport.04.04" and you will
notice your PassThru VCI name as one of its subkeys. This is the
location that DTS9 looks at when identifying PassThru devices.
2. Rename your PassThru VCI subkey. E.g. I renamed 'Tactrix Inc. -
OpenPort 2.0 J2534 ISO/CAN/VPW/PWM' to 'Tactrix Inc. DTS - OpenPort 2.0
J2534 ISO/CAN/VPW/PWM'. You do not need to rename anything that sits
under this subkey.
Doing this for each PassThru VCI that I use with both DTS9 and XENTRY
Pass Thru has resolved the Communication Error 99.58642.0 that I was
getting when trying to scan some models using my PassThru devices
with XENTRY Pass Thru 23.6.3.
I replicated this conflict by re-adding the DTS9 PassThru regkeys shared
on here and elsewhere and the error re-appeared, then manually renamed
them again (as above) and the error vanished.
Hope this helps someone.
Free download
