2017 A4 coding tweaks
10-31-2017, 01:49 PM
#991
Audiworld Basic Sponsor
VCP has the ability to load parameters for certain modules. This is particularly useful for taillight and headlight conversions. VCP uses container files that you can download from their server and then load into modules in the car. These parameters are not accessible or changeable with any other interfaces as of yet.
VCP can also flash modules like a dealership tool can. Say you have a new headlight module and don't want to head down to the dealership to have the actual firmware flashed onto it VCP gives you the ability to do this as long as the flash file is on the server.
VCP has similar guided functions like the dealership tools have as well. There is the option for the VIM (Video in Motion) manager which supports VIM for a fair number of models, though still waiting on the newest models.
It even has a security code finding app that will cycle through numbers to find the security codes that may not already be known. The PR Coder can set coding in specific ways for adding options by an option code. Say you have added the factory wiring for front parking assist and the option code is 7X2. You would be able to use that option code to have it set all of the coding needed to work with a factory style install of those sensors/wiring/modules.
I still use VCDS Hex-Net for coding for the most part since it's something I've used for a long time, but for any other more advanced functions VCP is what is needed.
Cheers,
VCP can also flash modules like a dealership tool can. Say you have a new headlight module and don't want to head down to the dealership to have the actual firmware flashed onto it VCP gives you the ability to do this as long as the flash file is on the server.
VCP has similar guided functions like the dealership tools have as well. There is the option for the VIM (Video in Motion) manager which supports VIM for a fair number of models, though still waiting on the newest models.
It even has a security code finding app that will cycle through numbers to find the security codes that may not already be known. The PR Coder can set coding in specific ways for adding options by an option code. Say you have added the factory wiring for front parking assist and the option code is 7X2. You would be able to use that option code to have it set all of the coding needed to work with a factory style install of those sensors/wiring/modules.
I still use VCDS Hex-Net for coding for the most part since it's something I've used for a long time, but for any other more advanced functions VCP is what is needed.
Cheers,
10-31-2017, 10:54 PM
#992
AudiWorld Member
VCP has the ability to load parameters for certain modules. This is particularly useful for taillight and headlight conversions. VCP uses container files that you can download from their server and then load into modules in the car. These parameters are not accessible or changeable with any other interfaces as of yet.
VCP can also flash modules like a dealership tool can. Say you have a new headlight module and don't want to head down to the dealership to have the actual firmware flashed onto it VCP gives you the ability to do this as long as the flash file is on the server.
VCP has similar guided functions like the dealership tools have as well. There is the option for the VIM (Video in Motion) manager which supports VIM for a fair number of models, though still waiting on the newest models.
It even has a security code finding app that will cycle through numbers to find the security codes that may not already be known. The PR Coder can set coding in specific ways for adding options by an option code. Say you have added the factory wiring for front parking assist and the option code is 7X2. You would be able to use that option code to have it set all of the coding needed to work with a factory style install of those sensors/wiring/modules.
I still use VCDS Hex-Net for coding for the most part since it's something I've used for a long time, but for any other more advanced functions VCP is what is needed.
Cheers,
VCP can also flash modules like a dealership tool can. Say you have a new headlight module and don't want to head down to the dealership to have the actual firmware flashed onto it VCP gives you the ability to do this as long as the flash file is on the server.
VCP has similar guided functions like the dealership tools have as well. There is the option for the VIM (Video in Motion) manager which supports VIM for a fair number of models, though still waiting on the newest models.
It even has a security code finding app that will cycle through numbers to find the security codes that may not already be known. The PR Coder can set coding in specific ways for adding options by an option code. Say you have added the factory wiring for front parking assist and the option code is 7X2. You would be able to use that option code to have it set all of the coding needed to work with a factory style install of those sensors/wiring/modules.
I still use VCDS Hex-Net for coding for the most part since it's something I've used for a long time, but for any other more advanced functions VCP is what is needed.
Cheers,
You seem to know the interface and it will be of great comfort to prospective owners if you could perhaps start a thread on this forum, dedicated to the VCP interface, explaining what it can do and how to use the VCP. Your last posting regarding this interface has already provided me with information I was not aware of despite spending a substantial amount of time looking for information on the interface. I (and many others I'm sure), would love to know more about the interface because it appears to be a lot more powerful than the others.
11-01-2017, 01:10 AM
#993
AudiWorld Senior Member
VCP has the ability to load parameters for certain modules. This is particularly useful for taillight and headlight conversions. VCP uses container files that you can download from their server and then load into modules in the car. These parameters are not accessible or changeable with any other interfaces as of yet.
VCP can also flash modules like a dealership tool can. Say you have a new headlight module and don't want to head down to the dealership to have the actual firmware flashed onto it VCP gives you the ability to do this as long as the flash file is on the server.
VCP has similar guided functions like the dealership tools have as well. There is the option for the VIM (Video in Motion) manager which supports VIM for a fair number of models, though still waiting on the newest models.
It even has a security code finding app that will cycle through numbers to find the security codes that may not already be known. The PR Coder can set coding in specific ways for adding options by an option code. Say you have added the factory wiring for front parking assist and the option code is 7X2. You would be able to use that option code to have it set all of the coding needed to work with a factory style install of those sensors/wiring/modules.
I still use VCDS Hex-Net for coding for the most part since it's something I've used for a long time, but for any other more advanced functions VCP is what is needed.
Cheers,
VCP can also flash modules like a dealership tool can. Say you have a new headlight module and don't want to head down to the dealership to have the actual firmware flashed onto it VCP gives you the ability to do this as long as the flash file is on the server.
VCP has similar guided functions like the dealership tools have as well. There is the option for the VIM (Video in Motion) manager which supports VIM for a fair number of models, though still waiting on the newest models.
It even has a security code finding app that will cycle through numbers to find the security codes that may not already be known. The PR Coder can set coding in specific ways for adding options by an option code. Say you have added the factory wiring for front parking assist and the option code is 7X2. You would be able to use that option code to have it set all of the coding needed to work with a factory style install of those sensors/wiring/modules.
I still use VCDS Hex-Net for coding for the most part since it's something I've used for a long time, but for any other more advanced functions VCP is what is needed.
Cheers,
http://vagcom96.ru/audi/q7-4m/
edit: I guess the car need less than 100km on it. not sure if that translate over to NA
Last edited by Dasaint; 11-01-2017 at 01:15 AM.
11-01-2017, 04:56 PM
#995
AudiWorld Member
Join Date: Apr 2017
Posts: 129
Likes: 0
Received 0 Likes
on
0 Posts
Anyone know if it is possible to adjust the automatic high beam threshold speed? It doesnt seem to activate until 25MPH. I leave on some dark and slow roads in the morning, would be nice for the automatic high beams to start at 10 or 15mph.
11-18-2017, 09:59 PM
#996
AudiWorld Newcomer
Join Date: Nov 2017
Posts: 3
Likes: 0
Received 0 Likes
on
0 Posts
mmi change
Hi,
I managed to smash my MMI screen in my 2017 Audi A4 190PS black edition B8 model. Audi quoted me £1300 for the job which I think is too
much.
I ordered another screen off ebay but I didn’t realise It was a different part number. The screen that came out of the car is “8W2919604” and the one I ordered is “8W2919605” (it came out of a 17 plate Audi A4 TFSI). The new screen has a different connection at the back, it’s blue in colour and has different locations for the locating tabs.
I swapped the motherboard out of the old screen and put it in the new screen and hooked it up. Everything works but the screen is blank. I then shaved a tab off the connection in the car, put the new motherboard with the new screen and hooked it up. Same thing happens, everything works but the screen is blank.
I’ve tried a soft reset etc and I’ve checked the fuses and all are okay. The reset did nothing and the screen is still blank.
I’ve called a few places and they reckon that the screen needs coded to the car.
I am not sure because I had the old motherboard in and the new screen, surely the car would recognise the original
motherboard?
Does anyone one have any experience with this matter or can anyone tell me if this is in fact true, that the screen needs coded to the car?
Thanks,
Liam.
I managed to smash my MMI screen in my 2017 Audi A4 190PS black edition B8 model. Audi quoted me £1300 for the job which I think is too
much.
I ordered another screen off ebay but I didn’t realise It was a different part number. The screen that came out of the car is “8W2919604” and the one I ordered is “8W2919605” (it came out of a 17 plate Audi A4 TFSI). The new screen has a different connection at the back, it’s blue in colour and has different locations for the locating tabs.
I swapped the motherboard out of the old screen and put it in the new screen and hooked it up. Everything works but the screen is blank. I then shaved a tab off the connection in the car, put the new motherboard with the new screen and hooked it up. Same thing happens, everything works but the screen is blank.
I’ve tried a soft reset etc and I’ve checked the fuses and all are okay. The reset did nothing and the screen is still blank.
I’ve called a few places and they reckon that the screen needs coded to the car.
I am not sure because I had the old motherboard in and the new screen, surely the car would recognise the original
motherboard?
Does anyone one have any experience with this matter or can anyone tell me if this is in fact true, that the screen needs coded to the car?
Thanks,
Liam.
11-18-2017, 11:29 PM
#997
Managed to get traffic sign recognition to work after months of work, as previously said you need VCP to get this working but I used ODBeleven to do the rest.
Tested it on UK road signs all works fine.
Getting the flash coding for cameras and country is a nightmare.
Tested it on UK road signs all works fine.
Getting the flash coding for cameras and country is a nightmare.
11-20-2017, 03:01 AM
#998
AudiWorld Super User
Thread Starter
Hi,
I managed to smash my MMI screen in my 2017 Audi A4 190PS black edition B8 model. Audi quoted me £1300 for the job which I think is too
much.
I ordered another screen off ebay but I didn’t realise It was a different part number. The screen that came out of the car is “8W2919604” and the one I ordered is “8W2919605” (it came out of a 17 plate Audi A4 TFSI). The new screen has a different connection at the back, it’s blue in colour and has different locations for the locating tabs.
I swapped the motherboard out of the old screen and put it in the new screen and hooked it up. Everything works but the screen is blank. I then shaved a tab off the connection in the car, put the new motherboard with the new screen and hooked it up. Same thing happens, everything works but the screen is blank.
I’ve tried a soft reset etc and I’ve checked the fuses and all are okay. The reset did nothing and the screen is still blank.
I’ve called a few places and they reckon that the screen needs coded to the car.
I am not sure because I had the old motherboard in and the new screen, surely the car would recognise the original
motherboard?
Does anyone one have any experience with this matter or can anyone tell me if this is in fact true, that the screen needs coded to the car?
Thanks,
Liam.
I managed to smash my MMI screen in my 2017 Audi A4 190PS black edition B8 model. Audi quoted me £1300 for the job which I think is too
much.
I ordered another screen off ebay but I didn’t realise It was a different part number. The screen that came out of the car is “8W2919604” and the one I ordered is “8W2919605” (it came out of a 17 plate Audi A4 TFSI). The new screen has a different connection at the back, it’s blue in colour and has different locations for the locating tabs.
I swapped the motherboard out of the old screen and put it in the new screen and hooked it up. Everything works but the screen is blank. I then shaved a tab off the connection in the car, put the new motherboard with the new screen and hooked it up. Same thing happens, everything works but the screen is blank.
I’ve tried a soft reset etc and I’ve checked the fuses and all are okay. The reset did nothing and the screen is still blank.
I’ve called a few places and they reckon that the screen needs coded to the car.
I am not sure because I had the old motherboard in and the new screen, surely the car would recognise the original
motherboard?
Does anyone one have any experience with this matter or can anyone tell me if this is in fact true, that the screen needs coded to the car?
Thanks,
Liam.
11-21-2017, 10:43 AM
#999
AudiWorld Senior Member
11-21-2017, 10:51 AM
#1000
AudiWorld Super User
Thread Starter
Could be that I swapped the high/low, but the fact remains that parts cannot be mixed, High MMI headhunt requires High MMI screen and vice versa.