That has nothing to do with the MIB.

The simplest way is to buy a LIN Convertor/module which gives you full control of the steering wheel buttons. I did the mod on my 2015 Superb, without the LIN Convertor you will have limit functionality and be able to use only the right side of the steering wheel.

on Facebook search for Jan Tiza, he is selling the modules which are plug n play.

1 hour ago, Awesam said:

The simplest way is to buy a LIN Convertor/module which gives you full control of the steering wheel buttons. I did the mod on my 2015 Superb, without the LIN Convertor you will have limit functionality and be able to use only the right side of the steering wheel.

on Facebook search for Jan Tiza, he is selling the modules which are plug n play.

This is Arduino module that works with CAN bus(not LIN) and does not work correctly. The Travel Assist button for some reason triggers View.

Double-clicking OK also triggers View.

From the factory, this is how it works on the FL:

Bottom left arrow - Menu

Right arrow - View

So, if you’re gonna retrofit TravelAssist, then it’s not possible with Arduino CAN module.

E.g. for mid FL Superb(07.2019 - 07.2020) Travel Assist can be easily activated, just coding

More details:

Edited 17 December, 202517 Dec by zacko_O

On 8.11.2022 at 16:10, RT_SGP said:

Aktualisierung:

 

1. Lenkradsteuerung - dies wurde durch einen LIN-Konverter gelöst, der die Programmierung von Tasten ermöglicht 
 

2. Fahrstufenauswahl und Start/Stopp-Knopf – Ich habe das Teil eingebaut und es funktioniert einwandfrei. Kauf-Link hier. Es gibt gerade ein 11.11-Angebot. Super Schnäppchen! 
 

https://www.aliexpress.us/item/3256802851402654.html

 

I was able to activate all buttons except for the onboard computer using part number 5E3919719 via firmware and data set. However, there is another part number for Karoq, Kamiq, Kodiaq, Scala, Fabia, Rapid, and Superb.

Happy New Year!

Can someone was able to identify the HEX code for the buttons on the steering wheel from Skoda Octavia Mk IV?
I would like to tweak 7208 FPA dataset in [19] - Gateway to activate "Sport" mode with "Voice" button (OR another button) like the "R" button from Golf MK VIII?

@Cairus , Can you help me with such details?

All the best.

How did they come to the conclusion that this works? The keys have their own LIN chip, and each key has a defined code.

This is Experimental 🙂

As I mention earlier I've been thinking to remap one of the existing steering wheel buttons (e.g. "Voice" on long press) to activate Sport driving profile without MIB3 UI interaction.

Is this going to work? OR a dedicated LIN adapter is needed?

15 hours ago, djmartzian said:

Can someone was able to identify the HEX code for the buttons on the steering wheel from Skoda Octavia Mk IV?

Gateway - Measured Values

Hello @zacko_O ,

Can you provide more details, where to look for the specific HEX codes?

I've been looking in [19] - Live Data, but I can't find them on MQBEvo platform.

Thank you.

Cheers

4 minutes ago, djmartzian said:

Hello @zacko_O ,

Can you provide more details, where to look for the specific HEX codes?

I've been looking in [19] - Live Data, but I can't find them on MQBEvo platform.

Thank you.

Cheers

Maybe you need press button to show values? it will show value in DEC

Cheers @zacko_O

I've checked but without any luck ☹️

Button code 1: is displaying the actual button that is pressed: "Voice", "Steering Heating", "A arrow left",...
Even code 1: is displaying: 1 click, 2 clicks,....

Nothing is displayed for Button code 2 and Event code 2 when any of the steering wheel buttons where pressed.

Any other ideas how to find the HEX code for 5WA Gateway?

Thx

45 minutes ago, djmartzian said:

Cheers @zacko_O

I've checked but without any luck ☹️

Button code 1: is displaying the actual button that is pressed: "Voice", "Steering Heating", "A arrow left",...
Even code 1: is displaying: 1 click, 2 clicks,....

Nothing is displayed for Button code 2 and Event code 2 when any of the steering wheel buttons where pressed.

Any other ideas how to find the HEX code for 5WA Gateway?

Thx

Voice - 0x19

Thank you @zacko_O for sharing the code for Voice button.

Do you have the HEX codes for other buttons from steering wheel? Can you please share them?

All the best.

But you do know that if you want a driving profile selection on the steering wheel, the button alone isn't the solution.

@Cairus , is an adapter mandatory?

Can you please provide more details?

Thank you

The data set for driving profile selection in the gateway also includes the method used for switching between profiles. Simply modifying it isn't possible. I myself converted from a button in the center console to a rotary knob.

9 hours ago, djmartzian said:

@Cairus , is an adapter mandatory?

Can you please provide more details?

Thank you

I did it with an adapter, but in mqb

Edited 5 January5 Jan by zacko_O

Hello @zacko_O / @Cairus ,

Thank you for your inputs.

I've found an interesting article:

https://www.drive2.ru/l/717744973889412385/

where the author mentions that you don't need any adapter with some minor tweaks in data set. But again this was tested on MQB platform.

Based on your expertise is this going to work for MQB-Evo?

All the best.

Edited 5 January5 Jan by djmartzian
Typo

Of course, if you know what you're doing.

Hello @Cairus ,

I've created a dataset based on the instructions from above article. Based on my logic, when "Voice" button is short pressed it should switch to "Sport" FPA profile without the UI interactions on MIB3.

Based on your expertise, is this correct?

Thank you

DA_0019_7208_38K_MZ0N_010FPA000003_MQB37WKONV_1push_voice_button.xml

Hello,

I've managed to create a new(hopefully correct) date-set that activates "Sport" FPA profile with "Voice" button (short press).

Source: https://www.drive2.ru/l/722508608016755839/

Cheers

DA_0019_7208_38K_MZ0N_010FPA000003_MQB37WKONV_voice_button_1push_sport.xml

Edited 7 January7 Jan by djmartzian

I'm not sure, I think it would be possible to adapt the newer key set for type: 5E3 919 719, so that the keys work the same as the older or original version: 3V0 919 719E.

For more information, I would need as accurate as possible pictures of the printed circuit board of the keyboards of type:

3V0 919 719

5E3 919 719

5E3 919 719E

What do you hope to achieve with this?

I could use these two keys that don't work right now...

What is the solution?