Voice Control and Speech - Issues and Questions

[Ryan_R]

Did any of the long coding numbers change when you compared before and after? Having the correct labels isn't super important here (this is how you start to work out the labels). Feel free to send both scans to me via PM.

[night_flight]

I just checked my Oct 2013 MY14 Highline and voice activation is not enabled . Just the standard mute/un-mute when pressed.

So, the quote above suggests that Ryan_R has sussed out how to enable this without a visit to the dealer. Can anyone share the process? I have a genuine VCDS cable and am happy to guinea pig this if someone can give me some pointers.

well I had bought "RNS510 with voice control" that is hardware related feature....some rn510 don't support this at all even if you do the coding is my guess...I know you guys have now different head units, however with the first batch of mk7s I m sure that the units would be all the same hence IT MUST be the software tweak! sometimes I am pissed VW is so slack to simple things like this...

[spikeyboy22]

Ryan_R: I reckon your suggestion for a long life video camera hidden surreptitiously in the vehicle somewhere is a great idea. However, the problem with the before/after VCDS scan is that Mr Ross's current software (ver 12.12.0) has some fundamental problems when it comes to scanning the "AU" chasis on which the MkVII is built. The big problem is that the controllers for the infortainment system and much of the electronics are currently not supported (and much of the other stuff is in German).
As you know, I've already had the voice control fix installed in my MkVII. and I've tried an "after" scan, without much success. I guess we will just have to wait for the next SW upgrade and hope that Mr Ross has turned his atention to better supporting the MkVII.

Any chance you could provide the before and after scans to Ryan R and see if he can see something

[Ryan_R]

We did see something

If you jump into address 5F: Information Electr. (J794) with VCDS, and check to see if your code matches this:
02730008FF00000011510001000900001F0100960100010245 (there may be differences between Trendline/Comfortline/Highline Golf's due to equipment differences)


Then try changing it to match this:
02730008FF00000011510001000900001F0100960100010247

Once you save the coding turn the car off then on again before checking. If the voice control now works... great (let us know). If not, just change the coding back to how it was and clear any fault codes that might have resulted. No harm done

Feel free to take VCDS screenshots as you go so you can start a thread

[DV52]

We did see something

If you jump into address 5F: Information Electr. (J794) with VCDS, and check to see if your code matches this:
02730008FF00000011510001000900001F0100960100010245 (there may be differences between Trendline/Comfortline/Highline Golf's due to equipment differences)


Then try changing it to match this:
02730008FF00000011510001000900001F0100960100010247

Once you save the coding turn the car off then on again before checking. If the voice control now works... great (let us know). If not, just change the coding back to how it was and clear any fault codes that might have resulted. No harm done

Feel free to take VCDS screenshots as you go so you can start a thread

Ryan_R I tried to PM but I couldn't get through (message from admin said that your email box was full).

Appropos of the coding values in your post (above) first, let me start by apologizing for telling you what you probably already know but my (very amateur) take on what I have seen of the VCDS screens strongly suggests that the software uses standard digital nomenclature.

At the bit level (i.e. as shown on the long coding screen - line 4), Mr Ross's software appears to allocate each of the eight bits in a simple binary fashion. By this I mean that the long coding screen appears to take each of the eight bits (in line 4) and to produce a bog-standard binary number.

At a byte level (i.e. as shown on the long coding screen - line 3), each of the bytes appear to be a standard hexadecimal pair.

This means (I think) that the process for translating "45" & "47" into the bit allocations is just a matter of doing a hexadecimal-to-binary conversion. In my youth (many years ago) I used to do these conversion by hand, but I find it much easier these days to use the converters on the web

Converting hexadecimal "47" to binary gives 01000111
Converting hexadecimal "45" to binary gives 01000101

So, if your hypothesis about "45" and "47" is correct, the key to Voice Control activation for the MkVII is to put a tick in the bit 1 box for byte 24. As a check for this logic, someone who hasn't had the Voice control fix should see binary 01000101 on the right-hand box on line 3 (of the long coding screen).

Again, my apology if you already know this stuff.

[Ryan_R]

Yes, I remembered the principle, just couldn't remember what number system it used


*waiting for someone to try and activate Voice Control and respond*

[scobb]

I've given this a go. First, I should say that I have a MY14 NZ-spec 103kW Highline, so this may require a different coding change to the Australian spec cars. The long coding is a little different to yours:

02730008FF00000021510001000900001F0100160100010045

I tried recoding by ticking the bit 1 box for byte 24, which indeed changes the last 2 digits of the long code from 45 to 47. As expected, this changes the binary value from 01000101 to 01000111. The coding change is accepted, but sadly, it makes no difference to voice control, which remains deactivated .

What I did notice changed was that RDS and TP were turned off when the coding change was applied.

As this tweak didn't work, I reset my coding back to the original default value.

So, no joy, I'm afraid.

[DV52]

I've given this a go. First, I should say that I have a MY14 NZ-spec 103kW Highline, so this may require a different coding change to the Australian spec cars. The long coding is a little different to yours:

02730008FF00000021510001000900001F0100160100010045

I tried recoding by ticking the bit 1 box for byte 24, which indeed changes the last 2 digits of the long code from 45 to 47. As expected, this changes the binary value from 01000101 to 01000111. The coding change is accepted, but sadly, it makes no difference to voice control, which remains deactivated .

What I did notice changed was that RDS and TP were turned off when the coding change was applied.

As this tweak didn't work, I reset my coding back to the original default value.

So, no joy, I'm afraid.

scobb: What a shame (that it didn't work). Ryan_R's logic was so compelling that I would have have bet that it was a certainty. Perhaps there are fundamental differences between Golf vehicles here and across "the ditch". The other possibility is coding variations between my13 & my14 models. It would be good if someone from Australia with a my13 model gave this a try
It's interesting that your coding has three bytes that are different (i.e. byte 23, byte 19, byte 8 ). I've become aware from another thread that one of the diferences between the two models (over here at least) is that TP appears to work on my14 cars, but doesn't work on my13 (at least not on my my13). I wonder if the TP answer is somewhere in the three different bytes? Something else for the resident VCDS boffins to think about I guess!!

[Ryan_R]

Just tick everything and see what you enable

[jdbrown1953]

The other thing to consider is the CD/SD card with the software fix may also contain the dictionary of commands which may not have been installed in the factory.