awesome!
awesome!
'86 Grand National
Has anyone with a avt cable other than eaglemark had a chance to try it? Its the same cable as tunercat uses for obd2 and I think there are a number of them around, but more in the USA than Australia. I expect it to be widely compatible but am looking forward to hearing how people go with it.
I tried it with the newer style Tunercat Can unit (AVT 852) and read out the .bin and then just to try it out, I changed the VIN in the PCM. The VIN change seemed to be instantaneous which surprised me. It worked PERFECTLY. Can the Seed/Key be displayed like the VIN and PCM serial number are? I think that would be a neat feature.
Jeff
98 GMC RCSB, 5.0, 4L80e, Moser M60, 4.10 gear, Homemade twin turbo w/Junkyard T3 turbos, 24x CNP, 12200411 PCM.
Good to hear :) The key is logged if you scroll back in the info window a couple of lines. I can add the seed if its useful.
98 GMC RCSB, 5.0, 4L80e, Moser M60, 4.10 gear, Homemade twin turbo w/Junkyard T3 turbos, 24x CNP, 12200411 PCM.
Yeah not there, after you hit read its in the detail log box down the bottom, but scrolls out of view. Ill update the interface in the next version.
Why??
LS1Flash-free.exe
Threat Name: Trojan.Gen.MBT
Norton AntiVirus?
I had a little free time the other day - so I gave it a go. I selected four 512KB PCMs from inventory - two with Service Number 09354896 (one with a 1999 OS, the other with a 2000 OS), and two with Service Number 12200411 (one with a 2001 OS, the other with a 2002 OS).
Each PCM was read with: PCMHacking.net software, TunerCat, HP Tuners, and EFILive (twice - once with V7.5 software, once with V8 software).
The PCMHacking.net software had very respectable read times (see attached PDF chart), and saved a *bin which was readable by the other softwares - therefore in no way corrupt.
The only minor issues (which are more aesthetic in nature than functional) were that the PCMHacking.net software identified all of the PCMs as being 12200411 variants, and indicated that all of the PCMs were locked (which technically they are, by the OEM - however most tuning software with this parameter use it to indicate a tuner lock / custom lock of some sort).
Awesome work Antus !
Attached is a PDF chart of areas I examined, and the results between the various software.
I still have my original serial tunercat cable,I'll download and bench test a few pcm's from the shelf as well and try it out.Game changer for the licensing scammers imo.
Between TP and tiny tuner that should cover the LS and V6 market for tuning without license's at least up till 2004ish?
Now just need some more definition/ADX files onhand.
With all the "spare" time I could spend in front of a computer I wish I could figure out how to make the def/adx files myself to help out.
Will this software make attempts to communicate with GM PCM's that are not distributed through GM North America?
79 Jeep Cherokee, AMC 401, T-18 manual trans, hydroboost, 16197427 MPFI system---the toy
93 Jeep YJ Wrangler, 4.0L, 5 speed, 8.8 rear, homebrew hub conversion and big brakes, hydroboost, 2.5in OME lift, 31x10.50's---the daily driver
99 Jeep WJ Grand Cherokee limited, 4.0L, auto, 2wd, leather and power everything, 99% stock---the long distance highway ride.
Buzz: thanks for the detailed level of testing, much appreciated. I dont think there is a way to get the pcm service number from the pcm, so to properly identify a 9354896 pcm I will need to create a list of OEM service numbers to OSID. The actual pcms arnt any different, and the operating systems are interchangeable. Especially as I start supporting 1mb pcms I'll need to do this.
1project2many: It will attempt to communicate with any VPW pcm. There is nothing different about the 12200411 and 9354896 pcms distributed in different parts of the world, and I am in australia developing against aussie vehicles. Even unsupported VPW pcms should display info, and depending how similar to the '0411 they are they might read or might not. I have been advised that LB7 duramax OSID 15189044 and 3904405 DO read. Possibly others but I will need OSIDs to whitelist them. This was just a fluke though, I dont have intention to support write on those yet as I have never even seen one. Maybe one day, though.
Agreed ... EFILive and HPT don't list the PCM Service Number for this very reason. TC does, but via an extensive look up table - which is linked to the OS used, but not to any hardware detected - a 2002 OS flashed into a 09354896 PCM will be inaccurately displayed as a 12200411 PCM.
My 2 cents ... simply remove this displayed parameter from your software (like EFILive and HPT have opted to do).
Bookmarks