PowerPCM_Flasher: my tool for E38 and E67

[clyde]

I got the exe from this post (PowerPCM_Flasher_0006) and the J2534 drivers from the OBDXPro website.

[ironduke]

sorry.. I meant the brute force tool..
Power PCM works for me with the gm mdi but I do know a lot of other devices do not work with it. Developer was great for putting it here, guessing he did what he needed with it and has not been here in quite awhile and I don't think there will be any compatibility updates for other tools unless he releases the source code public or even to a programmer here to attempt to keep it in house.

[clyde]

NP, It's ECU.BruteForcer.0.0.8.7z that you posed a while back.
I'll reach out to some friends and see if anyone has a gm mdi I can test with.

[ironduke]

NP, It's ECU.BruteForcer.0.0.8.7z that you posed a while back.
I'll reach out to some friends and see if anyone has a gm mdi I can test with.

ok, I had forgotten I posted an .exe here.. you'll need to install a .net for the brute force to work.. I do not think you need it for the powerpcm program to work..

[Tazzi]

I'm new to this and I'm trying to connect to an e38 (actually two) with no success.
OBDXPro VX (updated to latest firmware and J2534 driver installed)
Bench harness with 12.6v PS
I can connect and read the VIN with OBDXplorer but I'm getting same types of errors with both e38s and two different Win10 computers.
--
initialising Tool J2534 PassThru
OBDX Pro - VX...
ok.
connecting...
start diagnostic session (0x10 0x03)...ok.
disable normal communication (0x28)...ok.
security access (0x27)...
request seed...NOT ok, no valid seed received.
Wait 30s after power on or failed attempt.
connecting...
start diagnostic session (0x10 0x03)...ok.
disable normal communication (0x28)...ok.
security access (0x27)...
request seed...ok.
seed: 0x00000D30
key: 0x00009BD2
sending key...not ok, key wrong?

Any thoughts?

You would need to activate the J2534 logging for the VX so i can see the commands being sent and make sure its meeting the J2534 compliancy.
Iv had quite a few small developers incorrectly use some J2534 commands which a different J2534 tool may work with.