nicola
Junior Member
Posts: 69
|
Post by nicola on Nov 9, 2022 18:11:20 GMT
Try changing the service to developer I should have solved the new number accepted it |
|
|
|
Post by giobox on Jan 1, 2023 4:44:00 GMT
Hello, can someone please help me to calculate the code 10 C 5 Thank you in advance 10C5
|
|
|
|
Post by Thirsty on Jan 1, 2023 13:43:41 GMT
|
|
|
|
Post by giobox on Jan 2, 2023 9:34:46 GMT
Thanks 👍
|
|
|
|
Post by NOSCAR on Jan 6, 2023 2:17:02 GMT
Just today the same problem happened to me, recently, just a few months ago I made the change for a larger 8" screen and that's it. Fortunately I found this post in another forum and I was able to find the solution Since it is in Spanish I will try to translate it as correctly as possible, I also leave the link since it is easier for me to see it directly www.audisport-iberica.com/foro/topic/397030-borrar-error-b201a00-comprobaci%C3%B3n-gesti%C3%B3n-de-la-versi%C3%B3n-de-software/Good!! I bring you a small manual on how to eliminate the Error - B201A00- Software Version Management Check (1555 - Check Software Version Management) For all of you who have updated the MMI software at some point, you will have verified that several errors (warnings) are recorded in the 5F (MMI) module. All of them can be easily cleaned with VAGCOM or OBDeleven except the B201A00, since it remains permanently, and even if it is deleted, it reappears instantly But there is a very simple solution for that; I put the steps on how to do it with OBDeleven, and later with VAGCOM Recommendation: In case you are not very familiar with OBDeleven, it is recommended to make a backup copy of the 5F Control Unit 1º From OBDeleven, we enter the list of Control Units, and access the Electronic Information call 1 (also called 5F or MMI) 2º Within the module we mark the ADAPTATION option: 3º In the following list, look for the text CONFIGURATION OF THE ASSEMBLY MODIFICATION and click on it: "confirmation of the assembly modification 4º Now and depending on each car, a code will appear in hexadecimal format of 4 characters. As a general rule, they are usually 3 digits and a letter (from a to f), but in my case, they were 4 digits as seen in the screenshot: (in my case it said f2e) 5º Now, we enter this page mib-helper.com/im-so-xory/, and we introduce the code of 3 or 4 characters that we saw in the previous menu, and we give it to calculate. In my case, once calculated, it generates the following: 6º Now we return to OBDeleven, and click on the f2e digit so that it allows us to edit it, and thus introduce the new one that the calculator has generated for us (8c97). When we have entered it, we click OK, and at the bottom click on the GREEN Check to confirm the change: The initial code will not change (2 in my case), and it will still show the original, but it is NORMAL. 7º Now, we return to the list of the Control Units, and we enter again in the Information Electronics 1, and then in the FAULTS section: 8º There, we must update or refresh the list of errors that existed previously, and we will verify that the Error will have completely disappeared: 9º If, finally, we do a complete scan or if we access the list of Control units, we will verify that the error has already disappeared and the 5F Module has been completely cleaned NOT A: This process does not affect any type of previous configuration in the MMI at all, nor does it affect if Android Auto is activated or the maps that are installed |
|
|
|
Post by inmsdeane on Jan 7, 2023 5:25:00 GMT
I have the same issue. My code is 8A70
|
|
|
|
Post by vwjap on Jan 7, 2023 9:07:28 GMT
43a2
|
|
|
|
Post by traffordt59 on Jan 19, 2023 23:05:33 GMT
4c5f
|
|
|
|
Post by ruairi on Jan 29, 2023 22:19:12 GMT
Hi, hope someone can help. I did this confirmation of installation change using value 976 (initial value was c0a4) and it cleared the checking software version error, but now I have open circuit errors for rear bass/treble speakers that keep reappearing after being cleared. I only have the car a week and have been trying to clear the fault codes left by the previous owner. Please see the log below:
OBDeleven data log
Date: 2023-01-29 22:04
VIN: WVWZZZ3CZJP001497
Car: Volkswagen Passat
Year: 2018
Body type: Variant
Engine: CRLB
Mileage: 55383 KM
---------------------------------------------------------------
5F Multimedia
System description: MU-S-ND-ER
Software number: 3Q0035874C
Software version: 0478
Hardware number: 3Q0035874C
Hardware version: H41
Serial number: VWZAZ2T1418338
ODX name: EV_MUStd4CTSAT
ODX version: 001022
Long coding: 02840201FF00000051110101008808001F0100E601200000CF
Subsystems:
System description: ABT_Std-2_Nav
Software version: 8130
Hardware version: H50
Serial number: VWZ6ZJT1720040
Trouble codes:
B106713 - Right rear bass speaker Open circuit
static
Date: 2023-01-29 22:04:08
Mileage: 55383 km
Priority: 6
Malfunction frequency counter: 1
Unlearning counter: 137
Dynamic environmental data: 028676
B106813 - Right rear treble speaker Open circuit
static
Date: 2023-01-29 22:04:08
Mileage: 55383 km
Priority: 6
Malfunction frequency counter: 1
Unlearning counter: 137
Dynamic environmental data: 028676
B106513 - Left rear bass speaker Open circuit
static
Date: 2023-01-29 22:04:08
Mileage: 55383 km
Priority: 6
Malfunction frequency counter: 1
Unlearning counter: 137
Dynamic environmental data: 028676
B106613 - Left rear treble speaker Open circuit
static
Date: 2023-01-29 22:04:08
Mileage: 55383 km
Priority: 6
Malfunction frequency counter: 1
Unlearning counter: 137
Dynamic environmental data: 028676
|
|
|
|
Post by dv52 (Australia) on Jan 30, 2023 0:53:28 GMT
ruairi : Hi. First off - does this car have an AID dashboard - because I note that Byte 19, Bit 5 is set on the hex5F module which means that the MOST bus is enabled? It is strange that the speakers on both sides of the car are open-circuit. The common element of course is the connector-plug at the rear of the module housing - albeit the speaker plug is part of the quad-lock mechanism that secures ALL of the plugs, together. Have you removed the module from its location in the glove-box lately? If you have, then check the seating of plug N (see below)
If you haven't removed the module and assuming that this car does NOT have and external amplifier (and sub-woofer), check the records in History for any coding changes that have been made to the hex5F module whilst you have owned the car. If you find any - revert the setting to "old value"
Don
|
|
|
|
Post by ruairi on Jan 30, 2023 4:10:15 GMT
Hi Don, thanks for the reply! Yes, it has an AID dashboard. I haven't touched anything, but I get the impression the previous owner has done a bit of tinkering as there is a RVC installed which is also throwing errors and he has drilled holes in the centre console (which were hidden under a coin holder unbeknownst to me).
The only history I have for changes to 5f are from activating/deactivating the RVC while trying to determine if the camera installed is highline or lowline - there are no grid lines/other views on the camera picture at all. This is activated again at the minute as it was when I started. Another potentially noteworthy observation was the addition of control unit 44 (Steering Assist) during the gateway autocoding when I first connected the dongle and had an "Additional installations detected" fault. These are the only changes I've made with obdeleven.
There was a tone test CD in the glovebox for calibrating speakers I suppose... which I found unusual and could be a clue as the car is supposed to be standard otherwise as far as I know. Is it possible that the previous owner had an upgraded speaker system that was removed upon selling the car? Would these faults still exist if there was an external amplifier?
I love the car but the thought of all these potentially unknown changes/faults is triggering my OCD big time.
|
|
|
|
Post by ruairi on Jan 30, 2023 10:59:49 GMT
Update - this morning I had a control software wrong version fault along with the 4 open circuit faults mentioned - but these all went away when I cleared them and didn't come back. Maybe I just had to restart the MIB. Will keep you posted if they do reappear - now just to clear those pesky RVC faults!
Thanks again.
|
|
|
|
Post by ruairi on Jan 30, 2023 14:58:09 GMT
Looks like I spoke too soon - faults are back when ignition is off (as well as the control module software incompatible fault), and there is definitely no sound coming from the rear doors - and there's no fader option in the settings either:
OBDeleven data log
Date: 2023-01-30 13:35
VIN: WVWZZZ3CZJP001497
Car: Volkswagen Passat
Year: 2018
Body type: Variant
Engine: CRLB
Mileage: 55392 KM
---------------------------------------------------------------
5F Multimedia
System description: MU-S-ND-ER
Software number: 3Q0035874C
Software version: 0478
Hardware number: 3Q0035874C
Hardware version: H41
Serial number: VWZAZ2T1418338
ODX name: EV_MUStd4CTSAT
ODX version: 001022
Long coding: 02840201FF00000051110101008808001F0100F601200000CF
Subsystems:
System description: ABT_Std-2_Nav
Software version: 8130
Hardware version: H50
Serial number: VWZ6ZJT1720040
System description: ECE1 2023/24
Software version: 2010
Hardware version: ---
Serial number: --------------------
Trouble codes:
B200087 - Control module Software incompatible
static
Date: 2023-01-30 13:33:11
Mileage: 55392 km
Priority: 6
Malfunction frequency counter: 1
Unlearning counter: 137
Dynamic environmental data: 02867610030401016F6E6C696E6500
B106713 - Right rear bass speaker Open circuit
static
Date: 2023-01-30 13:31:59
Mileage: 55392 km
Priority: 6
Malfunction frequency counter: 1
Unlearning counter: 137
Dynamic environmental data: 028678
B106813 - Right rear treble speaker Open circuit
static
Date: 2023-01-30 13:33:06
Mileage: 55392 km
Priority: 6
Malfunction frequency counter: 1
Unlearning counter: 137
Dynamic environmental data: 028676
B106513 - Left rear bass speaker Open circuit
static
Date: 2023-01-30 13:31:59
Mileage: 55392 km
Priority: 6
Malfunction frequency counter: 1
Unlearning counter: 137
Dynamic environmental data: 028678
B106613 - Left rear treble speaker Open circuit
static
Date: 2023-01-30 13:33:06
Mileage: 55392 km
Priority: 6
Malfunction frequency counter: 1
Unlearning counter: 137
Dynamic environmental data: 028676
|
|
|
|
Post by dv52 (Australia) on Jan 30, 2023 21:10:46 GMT
OK - good valuable diagnostic information provided in your latest post that adds more pieces to the jig-saw puzzle!
Regarding your RVC dilemma - this is a more instructive view of the long-code string on your hex5F module:
Byte Hex Binary
00 02 00000010
01 84 10000100
02 02 00000010
03 01 00000001
04 FF 11111111
05 00 00000000
06 00 00000000
07 00 00000000
08 51 01010001
09 11 00010001
10 01 00000001
11 01 00000001
12 00 00000000
13 88 10001000
14 08 00001000
15 00 00000000
16 1F 00011111
17 01 00000001
18 00 00000000
19 E6 11100110
20 01 00000001
21 20 00100000
22 00 00000000
23 00 00000000
24 CF 11001111
Note: when reading my table - remember that Binary numbers are read from right-to-left. So the right-most digit in the Binary number is Bit 0 and the left-most digit is Bit 7.
The software switch that tells the hex5F module about the low-line version RVC is located on Byte 19, Bit 4. As you can read from my table, the value of Byte 19 is E6 (hexadecimal) and the equivalent Binary value is 11100110 - I've highlighted Bit 4.
So, as currently programmed, your hex5F module believes that it doesn't need to operate a low-line RVC. This setting is OK if the car has a high-line RVC installed, or if the car has NO RVC, at all!
It's easy to confirm if a high-line RVC is installed because your SCAN should report something like this:
---------------------------------------------------------------
6C Rear View Camera
System description: RVC Compact
Software number: 5Q0980556
Software version: 0170
Hardware number: 5Q0980556
Hardware version: H09
ODX name: EV_CamSysRVRVCPANAMQBAB
ODX version: 005007
Long coding: 0123060122002017000040
Trouble codes:
No trouble codes found
--------------------------------------------------------------- Note: your particular camera details might be different - but your SCAN should contain a "6C" module if a high-line RVC is installed.
Regarding the rear-speaker problem - hmm.......... yes, I agree with the conclusion of your "sleuthing" analysis that there might have been some speaker tinkering on this car in the past
As I have already said, the "Open circuit" descriptor suggests an issue with the physical speaker circuits. If you don't own a set of "keys" for removing the module from the glove-box (to check the rear quad-lock sockets), then maybe grab a multi-meter and check the impedance of the rear speakers. If these measure OK (low ohms) then, you will need to check the wiring/quad-connector.
Regarding the software version error - this is more problematic because OBD11 isn't likely to be able to fix this issue!!!
Don
|
|
|
|
Post by ruairi on Jan 30, 2023 22:26:54 GMT
Thanks Don, the more I dig the more bad I seem to find. I probably wouldn't have bought the car if I had realised how much the previous owner had messed around. It's very disheartening to have faults that you can't clear on the most expensive car you've ever owned. I've attached the history from yesterday before I managed to clear some of the codes, showing my full backup. There have been a few red flags such as Steering Assist (44) being added with the Autocoding function, and Parking Assist seems to be enabled in a few places though I'm pretty sure the car doesn't have it. There were also a lot of trailer/towbar options despite the car not having a towbar. I would love to reset everything to factory settings and start from a clean slate somehow but I don't think that's an option without a VW dealership or history of what the previous owner did. As you can see, I do indeed have the 6C control unit for the RVC - but when I set Byte 19 Bit 4 to E6 (not activated) the camera doesn't work at all (or at least the boot emblem doesn't open - I just get a black picture) - though I've read in some places that the Infotainment unit needs to be restarted for the camera to start working, so I may play about with this some more tomorrow. From what I can tell, all of the settings for both the highline/lowline RVC are/were activated. I just ordered the keys to remove the unit from the glovebox to check the plugs - so tomorrow I should have a better idea if its just a simple connection fault. If the plugs look fine then it's going back to the garage I bought it from for them to sort (fingers crossed). I can't see any tweeters in the rear doors when I shine a torch in, but it's difficult to see admittedly. I don't want to remove the door cards without first having a few extra clips on hand as I've had trouble with them breaking on other cars in the past. Lastly - as you mention and much to my dismay, the control module Software incompatible fault seems to be related to a failed update/multiple versions of firmware existing on the unit - again I can only assume this was the doing of the previous owner. I have seen some YouTube videos of people updating this with a sort of bootloader - but it might be a bit risky when there are no real symptoms otherwise. I very much appreciate your helpful and informative replies, thanks again. Attachments:history.txt (696.43 KB)
|
|
|
|
Post by dv52 (Australia) on Jan 30, 2023 23:27:42 GMT
hmm....... it must be my thick "Strine" (look it up) accent that's confusing - but I did say in my last response: So, as currently programmed, your hex5F module believes that it doesn't need to operate a low-line RVC. This setting is OK if the car has a high-line RVC installed, or if the car has NO RVC, at all! Since your SCAN reports a hex 6C module - leave Byte 19, Bit 4 = 0
Don
|
|
|
|
Post by ruairi on Jan 30, 2023 23:59:09 GMT
Yeah I will try it again tomorrow - it was activated intially as you can see from the history log, and is activated again at the moment because I just get a black image and the boot emblem doesn't swing open when I deactivate it and enable all the other highline settings/adaptations.
|
|
|
|
Post by ruairi on Jan 31, 2023 22:32:54 GMT
Keys didn't come today so speakers will have to wait until they do. I tried again with the RVC tonight. I tried to revert all the "lowline" coding/adaptations (byte 19-bit 4 as 0/not active in 5f, and other options inactive in Parking Assistance CU 66 - visual display/camera type/BAP/vehicle path display) and enable only the "highline" coding/adaptations (VPS_0X0B/VPS_0X0B_msg_bus/correspondence_HMI_RV_mode_~) according to posts on the forum, and restarted the MIB. What this results in is an additional "Function limited..." fault and no picture at all when I put the car into reverse - even though I can hear the camera opening on the tailgate. I feel that, assuming the camera is genuine/not dodgy, there is still some conflict between the 3 control units below in how the camera was configured when I got the car. At present, I get a picture and guidelines (and one Databus missing message fault), but no additional camera modes from the following settings ( dv52 (Australia) - I know that Byte 19 bit 4 should be 0 and other lowline settings are enabled in the below coding - but I get no picture at all without them at the minute and need to leave the car in a usable state for the wife, so I've reverted the settings to how they were before I started for now): 5F Multimedia System description: MU-S-ND-ER Software number: 3Q0035874C Software version: 0478 Hardware number: 3Q0035874C Hardware version: H41 Serial number: VWZAZ2T1418338 ODX name: EV_MUStd4CTSAT ODX version: 001022 Long coding: 02840201FF00000051110101008808001F0100F601200000CF Subsystems: System description: ABT_Std-2_Nav Software version: 8130 Hardware version: H50 Serial number: VWZ6ZJT1720040 System description: ECE1 2023/24 Software version: 2010 Hardware version: --- Serial number: -------------------- Trouble codes: B200087 - Control module Software incompatible static --------------------------------------------------------------- 6C Rear View Camera System description: RVC Compact+ Software number: 5Q0980568 Software version: 0100 Hardware number: 5Q0980568 Hardware version: H04 ODX name: EV_CamSysRVRVCARPANAMQBAB ODX version: 006008 Long coding: 01840201C2002011000040 Trouble codes: U112100 - Databus missing message static --------------------------------------------------------------- 76 Parking Assistance System description: PDC 8 Kanal Software number: 5QA919294B Software version: 0044 Hardware number: 5QA919294 Hardware version: H07 Serial number: 00030841861715800323 ODX name: EV_EPHVA18AU3700000 ODX version: 009035 Long coding: 0471151841 Trouble codes: No trouble codes found Would anyone be able to share their working long codes for these modules to help me pinpoint where the issue might lie? Thanks in advance! |
|
|
|
Post by dv52 (Australia) on Feb 1, 2023 2:55:03 GMT
So, there appear to be 3 x versions of this hex6C module: 5Q0980568, 5Q0980568A & 5Q0980568B. I don't know what the dataset in each version does, or how it differs for different makes/models
Anyhow, I found the module below from a discussion that I had on the Ross-Tech forum (a while ago, now - see HERE):
-------------------------------------------------------------------------------
Address 6C: Back-up Cam. (J772)
Part No SW: 5Q0 980 556 B HW: 5Q0 980 556 B
Component: RVC Compact H12 0231
Coding: 01840201A3002017000040
-------------------------------------------------------------------------------
If I compare the long-code strings on your module and the module above, I get this:
Byte Hex Binary Hex Binary
00 01 00000001 01 00000001
01 84 10000100 84 10000100
02 02 00000010 02 00000010
03 01 00000001 01 00000001
04 C2 11000010 A3 10100011
05 00 00000000 00 00000000
06 20 00100000 20 00100000
07 11 00010001 17 00010111
08 00 00000000 00 00000000
09 00 00000000 00 00000000
10 40 01000000 40 01000000
Note: your module is column 2 and 3 in my table
So, clearly the difference is Byte 04 & Byte 07
For Byte 04: - your module doesn't have Bit 0 set - I assume this is OK because your car doesn't have a towbar
- your module doesn't have Bit 5 set - I assume this is OK because your car doesn't have auto transmission
- your module has Bit 6 set - this is the software switch for a swinging logo.
I wasn't aware that these high-line cameras had a swinging logo!!
For Byte 07 - the software switches enable different " Correspondence_HMI_RV_Modes". Not sure how these work!
Don
|
|
|
|
Post by vwjap on Feb 1, 2023 8:05:40 GMT
dv52 (Australia)“For Byte 07 - the software switches enable different " Correspondence_HMI_RV_Modes". Not sure how these work!” These are different angles the highline camera displays, and put buttons on the right screen bar to change them, where the colour control is, but I’m not sure if this is what your asking
|
|
|
|
Post by ruairi on Feb 1, 2023 11:11:59 GMT
Thanks for the replies guys. So we know that the 6C coding is OK(ish) even though I can't seem to get rid of "databus missing message" from the RVC no matter what I disable/enable.
I've now set 5f byte 19 bit 4 to not active and VPS_0x0b to active and VPS_0x0b_msg_bus to comfort data bus and not getting any picture (not even a black screen) in park pilot/when shifting into reverse - I just see the parking sensor overlay full screen. Furthermore, I've got the function limitation fault again - current coding shown below - could it be that I have to select a different msg_bus?
5F Multimedia
System description: MU-S-ND-ER
Software number: 3Q0035874C
Software version: 0478
Hardware number: 3Q0035874C
Hardware version: H41
Serial number: VWZAZ2T1418338
ODX name: EV_MUStd4CTSAT
ODX version: 001022
Long coding: 02840201FF00000051110101008808001F0100E601200000CF
Subsystems:
System description: ABT_Std-2_Nav
Software version: 8130
Hardware version: H50
Serial number: VWZ6ZJT1720040
System description: ECE1 2023/24
Software version: 2010
Hardware version: ---
Serial number: --------------------
Trouble codes:
B200087 - Control module Software incompatible
static
U111100 - Function limitation due to missing message
static
---------------------------------------------------------------
6C Rear View Camera
System description: RVC Compact+
Software number: 5Q0980568
Software version: 0100
Hardware number: 5Q0980568
Hardware version: H04
ODX name: EV_CamSysRVRVCARPANAMQBAB
ODX version: 006008
Long coding: 01840201C2002011000040
Trouble codes:
U112100 - Databus missing message
static
---------------------------------------------------------------
76 Parking Assistance
System description: PDC 8 Kanal
Software number: 5QA919294B
Software version: 0044
Hardware number: 5QA919294
Hardware version: H07
Serial number: 00030841861715800323
ODX name: EV_EPHVA18AU3700000
ODX version: 009035
Long coding: 0471151841
Trouble codes:
No trouble codes found
|
|
|
|
Post by ruairi on Feb 1, 2023 18:15:00 GMT
Interestingly, an "interior camera" has appeared in the parking/maneuvering menu on the infotainment system, though it says function not available when I try to select it.
|
|
|
|
Post by dv52 (Australia) on Feb 1, 2023 23:03:34 GMT
.................. So we know that the 6C coding is OK(ish).................. Huh - I certainly don't know this!! Don |
|
|
|
Post by ruairi on Feb 1, 2023 23:55:29 GMT
Is there something else to consider other than the long coding you mentioned? EDIT: I'm being silly in assuming the coding you shared was confirmed as working, but I can't see what else I could change based on the coding/walkthroughs I've seen elsewhere. I will try some of the other VPS_0x0b_msg_bus settings tomorrow...
|
|
|
|
Post by ruairi on Feb 4, 2023 21:39:43 GMT
So I'm about to give up on the RVC and just live with the lowline functionality and the databus missing message fault. No matter what I change the VPS_0x0b_msg_bus to the outcome is the same... I'm starting to think it's just been wired incorrectly. I've been trying to find a wiring diagram for the highline cameras to confirm this but wasn't able to get great pictures tonight. There's a group of 3 red wires covered in insulating tape that seem to be for the camera and not sure there are any CAN connections. "Databus missing message" fault doesn't go away no matter what I disable in 6C either... When I set VPS_0x0b to activated I get an "additional camera" pop up in the Car menu (which says function not available when you try to select it) and Parking & Maneuvering settings - but still just the full screen OPS view and "Look!" message when in reverse/manually selecting Park Pilot via the dash button, as well as "Function limitation due to missing message" fault: Pics: photos.google.com/share/AF1QipPK40fE6vgBhPyKAVeP0P9beUX7QRt5Wgyjd23G2UW6v_TGUHQ1a_o8-It5l2bUCg?key=VXBuSDRVcTVoU0Jjeml3eDRjX2pzOGdSZThMMXFBI also finally checked the speaker wires according to your diagram above dv52 (Australia) and they look fine (also in pics above). Grasping at straws now but something I noticed was that the firmware for the MIB2STD is version 0478 - which is almost the most recent across all firmware series' (1xx, 2xx, 3xx, 4xx) - which makes me think this is something else that has been updated and may have caused issues with the speakers. Did some research into the MIB2 Toolbox (this will help me clear the Control module software incompatible fault too) and installing firmware so that could be my last resort if I can't find any other reason for the rear speakers not working/non existent fader sound setting. That, or find a local retrofitter and reluctantly throw some money at the problems. Latest scan with the settings/outcome mentioned above, if it is interest of to anyone. --------------------------------------------------------------- 5F Multimedia System description: MU-S-ND-ER Software number: 3Q0035874C Software version: 0478 Hardware number: 3Q0035874C Hardware version: H41 Serial number: VWZAZ2T1418338 ODX name: EV_MUStd4CTSAT ODX version: 001022 Long coding: 02840201FF00000051110101008808001F0100E601200000CF Subsystems: System description: ABT_Std-2_Nav Software version: 8130 Hardware version: H50 Serial number: VWZ6ZJT1720040 Trouble codes: U111100 - Function limitation due to missing message static --------------------------------------------------------------- 6C Rear View Camera System description: RVC Compact+ Software number: 5Q0980568 Software version: 0100 Hardware number: 5Q0980568 Hardware version: H04 ODX name: EV_CamSysRVRVCARPANAMQBAB ODX version: 006008 Long coding: 01840201C2002007000040 Trouble codes: U112100 - Databus missing message static --------------------------------------------------------------- 76 Parking Assistance System description: PDC 8 Kanal Software number: 5QA919294B Software version: 0044 Hardware number: 5QA919294 Hardware version: H07 Serial number: 00030841861715800323 ODX name: EV_EPHVA18AU3700000 ODX version: 009035 Long coding: 0471151841 Trouble codes: No trouble codes found --------------------------------------------------------------- |
|
|
|
Post by dv52 (Australia) on Feb 4, 2023 23:20:57 GMT
hmm........the long-code string on the hex6C remains unaltered
As I indicated in my previous response - if this camera module does NOT have a swinging logo (I don't think that it does), change Byte 04, Bit 6 to zero on the hex6C module.
Also, are the other software switches correctly set on the hex6C module - as per my previous reply
Don
|
|
|
|
Post by ruairi on Feb 4, 2023 23:39:06 GMT
Hi dv52 (Australia) - I assume the swinging logo is the camera inside the VW logo on the boot which opens when you put it in reverse - if so, it does indeed have this. All of the other settings are correct also - no towbar and manual transmission. |
|
|
|
Post by vwjap on Feb 5, 2023 8:40:33 GMT
2017 U.K. facelift with highline camera (programmed as a lowline) trailer assist and park assist 76 0B 71 16 71 51 6c 01 73 00 01 63 00 20 17 00 00 48 Mib2 std wiring      |
|
|
|
Post by ruairi on Feb 5, 2023 12:25:16 GMT
Thank you vwjap! When you say it's a highline coded as lowline, do you get the guidance lines and additional camera views (fisheye, trailer)? I'm going to get a closer look at the wiring as soon as I get a chance. For both highline/lowline, you have to set camera type to rear view in Parking Assistance CU (76) right? I'm trying to think of where there could be conflicts between the two configurations as I've seen some people just set VPS_0x0b settings without mentioning the gateway or parking assistance modules. |
|
|
|
Post by vwjap on Feb 5, 2023 12:43:58 GMT
So highline coding gives you different camera angles, and the speed with which the camera turns off, and a couple of other things that don’t matter
Lowline gives you no different camera angles, and the camera switches off the instant you take it out of reverse (giving you full screen guidance, which I personally prefer)
The bendy lines are set in the camera module, that’s why it needs a calibration, so no matter what coding they are there,
Don’t think i changed it to anything other than camera, and it works no matter if coded high or low
The only conflicts I get is when setting highline you have to switch off the lowline byte in 5f, and vice versa
|
|
