(Sorry, no current autoscan is available for a few days...see below for why. The car is a 2008 US-spec Audi A5 3.2, MT, with original incandescent tail lights and a recently updated BCM2 v2.0 control module)
TL;DR: What do the first 11 bits of BCM2 channels 195-210 do? Does anyone have them documented somewhere?
Last weekend, with the help of a family member and access to a VAS tool, I replaced the BCM2 module in my 2008 A5 because the old module had a failure in the Advanced Key feature. The box (8K0 907 064 AG) was replaced with a later part revision (8K0 907 064 CS), going from BCM2 v1.1 to BCM2 v2.0. That mostly went well, including getting my keys authorized in the new module. The car locks, unlocks, and starts normally. But the tail lights aren't working quite as expected. Okay, should easy enough to fix that with VCDS. Unfortunately, I left my HEX-CAN cable at my family member's place and won't have it back until the weekend.
I think the controller is treating my lights as RoW lights by default, since using my turn signals makes the outboard reverse bulb flash, instead of the outboard red tail/brake/turn light. Also, putting the car in reverse makes only the inboard reverse lamp come on, instead of both inside and outside white lights. This is likely because I'm using the new module's default adaptation values, whatever they may be. Unfortunately, while I captured the long coding of the old box in an Autoscan, I didn't think to grab a controller map for the old adaptation values (I didn't realize that's how the rear lights were configured).*
So until I get my cable back, while I can only tackle this problem abstractly, I'm trying to understand the schema for these adaptation values and plan how to properly recode the module once I have my cable. And that leads me to my actual question...
rlarsen's posts have been amazingly helpful in helping me figure out most of this. Good examples are here and here.
In that second link, rlarsen posts a table explaining the last 5 bits in each adaptation channel. Awesome! That tells me most of what I need to know. But I'm still curious about the first 11 bits. In his tables, the first 7 or 9 bits are colored green, but I can't seem to find anywhere that those are explained. Somewhere, perhaps on another board, I saw him mention that some of those bits control brightness, but I haven't been able to uncover any more detail than that. And those first 9 bits are different between the A5 and A4 examples, so I'd like to understand why. I mainly want to be able to construct my own proper coding values and understand why they are what they are.
Now it could be that these are all documented within VCDS software and I'll find out this question is moot when I get my cable back in a few days. I know a lot of adaptation channels have tooltips for calculating values. But maybe the cheatsheet isn't in the proram, and while I'm waiting around with too much time to think about it, I'm trying to understand as much as I can now.
(*I could resinstall my old BCM module just to get the adaptation values, but I can't risk putting all the car's controllers in Component Protection, as I'm far away from my inside connection, so not in a position to clear it out without a trip to the dealer. And I don't know that putting the new module back in would clear the CP for any boxes that did get tripped. For the same reason, SVM is not a current option...though paying the local dealer for SVM is my fallback plan if I run into unresolvable issues)
TL;DR: What do the first 11 bits of BCM2 channels 195-210 do? Does anyone have them documented somewhere?
Last weekend, with the help of a family member and access to a VAS tool, I replaced the BCM2 module in my 2008 A5 because the old module had a failure in the Advanced Key feature. The box (8K0 907 064 AG) was replaced with a later part revision (8K0 907 064 CS), going from BCM2 v1.1 to BCM2 v2.0. That mostly went well, including getting my keys authorized in the new module. The car locks, unlocks, and starts normally. But the tail lights aren't working quite as expected. Okay, should easy enough to fix that with VCDS. Unfortunately, I left my HEX-CAN cable at my family member's place and won't have it back until the weekend.
I think the controller is treating my lights as RoW lights by default, since using my turn signals makes the outboard reverse bulb flash, instead of the outboard red tail/brake/turn light. Also, putting the car in reverse makes only the inboard reverse lamp come on, instead of both inside and outside white lights. This is likely because I'm using the new module's default adaptation values, whatever they may be. Unfortunately, while I captured the long coding of the old box in an Autoscan, I didn't think to grab a controller map for the old adaptation values (I didn't realize that's how the rear lights were configured).*
So until I get my cable back, while I can only tackle this problem abstractly, I'm trying to understand the schema for these adaptation values and plan how to properly recode the module once I have my cable. And that leads me to my actual question...
rlarsen's posts have been amazingly helpful in helping me figure out most of this. Good examples are here and here.
In that second link, rlarsen posts a table explaining the last 5 bits in each adaptation channel. Awesome! That tells me most of what I need to know. But I'm still curious about the first 11 bits. In his tables, the first 7 or 9 bits are colored green, but I can't seem to find anywhere that those are explained. Somewhere, perhaps on another board, I saw him mention that some of those bits control brightness, but I haven't been able to uncover any more detail than that. And those first 9 bits are different between the A5 and A4 examples, so I'd like to understand why. I mainly want to be able to construct my own proper coding values and understand why they are what they are.
Now it could be that these are all documented within VCDS software and I'll find out this question is moot when I get my cable back in a few days. I know a lot of adaptation channels have tooltips for calculating values. But maybe the cheatsheet isn't in the proram, and while I'm waiting around with too much time to think about it, I'm trying to understand as much as I can now.
(*I could resinstall my old BCM module just to get the adaptation values, but I can't risk putting all the car's controllers in Component Protection, as I'm far away from my inside connection, so not in a position to clear it out without a trip to the dealer. And I don't know that putting the new module back in would clear the CP for any boxes that did get tripped. For the same reason, SVM is not a current option...though paying the local dealer for SVM is my fallback plan if I run into unresolvable issues)