Notices
A6 (C7 Platform) Discussion Discussion forum for the C7 Audi A6 produced from 2011 - 2017

VAG-COM (VCDS) coding for 2016 FL A6/A7

Thread Tools
 
Search this Thread
 
Old 02-04-2017, 02:42 PM
  #71  
Banned
 
rockylivingston's Avatar
 
Join Date: Feb 2016
Posts: 9
Likes: 0
Received 0 Likes on 0 Posts
Default

Originally Posted by Smooremin
Any update on VIM? I tried to read through the spanish thread but got lost...

OBDeleven: Audi, Volkswagen, Seat & Skoda diagnostic system
Old 02-14-2017, 03:05 AM
  #72  
AudiWorld Senior Member
 
manishaudi's Avatar
 
Join Date: Aug 2011
Location: California, US
Posts: 1,193
Received 2 Likes on 2 Posts
Default

Originally Posted by Smooremin
Any update on VIM? I tried to read through the spanish thread but got lost...
Originally Posted by WL26
Has anyone ever figured out the VIM in the C7 FL?
No, It doesn't seem that anyone has yet
Old 02-17-2017, 03:12 AM
  #73  
AudiWorld Member
 
oswalde2000's Avatar
 
Join Date: Aug 2015
Posts: 75
Likes: 0
Received 0 Likes on 0 Posts
Default

Anyone used obdeleven to activate VIM on a 2016 A6 yet? I got the device but haven't been able to activate VIM. It fails everytime I try with the one-click app they have.
Old 02-18-2017, 12:19 PM
  #74  
AudiWorld Member
 
oswalde2000's Avatar
 
Join Date: Aug 2015
Posts: 75
Likes: 0
Received 0 Likes on 0 Posts
Default

I finally got VIM to work in my 2016 A6 through the obdeleven app.
Now trying to figure traffic sign recognition.
Old 02-20-2017, 01:26 AM
  #75  
AudiWorld Member
 
oswalde2000's Avatar
 
Join Date: Aug 2015
Posts: 75
Likes: 0
Received 0 Likes on 0 Posts
Default

Sorry I have to resurrect this thread. I was reading on vwaudiforum uk and saw the following to enable Traffic Sign Recognition.

- 17 Instruments, Long Coding, Byte 05, Bit 2 on
- 8E Image Processing, Long Coding, Byte 02, Bit 0 on
- MMI Hidden Menu: car/cardevicelist, VZE on
- MMI Hidden Menu: car/carmenuoperation, VZE => 5

Problem is I don't see a Bit 2 when I get into Instruments, Long Coding, Byte 05. What's wrong here? I have attached screenshots below.

17-Instruments

Coding

Long Coding

Byte 5...
No Bit 2
Old 02-20-2017, 01:47 AM
  #76  
AudiWorld Member
 
oswalde2000's Avatar
 
Join Date: Aug 2015
Posts: 75
Likes: 0
Received 0 Likes on 0 Posts
Default

Additionally I did an autoscan and got some faults. Is there something to worry about? Should I take it to the dealer since I'm still under warranty? But my concern is how did I found out about the faults since the car is not throwing up any check engine lights or any signs of a malfunction. How do I approach this with the dealer. Of course the German dealership seems to be very nice and I've been servicing the car with them since I took delivery in 2015.

*05-Acc/Start Auth. -- Status: Malfunction 0010
*17-Instruments -- Status: Malfunction 0010
*19-CAN Gateway -- Status: Malfunction 0010
*2E-Media Player 3 -- Status: Cannot be reached 0100
*46-Central Conv. -- Status: Malfunction 0010
*52-Door Elect, Pass. -- Status: Not registered 0001
*6D-Trunk Elect. -- Status: Cannot be reached 0100

A full scan is attached.
Attached Files
Old 02-27-2017, 07:43 PM
  #77  
AudiWorld Member
 
Ricckky's Avatar
 
Join Date: Oct 2015
Location: Washington DC Metro
Posts: 94
Likes: 0
Received 0 Likes on 0 Posts
Default

Originally Posted by oswalde2000
Additionally I did an autoscan and got some faults. Is there something to worry about? Should I take it to the dealer since I'm still under warranty? But my concern is how did I found out about the faults since the car is not throwing up any check engine lights or any signs of a malfunction. How do I approach this with the dealer. Of course the German dealership seems to be very nice and I've been servicing the car with them since I took delivery in 2015.

*05-Acc/Start Auth. -- Status: Malfunction 0010
*17-Instruments -- Status: Malfunction 0010
*19-CAN Gateway -- Status: Malfunction 0010
*2E-Media Player 3 -- Status: Cannot be reached 0100
*46-Central Conv. -- Status: Malfunction 0010
*52-Door Elect, Pass. -- Status: Not registered 0001
*6D-Trunk Elect. -- Status: Cannot be reached 0100

A full scan is attached.
Did you save a complete scan before you made any changes with vagcom or odbeleven? You could compare the two to see if the faults were already there or appeared after you made changes. If you're a vagcom customer, you might get better help posting your scan in their forums or ask your dealer if they can figure them out.

I'm assuming you're in the US; for the traffic sign recognition, I've seen a few posts saying that doesn't work in the US. Some of the coding references are in our software, but from what I understand, it doesn't recognize US signs (different shapes, sizes, etc).
Old 03-02-2017, 12:26 PM
  #78  
AudiWorld Junior Member
 
scottfree's Avatar
 
Join Date: Mar 2017
Posts: 13
Likes: 0
Received 0 Likes on 0 Posts
Default

I was able to get VIM working on my 2016. Weird part is accidentally ran the app with the car running even tho your supposed to turn it off, and it worked with no problems.
Old 03-03-2017, 02:35 AM
  #79  
AudiWorld Senior Member
 
19hole's Avatar
 
Join Date: Aug 2014
Posts: 1,134
Received 102 Likes on 81 Posts
Default

Originally Posted by scottfree
I was able to get VIM working on my 2016. Weird part is accidentally ran the app with the car running even tho your supposed to turn it off, and it worked with no problems.
Can you post the steps you took to make it work please.
Old 03-03-2017, 07:06 AM
  #80  
AudiWorld Junior Member
 
scottfree's Avatar
 
Join Date: Mar 2017
Posts: 13
Likes: 0
Received 0 Likes on 0 Posts
Default

Originally Posted by 19hole
Can you post the steps you took to make it work please.
oops, I meant to say with the obdeleven.

I just followed the instructions, plugged in obdeleven, ran the app for VIM on MIB.


Quick Reply: VAG-COM (VCDS) coding for 2016 FL A6/A7



All times are GMT -8. The time now is 02:59 PM.