T43 2010 can compatibility

[hjtrbo]

ECM to TCM compatibility is the 2nd hurdle. This comes down to CAN communication setup between the 2 modules, the U0100/0101 codes are directly related to the SOHM configured on each module. The ecu in your instance is expecting to receive data on a specific can ID so it knows it's got a healthy connection to the TCM. So in this case it's likely that while the trans is happy, the ECU is not getting what it expects the TCM to be broadcasting to & flags the fault.

I've never dealt with U codes. Am I right thinking dealer level scan tools won't give the specific can id that failed?

[hjtrbo]

wuld you look at that lol, it works!! why is there so much conflicting information on flashing OS to the TCM? it makes it super hard to figure out what is up and down..

Did that OS combo flag a U code?

[Tre-Cool]

ECM to TCM compatibility is the 2nd hurdle. This comes down to CAN communication setup between the 2 modules, the U0100/0101 codes are directly related to the SOHM configured on each module. The ecu in your instance is expecting to receive data on a specific can ID so it knows it's got a healthy connection to the TCM. So in this case it's likely that while the trans is happy, the ECU is not getting what it expects the TCM to be broadcasting to & flags the fault.

I've never dealt with U codes. Am I right thinking dealer level scan tools won't give the specific can id that failed?

Nah, no scan tool flags what the specific error code traces back to.

[tonn0297]

So my knowledge there are 2 things with the compatibility.

1 is the hardware taking the flash, so pre 2009 will take anything to 2006 & the same for 2006 to 2009.

2009.5/2010 will take anything to end of production for our commodores, since most Operating systems have some overlap to the wider GM world I can't see why they wouldnt work. I've flashed a 2012 tcm to 2017 VF & it worked.

ECM to TCM compatibility is the 2nd hurdle. This comes down to CAN communication setup between the 2 modules, the U0100/0101 codes are directly related to the SOHM configured on each module. The ecu in your instance is expecting to receive data on a specific can ID so it knows it's got a healthy connection to the TCM. So in this case it's likely that while the trans is happy, the ECU is not getting what it expects the TCM to be broadcasting to & flags the fault.

if the box is shifting as expected, just turn the dtc code off.

after the update to 2017 OS, i get 2 error codes,
0x7EA: P0658 - Actuator Supply Voltage A Circuit Low (Pending, Current, Permanent)
0x7EA: P0962 - Pressure Control Solenoid A Control Circuit Low (Permanent)

wuld you think that is incompatible hardware or a wiring issue? I dont recall that issue with the other OS

[tonn0297]

after downgrade of OS to the 24256125 i still have the P0658, Pending and current
this dont seem too great

firefox_W5Xe8m0X45.png

[tonn0297]

Do we have the ability to check hardware pinout from the Bin? I'm thinking of they swapped some pins between the 2010 to 2013 or 2017 (this seems to be the most common year stated on sonax replacement tcm and alike)

[antus]

Not easily from the bin. Very advanced skills required and very few who could do it. Its best to get it from vehicle wiring diagrams.

[tonn0297]

Not easily from the bin. Very advanced skills required and very few who could do it. Its best to get it from vehicle wiring diagrams.

yea thats what i assumed... issue is the wiring diagram do not show the layout of the internal MCU or pins.. so ill take the pan down, thanks for the pointers!

[hjtrbo]

The fault still there with 909 flashed in? Have you got a log from before you flashed in the new OS? The log stores any fault codes under the vehicle info tab.

[antus]

@tonn0297 do you mean chip level pinout? Not TCM connector pinout? I am thinking the TCM connector should be documented and you can see any power pins changed that might cause that DTC and be something fixable with wiring.