14 juni 2016 om 13:27 #386
Daar het standaard Raspbian image zich prima leent voor het installeren van je can-bus module heb ik gekozen om deze distro hiervoor te gebruiken.
Vervolgens kun je hier relatief eenvoudig KODI aan toevoegen, door de volgende commando’s te geven vanuit een SSH Terminal (Putty bijvoorbeeld)
[sudo apt-get update]
[sudo apt-get install kodi]
Op dit moment is Kodi Krypton (v17) de meest recente versie, die wordt geïnstalleerd door bovenstaande commando.
22 april 2017 om 20:08 #8087
- Dit onderwerp is gewijzigd 5 jaren, 4 maanden geleden door Janssuuh.
I’m trying to get your custom RNS-E skins working but the current Kodi Krypton won’t accept them.
I’ve tried changing this line <import addon=”xbmc.gui” version=”5.3.0″/> to show version”5.12.0″ which allows the upload but the skins still do not work.
Do you know what else might need changing on the skin?6 mei 2017 om 23:08 #8440
I assume you’re not using a Kodi install on top of the default Raspbian build?
Latest Kodi version on this build is 15.2.
If you’re using Krypton on OSMC, or OpenElec, my skin is not able to use the needed Python nor the C+ engines and would therefore return errors.
If you’ve managed to get Krypton to work on top of a Raspbian build though I’ll be happy to help you get the skin to work!14 mei 2017 om 12:50 #8711
Yes Raspbian, but I installed RetroPi and added the Kodi option so I’m wondering if all the libraries were installed.
I don’t know where to begin modifying your skin to work with Krypton so any help would be appreciated.
Dom16 mei 2017 om 08:41 #8763
I’ll try to reproduce your install somewhere at the end of this week.
Of course I’m very curious what changes need to be made to the skin to make it operational with Krypton.
Jeroen21 mei 2017 om 10:53 #8916
I’m also using Kodi 17 (Krypton) with Raspbian Jessie and can’t install the skin. The install process ends up with an error message.
Perhaps the skin isn’t compatible with Krypton?
If the skin works, I’ll try to connect your solution to my 2007 A6 4F with MMI 2G High. I think, the A6 MMI-Controls work in a different way than the RNS-Controls (the GUI of both systems looks nearly the same but has different hardware and a different OS) – but perhaps the CAN-IDs are the same or I simply have to replace them with the 4F-IDs.
Keeping the fingers crossed. 😉
BTW: Jeroen, your solution is by far the best and most professional, I’ve seen around the whole wide net. That was, what I was looking for. It’s important for me to “emulate” the look of the MMI-GUI to make it look as original as possible. Any other solution looks like a cheapo China-RNS.22 mei 2017 om 14:38 #8942
Thanks for liking the skin 🙂
I know what you’re saying about making it ‘as OEM as possible’!
I haven’t had the time to check on the Krypton issue. Hopefully I find some time tonight.
About the 2G MMI connection;
– Probably there are again a Can-L and a Can-H wire, which you want to connect to your raspberry
– First thing to check is whether the Bitrate is or isn’t the same as on the B6/B7 infotainment bus (100K).
I added an auto-log function to the skin, which logs the first 7500 messages (if bitrate is consistent)
(The logfiles are saved at “pi/home/rnslogs” with included date/time stamps. But it will only be triggerd if the date/time was sent over the bus – might be something I’ll need to find a workaround for in your case.)
If the Bitrate is correct and the log works you could save 2 logs;
1) log of idle state (probably with ignition key on) doing ‘nothing’
2) log again with same conditions (no doors open / doing anything), but with pressing you MMI buttons as soon as the skin is loaded.
With the 100k my bus works with, within 1 to 2 minutes the first 7500 messages are captured.)
Afterwards you just try to find differences in used ID’s.
Of course I’ll be very happy to help you with this!
Jeroen22 mei 2017 om 20:18 #8948
Thanks a lot, man! Your site and help rocks!
I ordered the PiCAN2-Board from SK Pang today. If it arrives by (hopefully) next week, I will connect it to my CAN-Bus. So it isn’t urgent to make the skin run with Krypton.
Indeed there is a twisted pair of H-and-L-Canwire in the trunk of my Avant, but this is only for the Comfort-CAN. The A6 4F has three different CAN-Networks: Engine-CAN, Comfort-CAN (Controlling Ignition, Doors, Windows, Lights, …) and Multimedia-CAN.
The controls on the steering wheel use the CAN-Bus, while the Main-Control in the Center-Console uses RS232-Serial-Protocol to send its commands to the MMI-Headunit. What a mess. But we will see, as soon as we can do some logging and sniffing. ;-P
Stefan14 juni 2017 om 09:34 #9465
anything new about using the skin with Kodi 17 Krypton? 😉22 juni 2017 om 13:39 #9625
It seems to be a bit more of a pain then I expected.
Lots of xml templates were changed , deleted and / or merged (comparing Kodi 15 to Kodi 17).
Also since latest official version of Kodi is still 15 I would have to maintain 2 versions of the skin :-S
I’ve read somewhere an A6 4F uses MOST Can-Bus (optical bus). Did you get to manage any communication between your car and the raspberry?
Jeroen26 juni 2017 om 14:20 #9711
Uhhh… seems to be really a lot of work for you to make your cool skin work with Kodi 17. Could be a pain in the ass. So, another solution could be, to install Kodi 15 under Raspbian – just to be able to use your skin.
If you can manage it to make it work with Kodi 17+ it would be really cool and of course I would pay for it!
Yes, the A6 4F uses more bus-topologies. As already mentioned, 1 CAN-Network for the engine / drivetrain, 1 CAN-Network for Comfort-Functions. These are normal twisted wires CANs.
The optical MOST-BUS is the multimedia bus – only for controlling and monitoring the multimedia-devices like radio, TV, CD-changer, AMI and so on – and for transporting their multimedia-contents.
MOST- and wired CAN-Bus get connected in the CAN-Gateway.
The A6 4F Facelift (since 2008 / with MMI 3G) got rid of the MOST-Bus. It uses the wired CAN-Network for exchanging multimedia-contents. I don’t know, why they dropped the MOST… perhaps the production was too cost-intesive.25 juli 2017 om 13:57 #10442
Hi Don / Stefan,
Finally got it to work with Krypton…
Please get your copy from the download section 🙂
Jeroen25 juli 2017 om 16:31 #10500
You’re an absolute star Jeroen.
Many thanks for all your hard work. I’ll try it out later this week. really looking forward to it.
Dom30 juli 2017 om 01:22 #10655
No luck. I installed the skin and the RNS-E skin logo briefly appeared in the top right of the screen before the screen went blue with just the clock showing in the top right. Also a pinging noise every second.
The only way to stop it was to disable the skin through the web interface.
Not sure if it makes a difference but my pi is still sitting under my TV until I get it configured correctly. I changed the screen resolution through the web interface to 640×480 but this made no difference.
My Krypton is showing version 17.1
Dom3 augustus 2017 om 17:13 #10775
There seems to be an issue getting first time default settings to work.
I commented this out (default settings will load on second boot).
Would you try 0.0.33 version please?
- Je moet ingelogd zijn om een reactie op dit onderwerp te kunnen geven.