LZ4/LX9 Canyon Swap Prep

[antus]

For the T42 trecool has looked in to making pcms and tranmissions more compatible and posted lots of notes in this thread here viewtopic.php?t=6820 and viewtopic.php?p=135922#p135922

I don't have an answer for exactly what you need or if it can be done but from the above threads I think you can turn different messages on and off and it can sometimes be done if you know which messages are needed and if the needed ones are supported. You'd probably need AI to help you, vehicle logs, and obviously not all combinations would be possible.

[gixxer92]

Can't really find any information on disabling VATS in the E67 computers, apparently it's complicated and difficult and all those fun things.

Claude's on the case of the E67 features needed, unfortunately the 3530 PCM may not be the way to go-I have a 12607096 unit as well but I am trying to get the supercharger support patched into the LZ9 OS, as well as actually getting VATS disabled. I did not want to have to support HPtuners anymore but it's looking like I may have to give them money again. (Partially because the school I work at does not have access to their old HPtuner stuff anymore, as it was stolen...They ask to use mine all the time but if I can get them to pay for the upgrade then maybe I can justify it.)

I have my data on the E67 from the Cadillac OS 12632176
0x1C1042: Immobilizer algorithm selection, signed 16-bit big-endian. Source labels are 0 = NAO, 1 = PPEI3, 2 = GMIO.
0x1C1044: Immobilizer function enable, unsigned byte. Source labels are 0 = OFF, 1 = ON.

Hope that helps.

[kur4o]

VATS on e67 is hardcoded to OS, to turn it off you need to patch the OS, if you have any problem doing it, I can apply the patch for you.

[Xnke]

I have my data on the E67 from the Cadillac OS 12632176
0x1C1042: Immobilizer algorithm selection, signed 16-bit big-endian. Source labels are 0 = NAO, 1 = PPEI3, 2 = GMIO.
0x1C1044: Immobilizer function enable, unsigned byte. Source labels are 0 = OFF, 1 = ON.

Hope that helps.

That may be helpful. I'm currently working with OSID 12604676, and plan to work on 12606475 as it's more common and covers more target vehicles. I only started with 12604676 because I have a matching ECM BIN and TCM BIN from the same vehicle to start with, and the hardware ID is the same for both - 12603530.

UNFORTUNATELY, the 3530 hardware has the hard 63.5lbs/hour injector limit, and can only handle 2006 operating systems. I also have hardware ID 12607096, which covers 2007, 2008, and early 2009 applications, but still supposedly has the 63.5lb/hour injector limit.

VATS on e67 is hardcoded to OS, to turn it off you need to patch the OS, if you have any problem doing it, I can apply the patch for you.

If I were to send you three different OS's, can you help me patch them? 4676, 6475 are the two I am currently working on but both have the supposed 2006 year OS/Hardware lock issue, and 7096 probably doesn't? If you only have time to look at one of them, 6475 is probably the BIN that I will have to start the actual hardware testing with, if 4674 is not going to flash onto the hardware I have. (Malibu OS vs G6 OS)

Thank you both-I'll report back on getting the ECU's to crank and start the engine as soon as I finish the run-in-stand harnesses. Plan is to start the harness wiring next sunday.

[Xnke]

I have my data on the E67 from the Cadillac OS 12632176
0x1C1042: Immobilizer algorithm selection, signed 16-bit big-endian. Source labels are 0 = NAO, 1 = PPEI3, 2 = GMIO.
0x1C1044: Immobilizer function enable, unsigned byte. Source labels are 0 = OFF, 1 = ON.

Hope that helps.

OK-so this address pair is blank in 2006 BINs, and only has data in the 2007 Uplander and 2009 Canyon bins, in my bin collection. Looking for similar code located 0x1C0AF0 in the Malibu 2006 BIN, and the malibu and canyon match up byte for byte, just in a different location. The Impala has a different value, 1 instead of 0.

So:

Code: Select all

	BIN FILE		Selector			Enable Flag
2006 Malibu 12604676 	0x1C0AF0 = 0 (NAO)		0x1C0AF2 = 1 (ON)
2006 G6 MT 12604676	0x1C0AF0 = 0 (NAO)		0x1C0AF2 = 1 (ON)
2006 G6 AT 12606475	0x1C0AF0 = 0 (NAO)		0x1C0AF2 = 1 (ON)
2006 Impala 12606475	0x1C0AF0 = 1 (PPEI3)		0x1C0AF2 = 1 (ON)
2009 Canyon 12630465	0x1C1042 = 0 (NAO)		0x1C0AF2 = 1 (ON)

Claude has determined that in the Malibu and G6 OS, doing Enable = 0 skips the NAO password check, but only if the second check at 0x1315D0 is also a 0. 0x1315D0 returns a 1 when a 16 bit value in RAM located at 0x3F71A8 is not 0 or FFFF and is not the bitwise complement of a second value at 0x3F71A0. Haven't chased down the sources of those RAM locations yet. The Impala OS (Even with the same OSID!) does not handle it the same way.

[kur4o]

I ported the e38 patch to cover e67[file rename]
for universal patcher
extract the tableseek to xml folder and extract the patch to patch folder.

Than you can apply and find the immo tables on any e67 bin you have. The immo tables only configure different types of immo level, can`t really turn it off, verified in e38 disassembly. e67 might have something left over.

After patch is applied you need to overwrite OS.