|
|
Post by bobloblawgti on Mar 29, 2022 19:53:20 GMT
Hi all -- I did the power folding mirror retrofit on my NAR 2019 GTI about a year ago. Went great, everything works fine, but about six months ago I started seeing a static error show up: B11FA29 Position sensor for mirror adjustment - Implausible signal. Clearing it gets rid for a couple days but then it comes back. Any coding changes I can make to resolve? Full scan attached: OBDeleven_Log.txt (5.25 KB)  |
|
|
|
Post by dv52 (Australia) on Mar 30, 2022 22:28:58 GMT
hmm..... generally speaking an "implausible signal" error means an equipment problem rather than a coding issue and I suspect that this is the case here You could try this: - Go to the driver door module
- Select Live Data
- Enter "memory" into search box and select mirror memory
- Operate the driver side position buttons - does X coordinate and Y coordinate values change?
Don
|
|
|
|
Post by bobloblawgti on Apr 1, 2022 22:12:32 GMT
Thanks dv52 (Australia) ! Here's what live data looks like:  I have no issues with passenger mirror memory/mirror dip. Sometimes I have to parallel park on the driver's side of the car, so a few months ago I enabled the corresponding memory/mirror dip settings for the driver door. It never ended up working correctly, and that's when this code started showing up:  So I changed everything back to how it was before hoping it would resolve:    But the code remains static. Appreciate any more thoughts you might have! |
|
|
|
Post by bobloblawgti on Apr 5, 2022 3:37:04 GMT
dv52 (Australia) tried resetting mirror settings in the infotainment and clearing the code so we'll see if it stays gone. Not confident though :\
|
|
|
|
Post by bobloblawgti on Apr 18, 2022 12:59:15 GMT
|
|
|
|
Post by dv52 (Australia) on Apr 18, 2022 20:04:36 GMT
Post-up the long-code strings on both passenger and driver doors - please
Don
|
|
|
|
Post by bobloblawgti on Apr 19, 2022 4:58:02 GMT
dv52 (Australia) Not totally sure how to export the whole long coding aside from screenshots of all the drop downs; will this do the trick?  Driver door  Passenger door Thanks!
|
|
|
|
Post by dv52 (Australia) on Apr 19, 2022 21:10:15 GMT
^ ^ ^ HMM............ so both modules still have mirror-dip active and both mirrors believe that they have memory modules (when they don't according to your LIVE DATA pictures?
And both are folding mirrors - is this correct?
Don
|
|
|
|
Post by bobloblawgti on Apr 20, 2022 19:00:52 GMT
dv52 (Australia) yep both are folding mirrors retrofitted in. It's entirely possible the driver door does NOT have a memory module, so perhaps disabling mirror dip on the driver door will help? It's already disabled via all the drop downs but you're saying the coding indicates it is in fact still enabled?
|
|
|
|
Post by dv52 (Australia) on Apr 20, 2022 22:52:57 GMT
@bobloblaqwgti :
As I said, the Live Data picture that you previously posted indicates that the module does NOT have the required memory module - see entry "install"=not installed.
Now, I'm not sure to which module this picture applies - but if it's the driver door, then it's not surprising - because it's very unusual for driver door modules on mk7/mk7.5 to have memory modules. Mirror-dip-on-reverse is a passenger side thing!
My suggestion is that you also check if the passenger-side door module has a memory module. If you get the same results as the Live Data picture that you posted, then the answer is NO.
In any event, depending on the results of your tests - disable "memory_mirror" and "position_memory_with_rear_gear" on whichever modules DON'T have memory. Then clear the errors- do they re-appear? If so, post-up the long-code string on the module(s) that report the error (scroll-down to "advance Information" and cut-and-paste the long-code value into a new post)
Don
|
|
|
|
Post by bobloblawgti on Apr 21, 2022 20:15:22 GMT
dv52 (Australia) : Appreciate the replies! As for next steps: My suggestion is that you also check if the passenger-side door module has a memory module. If you get the same results as the Live Data picture that you posted, then the answer is NO. The passenger side does indeed have a memory module; live data is visible:  In any event, depending on the results of your tests - disable "memory_mirror" and "position_memory_with_rear_gear" on whichever modules DON'T have memory. Then clear the errors- do they re-appear? So, as far as I can tell, "memory_mirror" and "position_memory_with_rear_gear" are both already disabled in the Driver Door module. As the error started appearing after I enabled them, my first step was to disable them to see if that resolved the error. Unfortunately even with them both disabled, the error persists:   If so, post-up the long-code string on the module(s) that report the error (scroll-down to "advance Information" and cut-and-paste the long-code value into a new post) The error hasn't come back since last I cleared it so if there's something there I'll have to wait until it's back. But I took a look at the module under Advanced Identification (didn't see Advance Information) only shows these options:  You mentioned earlier from my long coding screenshot that it looks like memory mirror is enabled even though it's disabled in the drop downs -- is there an adjustment I can make in there perhaps? Appreciate all the help!
|
|
|
|
Post by dv52 (Australia) on Apr 21, 2022 22:12:57 GMT
The passenger side does indeed have a memory module; live data is visible: OK - good news !! So, as far as I can tell, "memory_mirror" and "position_memory_with_rear_gear" are both already disabled in the Driver Door module. As the error started appearing after I enabled them, my first step was to disable them to see if that resolved the error. Unfortunately even with them both disabled, the error persists: hmm........I'm not sure why this is so difficult - but I continue to be confused by your conviction in this matter! Here's a copy of your earlier pics: Driver door Passenger door Notice that the long-code strings for the modules on both sides of the car are the same (they shouldn't be the same - see comment below)?
The long-code values in your pictures translate to hexadecimal/binary values like this: <----------------------------BITS----------------------->
Byte HEX 7 6 5 4 3 2 1 0
00 00 0 0 0 0 0 0 0 0
01 3F 0 0 1 1 1 1 1 1
02 13 0 0 0 1 0 0 1 1
03 20 0 0 1 0 0 0 0 0
04 DE 1 1 0 1 1 1 1 0
05 00 0 0 0 0 0 0 0 0
06 04 0 0 0 0 0 1 0 0
07 00 0 0 0 0 0 0 0 0
08 00 0 0 0 0 0 0 0 0
09 00 0 0 0 0 0 0 0 0
10 00 0 0 0 0 0 0 0 0
11 00 0 0 0 0 0 0 0 0
So, from my table above which lists the status of each software switch in the module's long-code string - notice that for Byte 04: - Bit 2=1 ("memory_mirror")
- Bit 3 =1 ("position_memory_with_rear_gear").
This means that the two features are ACTIVE (despite your conviction)!!
You mentioned earlier from my long coding screenshot that it looks like memory mirror is enabled even though it's disabled in the drop downs -- is there an adjustment I can make in there perhaps? Appreciate all the help! See my comments above
Way forward
So bottom line = the 2 x modules in this car SHOULD NOT have the same long-code values because clearly they have different equipment installed (i.e. the passenger module has a memory module - and the driver side does not!!) Now that we have confirmed some basic facts (I hope) - I suggest that you look in History - go back as far as possible in time to the earliest record for a change related to each door module. Note the "old value" for the long-code string. Then change the value of each module to their respective "old value". This will revert the long-code of your door modules back to their factory value. Then (and only then) - if you want to enable mirror dip on the passenger side mirror (not possible on driver-side module), change Byte 04, Bit 2 =1 and Bit 3=1Don |
|
|
|
Post by bobloblawgti on Apr 22, 2022 16:45:20 GMT
dv52 (Australia) so the fact that they both say "not active" in the long coding drop down menus means they could still be "active" in the long coding? The long coding in the photos for both doors is different; one says D4 and the other says DE. Not sure if that's relevant or not, but my claim that it's disabled in the driver door comes from all the listings in the screenshots above saying "not active". I'll double check the long coding bytes and bits when I get out to the car again, though. Thank you!
|
|
|
|
Post by dv52 (Australia) on Apr 22, 2022 22:04:22 GMT
oops........... my bad - yes, passenger door Bye04 = D4= 1101 0100, This means Bit 2 =1, Bit 3 =0.
As for your other question about "not active" - I don't know the answer (I'm just going from the long code - with the correction above)
Again, try my suggested "way forward"
|
|
