2007 Audi Q7 MMI Problems

   #1  

BostonSlaya

Verified VCDS User
Verified
Joined
Mar 4, 2015
Messages
337
Reaction score
88
Location
Rhode Island, USA
VCDS Serial number
C?ID=240768
I purchased my wife a Q7 for X-Mas CHEAP! I knew it had and MMI Problem but car runs fantastic... So I thought hey I have gone through a lot with my Audi A8 I'll tackle this lol.. SO with this said I tried to run a complete AutoScan and I cannot at all, It starts then it just cuts out and tells me that failure to communicate (-99)... I have made sure my power management in the computer is good and also check USB Hub to make sure that it was not enabled to power out. Anyways I had some success with the dataBus check and this is what I got below. I could really use some guidance on getting this MMI to work. I unplugged the Fiber lines from several modules in the back boot like the navigation and so on and put a Loop on it, there is not normal red light coming from any of them at all. I have been looking everywhere online with no luck. I would love to post a full AutoScan but I'm not sure what's going on with that or I would have. If I can get some people to shine some light that would be great, thanks so much....



Code:
Thursday,22,December,2016,18:46:15:14758
VCDS -- Windows Based VAG/VAS Emulator Running on Windows 10 x64(Parallels)
VCDS Version 16.8.4.2 (x64)
Data version: 20161129 DS267.0
www.Ross-Tech.com





--------------------------------------------------------------------------------
--------------------------------------------------------------------------------


Control Module Part Number: 4L0 910 468 
  Component and/or Version: J533__Gateway   H06 0040

Optical Bus Diagnostic : Standard

Controller          	Electrical          	Optical             
19-CAN Gateway      	OK                  	OK                  
07-Control Head(High/D3)	OK                  	OK                  
0E-Media Player 1   	OK                  	OK                  
47-Sound System     	ERROR               	ERROR               
56-Radio            	OK                  	OK                  
37-Navigation       	OK                  	ERROR               
0F-Digital Radio(SAT)	OK                  	OK                  

************************************************************
 
   #2  

Uwe

Benevolent Dictator
Administrator
Joined
Jan 29, 2014
Messages
49,245
Reaction score
33,795
Location
USA
VCDS Serial number
HC100001
How about just the Gateway Installation List? There's a button for that on the Auto-Scan screen.

-Uwe-
 
   #3  

BostonSlaya

Verified VCDS User
Verified
Joined
Mar 4, 2015
Messages
337
Reaction score
88
Location
Rhode Island, USA
VCDS Serial number
C?ID=240768
Sorry I should have mentioned the gateway installation list does show up fine without a problem
 
   #4  

Uwe

Benevolent Dictator
Administrator
Joined
Jan 29, 2014
Messages
49,245
Reaction score
33,795
Location
USA
VCDS Serial number
HC100001
   #5  

BostonSlaya

Verified VCDS User
Verified
Joined
Mar 4, 2015
Messages
337
Reaction score
88
Location
Rhode Island, USA
VCDS Serial number
C?ID=240768
Also when I try to clear all the DTCs at once it also will disconnect and say not supported
 
   #6  

BostonSlaya

Verified VCDS User
Verified
Joined
Mar 4, 2015
Messages
337
Reaction score
88
Location
Rhode Island, USA
VCDS Serial number
C?ID=240768
Code:
Gateway Installation List:  4L0 910 468 

00-Steering Angle Sensor -- Status: OK 0000
01-Engine -- Status: OK 0000
02-Auto Trans -- Status: OK 0000
03-ABS Brakes -- Status: OK 0000
05-Acc/Start Auth. -- Status: OK 0000
07-Control Head -- Status: Cannot be reached 1100
08-Auto HVAC -- Status: OK 0000
09-Cent. Elect. -- Status: OK 0000
0E-Media Player 1 -- Status: Cannot be reached 1100
0F-Digital Radio -- Status: Cannot be reached 1100
15-Airbags -- Status: OK 0000
16-Steering wheel -- Status: OK 0000
17-Instruments -- Status: OK 0000
19-CAN Gateway -- Status: Malfunction 0010
36-Seat Mem. Drvr -- Status: Malfunction 0010
37-Navigation -- Status: Cannot be reached 1100
3C-Lane Change -- Status: OK 0000
42-Door Elect, Driver -- Status: OK 0000
46-Central Conv. -- Status: OK 0000
47-Sound System -- Status: Cannot be reached 1100
4F-Centr. Electr. II -- Status: OK 0000
52-Door Elect, Pass. -- Status: OK 0000
55-Headlight Range -- Status: OK 0000
56-Radio -- Status: Cannot be reached 1100
61-Battery Regul. -- Status: Malfunction 0010
62-Door, Rear Left -- Status: OK 0000
65-Tire Pressure -- Status: Cannot be reached 1100
6D-Trunk Elect. -- Status: Malfunction 0010
6F-Centr. Conv. II -- Status: Malfunction 0010
72-Door, Rear Right -- Status: OK 0000
77-Telephone -- Status: Cannot be reached 1100
 
   #8  

Uwe

Benevolent Dictator
Administrator
Joined
Jan 29, 2014
Messages
49,245
Reaction score
33,795
Location
USA
VCDS Serial number
HC100001
Interesting. There's one module that "Cannot be Reached' that's not on the optical bus, e.g. 65-Tire Pressure, but the rest looks more-or-less as I'd expect for a car with a broken MOST ring.

At what point does the Auto-Scan cut out and give you failure to communicate?

Have you got a battery charger connected to it? Or at least letting the engine run?

Also, can you run a full scan on your A8 with the exact same VCDS setup (same computer, same interface)?

Yes, I'm grasping at straws here, 'cause there's nothing super-obvious.

-Uwe-
 
   #9  

Jack@European_Parts

Gone But Not Forgotten
Professional VCDS User
Joined
Jan 29, 2014
Messages
21,923
Reaction score
9,308
Location
Montgomery, NY, USA
VCDS Serial number
C?ID=57337
Can you enter any modules individually by hex address?

Please try and report back.........

What is latency setting of interface or USB drivers when tested/observed?
 
   #10  

BostonSlaya

Verified VCDS User
Verified
Joined
Mar 4, 2015
Messages
337
Reaction score
88
Location
Rhode Island, USA
VCDS Serial number
C?ID=240768
Interesting. There's one module that "Cannot be Reached' that's not on the optical bus, e.g. 65-Tire Pressure, but the rest looks more-or-less as I'd expect for a car with a broken MOST ring.

At what point does the Auto-Scan cut out and give you failure to communicate?

Have you got a battery charger connected to it? Or at least letting the engine run?

Also, can you run a full scan on your A8 with the exact same VCDS setup (same computer, same interface)?

Yes, I'm grasping at straws here, 'cause there's nothing super-obvious.

-Uwe-
The tire pressure is because I pulled the fuse out earlier. Yes I had a battery charger connected and the car running. I'll go run a full auto scan on mine and see what happens now. I'll be back with an answer in about 5 mins. Thanks so much for your help really.
 
   #11  

BostonSlaya

Verified VCDS User
Verified
Joined
Mar 4, 2015
Messages
337
Reaction score
88
Location
Rhode Island, USA
VCDS Serial number
C?ID=240768
OK So I went to run a full AutoScan on my A8 and same thing. I uninstalled VCDS and the reinstalled and still does the same thing. This is so odd because I used this computer from day one!! I know what I could do maybe, I could use my Crista Bluetooth to do a full AutoScan and post it maybe that would help. I wish I had another computer for this to try with but I don't. I wish VCDS worked for a Mac lol..

Oh P.S It cut's out right at o1 Engine


Interesting. There's one module that "Cannot be Reached' that's not on the optical bus, e.g. 65-Tire Pressure, but the rest looks more-or-less as I'd expect for a car with a broken MOST ring.

At what point does the Auto-Scan cut out and give you failure to communicate?

Have you got a battery charger connected to it? Or at least letting the engine run?

Also, can you run a full scan on your A8 with the exact same VCDS setup (same computer, same interface)?

Yes, I'm grasping at straws here, 'cause there's nothing super-obvious.

-Uwe-
 
   #12  

BostonSlaya

Verified VCDS User
Verified
Joined
Mar 4, 2015
Messages
337
Reaction score
88
Location
Rhode Island, USA
VCDS Serial number
C?ID=240768
OK Here is a full scan from Carista

Code:
ECU info obtained with Carista 330099 for iOS:

VIN: WA1BY74L27D066562

CAN network gateway
Part #: 4L0910468
Coding: E5D7BE77343A02 (hex)
Component: J533__Gateway
Fault codes:
00384 Optical Databus

Engine
Part #: 03H906032BG
Coding: 1175 (decimal)
Component: Q7 3.6-FSI-LEV2
[No fault codes]

Engine (2)
[failed to connect]

Engine (3)
[failed to connect]

Transmission
Part #: 4L0910156C
Coding: 2 (decimal)
Component: AG6 0AT 3,6 FSI
[No fault codes]

ABS
Part #: 4L0910517A
Coding: 33809 (decimal)
Component: ESP ALLR
[No fault codes]

Brake booster
[failed to connect]

Parking brake
[failed to connect]

Power steering
[failed to connect]

Steering angle
[failed to connect]

Active steering
[failed to connect]

Steering wheel
Part #: 4F0910549
Coding: 2042 (decimal)
Component: Lenksäulenmodul
[No fault codes]

Airbags
Part #: 4L0910655A
Coding: 14131 (decimal)
Component: 73 AIRBAG AUDI8R
[No fault codes]

Instrument cluster
Part #: 4F0910930C
Coding: 2641268 (decimal)
Component: KOMBIINSTR. M73
[No fault codes]

Infotainment display
[failed to connect]

Infotainment display (front)
[failed to connect]

Infotainment display (rear)
[failed to connect]

Infotainment display (rear left)
[failed to connect]

Infotainment display (rear right)
[failed to connect]

Infotainment display (roof)
[failed to connect]

Navigation
[failed to connect]

Voice control
[failed to connect]

Radio
[failed to connect]

Digital radio
[failed to connect]

Satellite radio
[failed to connect]

Sound system
[failed to connect]

Media player
[failed to connect]

Media player
[failed to connect]

Media player
[failed to connect]

Media player
[failed to connect]

TV tuner
[failed to connect]

Digital TV tuner
[failed to connect]

Infotainment system
[failed to connect]

Infotainment system 2
[failed to connect]

Telephone
[failed to connect]

Immobilizer
[failed to connect]

Towaway protection
[failed to connect]

Headlight aiming
Part #: 4F0910357F
Coding: 21 (decimal)
Component: AFS 1
[No fault codes]

Left headlight
[failed to connect]

Right headlight
[failed to connect]

Tire pressure monitor
Part #: 4F0910273B
Coding: 62424 (decimal)
Component: Reifendruck 3
Fault codes:
01833 Antenna for Tire Pressure Monitoring, Rear (R96)

Tire pressure monitor
[failed to connect]

Heater & air conditioning
Part #: 4L0910043
Coding: 524326 (decimal)
Component: KLIMABETAETIGUNG
[No fault codes]

Rear heater & A/C
[failed to connect]

Auxiliary heater
[failed to connect]

Auxiliary heater
[failed to connect]

Parking sensors
[failed to connect]

Parking/steering assist
[failed to connect]

Auto-leveling suspension
[failed to connect]

All-wheel-drive system
[failed to connect]

Differential lock
[failed to connect]

Chassis
[failed to connect]

Suspension
[failed to connect]

Central electronics
Part #: 4F0910279K
Coding: 14123 (decimal)
Component: ILM Fahrer
[No fault codes]

Central electronics 2
Part #: 4F0910280
Coding: 12001 (decimal)
Component: ILM Beifahrer
[No fault codes]

Body/convenience system
Part #: 4L0910289D
Coding: 7632925 (decimal)
Component: Komfortgeraet
[No fault codes]

Body/convenience system
Part #: 4L0910290A
Coding: 3595 (decimal)
Component: ILM HINTEN 2
Fault codes:
02961 Lamp in Bumper; Rear Right

Driver's door
Part #: 4L0910793B
Coding: 35531 (decimal)
Component: TSG FA
[No fault codes]

Front passenger's door
Part #: 4L0910793B
Coding: 35531 (decimal)
Component: TSG BF
[No fault codes]

Rear left door
Part #: 4L0910795B
Coding: 35338 (decimal)
Component: TSG HL
[No fault codes]

Rear right door
Part #: 4L0910795B
Coding: 35338 (decimal)
Component: TSG HR
[No fault codes]

Trunk
Part #: 4L0910945
Coding: [none]
Component: ValeoHeckdeckel
[No fault codes]

Driver's seat
Part #: 4F0910760
Coding: 82946 (decimal)
Component: Sitzmemory FS
Fault codes:
01446 Givers for backrest adjustment, driver's seat (G230)
00003 Control Module

Front passenger's seat
[failed to connect]

Rear seat
[failed to connect]

Rear seat (driver's side)
[failed to connect]

Entry assist (driver)
[failed to connect]

Entry assist (passenger)
[failed to connect]

Ignition authorization
Part #: 4F0910852
Coding: 131 (decimal)
Component: FBSAUDIC6 ELV
[No fault codes]

Battery regulator
Part #: 4L0910181
Coding: [none]
Component: J0644 BEM
[No fault codes]

Battery charging
[failed to connect]

Convertible top
[failed to connect]

Roof electronics
[failed to connect]

Windshield wipers
[failed to connect]

Trailer
[failed to connect]

Adaptive cruise control
[failed to connect]

Lane-change system
Part #: 4L0910566A
Coding: 1 (decimal)
Component: J0769_SWA_Master
[No fault codes]

Lane-maintain system
[failed to connect]

Position sensing
[failed to connect]

Back-up camera
[failed to connect]

Telematics
[failed to connect]

Driver ID
[failed to connect]

Intercom
[failed to connect]

Additional functions
[failed to connect]

Operations
[failed to connect]

Hybrid engine
[failed to connect]

Back-up camera
[failed to connect]

Image processing
[failed to connect]

Sliding door (left)
[failed to connect]

Sliding door (right)
[failed to connect]

Thermal Management
[failed to connect]

Structure-borne sound
[failed to connect]

External noise actuator
[failed to connect]

Driver assist front sensor
[failed to connect]

Rear axle steering
[failed to connect]

Rear axle steering 2
[failed to connect]

Steering column lock
[failed to connect]

Special vehicle assist
[failed to connect]

Sensor electronics
[failed to connect]

A/C compressor
[failed to connect]

3rd row seats
[failed to connect]

Gear selector switch
[failed to connect]

Heads-up display
[failed to connect]

Night view
[failed to connect]

Onboard Camera
[failed to connect]

Multicontour seat (driver)
[failed to connect]

Multicontour seat (passenger)
[failed to connect]

Multicontour rear seat (driver's side)
[failed to connect]

Multicontour rear seat (passenger's side)
[failed to connect]

Adaptive cruise control 2
[failed to connect]

Hybrid battery
[failed to connect]

Seatbelt pretension (front left)
[failed to connect]

Seatbelt pretension (front right)
[failed to connect]

Microphone
[failed to connect]

Infotainment interface
[failed to connect]

Reductant control
[failed to connect]

Brake sensors
[failed to connect]

Roof electronics 2
[failed to connect]

Auxiliary display
[failed to connect]

Motor mounts
[failed to connect]

Rear driver's door
[failed to connect]

Rear passenger's door
[failed to connect]

Sliding door (rear, left)
[failed to connect]

Sliding door (rear, right)
[failed to connect]

Battery charging
[failed to connect]

High-volt battery charging
[failed to connect]

Transmission 2
[failed to connect]

DC/DC converter
[failed to connect]

Pedestrian protection
[failed to connect]

Sunroof
[failed to connect]

Lane-change system 2
[failed to connect]

Front axle lift
[failed to connect]

Roll control 1
[failed to connect]

Roll control 2
[failed to connect]

Light control 2 (left)
[failed to connect]

Light control 2 (right)
[failed to connect]

LED headlight power (left)
[failed to connect]

LED headlight power (right)
[failed to connect]

Obtained with Carista 330099 for iOS.
Download app: https://itunes.apple.com/app/id954363569
Facebook: https://www.facebook.com/caristaapp
 
   #13  

BostonSlaya

Verified VCDS User
Verified
Joined
Mar 4, 2015
Messages
337
Reaction score
88
Location
Rhode Island, USA
VCDS Serial number
C?ID=240768
Thanks for you reply, Yes I can get into the modules directly or corse not the ones that say can not be reached.
I have no idea how to check the Latency setting of interface or USB...
Can you enter any modules individually by hex address?

Please try and report back.........

What is latency setting of interface or USB drivers when tested/observed?
 
   #14  

Uwe

Benevolent Dictator
Administrator
Joined
Jan 29, 2014
Messages
49,245
Reaction score
33,795
Location
USA
VCDS Serial number
HC100001
OK So I went to run a full AutoScan on my A8 and same thing. I uninstalled VCDS and the reinstalled and still does the same thing. This is so odd because I used this computer from day one!! I know what I could do maybe, I could use my Crista Bluetooth to do a full AutoScan and post it maybe that would help. I wish I had another computer for this to try with but I don't. I wish VCDS worked for a Mac lol..
Tell us about this computer please. Make, Model, CPU, RAM, version of Windows, etc.

-Uwe-
 
   #15  

BostonSlaya

Verified VCDS User
Verified
Joined
Mar 4, 2015
Messages
337
Reaction score
88
Location
Rhode Island, USA
VCDS Serial number
C?ID=240768
It's a MacBook Pro 2.7 quad core 16gb ram 1TB Solid state drive. I'm running windows 10 Pro on Parallels virtual machine running the same specs


Tell us about this computer please. Make, Model, CPU, RAM, version of Windows, etc.

-Uwe-
 
   #16  

Uwe

Benevolent Dictator
Administrator
Joined
Jan 29, 2014
Messages
49,245
Reaction score
33,795
Location
USA
VCDS Serial number
HC100001
It's a MacBook Pro 2.7 quad core 16gb ram 1TB Solid state drive. I'm running windows 10 Pro on Parallels virtual machine running the same specs
D87tM6.gif
 
   #18  

Uwe

Benevolent Dictator
Administrator
Joined
Jan 29, 2014
Messages
49,245
Reaction score
33,795
Location
USA
VCDS Serial number
HC100001
Lol yup! So does the Carista scan help?
No, because we've already determined with a high degree of confidence that the problem isn't the car. The reason that running VCDS in Windows inside a VM inside another OS is officially "Not Supported" is because there's too many variables that can break things. An update the host OS can break it. An update to the VM hypervisor can break it. An update to Windows that might be fine running on native hardware could break things when it's run in a VM. Heck, even an update to VCDS that runs fine in native Windows versions could break thing, but with zillion different combinations/permutations of host OS, VM hypervisor, and Windows versions we're not in any position to test all that.

Please beg/borrow/steal a cheap laptop somewhere that runs Windows natively. Or try Bootcamp. Or try a different VM hypervisor.

-Uwe-
 
   #19  

BostonSlaya

Verified VCDS User
Verified
Joined
Mar 4, 2015
Messages
337
Reaction score
88
Location
Rhode Island, USA
VCDS Serial number
C?ID=240768
Ok I will do so, I'll have a scan put up in a little when I get off of work, thanks

No, because we've already determined with a high degree of confidence that the problem isn't the car. The reason that running VCDS in Windows inside a VM inside another OS is officially "Not Supported" is because there's too many variables that can break things. An update the host OS can break it. An update to the VM hypervisor can break it. An update to Windows that might be fine running on native hardware could break things when it's run in a VM. Heck, even an update to VCDS that runs fine in native Windows versions could break thing, but with zillion different combinations/permutations of host OS, VM hypervisor, and Windows versions we're not in any position to test all that.

Please beg/borrow/steal a cheap laptop somewhere that runs Windows natively. Or try Bootcamp. Or try a different VM hypervisor.

-Uwe-
 
   #20  

ivagp

Verified VCDS User
Verified
Joined
Jul 15, 2014
Messages
702
Reaction score
285
Location
USA
VCDS Serial number
C?ID=95551
what kind of roof dose the car have
 
Back
Top