pcmhacking.net

@BoominSVX Thanks for the post, and good luck on the XDF. You should be able to compare some other GM bins of the same era and look for similar patterns and similar order in things to locate tables. Its a big job, but it is possible!
@megajuz3003 Tazzi spotted a timing issue in the J2534 driver (it was waiting 6 seconds for modules to respond, not 2 or less like other devices, and the bus was reverting to 1x). Ive pushed up a fix (tx and rx timers both to 2 seconds in the J driver, and its working on the bench for me now. We'll release an update shortly that will work for you.

antus wrote: @megajuz3003 Tazzi spotted a timing issue in the J2534 driver (it was waiting 6 seconds for modules to respond, not 2 or less like other devices, and the bus was reverting to 1x). Ive pushed up a fix (tx and rx timers both to 2 seconds in the J driver, and its working on the bench for me now. We'll release an update shortly that will work for you.

Awesome. Thanks for that... I did have a look through some of the code last night and you guys have done amazing work. If my code was half a good I’d be a happy guy


EDIT:

just made the suggestions you mentioned earlier.. I seemed to get further on a read but still no go.. mild heart attack later had to pull the ecu fuse for a little while to get the car started


i might just wait untill the new update gets released

Looks like you might have deleted a bit out of the coding? I dont see a request to go to high speed or programming mode ect in that log.

my original suggestion was to disable 4x so it got around that but didnt fix the 6 second timeout. Use the release-002 branch now which is the same as the last release but with the fix, or use the develop branch if you want the absolute latest, but beware thats a work in progress and your results will (probably) vary each time you download again. https://github.com/LegacyNsfw/PcmHacks/tree/Release/002

I just uploaded a .zip file of the new release here:

https://github.com/LegacyNsfw/PcmHacks/ ... F12%2F08.1

This should fix the issues with J2534 tools. If you have one, please give it a try and let us know how it goes.

Sorry for if this has been covered but I read through others info & looks like they have been able to successfully use with ELM?
I can't get it to connect with PCM Hammer, but have another program I can use elm with & connects fine like this...
[10:44:08:522] Testing Comport: COM9 at Baudrate: 38400
[10:44:08:725] ELM Device Successfully Found!
[10:44:08:787] Requesting Fast 115200 Baud..
[10:44:08:803] ELM Device Accepted Baud Change Command, Checking Communications..
[10:44:08:881] ELM Device Sent ID frame..Responing with CR
[10:44:08:881] ELM Device Accepted Baud Change Command!
[10:44:08:881] Disabling Echo...
[10:44:08:881] Echo Disabled Successfully!
[10:44:08:881] Disabling LineFeed...
[10:44:08:896] LineFeed Disabled Successfully!
[10:44:08:896] Clearing filters...
[10:44:08:896] Filter Cleared
[10:44:08:896] Enabling Headers...
[10:44:08:896] Headers Enabled Successfully!
[10:44:08:896] Allowing Long Frames...
[10:44:08:896] Long Messages Enabled!
[10:44:08:896] Setting Timeout...
[10:44:08:912] Timeout Set Successfully!
[10:44:08:912] Setting VPW Protocol...
[10:44:08:912] Protocol Set Successfully!
[10:44:08:928] Setting VPW Headers...
[10:44:08:943] Custom VPW Headers Set: 6C10F1
[10:44:08:943] Checking Input Voltage..
[10:44:08:943] Voltage Found!
[10:44:08:959] Connection Established!
[10:44:14:746] Setting VPW Headers...
[10:44:14:746] Requesting VIN..
[10:44:14:778] VIN Part1: 6C F1 10 7C 01 00 36 48 38 56 55 E1
[10:44:14:793] VIN Part2: 6C F1 10 7C 02 4B 38 30 46 32 4C 2C
[10:44:14:824] VIN Part3: 6C F1 10 7C 03 39 31 30 39 30 33 38
[10:44:14:824] VIN Read Completed!
[10:44:22:749] Setting VPW Headers...
[10:44:22:749] Setting VPW Headers...
[10:44:22:780] Seed= 67 D5
[10:44:22:780] Trying Key: 0xBDE6
[10:44:22:812] Key is Correct: BDE6
[10:44:22:890] Vin Part 1 written successfully..
[10:44:23:046] Vin Part 2 written successfully..
[10:44:23:139] Vin Part 3 written successfully..
[10:44:23:139] Vin Successfully changed to: 6H8VUK80F2L910903
[10:44:25:011] Setting VPW Headers...
[10:44:25:011] Requesting Serial..
[10:44:25:027] Serial Part1: 6C F1 10 7C 05 32 45 42 33 0E
[10:44:25:058] Serial Part2: 6C F1 10 7C 06 42 45 51 33 2B
[10:44:25:089] Serial Part3: 6C F1 10 7C 07 32 31 37 39 0C
[10:44:25:089] Serial Read Completed!

VX L67 Getrag wrote:Sorry for if this has been covered but I read through others info & looks like they have been able to successfully use with ELM?
I can't get it to connect with PCM Hammer, but have another program I can use elm with & connects fine like this...

Make sure your using a SX or MX from scantool.net with PCM Hammer. They support a big buffer for reading/writing to the LS1 ECUs

Elms are hit and miss, and will probably never be able to read and write. There are just too many different devices to try and I dont think there is much point trying to get the support correct for vin change. The scantool device and the allpro have a more standard programming interface and are much more capable, and thus are what we are testing and reading/writing (in development) with.

Ahh cool thanks for the replies, I just thought as it was working with other software it may be capable.
I had a look at scantool.net & looks like the SX is out of stock & MX is too expensive for 1 time customers, I'll see if they can get the allpro usb adapter as I think they were only $35.

allpro is good, and the cheapest. scantool mx are best from ebay, if you can handle the wait from china and want a good price try: https://www.ebay.com.au/itm/OBDLink-SX- ... 3222662871
I didnt get mine from that vendor. They say their legit but I cant vouch for them.

Actually, maybe use a J2534 device. I expect you'd have an MDI?