|
|
Post by prefatcher on Mar 17, 2024 14:45:35 GMT
Hello, I stumblde on a problem during my parking sensors retrofit..... Every thing is connected but have a problem on dash when trying to activate ParkPilot with button.  Buton working as you can see from picture above. __________________________________________________________________  Menu for ParkPilot working as well... buzzers giving fead back when changing volume __________________________________________________________________   But when I press ParkPilot button or change my gear to "Reverse" I get an error "ParkPilot currently unavailable" on my infotainment screen as well on my dash as shown above. __________________________________________________________________  Connection to parklift module possible, changing coding possible as well... __________________________________________________________________  I checked live fault codes and get error above with "DataBus" Also things that were changed: Coding 19 CAN Gateway - Installation List - 10 Park/Steer Assist 5F Infotainment - Adaptation - set all to active Vehicle function list - BAP-parking_assist_0x0A - Vehicle menu operation-menu_display_pdc Vehicle menu - Operation-menu_display_pdc_over_threshold_high Does any one have any clue what could the problem be here? Im kinda stuck, any help would be highly appreciated  Note: This is my "testing" phase before drilling holes in my bumpers so wiring looms are connected to sensors but are on layed on the ground.... car is disassembled, seats are not present in the car and battery was disconnected a few times thats why so many light on dash I was thinking maybe I should put everything togather and clear all faults and try again as as a lot of systems dont work when you disconnect tha battery untill you go for a ride... hmmm any thoughts? I just dont want to drill holes in my bumper than find out out that parking system doesnt work |
|
|
|
Post by mathi9020010 on Mar 17, 2024 17:06:53 GMT
Update your vcds Software and you see where the Error is Coming from.
You did Code the pdc Module + 5F?
Any other?
|
|
|
|
Post by prefatcher on Mar 17, 2024 17:38:48 GMT
Hi mathi9020010 , Error is coming from PDC module: PDC module - fault codes and than mentioned error is displayed:  Just for info if i clear faults and rescan it only mentioned error above comes back in PDC module and "error:ParkPilot" is displayed again on dash PDC module was coded: Byte 1:  Byte 2:  Byte 3:  Byte 4:  5F as mentioned above: (changed to active) Vehicle function list - BAP-parking_assist_0x0A - Vehicle menu operation-menu_display_pdc - Operation-menu_display_pdc_over_threshold_high and also: 19 CAN Gateway - Installation List - 10 Park/Steer Assist should this be activated only if youi have automatic parking? because i only have normal 8 OPS without automatic parking...? |
|
|
|
Post by dv52 (Australia) on Mar 17, 2024 20:32:18 GMT
19 CAN Gateway - Installation List - 10 Park/Steer Assist should this be activated only if youi have automatic parking? because i only have normal 8 OPS without automatic parking...? Yes, you need to tell the Gateway module to start including the hex10 module into CAN network communications- this is done by ticking the box for 10 Park/Steer Assist in the Gateway Installation List (GIL).
The matter of whether the version hex10 module is either Park Pilot (your installation), or Park Assist (what you call "automatic parking") is determined by the module itself and how it's coded. However, in BOTH versions the hex10 module MUST be ticked in the GIL.
Maybe mathi9020010 has a better answer - but from my quick look at your long-code string, I suggest that you set Byte 04, Bit 6 = 0. Yes, I assume that you set this Bit because this car has Start/Stop - however by setting this Bit, you will use the internal version software within the hex10 module for this function, rather than external version software within the car's EMS (Energy Management System) that is used on MQB platform cars (like this Golf). So, I suggest that you turn-off the Start/Stop software within the hex10 module.
Don
PS: I think that I can guess why this VCDS cable is using out-of-date software (naughty you!!)
|
|
|
|
Post by prefatcher on Mar 18, 2024 16:17:41 GMT
Hi dv52 (Australia)Start/stop function on Byte 04 set to Bit 6 = 0 but the problem insists... tryed to check voltage on all sensors they all get around 11.5V and resistance between GND and power pin on all sensors is around 2,5 MΩ I guess that is OK.... this problem is driving me crazy  Maybe updaiting firmware will change anything? PS: that will be our little secret   |
|
|
|
Post by dv52 (Australia) on Mar 18, 2024 20:05:11 GMT
prefatcher : OK - our "little secret" it shall be!!
Post-up an unedited copy of an auto-scan and let's see how this car was factory built
Don
|
|
|
|
Post by prefatcher on Mar 18, 2024 21:50:31 GMT
dv52 (Australia) thank you for your time, scan in attachment.. Just a reminder that battery was disconnected so there are a lot of fault... car is without seats so faults on airbags from that...front and back bumper are off the car and both rear lights are disconnected, currently doing "testing phase" so sensors are connected but on the ground and not yet installed.
This 2 faults under 76 Pakring Assistant are not valid because I disconnected this two sensors to measure voltage and resistance:B107914 - Right rear park assist sensors Open circuit/short circuit to ground Intermittent B10F714 - Left front park assist sensor Open circuit/short circuit to ground Intermittent This one is present always and comes back even if I clear faults under : U112300 - Databus error value received
staticI have googled this fault and it can come back as "bad connection" I connected PDC-s power to light switch T10h pin 4 (black/yellow) as it is connected straight to fuse SC34...I splintered the wire and add another one to it using heat shrink with a little solder in the middle so maybe connection is not the best... will redo the connection with proper soldering tomorrow but I think powering the module itself is not a problem as it is working normally and can access it and code it. I was wondering maybe ParkPilot is not working due to battery being disconnected just like ACC and other system untill you go for a ride and restart car couple of times...hmmm Attachments:OBDeleven_Log.txt (5.16 KB)
|
|
|
|
Post by dv52 (Australia) on Mar 19, 2024 21:35:05 GMT
@prefactcher: hmm......... no offense intended - but your SCAN is a tad messy!! Clearly there's lots happened to this car! Obviously you have both VCDS and OBD11! I'm not sure if you have compared the two - but while both diagnostic devices have their individual merits and disadvantages- the quality of OBD11's SCAN reports is NOT one of its good points (IMO, of course). Examples of the deficiency of OBD11's report include: - The version of the SCAN report in your attachment fails to disclose the module's long-code string.
- OBD11 users must manually enable the Freeze-frame data facility (VCDS does this as default).
- The summary module list at the top of the VCDS report is missing in OBD11 scans. This is more of a nice-to-have facility rather than an outright deficiency. Nevertheless, it's a handy-dandy quick reference guide to the health of the car in general - very nice indeed!!
So - please do the following and post a fresh SCAN: - Enable Freeze-frame data on your OBD11 account - see HERE
- Clear ALL faults prior to making the new SCAN so we get ONLY the current problems. Don't worry about the past errors - OBD11 will retain a copy of historic reports
Don
|
|
|
|
Post by prefatcher on Mar 20, 2024 15:34:24 GMT
I cleared all faults and rerun scan on VCDS, scan in attachment....Im sorry I cant provide you with better scan results as this is current state of my car:  Im just waiting for it to explode at this point I got some other instructions on coding when retrofiting 8 OPS I will leave it in attachment as well.. I followed it but problem still insists... I coded all as in instructions but cant find: 19 CAN-Gateway → Adaption →installation list; specified installationns-ParkingAssistance In instructions it says it needs to be set to "coded" but I cant find it even with search option... Could this be the problem? Instructions too big so I just screened it :  Red square: cant find  Attachments:log.txt (21.66 KB)
|
|
|
|
Post by dv52 (Australia) on Mar 21, 2024 1:00:18 GMT
Im just waiting for it to explode at this point " " I too hope that the loose stools in the brown stuff don't collide with the fan blades!!
I am impressed with your picture. It clearly shows the amount of work that you have obviously put into this project - respect!! So- with my apology if you already know this stuff but VCDS and OBD11 report the module that you call "Parking Assistance" differently - like this: - OBD11 calls this module Parking Assistance and it identifies the module as living at address hex76 on the CAN network
- VCDS calls this module Park/Steer Assist and it identifies the module as living at address hex10 on the CAN network
I have no idea why this happens - but if you look at your 2 x SCANs, you will see that the module details are the same despite the module having 2 x different identifiers! Also, if you look at the hex10 module on your latest SCAN (from VCDS) - notice that the 2 x Open circuit/short circuit to ground errors that were on the hex76 module on your earlier SCAN (from OBD11) are no longer present. These errors were generated during the install/testing part of your project and they were deleted when you "cleared all faults and rerun scan on VCDS"!
I got some other instructions on coding when retrofiting 8 OPS I will leave it in attachment as well.. I followed it but problem still insists... I coded all as in instructions but cant find: 19 CAN-Gateway → Adaption →installation list; specified installationns-ParkingAssistance In instructions it says it needs to be set to "coded" but I cant find it even with search option... Could this be the problem? This is a problem that doesn't exist - because the Parking Assistance (Park/Steer Assist) module is already registered in the Gateway Installation List (GIL). If the module was NOT in the GIL - it wouldn't be successfully reported in your SCAN reports! If you want to check - do this with VCDS: - Ignition ON, Engine-OFF
- Fire-up VCDS and connect to the dongle
- From the Select Control Units screen, click 19-CAN Gateway
- On the screenshot below - select Installation List
- Check that the box for module 10- Park/Steer Assist is ticked
 As a way forward for this problem - this is a more convenient view of the long-code string on the 10-Park/Steer Assist module from the VCDS SCAN:
Byte Hex Binary
00 04 00000100
01 31 00110001
02 15 00010101
03 11 00010001
04 11 00010001
Remember that Binary numbers are read from right-to-left. This means that Bit 0 is the right-most digit and Bit 7 is the left-most digit
I don't like these 2 x coding values: - Byte 00, Bit 2 =1 - setting this Bit tells the module that this car has Hybrid/Electric drive
- Byte 03, Bit 0 =1 - setting this Bit tells the module that this car has a manually removable trailer hitch. However, the SCAN does NOT report that this car has a trailer module
So, I suggest that you change the long-code string on the 10-Park/Steer Assist module as follows: - Byte 00 =hex00=00000000
- Byte 03=hex10=00010000
After the change, clear all faults and check that the module is error free
Don
|
|
|
|
Post by prefatcher on Mar 21, 2024 15:23:04 GMT
Reporting back, I can confirm that 19-CAN Gateway → Installation List 10 →Park/Steer Assist is indeed ticked. I changed coding values as you instructed: - Byte 03=hex10=00010000, where coding was accepted. But when I tried to change: - Byte 00 =hex00=00000000  VCDS comes back with some kind of error: "Coding rejected" "Error 31: Request out of range":  It doesnt let me code it, I tried to put in 16-Security Access: number 71679 or 20103 still same error. I cleared all faults and rescan. Previously we had 2 faults in PDC module, now only one insists same as before which is probably correlated with that Byte 00 of Bit 2 set to 1.  I was thinking....this PDC modules OEM number is 5QD 919 294 H I got this PDC module from sbadyard (lol c r a p is censured) but dont know what kind of drive (Hybrid/electric or normal) was present in car in which I got this module from. Maybe Volkswagen made it so there are different PDC modules for different kind of drives.....Maybe last number in OEM number correlates to different characteristics of PDC module and whith which car it is compatible with. Maybe that byte 00 is hard coded so you cant change it or am I wrong? In that case I would have to buy another module with correct last letter for my type of car or if it is possible to flash current one some how hmmmm...... |
|
|
|
Post by dv52 (Australia) on Mar 21, 2024 23:34:26 GMT
prefatcher : Well done - at least you are moving in a forward direction and the error codes are reducing in number!!
Yes, I like your thinking about the possible significance of "H" on your module part number. Extrapolating your hypothesis, my hunch is that the dataset in this module might well be intended for a Hybrid/Electric drive (dataset=firmware in VW speak) and this is the reason why coding change to Byte 00 is prohibited.
If it's possible - I suggest that you visit the spare-parts department for your local VW dealer and enquire whether your hypothesis is correct. Please advise your finding (I'm interested)
Don
a
|
|
|
|
Post by prefatcher on Mar 22, 2024 19:54:37 GMT
Today I talked via mail with authorized VW dealer here in Slovenia and of course they couldent help me with more "technical" question as I assumed.....but they did provide me with this:     Im sorry but its not in english. All parts for parking from brackets for sensors to sensors and PDC modules but no description or meaning for last letter in OEM code. Only thing that catched my eye was:  I guess last letter indicates from when to when different modules were installed in cars (I guess each year different letter) ... but have no idea if modules are tha same or different in any kind....But there is more, I have a coworker who drives golf 7 with parking sensors from factory normal 8K not PLA..... I begged him for me to connect to his OBD port and just check OEM number of his PDC module.... after some back and forth he agreed (Now I own him lunch ) ...I connected to his car and can confirm that his PDC module OEM number is 5Q0 919 294 K and was coded 0031151011 (without 04 in front).... I guess im off to buying a new PDC module.... I will report back when I get a new PDC module |
|
|
|
Post by golf75retrofit on Apr 14, 2024 15:40:38 GMT
Have a look in the addaptions of your 76 module. There's one called eCall Mute, try setting that to Not activated and see if your error disappears.
Seems to be an adaptation channel on newer PDC/PLA modules.
Took me ages comparing adaptation channels on our other MK7 to figure out what was causing the fault.
|
|
