pcmhacking.net

kur4o wrote: ↑Thu Apr 25, 2024 10:37 pm 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

Tre-Cool wrote: ↑Fri Apr 26, 2024 12:58 pm 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

kidturbo wrote: ↑Fri Apr 26, 2024 1:31 pm 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 wrote: ↑Fri Apr 26, 2024 6:01 pm 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..