ozgti
New Member
Posts: 8 
|
Post by ozgti on Dec 7, 2016 23:05:41 GMT
Hi All,
Anyone have clue as to what this is.....only started showing recently....no info on google from what I can see
19 Gateway
System description: GW MQB High
Software number: 5Q0907530AJ
Software version: 1244
Hardware number: 5Q0907530F
Hardware version: 128
Serial number: 0004571055
ODX name: EV_GatewLear
ODX version: 013020
Long coding: 030100343F085900FB00027E9C0F00010001050000000000000000000000
Subsystems:
System description: J367-BDMHella
Software version: 8050
Hardware version: H04
Serial number: 0440389403
System description: E221__MFL-DC1
Software version: 0040
Hardware version: H11
Serial number: 29160000385600106081
Long coding: 2DFFFF
Trouble codes:
U006500 - Vehicle Communication Bus E Performance
Intermittent
Malfunction frequency counter: 1
Terminal 15: Off
Supply voltage, terminal 30: 12.4 V
Unlearning counter: 14
Date: 2016-11-26 12:20:38
Mileage: 4960 km
Unknown ambient data:
Priority: 2
Regards
Jason
|
|
ozgti
New Member
Posts: 8
|
Post by ozgti on Dec 8, 2016 2:24:00 GMT
|
|
|
|
Post by dv52 (Australia) on Dec 8, 2016 21:45:31 GMT
Ozgti:Interesting trouble code!!
Have you tried clearing the DTC and seeing if it returns (the fault-frequency is 1 - so the error hasn't re-appeared in any ignition cycle since 26 November)? Were you doing anything to the car @ 2016-11-26 12:20:38? Go back to your History file and look for any changes to the Central electrics control module around (and before) this date. If you find anything remotely related - consider reverting the setting to the original value.
Don
|
|
|
|
Post by akhzari on Dec 8, 2016 23:34:30 GMT
Same error, only today connected so no changes are made.
U006500 - Vehicle Communication Bus E Performance
Intermittent
Terminal 15: Off
Supply voltage, terminal 30: 12.5 V
Unknown ambient data:
Date: 2016-11-18 21:08:48
Malfunction frequency counter: 2
Unlearning counter: 81
Mileage: 332 km
Priority: 2
Vehicle Communication Bus E Performance - What does this mean?
|
|
ozgti
New Member
Posts: 8
|
Post by ozgti on Dec 12, 2016 3:29:07 GMT
Hi Don
Yes I am sure I have cleared it twice previously ....thats why I am curious as to what it could be.
Everything seems normal on the car and also I dont have any warning lights or anything like that.
Might just have to go through all changes made and see if any dates match around original date of first event.
Interesting that a Akhzari had same code.....wonder if it is a software issue withe OBD11 unit?
|
|
|
|
Post by dv52 (Australia) on Dec 12, 2016 6:03:48 GMT
Hi Don Yes I am sure I have cleared it twice previously ....thats why I am curious as to what it could be. Everything seems normal on the car and also I dont have any warning lights or anything like that. Might just have to go through all changes made and see if any dates match around original date of first event. Interesting that a AkhzariAkhzari had same code.....wonder if it is a software issue withe OBD11 unit? ozgti: Yes it is coincidental - compare your history file with that of Akhzari. (see the thread "Help to understand what the problem is " - see if you both implemented the same Apps/manual tweaks
Don
|
|
|
|
Post by aguscalderon on Feb 10, 2017 6:58:43 GMT
Did you found what this is about? I have the same error code on a seat leon my16 before any change was made  |
|
pede
New Member
Posts: 2
|
Post by pede on Oct 13, 2018 19:59:30 GMT
Hi
I have the same problem, anyone knows what it is. error code U0006500?
|
|
|
|
Post by ofektal8 on Oct 14, 2018 22:44:06 GMT
Im pretty sure this happend to me after tapping to the headunit can wires.
|
|
pede
New Member
Posts: 2
|
Post by pede on Oct 15, 2018 18:33:14 GMT
I have a aftermath headunit.Just do not know how long I've had the error code. So you may be right. Thank you.
|
|
|
|
Post by ofektal8 on Oct 15, 2018 22:32:43 GMT
It shouldnt stay, after I Tapped into the CAN Wires i saw that fault, but next time i turned the car on it was gone.
|
|
mu81n
New Member
Posts: 17
|
Post by mu81n on Mar 15, 2021 0:44:43 GMT
Any resolution to this dtc? This dtc appeared after I installed RNS315 and obdeleven automatically chose my installation list within channel 19.
|
|
|
|
Post by NOSCAR on Jan 6, 2023 2:04:02 GMT
...
|
|
1en1
New Member
Posts: 1
|
Post by 1en1 on Feb 17, 2023 17:06:27 GMT
Hi guys!
I need real help…
I think a messed up with the MMI, the screen wasn’t poping up after the ignition… [ I had to switch it on every time besides leaving it on when I switched off my car (A3 2013 8v) ]
I restarted the system with the 3 button push aaaaand… bum
Now it is dead….
Yesterday a went to Audi and they said to rewrite the data on the MMI hoping it would pick up… if not I had to change “the stereo”
Before the MMI I had a crash, nothing to bad as it could have resulted, but my left headlight and windshield watertank cracked. So I’ve got the warning to fill up the tank on my dash.
I did no modifications yet with my OBD, so I’ve got no history before this:
O BDeleven vehicle history log
Date: 2023-02-17 13:57:11
VIN: WAUUYC8V5DA067802
Car:
Year: 2013
Body type: UNKNOWN
Engine: CMBA kW ( hp) l
Mileage: 150437 km
---------------------------------------------------------------
09 Central Electrics
System description: BCM MQBAB H
Software number: 5Q0937084Q
Software version: 0106
Hardware number: 5Q0937084Q
Hardware version: H14
Faults:
B126301 - Tank lid unlock activation
Electrical error
static
Priority - 4
Malfunction frequency counter - 1
Unlearning counter - 79
km-Mileage - 150348 km
Unknown ambient data - 000100809D
Terminal 15 status - Off
Terminal 50 status - Off
Voltage - 12.8 V
Outside air temperature - 28.5 °C
Status Bremslichtschalter (HW) - Off
Status Bremslichtschalter (CAN) - Off
Off - operated
Parking light - not activated
Automatic high beam assist - not activated
Low beam - not activated
Parking light left - not activated
Parking light right - not activated
Stoerschutzzaehler - 0
date - 2023-02-16 15:10:20
---------------------------------------------------------------
17 Dashboard
System description: KOMBI
Software number: 8V0920870
Software version: 0570
Hardware number: 8V0920870
Hardware version: H24
Faults:
U111000 - Function restriction due to communication interruption
static
Priority - 6
Malfunction frequency counter - 1
Unlearning counter - 79
km-Mileage - 150348 km
date - 2023-02-16 15:09:23
U111000 - Function restriction due to communication interruption
static
Priority - 6
Malfunction frequency counter - 1
Unlearning counter - 79
km-Mileage - 150348 km
date - 2023-02-16 15:09:23
U111000 - Function restriction due to communication interruption
static
Priority - 6
Malfunction frequency counter - 1
Unlearning counter - 79
km-Mileage - 150348 km
date - 2023-02-16 15:09:23
---------------------------------------------------------------
19 Gateway
System description: GW MQB High
Software number: 5Q0907530J
Software version: 1126
Hardware number: 5Q0907530F
Hardware version: 125
Faults:
U006500 - Vehicle Communication Bus E
Performance
static
Priority - 2
Malfunction frequency counter - 1
Unlearning counter - 79
km-Mileage - 150348 km
Supply voltage, terminal 30 - 13.5 V
Terminal 15 - On
Unknown ambient data -
date - 2023-02-16 15:09:20
|
|
|
|
Post by dv52 (Australia) on Feb 17, 2023 21:51:43 GMT
It's a pity that only part of your SCAN report has been provided in your post!! I suspect that many folk truncate their SCAN so as not to make their post too long - alas, this practice is invariably antithetical (look it up) to the prime objective when writing posts; this objective being to provide diagnostic information in the hope that a problem can be fixed!! It may not be evident to those writing posts, but for those of us trying to make sense of what's happened to a car- there is much that can be gleaned from providing a FULL (meaning - completely unedited) SCAN report. These FULL reports contain valuable information in apparently unconnected fault data that can be instrumental in successfully diagnosing problems. If you want to make your post pretty and short - it's far better-er to simply add the FULL SCAN report as an attachment (IMO, of course)!!  OK, rant over - let's discuss your particular problem.
I'm fairly sure that the fault Vehicle Communication Bus E -refers to what MQB platform cars (like your Audi A3 8V) call the "Extended CAN bus". Not all MQB vehicles have this CAN bus - but I note that this car has a High version Gateway module, so this car does have this bus. The Extended CAN bus contains most of the modules allocated to the driver assistance systems and the high-level topology of this bus looks like this:
As you can see, the master-module (meaning the coordinating module) for the E bus is J533 - this is the module that OBD11 identifies as the Gateway module in your SCAN report. This explains why the U006500 error appears in the hex19 module.
As is also evident from the diagram, the E bus controls "extended" lighting functions in the headlight fittings - like AFS style Cornering lights and dynamic light assist function- and it also manages the front camera for driver assist systems (R242)
Now, I'm not sure what driver assist systems have been installed on this car because the SCAN is incomplete - but I suspect from your words "I had a crash, nothing to[o] bad..........but my left headlight..cracked" that the Gateway fault is related to what Aussie Strine (again, look it up) calls the "bingle"!!
Finally - I make no comment on your particular question about the MMI because this module is also missing from the SCAN (it's the module that lives @ address hex5F on the CAN network)
It's unlikely (but it's possible) that the MMI problems are related to the Gateway fault. Notice that this module is absent from my picture above (it's call "J794" in the CAN diagrams) - however, since no diagnostic information has been provided about the MMI, I'd rather not make any comment about this matter
Finally, there's a fundamental inconsistency in your words: - "I think a messed up with the MMI, the screen wasn’t poping up after the ignition", AND
- "so I’ve got no history before this"
I assume that the first statement means that coding changes of some type were made to the hex5F module - So your History records should contain information about these changes! Please post-up these records
Don
|
|
|
|
Post by balooski on May 21, 2024 15:24:12 GMT
Hi folks!
Did you ever get this figured out? I have the same symptom on my car, of the MMI not turning on with ignition.
Then it wouldn't turn on at all. I pressed and held the eject button for a few seconds, and it came back on. But still, won't turn on with ignition. Everything else seems to function correctly. I'll gladly post a VSR if it will help.
A few missing message DTC's and the same Bus E missing message as above.
I'm thinking either my gateway is dying, or the MIB1 is. Question is, how do I even diagnose this?
|
|
