Hopefully someone will be able to tell me what I'm doing wrong.

Another Briskodian has a nice new Yeti Elegance (no sunroof so I'm not jealous in the slightest) which came with a Bolero fitted from the factory. All the controls on the MFSW worked with the Bolero.

He's changed it for a Columbus which I have successfully coded in and all is good.

Except the volume knurled roller switch doesn't control the volume. If pressed, it mutes the volume.

I've tried to read the output from the MFSW buttons but can't get any readings to show from any buttons.

This makes me think that either I'm doing something wrong with VCDS or it's not able to read the output (most likely the former).

What should I be doing to read the output and see if there is a signal from the errant roller switch from the MFSW controller?

I wonder if the Columbus effectively has an option for how that wheel works? Have you looked at the tone settings on the unit itself?

On your actual question I tried the measuring blocks on the steering controller when I was trying to work out why my mfsw phone button wasnt working and found nothing either.

As the fellow Briskodain who KBPhoto has kindly been helping, I will investigate on the Columbus itself. I am amazed as to why it's not working as the other controls are fine. I now have all the Sat-Nav instructions showing in my MFD but finding the lack of volume control on the MFSW a little annoying.

I am surprised too. Thats why I wondered if its because the Columbus has more functionality and hence the roller wheel does something else by default...

I don't understand two things:

Why a Bolero worked fine, but a Columbus works except one roller button;

Why it appears impossible to read the output from the MFSW buttons despite the options being listed.

If anyone has suggestions for either, I'd love to hear them.

I can't think what else a wheel marked for volume would control on a Columbus...

Hmmm does seem odd. I wonder if its worth popping the Bolero back in to rule out the button playing up at a coincidental point..

jerbear: are you able to try that as a way of eliminating one possibility?

 

The coding changes we made yesterday won't affect it at all.

Hi KBPhoto,

Yes I will swap it tomorrow and see if it works.

Let you know the outcome.

Thanks

Well I've swapped the radio back for the Bolero and it all worked ok. Popped the Columbus back in and no volume control on the MFSW again. Been through all the radio handbook, nothing to explain it there. Umhhh...

That seems to discount any obvious coding issues.

Anyone know if it is possible to read the output of the roller wheel and reassign its function?

Anyone else experienced this when retro fitting a Columbus?

Jerbear: what part number is your Columbus (and year)? I presume it worked correctly in your Vrs?

Can I get details off the screen or will I have to pull it out again?

Think it was 2010 YOM.

I presume that you have tried turning sound up and down with the knob on the Columbus to eliminate an issue with the unit?

We did that. And it was fine.

Does seem to be a communication issue with a Columbus that pre-dates the vehicle.

Agreed. Maybe a software update will help as its only on 2764.

Could be worth a try.

Jerbear: I have 4020 firmware disk which I have used on my Columbus with same part number if you want to try that.

Worth a go. PM 'd you.

Thanks all so far.

Pleased to report that jerbear is now sorted.

An upgrade to 4020 (from 27xx) sorted the button. Thanks to Adam for spotting the older firmware and suggesting trying an upgrade.

I'll leave this thread open in the hope that someone may be able to explain how to read the output from the MFSW buttons as a point of interest at this stage.

Isn't there a modified firmware for Octavia MFSW from Josi somewhere? Or is that just for earlier vehicles?

 

Take a look here

http://vwnavi.com/volkswagen-factory-fit-navigation-systems/rns-510-mfd3-navi-system/firmware/13672-unofficial-272x-software-swl-recovery-cd.html

Just a quick thank you for the replys and to Adamal for the suggestion and especially KBPhoto for taking the time once again to help.

To me, that's what these forums are all about, being able to help fellow members. A constant source of invaluable information, with a hint of nonsense here and there ....lol

No problem, very much agreed. Glad its sorted.