E67 to T87/T87A TCM interface needed

[Tre-Cool]

Couple of logs from a Holden VZ, this was a 6 month model run back in 2006 prior to the release of the VE model (later exported as the g8 in 2009).
They had E38/T42,ABS,PIM module on the canbus.

1 log is key on, engine off.
2nd log is engine running & me moving the shifter through P,R,N,D etc (not in that order as started it in N).
3rd/4th log will be a 2011 HSV GTS - E38/T43

Logged via Ixxat's Cananalyzer software.

VE-E38-T43-Engine-Off.csv

(1.01 MiB) Downloaded 18 times

VE-E38-T43-Engine-On.csv

(1.01 MiB) Downloaded 17 times

VZ-E38-T42-Engine-Off.csv

(720.4 KiB) Downloaded 17 times

VZ-E38-T42-Engine-On-Shifter-Cycle.csv

(1.03 MiB) Downloaded 18 times

[kidturbo]

If I counted correctly this is where bytes are stored from that message,
r31 is the offset they get stored in numerical order.

Now tracing down to individual bits will take some time, due to ppc crap code.

Here is how bits are copied for first byte , r4 is the bit position, some bits might get inversed

Code: Select all

M:000A5808 sub_A5808:                              # CODE XREF: sub_A5930+18p
ROM:000A5808                 lis       r11, VeEODI_b_EngOilSensedVld@h
ROM:000A580C                 lbz       r11, VeEODI_b_EngOilSensedVld@l(r11)
ROM:000A5810                 li        r4, 0
ROM:000A5814                 cmpwi     r11, 0
ROM:000A5818                 bne       loc_A5820
ROM:000A581C                 li        r4, 0x80 # 'Ç'
ROM:000A5820
ROM:000A5820 loc_A5820:                              # CODE XREF: sub_A5808+10j
ROM:000A5820                 lis       r12, VeEOPI_b_ValidEngOil@h
ROM:000A5824                 lbz       r12, VeEOPI_b_ValidEngOil@l(r12)
ROM:000A5828                 cmpwi     r12, 0
ROM:000A582C                 bne       loc_A5834
ROM:000A5830                 ori       r4, r4, 0x40
ROM:000A5834
ROM:000A5834 loc_A5834:                              # CODE XREF: sub_A5808+24j
ROM:000A5834                 lis       r12, VeEOPC_b_EngOilPresLoWarnLmp@h
ROM:000A5838                 lbz       r12, VeEOPC_b_EngOilPresLoWarnLmp@l(r12)
ROM:000A583C                 cmpwi     r12, 0
ROM:000A5840                 beq       loc_A5848
ROM:000A5844                 ori       r4, r4, 0x20
ROM:000A5848
ROM:000A5848 loc_A5848:                              # CODE XREF: sub_A5808+38j
ROM:000A5848                 lis       r12, VeEODC_b_EngOilLvlLoLmp@h
ROM:000A584C                 lbz       r12, VeEODC_b_EngOilLvlLoLmp@l(r12)
ROM:000A5850                 cmpwi     r12, 0
ROM:000A5854                 beq       loc_A585C
ROM:000A5858                 ori       r4, r4, 0x10
ROM:000A585C
ROM:000A585C loc_A585C:                              # CODE XREF: sub_A5808+4Cj
ROM:000A585C                 lis       r12, VeEODC_b_OilChangeIndOn@h
ROM:000A5860                 lbz       r12, VeEODC_b_OilChangeIndOn@l(r12)
ROM:000A5864                 cmpwi     r12, 0
ROM:000A5868                 beq       loc_A5870
ROM:000A586C                 ori       r4, r4, 8
ROM:000A5870
ROM:000A5870 loc_A5870:                              # CODE XREF: sub_A5808+60j
ROM:000A5870                 lis       r12, VeFEQR_HotCoolantMode@h
ROM:000A5874                 lbz       r12, VeFEQR_HotCoolantMode@l(r12)
ROM:000A5878                 cmpwi     r12, 0
ROM:000A587C                 beq       loc_A5884
ROM:000A5880                 ori       r4, r4, 4
ROM:000A5884
ROM:000A5884 loc_A5884:                              # CODE XREF: sub_A5808+74j
ROM:000A5884                 lis       r12, ((VeECTI_b_EngHotStopEng+0x10000)@h)
ROM:000A5888                 lbz       r12, VeECTI_b_EngHotStopEng@l(r12)
ROM:000A588C                 cmpwi     r12, 0
ROM:000A5890                 beq       loc_A5898
ROM:000A5894                 ori       r4, r4, 2
ROM:000A5898
ROM:000A5898 loc_A5898:                              # CODE XREF: sub_A5808+88j
ROM:000A5898                 lis       r12, VeFANC_b_AC_OffRequest@h
ROM:000A589C                 lbz       r12, VeFANC_b_AC_OffRequest@l(r12)
ROM:000A58A0                 cmpwi     r12, 0
ROM:000A58A4                 beq       loc_A58AC
ROM:000A58A8                 ori       r4, r4, 1
ROM:000A58AC
ROM:000A58AC loc_A58AC:                              # CODE XREF: sub_A5808+9Cj
ROM:000A58AC                 clrlwi    r3, r4, 24
ROM:000A58B0                 blr
ROM:000A58B0 # End of function sub_A5808

You seem to be headed in correct direction. The R3 values in Green are our Msg to Byte Positions 0-7. Further broken down to the bit level for split Bytes. Then there should be some scaling related math linked to our ADC values. But you're on it.

Maybe we should start a new topic on it. Looks like it might get petty deep..

[kidturbo]

Couple of logs from a Holden VZ, this was a 6 month model run back in 2006 prior to the release of the VE model (later exported as the g8 in 2009).
They had E38/T42,ABS,PIM module on the canbus.

1 log is key on, engine off.
2nd log is engine running & me moving the shifter through P,R,N,D etc (not in that order as started it in N).
3rd/4th log will be a 2011 HSV GTS - E38/T43

Logged via Ixxat's Cananalyzer software.

VE-E38-T43-Engine-Off.csv
VE-E38-T43-Engine-On.csv
VZ-E38-T42-Engine-Off.csv
VZ-E38-T42-Engine-On-Shifter-Cycle.csv

Sweet.. I'll have a quick looksee.

[kidturbo]

First interesting thing from your 2006 E38 file is our 0x0C9 ID. In your capture it's 8 bytes long, but in most of the US versions I've seen that is only 7 bytes.. That last byte is Boost Pressure.

" C9","8","00 00 00 00 00 40 08 00"

I need to dl the software to view that csv correctly. But besides that, it looks to be all just standard high speed GMLAN messages.

[kidturbo]

First interesting thing from your 2006 E38 file is our 0x0C9 ID. In your capture it's 8 bytes long, but in most of the US versions I've seen that is only 7 bytes.. That last byte is Boost Pressure.

" C9","8","00 00 00 00 00 40 08 00"

I need to dl the software to view that csv correctly. But besides that, it looks to be all just standard high speed GMLAN messages.

Hold the presses..


"110","8","00 00 00 00 00 2C 00 38"
"120","8","02 70 02 70 42 70 02 A8"
"124","5","00 02 70 02 70"
"380","8","02 1A 00 00 A0 00 EA 0E"


I downloaded those files backwards.

The one with you shifting is what I call the Corvette Only Protocol. And what I had been told was used by Holden.. Winner... The VZ is second vehicle now I know to use it. Who did the body control in those? Does it small like Bosch or Delphi ??

So the 2011 is the 0x0C9 data above, which is our standard GMLAN set.. So now we need to fine the Switch in all the E38 OS release to flip those on demand. That would be cool.. But now that we know that ya have both protocols floating around over there, just need to that keep in mind and match CANbus hardware.

[Tre-Cool]

the vz 6lt was a special car, only produced for like 6-9 months because from jan 1 to september (slight production overlap with VE) they introduced euro 3 or 4 emissions at the start of the year & i suspect because holden had already worked all that shit out for the upcoming VE model, they used the engine powertrain setup from that, rather then continuing with the 5.7 LS1 controller.

PIM module does ALDL translation for BCM/Dash Cluster, Cruise control stalk also gets wired to PIM.

s-l400-3781839143.jpg (20.2 KiB) Viewed 251 times

VZ pim.JPG (129.48 KiB) Viewed 251 times

I'm going to start pulling the 4l65e out of the vz now & put the 6l80e in place. I'm just going to dummy up some wiring to the t42/NSBU wires before i modify the engine harness.

[kidturbo]

That is an interesting piece. Not a complete body control module, however it has 2 pair of canbus wires. GM had a tendency to do that with a few modules like the TCM's. Basically they were just daisy chaining some the nodes together to save wiring. However for that PIM module, I would like to see where those both run. Typically if you check for continuity between the matching colors, will tell you if they are linked on the board like all the rest. It's possible that has gateway duties, and if so, there will be no continuity between the 2 Tans and TN/Bk. I didn't see any single wire CANbus there like would go to a dash.

For your particular swap situation, I'd start looking for your preferred TCM OS that would have came in a Corvette up to 2014 I believe.. That should work with your Holden chassis straight outa the box. Anything later years, like a T87, ain't likely to work because to my knowledge GM scrapped all those ID's from all code.. So it limits the years, but opens up some hardware. Hope that helps..

[Tre-Cool]

That is an interesting piece. Not a complete body control module, however it has 2 pair of canbus wires. GM had a tendency to do that with a few modules like the TCM's. Basically they were just daisy chaining some the nodes together to save wiring. However for that PIM module, I would like to see where those both run. Typically if you check for continuity between the matching colors, will tell you if they are linked on the board like all the rest. It's possible that has gateway duties, and if so, there will be no continuity between the 2 Tans and TN/Bk. I didn't see any single wire CANbus there like would go to a dash.

For your particular swap situation, I'd start looking for your preferred TCM OS that would have came in a Corvette up to 2014 I believe.. That should work with your Holden chassis straight outa the box. Anything later years, like a T87, ain't likely to work because to my knowledge GM scrapped all those ID's from all code.. So it limits the years, but opens up some hardware. Hope that helps..

Heres the factory diagram for the VZ Can bus.

I'm think i'll be good on this upgrade as holden released a ve commodore in 2006/07 with similar tune files that came with both the t43 & t42 to export to Saudi Arabia. I've already got the different switches defined/mapped out already.

I've now got the 6l80e box in, just need to do some temporary patching & runs the trans cooler lines before i can attempt to start it up again. then it's new tail shaft time.

forgot to mention im using an early 08 tcm which should still be compatible.

[kidturbo]

Good info. I'm not sure what GM actually called this second set of HS GMLAN ID's, but it would helpful to categorize what PCM hardware OS versions ran it. For now, at least ya know what your lookng for in the ID structure for anything in question. If CAN ID's are all dec, it's Corvette / Holden version.

[kur4o]

Did some changes to e38 tableseek file, and now it will find the TX and RX tables stored in OS for any e38 e67 bin. End of table is open, so user needs to figure where it ends, Usage will be for display mainly.


Extract file to XML folder overwriting previous versions.