Connects 2 wheel interface

[T6_FunBus]

Hi guys,

I’ve got a weird issue, I have the t6 connects 2 fitting kit, and the steering interface is not working. The only button I can map is the telephone button, nothing else is detected.

I have connected to a sony xav3250, instructions day no wire cut is required.

Also connected exactly as per the guide in the correct order but still no dice.

Any ideas please?

Thanks.

 

[Dav-Tec]

Which kit was it, should be plug and play

 

[T6_FunBus]

Not sure what this is lol

 

[T6_FunBus]

Which kit was it, should be plug and play

CTKVW17, its weird the only button the sony recognises is the telephone button .

 

[T6_FunBus]

Ahh thats the USB lead, already got one of them on the way.

So the connects2 interface juat won’t work with the xav3250 and my wheel for some reason. I’ve disconnected and reconnected in the correct order as per the connects 2 video many times, and done a factory reset to the unit, but still the only button the head unit will detect when trying to map is the phone button, none of the others do anything

The patch lead us a universal and for SONY units all three loops should be connected (which it is by default) and use the 3.5mm remote jack (connected correctly).

I just don’t get it. It was a retrofitted mfsw, but if it worked and was sending signals over can to the factory HU, and the phone button works, I can’t see why it shouldn’t work on the sony.

At a bit of a loss tbh.

 

[T6_FunBus]

Hmm, wondering if it is the patch lead, it shows this works for Sony, but maybe it is outdated. Does anyone have the pin out or picture of SONY lead so I can compare? Can’t seem to find an accurate one online.

 

[T6_FunBus]

not sure if either if these two have any bearing, I can’t clear one and the other clears and comes straight back, could be as the factory radio has been removed, but also wondered if a fault was now stopping it from working.

Not sure why everything always has to be such a pain in the ass with the transporter. Fitted headunit, controller etc to my audi fine, all worked. Said to the wife earlier the hard part was all done (pulling the van apart to run wires for the cameras) and should be done in an hour, all night pissing about on something that should just ‘work’ again. Sigh.

 

[T6_FunBus]

Oh also if someone has a dab adapter for the black factory connector to the Sony hu let me know as I need to order on at somepoint. Ta.

 

[T6_FunBus]

Anyone? Can’t believe that no one has fitted a 3250 and a ctkvw17 kit to a t6?

Pulled it all out again, its wired as per instructions, checked firmware, checked jumper configuration (found an article saying jumper 4 needs to be off for ‘some’ Sony headunits, tried - no joy.

Checked prt numbers - correct.

Checked patch lead wiring, and is correct (as per instructions, J 1 2 3 all enabled).

The ONLY button the headunit will pick up is the telephone button, no others are detected at all.

If I can’t get volume and track buttons working then its coming back out :/

 

[Dav-Tec]

Ok so the fault are because it can't see the factory headunit anymore and nothing to do with the SWC issue

 

[T6_FunBus]

Does anyone have a CTSONYLEAD they can share the wiring of so I can compare to my universal patch lead?

looks identical from what I can find online.

Removed all again and reset, still only the phone button detected.

The interface module is a CTSVW015.2

Has anyone had a problem where 5F isn’t responding so it locks out the radio wheel controls?

All other MFSW buttons work still, just no volume and skip forward / back for radio.

Thanks.

 

[T6_FunBus]

Soooooo, I've double checked what I can on the lead.

J1, J2, J3 - link made as mentioned
pin 5 is ground
pin 6 is key 1
pin 4 is key 2

The problem is, I cannot see how the 3.5mm jack is wired as it is sleeved, but the wires on the universal patch lead are at least in the correct pins.

Sony also do their own lead, RC-SR1, which can be spliced into the correct wires, black ground, green input 1, brown input 2. So I could just get the official Sony lead and splice it in, or just grab the SONYCTLEAD and see if that works, but, I can't see it being wired any different to be honest. Order looks to be the same from the limited pictures I can see online.

Inside the CTSVW015.2, by default jumper 123 are off, 4 is ON. I did try with 4 also OFF as directed on the AEPRO website for some SONY machines, but it made zero difference (still only the phone button works). Also for kicks I tried randomly toggling all on or off and it rendered the unit inoperative (not that it made much difference to having only ONE button working).

If the patch lead is OK, I could try another CTSVW015.2, but I am not convinced its the problem. The HU is also brand new, and can see the phone key, so I am not convinced that would be faulty either.

Maybe its a coding thing, my MFSW was retrofitted, but installing the original RCD330 everything works again as expected, so who knows.

 

[T6_FunBus]

Feel like I am talking to myself here other than @Dav-Tec lol.

But anyway, still useful to sound out and if / when I get this fixed, hopefully it’ll help any other owners or trade members if they come across this issue rather than burning hours head scratching.

I’ve read a thread on a Golf forum that someone had issues with Alpine functionality with canbus and 5F communications errors. Now as the connects2 is marketed as ‘plug and play’, I figure nothing else should need to be done. But I’m not happy with the databus signal error. I cannot clear the error unless the original headunit is refitted (rcd330). And as mentioned, when the RCD330 is connected the buttons work.

I’m going to try a new patch cable on the off chance the cable is faulty, but I doubt it’ll make any difference unless somehow the fault is in the 3.5mm cable from factory.

Seems a strange coincidence that the control unit knows 5F is not present and communicating and so the multimedia buttons aren’t working.

Telephone button and all others on the wheel work…

If I can figure out the coding on obdeleven (starting to wish I got vcds instead tbh) I couod remove 5F and replace with radio, but, others that have done that still get errors. Obdeleven doesn’t show labels for coding options in gateway, only byte / bit, so no clue what 5f would be ticked on there atm vs radio.

Also had an email from connects2, they say some if the VW interfaces come pre configured for pioneer, and jumper switch needs changing in the unit, so I’ve removed it, opened the case and changed the jumper configuration as they have requested for Sony. Will leave out of the van and all disconnected so power can drain and will reconnect, but, I’m still not confident the jumper configuration is the problem.

Cheers.

 

[T6_FunBus]

Another update, changing jumper setting rendered even the phone button inoperable. So put it back to default and phone button working.

Can hi and lo are wired correctly into the input of the connects2.

So it really should just work. Unless there is some carefully guarded secret that the vans control unit stops sending signals to the (missing) multimedia unit when it’s a science is detected.

If that was the case I’d expect there to be an issue raised by someone on thus already on this forum.

So next new patch cable, which I am convinced will also fail, then new connects box, then I guess on to attempting to troubleshoot coding issues. Fun! Love transporters, has to be the worst vehicle I have had for installing things that should work but don’t!

 

[T6_FunBus]

Removed 5F added radio - no difference

 

[T6_FunBus]

Ok, think I've worked out the problem, I'll still try the patch lead but I am convinced it is a waste of time.

I have a MFSW retrofit, and its the later type - cruise on wheel NOT stalk. Most earlier T6 highlines had cruise on stalk, and the MFSW harness / button config is different.

The wheel I have retrofitted is a later highline style with cruise on wheel.

Now as I think about it this is starting to make sense, the telephone button works - this is in the same configuration along with menu buttons as the standard MFSW. However, where the audio buttons normally would be, there are cruise buttons. These buttons are under cruise in the control module and they are up, down, left right etc. I cannot find the volume or skip track buttons anywhere in live date within the module. Now clearly they work but, the up down, left right buttons would normally be asigned to the radio, not cruise on the standard wheel, as cruise is on stalk.

So, I am thinking the interface for for the standard wheel and stereo combo is configured only for the older setup.

Now my wheel is of the configuration of the later MiBII system. This has a different connects2 control box, which I assume is configured to the later system and MFSW buttons commands.

So there are two problems here, 1 the later Mibii system also has a different dash cluster and other parts, which may still render the later SWC useless, and, the later SWC is expensive just to try and may or may not work with some of the other original non mibii functions...

So I am a bit pissed off. The solution might be that I have to ditch my SW controls and add cruise on stalk and reconfigure / get new buttons, or try to find another universal interface which listens and can be programmed / customised to interpret the signals.

Either way a complete ball ache for what should have been a real cost effective and simple 'upgrade'. Sigh...

Not sure if any of the audio experts / trade members on here would know a way around this, as if this is the issue (seems highly likely no?) then there will be more with the issue who have upgraded wheels and later wish to change stereo.

 

[T6_FunBus]

@Absolut5 thoughts? Do you have a universal interface that can be receive any signal and be programmed manually? Just checked your site but cannot see any products.

 

[Dav-Tec]

I've whatsapped you mate think you barking up the wrong tree completely mate

 

[Absolut5]

Sorry late to this post, as totally wiped out over busy week ..

let me read through it and pm you back

 

[Lightrofit]

Post a pic of your steering wheel