antus wrote:Efilive v7.5.x in trial mode will open bin files and tell you about the contents, but it will not save back to bin format. Its a good tool for testing and learning about reads and while those reading this thread probably are not looking for a tool from one of the big players - if you did want something more capable and with support for many more and newer types of pcms i'd recommend efilive as a company who have a good attitude and dont rip their customers off like some big players.
thank you SIR.
I'm happy to have stumbled into this community.
I'll be adding more bin files in the coming weeks, now that I have the bench harness and cables in hand.
(Is this the correct forum to upload the bins?)
Have had a look at the LQ4 bin posted, attached XDF shows the VIN and calibration partnumbers in the ECU.
The PDF is from TIS2WEB, I entered the VIN found in the bin file.
You do not have the required permissions to view the files attached to this post.
cars: 83 Ford Ranger, a friend's 91 Mustang that I'll be ls swapping with him (more like for him) and my daily driver 03 Silverado 2500hd rust bucket, lastly an lm7, lq4, and ly6 on stands
To update y'all, I purchased an Obdlink SX to try and maybe rule out the interface. It worked! the used pcm is not bad but damn the sx is slooooowwwwwww lol.
quick little breakdown of what did/didn't work:
(0411 w/12208322 os)
Pcm Hammer v4/5 w/mdi2 failed to read full contents (see earlier post for debug)
" " " " flash successful (w/bin & xdf found online)
GM SPS w/mdi2 flash successful (oem calibration)
Pcm Hammer v5 w/SX read full contents successfull (both attempts home and work)
have not tried a flash w/the SX tool yet (the read took at least a 1/2hr)
Hope this helps! Thanks again for all the hard work!
To update y'all, I purchased an Obdlink SX to try and maybe rule out the interface. It worked! the used pcm is not bad but damn the sx is slooooowwwwwww lol.
quick little breakdown of what did/didn't work:
(0411 w/12208322 os)
Pcm Hammer v4/5 w/mdi2 failed to read full contents (see earlier post for debug)
" " " " flash successful (w/bin & xdf found online)
GM SPS w/mdi2 flash successful (oem calibration)
Pcm Hammer v5 w/SX read full contents successfull (both attempts home and work)
have not tried a flash w/the SX tool yet (the read took at least a 1/2hr)
Hope this helps! Thanks again for all the hard work!
Tried finding your log with the MDI2 for reading but dont see it posted?? Can you post it again?
Your Local Aussie Reverse Engineer
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
cars: 83 Ford Ranger, a friend's 91 Mustang that I'll be ls swapping with him (more like for him) and my daily driver 03 Silverado 2500hd rust bucket, lastly an lm7, lq4, and ly6 on stands
As far as I can see.. the MDI2 is failing to receive a large frame back! Weird!
It attempts to request the first block from the ECM, and gets no response, on the second reattempt, it does receive a response by its extremely short.
Im wondering if the MDI2 is not very good for large VPW packets maybe? Will need to edit the packet size and see if it works at smaller ones first.. and go from there.
Your Local Aussie Reverse Engineer
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
Small correction: The kernel's 2k limit is for writing, not reading. Pete was able to read packets over 10k using a DVI prototype.
That said, this particular device might have a sub-4k maximum packet size, so it's definitely worth trying with 2k or even 1k if that's what it takes.
Right now the app assumes that any J2534 device can handle 4k packets, but that might not be a safe assumption.
Please don't PM me with technical questions - start a thread instead, and send me a link to it. That way I can answer in public, and help other people who have the same question. Thanks!
May need to put some more debug messages for the J status code when reading out messages... may give some clues to whats happening. For all we know, its a bug in the current MDI2 firmware.
Whens the last time it was used with something like SPS for updating a vehicle? Have you let SPS update to the latest MDI manager, and then let the manager install latest firmware?
Your Local Aussie Reverse Engineer
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
but damn the sx is slooooowwwwwww lol.
