View Full Version : 2006 TrailBlazer Tune?
JustinD
October 2nd, 2009, 07:13 AM
My buddy has an 06 Trailblazer and he asked if I could shut off his TQ managment and make some adjustments so it isn't so much of a sled, I tune my Duramax but have no idea where to start with this Trailblazer. Any help would be appriected. Thanks
ScarabEpic22
October 2nd, 2009, 07:36 AM
Turning off TM will help a little, the spark tables need a little massaging too from what Ive seen. My specialty is the 02-05 I6s, havent had the chance to see an 06+ one yet. Post up his stock tune and Ill make a few adjustments for you, then go see how they work out.
JustinD
October 2nd, 2009, 08:14 AM
Thanks Man, I'll post it this weekend.
JustinD
October 2nd, 2009, 01:45 PM
I tried to read it and keeps giving me a error message can't communicate with V2 flash scan I disconnected and re connected a bunch of times and even restarted the computer. Still get the same message.
Chevy366
October 3rd, 2009, 05:50 AM
Strange , maybe Erik or someone will see this and give some input .
I have to sometimes plug into OBDII port , turn key on then plug into USB on laptop .
Have you just recently upgrade firmware , boot block ?
joecar
October 3rd, 2009, 09:59 AM
Can you post the log text that is displayed...
You may have to disable the countdown timer display.
JustinD
October 7th, 2009, 01:09 PM
Still having same problems, I checked the bootblocker version it is the newest one, and I updated my EFI software to the latest version. I am stumped. Anyone have any idea?
ScarabEpic22
October 7th, 2009, 05:58 PM
So you have V7.5.6 build 99 and V8.1.2 build 75, V2 bootblock 2.06.02 and fw 2.06.16? Hmm, can you follow THIS GUIDE (http://www.efilive.com/index.php?option=com_content&view=article&id=111&Itemid=121) and report the problem to support?
Chevy366
October 8th, 2009, 08:52 AM
Just tried reading a 06 P12 and could not , first attempt went to about 60% , gave interrupt error , second attempt got about 20% , interrupt error , third try got about 90% and crashed the Flash application to desktop .
So it seems the software is not working correctly here either , I did not try slow read , but best I remember that was how I had to do it last time (unchecked fast read) .
Sent the 3 .blx files to support .
ScarabEpic22
October 8th, 2009, 10:44 AM
Hmmm interesting, I dont have a P12 to test it on here but sounds like theres a bug somewhere that popped up.
JustinD
October 14th, 2009, 04:58 AM
Any news on this?
Chevy366
October 14th, 2009, 07:13 AM
Not yet .
Kind of funny the P10s can be read with the new BBR function and they are the same platform , 360 , I have not looked to see if there are any PWMs different on the data bus .
Erik , you do any research into the modules differences between a P10 and P12 ?
I think Erik was going to do a P12 to P10 swap at one time .
But best I remember "SNAIL MODE" is the way to read the P12 , will confirm today I promise .
JustinD
October 14th, 2009, 07:15 AM
Thanks man I appriecate it.
Chevy366
October 14th, 2009, 09:13 AM
Okay , just tried "Snail Mode" , twice , FAILED .
Went to 184k and stopped , will send .blx to support .
JustinD
October 14th, 2009, 11:07 AM
Ok, thanks.
ScarabEpic22
October 15th, 2009, 07:45 PM
Not yet .
Kind of funny the P10s can be read with the new BBR function and they are the same platform , 360 , I have not looked to see if there are any PWMs different on the data bus .
Erik , you do any research into the modules differences between a P10 and P12 ?
I think Erik was going to do a P12 to P10 swap at one time .
But best I remember "SNAIL MODE" is the way to read the P12 , will confirm today I promise .
There are a lot of internal differences between the P10 and P12. Think of a P10 as a 4cyl PCM from 99-02 that can run the exhaust VVT on the LL8 and the P12 as an E40 with trans support. Heck the P12 and E40 use the same bench harness wiring...
Ive got a test 03 P10 and 06 P12 sitting in my room right now, biggest issue Ive encountered is finding the PCM connectors already pinned with a pigtail on them for the P12 connectors. I talked to EFI Connection and can get the P12 connectors, pins, and wire but its not cheap. $45 for the connectors, $.50 ea for pins (need about 120-125 of them!), wire probably 1ft per pin (so like 120-125ft) at $.30 or something. And I dont have the proper crimping tool as I hear the PCM pins are finicky. So I have it partially ready but not sure I want to drop another $200-300 into a project I dont even know will work especially since no one is really interested in BOOSTING their 02-05 I6. 06-09 I6s using the P12 and E67 can do it already but no one has looked at them, bummer.
BTW its a P10 to P12 swap, not P12 to P10. Yes EFILive has more P10 tables but the P12 is a much more capable controller.
Chevy366
October 16th, 2009, 05:04 AM
Still have not heard from support on the issue , must have confused them . :grin:
Erik , I figured there was some internal differences between the PCMs , but what are the differences in the data buses on the 360 platform ?
It seems from what support is saying and the error , there is a interruption from a communication on the data bus , was just wondering if the data bus communication (same modules) on the P10 is the same as the P12 , how many and if there are any differences in the modules on the chassis . If the P12 is close to the E40 and the E40 works in fast/slow read mode why not the P12 ?
Yes , I meant P10 to P12 .
ScarabEpic22
October 16th, 2009, 09:45 AM
There arent any databus differences between the 02-05 and 06+ ones AFAIK. 06+ are CAN compliant however, this is why the E67 is used for the 07-09 GMT360 V8s and 08-09 I6s instead of the E38.
Shouldnt be any different modules on the bus, I know the BCM changed part numbers and this is where Im thinking there might be issues... Just because the P12 and E40 are similar doesnt mean they use the same bootloader, OS, or read/write protocol. Even if they do, you have to select P12 or E40 before trying a read (try the E40 on a P12, prob wont work).
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.