Discovered a slightly BIG freaking issue with sticking this T87 into the 2005-2010 truck chassis.
While we can make the TCM speak happily with the E35A/B ECM by tagging on a few missing packets of required data, that can be assembled from existing CANbus data, the TCM really doesn't like any of the other nodes on our CANbus network. GM added a extra byte or two of data to almost every packet sent by our BCM and EBCM after model year 2010. And our T87/A TCM's are coded to accept only certain packet lengths per each ID. The same issue I ran into with the E38 gasser swap. And was able to fix with a simple CAX file mod to the ECM OS, adding 1 Byte onto 1 ID. In this case, we need to modify about 5 ID's in 2 differnt devices..
On the favorable outlook side, for stand alone ECM/TCM swaps and probably all LBZ trucks, I think we can make this little swap work just fine without much trouble.. Will either need to disable the U DTC's in the TCM, or feed it enough garbage to satisfy that the missing nodes are alive. Either way, I don't see a problem making the ECM/TCM run without any BCM/EBCM data. But I now see the reason why nobody with fancy hardware has been pushing an LMM T87A option. The BCM and EBCM of that year are just not very compatible with the newer version of GMLAN.
That doesn't mean one couldn't update the BCM and EBCM modules to fix this issue also. Several options to try, starting with just disabling the DTC's in the TCM and see how it responds. But any tables related to cruise control aren't gonna be happy.. It also expects to see 4 wheel speed sensors, rather the the 3 wheel speeds in a LMM. There are also some rolling counters and brake pedal pressure paramaters missing from our LMM chassis data that is going to take a bit of reading, and hacking thru the TCM bin files see if they hold any importance. For now, it's 50/50 on the LMM's..
While we can make the TCM speak happily with the E35A/B ECM by tagging on a few missing packets of required data, that can be assembled from existing CANbus data, the TCM really doesn't like any of the other nodes on our CANbus network. GM added a extra byte or two of data to almost every packet sent by our BCM and EBCM after model year 2010. And our T87/A TCM's are coded to accept only certain packet lengths per each ID. The same issue I ran into with the E38 gasser swap. And was able to fix with a simple CAX file mod to the ECM OS, adding 1 Byte onto 1 ID. In this case, we need to modify about 5 ID's in 2 differnt devices..
On the favorable outlook side, for stand alone ECM/TCM swaps and probably all LBZ trucks, I think we can make this little swap work just fine without much trouble.. Will either need to disable the U DTC's in the TCM, or feed it enough garbage to satisfy that the missing nodes are alive. Either way, I don't see a problem making the ECM/TCM run without any BCM/EBCM data. But I now see the reason why nobody with fancy hardware has been pushing an LMM T87A option. The BCM and EBCM of that year are just not very compatible with the newer version of GMLAN.
That doesn't mean one couldn't update the BCM and EBCM modules to fix this issue also. Several options to try, starting with just disabling the DTC's in the TCM and see how it responds. But any tables related to cruise control aren't gonna be happy.. It also expects to see 4 wheel speed sensors, rather the the 3 wheel speeds in a LMM. There are also some rolling counters and brake pedal pressure paramaters missing from our LMM chassis data that is going to take a bit of reading, and hacking thru the TCM bin files see if they hold any importance. For now, it's 50/50 on the LMM's..