Hammer not reading ECU
Re: Hammer not reading ECU
You have communication issues with pcm. Investigate that first.
Test connection with universal patcher and see if you can datalog.
Test connection with universal patcher and see if you can datalog.
Re: Hammer not reading ECU
Finally had a chance to look again. Have tested the bench harness and all ok. Have tested the datalogging as you suggested and seemed to connect ok. As soon as i try to read pcm it doesn't read it. Have got OBDX Pro GT adaptor. Downloaded and installed everything again but nothing fixed it. Have tried this on another pcm and same thing. The power light on the OBDx is on red. The OBD light is flashing green and the middle one is off. I have a benchtop 20 amp power supply set at 12.8 volts and pulling 410ma with pcm on. I have it wired as per attachment
- antus
- Site Admin
- Posts: 8261
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: Hammer not reading ECU
Are you using obdxpro native support? The J2534 option on it doesnt work properly with pcmhammer, the native option as a com port does.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
Re: Hammer not reading ECU
I have tried everything. I can only assume that their is something wrong with the pro GT as it just won't connect at all where i did have it connecting last time i had looked at it a few months ago. Will see if i can find another cable for it but everything else checks out. Don't know if uninstalling and reinstalling everything will achieve anything except wasting more of my time
Re: Hammer not reading ECU
It is possible gt is not supported with pcmhammer, try some older version of hammer.
You can also try running this script in universal patcher to confirm gt is good-> logger->
select device->connect->vpwconsole tab->check print to screen->upload script button->select attached file and wait till script stops running
You can also try running this script in universal patcher to confirm gt is good-> logger->
select device->connect->vpwconsole tab->check print to screen->upload script button->select attached file and wait till script stops running
- Attachments
-
- P01_read_1000_x4_v1_512kb.txt
- (4.13 KiB) Downloaded 49 times
- antus
- Site Admin
- Posts: 8261
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: Hammer not reading ECU
No its not possible GT is not supported. The OBD X Pro guys maintain the code in the app. The only gotcha is the need to use native support, not J2534. @Tazzi if you want to update the J2534 support in the tool or drivers so both modes work, please do.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
Re: Hammer not reading ECU
I’ll look into it tomorrow
Technically the way masking being done in pcmhammer is outside the SAE spec but it doesn’t appear to affect any dealership software so I’ll add the fix.
Your Local Aussie Reverse Engineer
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
-
- Posts: 52
- Joined: Thu Feb 07, 2013 1:49 pm
- cars: 2002 Camaro
2008 Pontiac G8
Re: Hammer not reading ECU
Why get into pcmhammer operating outta SAE but works. Just say yeah I’ll fix it….
Re: Hammer not reading ECU
I have tried both and using the serial i get the message " unable to connect to serial com 4"
- antus
- Site Admin
- Posts: 8261
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: Hammer not reading ECU
I'd be happy to fix anything to be within spec. The whole J2534 part of the app was donated by Envyous, and there is a DLL blob we don't have source to. If the application interface needs to be changed on the C# side, we should look at it. Going outside of spec only creates more problems down the track. Best option, also the most work, would be to remove the dll blob completely and move to the J2534dotnet library, like Universal Patcher uses. UP uses a lot of code from hammer for device drivers in the logger, so it should be kinda similar. I am not sure exactly what that'd take, though. I did look at the code in UP 6 months ago and it was different enough in the comms layer that it'd take a decent session to think about the impact, not just cut n paste updated code back in. The code is in here https://github.com/joukoy/UniversalPatc ... er/Devices
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396