2010 Cadillac CTS 3.6L DI Tuning

[Cougar281]

Is the 2010 CTS 3.6DI supported or isn't it? In the 'Supported vehicles' list on the website, you guys list the 2010-2013 CTS 3.6L as being an E39 or E39A, and the 08-09 being the E69. Apparently either that's not correct, or the auto detect functionality is busted. Not sure what the answer really is, but I guess either you guys have the cutoff years wrong, or GM did something other than what they said. According to the auto detect functionality, it's actually an E69, and this car was built in 6/2010, meaning it's just short of being a 2011, so it's not like it was a first run of 2010's that got some of the leftover parts from 2009.

Any thoughts? Assuming it IS actually an E69, Since the LML went from 'we're not doing ANYTHING EVER' to 'We now support FLASHING but not reading or tuning' to 'We now support Flashing and Tuning' (Tuning may still be in beta; I haven't really been following it), I have at least a LITTLE hope that at some point the E69 might be fully supported.

[GMPX]

Pretty sure the Auto detect is working fine, it really can't ever get it wrong, it either identifies the ECM using specific commands for each ECM type.
So back to your question, I have Cadillac CTS V6 reads from 2010 models using an E39 ECM, I suspect it might be a case of a transitional period as they changed motors, maybe different models came with different engines? I can't offer you any more than that, walk in to a Cadillac dealer plug in to numerous 2010 CTS's and you'll get a mix of E39 & E69.

I really, really doubt we will ever support these, being Bosch I thought they would be odd, but they are beyond that and I'll be totally honest and tell you I have no motivation to put myself through the pain of learning the ins and outs of that ECM. We offer read and flash support because there is several tuners who do their own tuning (in Hex?) on these ECM's.

Cheers,
Ross

[Cougar281]

Very strange... I could see it having the older ECM if it was an early run, like August/September 2009, but being June 2010, you'd think the transition would be gone.

As far as I can tell, the only engine options on the CTS were the 3.0, 3.6DI and then the 6.2 in the V, so I don't know what their story is. Maybe it has something to do with what plant it was built at?

Would it be a possibility to add an autodetect option in the V2 BB options? I would imagine full autodetect and read probably wouldn't be possible, but something that would simply go out, probe the ECM & TCM and tell you what they were?

[GMPX]

Would it be a possibility to add an autodetect option in the V2 BB options?
The problem with that is each ECM / TCM requires its own read / write bootloader and script, you would need to copy over every read/write script if that was to work because once it finds a match it then needs the specific files for that controller, problem is that would require about 2.5Mb. It's not a bad idea though.

[ScarabEpic22]

FS V3 needs additional internal config space? Heck if you could reallocate all of a V2s internal space to be config that'd be fine with me, Ive read and flashed 1 time without a SD card in the 6/7 years Ive had my V2.

[kangsta]

Have a look at the ECM, it will be really obvious if it is a Bosch or Delphi controller.

[Cougar281]

The problem with that is each ECM / TCM requires its own read / write bootloader and script, you would need to copy over every read/write script if that was to work because once it finds a match it then needs the specific files for that controller, problem is that would require about 2.5Mb. It's not a bad idea though.

Each one would need it's own bootloader just to 'ping' it and return what kind it is?

[GMPX]

No, maybe I misunderstood what you meant. You just want to see the ECM type, not necessarily read it out? To read it out would require a bootloader, to figure out which ECM it is does not. But the recognition is only as good as what information we have, in other words if you walked up to a vehicle that had some obscure ECM then it won't be able to tell you what it is.

[Cougar281]

No, maybe I misunderstood what you meant. You just want to see the ECM type, not necessarily read it out? To read it out would require a bootloader, to figure out which ECM it is does not. But the recognition is only as good as what information we have, in other words if you walked up to a vehicle that had some obscure ECM then it won't be able to tell you what it is.

True, if it's unknown, it would remain unknown, but in the example of this CTS where apparently two different cars of the same year with the same engine could have two different ECMs, it could be handy...

Dont' get me wrong, the idea of auto-read would be neat... Have two lines in the Read menu:

Read ECM/PCM
Read TCM

But like you said, there simply isn't enough config space for that. Would it be possible to allow the config space size to be changed like Scarib mentioned? Maybe make it so it can be changed in the BBX options? Then if the Autoread idea ever did come into existence, it would be possible to have enough space to do it. If the V2 can't be changed in such a fashion, mayve bive the V3 1GB onboard memory? :)

[GMPX]

I don't know, Paul would have to answer that, but I'm betting he will say that he is not about to 'break' the core of V2.

[Cougar281]

Dumb related question..... If some enterprising individual were to map out the E69, could they write a CAX file to make it tunable, or do the CAX files require base tuning support in EFILive to be able to work?

[GMPX]

No, the V7.5 Tune Tool does not understand the E69 file layout..........and probably never will.

[ScarabEpic22]

No, the V7.5 Tune Tool does not understand the E69 file layout..........and probably never will.

So you're saying there's hope in V8 Tune editor?

(Shut it down now Ross... :D)

[GMPX]

My kids accept the answers I give them better than you guys :laugh:

[ScarabEpic22]

My kids accept the answers I give them better than you guys :laugh:

Haha, Id rather have you say BOTH V7.5 and V8 so no one else asks in a year or two.

[Cougar281]

So I just noticed in the 'Resolved Issues' list for the current pre-release '2.E69 tune files no longer report errors when being opened in the V8 software.' and that it does recognize my E69 read... So does this mean that at some point you'll put yourself through the pain of mapping the E69 for the v8 software (If you haven't already)? I know 'the other guys' support it, and you didn't want to go through mapping it, however, to be fair, you guys also said 'WE WILL NEVER EVER SUPPORT THE LML. PERIOD. EVER.'.... Then it went to 'we can flash it but no editing' to 'full tuning support if you can get the base file'. With the LBZ, LMM, LML & E69 all being Bosch, I would think they're all relatively equally insane 'under the hood'...:pokey::grin:

I know you can't comment on what's coming until it's out... Just speculating/hoping - I mean, why would you even bother having the software properly load the tune file if you didn't have some kind of plan to support it?

[GMPX]

So I just noticed in the 'Resolved Issues' list for the current pre-release '2.E69 tune files no longer report errors when being opened in the V8 software.' and that it does recognize my E69 read... So does this mean that at some point you'll put yourself through the pain of mapping the E69 for the v8 software (If you haven't already)?
I can give you this guarantee, I will NEVER spend one minute mapping the Bosch gas ECM's, can't say it any more clearly than that.


I know 'the other guys' support it
And?


I mean, why would you even bother having the software properly load the tune file if you didn't have some kind of plan to support it?
Simple answer, EFILive (really Autocal) provides a very conveient means for delivering tunes. We have a number of customers who are quite knowledgeable on the Bosch gas ECM's who develop their own tunes with tools other than EFILive, we just provide them an alternative to ECM swapping. But as usual supporting 'just flashing' on these presents some issues (Boschisms), eg, who makes two different ECM's with four different unlock algorithms, madness!