Milezzon
  • Posts: 14
  • Joined: 8/7/2019
Hi all,

Just got my car back from my local Audi garage and I noticed that my MMI buttons does not work. When I checked my Realsun Settings the Can information is gone, see picture. I have tried to load the Can file from Google drive, and it says success but when I restart my RSNAV device the problem remains. Have also tried to do a factory reset but still no luck. Anyone got any suggestions how to solve my problem? Running the latest RSNAV software.

Picture 

Regards
Erik
2016 Audi A3 8V 2.0 TDI Quattro, MMI Low/standard, RSNAV 7" Android 7, Hardware Version 3.0
DennisMitchell
  • Posts: 43
  • Joined: 8/5/2019
Scary. I would check the RSNAV harness connections, especially connections to CAN-BUS Gateway.
2014 Audi Q5 TDI Premium Plus, MMI HN+, B&O audio, RSNAV 8.8" Android 6, Hardware Version 1
Milezzon
  • Posts: 14
  • Joined: 8/7/2019
Hmm yeah, I probably must check the connection, it’s a very strange issue in my point of view. The good thing is that the device at least works but not as fluent as before, for instance it is a bit of a pain to go between Audi original interface and RSNAV interface. But everything works in the RSNAV device except the automatic brightness of the display.

Thanks Dennis!

2016 Audi A3 8V 2.0 TDI Quattro, MMI Low/standard, RSNAV 7" Android 7, Hardware Version 3.0
Milezzon
  • Posts: 14
  • Joined: 8/7/2019
Hi all,

The problem is now solved. It was not related to the hardware, loose connection etc. instead the problem was the CAN protocol. In other words, in the recent android 7 update you can choose the CAN protocol and I choose “A3” because that’s my car. Apparently, the change take place when you restart the device that’s why I did not experience any change in the beginning.
Now to the fun bit, the “A3” CAN protocol is NOT for Audi A3 and if used, the CAN row in the System Version Information row is blank and no MMI buttons works. The correct CAN protocol for Audi A3 is "A4L" and the change take place when you restart the device.
It took some time to realize this and I hope it can help someone in the future.

Regards
Erik
2016 Audi A3 8V 2.0 TDI Quattro, MMI Low/standard, RSNAV 7" Android 7, Hardware Version 3.0
DennisMitchell
  • Posts: 43
  • Joined: 8/5/2019
Interesting! Go figure.
2014 Audi Q5 TDI Premium Plus, MMI HN+, B&O audio, RSNAV 8.8" Android 6, Hardware Version 1
Benny
  • Posts: 1
  • Joined: 8/22/2019
Originally Posted by: Milezzon

Hi all,

The problem is now solved. It was not related to the hardware, loose connection etc. instead the problem was the CAN protocol. In other words, in the recent android 7 update you can choose the CAN protocol and I choose “A3” because that’s my car. Apparently, the change take place when you restart the device that’s why I did not experience any change in the beginning.
Now to the fun bit, the “A3” CAN protocol is NOT for Audi A3 and if used, the CAN row in the System Version Information row is blank and no MMI buttons works. The correct CAN protocol for Audi A3 is "A4L" and the change take place when you restart the device.
It took some time to realize this and I hope it can help someone in the future.

Regards
Erik



Thank you for the hint 👍 . I had the same issue since the installation a week ago. I drive an A4. Selected was the CAN protocol "A4L". The right protocol is "Q5.V2....". That`s a bit confusing. Now it finally works 😄


Regards
Benny


2013 Audi A4 3.0TDI Quattro, MMI3G Basic, AMI, RSNAV 10,25", Android 7, HW3.0
a_s-Oo4
  • Posts: 13
  • Joined: 10/22/2019
Hey! So I'm having a automatic brightness display issue also. I'm not sure if this will fix it, but it's worth a try. My 10.25 install is in a B8 A5 so I don't really know what setting in the CAN protocol needs to be selected.
Does anyone have any insight to this for me?

-A
2011 Audi A5 2.0T Prestige Quattro, 6MT, MMI3G High, B&O, RSNAV 10.25", Android 7, HW3.0
erik83
  • Posts: 91
  • Joined: 8/5/2019
Originally Posted by: a_s-Oo4

Hey! So I'm having a automatic brightness display issue also. I'm not sure if this will fix it, but it's worth a try. My 10.25 install is in a B8 A5 so I don't really know what setting in the CAN protocol needs to be selected.
Does anyone have any insight to this for me?

-A



I also have an A5 and I have CAN: Q5.V2.0.2.181226

Not associated to RSNav, just a community member helping.
2012 A5 2.0 TFSI Quattro (B8.5), MMI 3G BNav (EU)
RSNav 10.25" Hardware 3 , Android 6, System: M8.q5.2.0.1.04122016, MCU: 7.6.1212, CAN: Q5.V2.0.2.181226
a_s-Oo4
  • Posts: 13
  • Joined: 10/22/2019
@erik83

Thank you so much!!! I changed the CAN protocol to Q5 and that did the trick for most of my issues. 👍
It's weird that it's not named A5, but no biggie. I'll just make a mental note for myself to leave that setting as is.

2011 Audi A5 2.0T Prestige Quattro, 6MT, MMI3G High, B&O, RSNAV 10.25", Android 7, HW3.0
erik83
  • Posts: 91
  • Joined: 8/5/2019
glad it worked.

It would be nice to learn from Daniel why A3 needs A4L as CAN protocol, A4 needs Q5, and A5 needs Q5. That's a really odd convention
Not associated to RSNav, just a community member helping.
2012 A5 2.0 TFSI Quattro (B8.5), MMI 3G BNav (EU)
RSNav 10.25" Hardware 3 , Android 6, System: M8.q5.2.0.1.04122016, MCU: 7.6.1212, CAN: Q5.V2.0.2.181226
Forum Jump  
  • You cannot post new topics in this forum.
  • You cannot reply to topics in this forum.
  • You cannot delete your posts in this forum.
  • You cannot edit your posts in this forum.
  • You cannot create polls in this forum.
  • You cannot vote in polls in this forum.