Epiphany
Well-Known Member
The Telematics Control Unit module can be seen here in orange in the following diagram which depicts the vehicle's various control modules. It operates on the High Speed Controller Area Network 4 (HS-CAN4) "at a maximum data transfer speed of 500 Kbps and is designed for real time audio, multimedia and driver information transfer and control."
There are probably a few ways to skin this cat with the issue being added complexity when seeking the most detailed method to "better manage" your choice to share or not share certain data sets (if at all). Aside from fuse pulling or antenna blocking/removal, etc, there is likely a way to convince certain module addresses to join the cause of independence and freedom.
This little gem I link below shows the module address responsible for it all going down, 754 in the TCU. IDS likely won't allow what I'm getting at but FORScan will. You just have to know what is happening at each address and how to get it to work (or not) for you.
The above says there aren't any "available program parameters" but if you understand how this works you know this isn't always true. It just takes a lot of time and testing. And FORScan.
The following is a screen shot from a comparator tool I use that allows taking a close look at the as built files that were "assigned" to a given vehicle, in this case, mine. The column to the left shows the 754 (TCU) module address, along with relevant data sets and binary code. Those that did the calibration work have all the information that would make this a potentially very simple task (come out, come out, wherever you are!) but thanks to corporate policy and lawyers that would likely never happen. Note that I can scroll down much further as the 754 address goes all the way down to 754-18. Longshot, but there may be something to be uncovered here. I may contact a gentleman that writes as-built files to see how familiar he is in this particular area. He wrote me a file removing the annoying "double-horn honk" a while back when nobody else knew how to do it with the '20 S550 variants.
There are probably a few ways to skin this cat with the issue being added complexity when seeking the most detailed method to "better manage" your choice to share or not share certain data sets (if at all). Aside from fuse pulling or antenna blocking/removal, etc, there is likely a way to convince certain module addresses to join the cause of independence and freedom.
This little gem I link below shows the module address responsible for it all going down, 754 in the TCU. IDS likely won't allow what I'm getting at but FORScan will. You just have to know what is happening at each address and how to get it to work (or not) for you.
The above says there aren't any "available program parameters" but if you understand how this works you know this isn't always true. It just takes a lot of time and testing. And FORScan.
The following is a screen shot from a comparator tool I use that allows taking a close look at the as built files that were "assigned" to a given vehicle, in this case, mine. The column to the left shows the 754 (TCU) module address, along with relevant data sets and binary code. Those that did the calibration work have all the information that would make this a potentially very simple task (come out, come out, wherever you are!) but thanks to corporate policy and lawyers that would likely never happen. Note that I can scroll down much further as the 754 address goes all the way down to 754-18. Longshot, but there may be something to be uncovered here. I may contact a gentleman that writes as-built files to see how familiar he is in this particular area. He wrote me a file removing the annoying "double-horn honk" a while back when nobody else knew how to do it with the '20 S550 variants.
Sponsored
Last edited: