Related
Hi MTCD community.
Thanks to the time between the years (that's how we call December 27th to 31st in Germany), I had time to upgrade my HU. Up to now I had a RK3188 quad-A9 one (Erisin ES2508B, KGL) that had a proprietary power connector and a external canbus decoder box. (more information here: http://vi.vipr.ebaydesc.com/ws/eBay...descgauge=1&cspheader=1&oneClk=1&secureDesc=0 )
That external canbus decoder of the unit has a few dedicated output pins for illumination, reverse gear and a UART (?) style digital RX/TX connection to send wheel-button key commands. It's a perfect example for a Chinese product. This solution it easy and works - almost:
On Mercedes cars the wheel-buttons are used to steer the so called Kombi (KI). KI and HU are connected via canbus. Key commands are send in one specific can-message. The canbus decoder box is said being made specifically for Mercedes cars. While it correctly decodes button presses it fails to decode the current KI menu. As a result the HU will always interpret the "prev./next" buttons, even when you're not in the KI's Audio menu. As a result you either stop using your KI (bad option) or you disable some keys in the HU (that's what I did). The decoder box is also only reading the canbus and thus not able to send audio titles or the current radio frequency/station name to the KI.
Because of the decoder box sitting between HU and KI I never tried to enhance functionality because that would have ment either connecting another R/W canbus dongle to the HU or replacing the chinese decoder box and reverse engineering the RX/TX communication between decoder box and HU.
---
The newer PX5 unit that I now own (Erisin ES7689C, KGL?/LM?, http://www.ebay.co.uk/itm/Android-8...s-W203-W209-/123151147422?hash=item1cac61619e ) has a Quadlock connector (that's the correct name for the multi pin connector that became popular on HUs beginning in the early 2000th) and no external canbus decoder box (it is indeed perfectly plug'n'play). It is also able to identify itself to the KI as Radio which means it is also writing to the canbus. Compared to an original OEM HU, information is still extremely limited and it again fails to interpret only wheel-button commands send from the KI's Audio menu. - But, it is able to write to the canbus, so potentially this is a much better starting point for enhancements.
Now the key question: Does anyone know how the HU is communicating with the canbus? Is the decoder box just inside the HU's housing (and again being an extra translation module) or is it a proper canbus device controlled by an app or service from inside the HUs android?
Good piece of info mate. Thanks a lot
Unfortunately i am not able to answer the question due to limited knowledge.
I own a Mercedes w164 and have the same issues and i am keen to find a solution. Open a thread for that too here > https://forum.xda-developers.com/an...t/adapter-help-mercedes-t3903165#post79005544
My MTCD idetails are :
Unit: MTCD PX5
MCU: MTCE_GS_V3.00_3
ROM: Halk9 Mod 3.1 (Android 8)
Can Adapter : GS 10280514 / HW:V2 SW:V3
Can adapter Setting: 23 Benz_B200(simple)
On another thread more HW related you can find pleanty of info >
https://forum.xda-developers.com/an...elopment/mercedes-benz-class-comfort-t3680320
Also this guy did some work on canbus : http://honeysw.com/canproject.php
and here another piece of info : https://forum.xda-developers.com/an...-units-qa/how-bus-messages-make-unit-t3352343
Hi I also have a MB lol, a w203.
I have been through several head units of types makes etc, so know exactly what you mean. Although I never heard of 'ki' before.
My latest unit I have is def very good (best was a pioneer with separate car-pi can decoder) and that is also an erisin.
Great minds an all that eh!
The unit I have is a 4/32gb android 8. MTCE. It was working very well until I developed a problem with my reverse camera signal not getting picked up. Was switching OK but no image??
Anyway I bit the bullet and installed the custom rom by Malaysk which helps the camera but no steering control (for me) on 3rd party apps.
There is some talk about mtce files etc but I couldnt get anything to work until I installed a brilliant prog called mtcdtools (free from github).
Very techy to understand / use but with the info and help from others managed to replicate enough to get the two up/down left buttons working perfectly on all apps. It starts up by itself and stays in background. I'm very pleased with result and sure it could do much more if i only knew how. Def give it a go.
Also the up/downs only while in the audio sub menu and they operate whichever music app is running even while in the background if that makes sense. The right volume buttons always worked anyway, and with the phone.
I think the real challenge now will be getting info in the dash display to correspond with what ever app is on top. Currently mine just says audio off when using dab, but displays station number in radio and time elapsed from music player., but nothing from nav.
Hi
I have purchased an Android HeadUnit for my Renault Megane 2 (2007) from AliExpress. Every function works except the steering wheel controls. The unit has the UIS7862 CPU @1.8Ghz, 6gb Ram and 128gb storage. I have installed the CanBox correctly and tried many CanBox settings in factory menu, but I cannot get the control app to enter learning mode. Does anyone have any idea? Maybe the built in key map application is at fault (com.syu.steer).
Did you find a solution to your problem yet?
I'm stuck at the exact same scenario, same unit. The support over at AliExpress mention to me to select "XP" for canbox settings. However, my canbus module is by Raise, hence I should be using the "RZC"
Also, my reverse cam doesnt work too.
Pls share your findings. Thank you!
I got the steering wheel keys to work with a custom controller made by an engineer in my country specifically for my car and my HeadUnit. The controller is connected directly to the wheel controls and the "key" wire on my HeadUnit. I had to disassembly the steering wheel base and route the cable around the original one. Now I can map every key to an action in the Key Learning app. For the backup camera, because I used a wireless kit, I couldn't use the "back" camera wire to trigger the HeadUnit to switch to it. The kit came with a receiver which only had power wires and a yellow RCA cable. I wired the receiver's power cables to the ACC power so that the receiver only powers on when the engine is running and I managed to map a button on the steering wheel to switch to the RCA input. Now when I want to use back up camera, I just need to press a button to see the image. The camera's transmitter is wired to the license plate bulb and I managed to fit it in the rear bumper.
This wasn't a "plug and play" experience that the Chinese seller promised, but overall I can say I am pretty happy with the end result. The audio quality is wayyy better than the stock HeadUnit. I didn't know that my stock speakers could get that loud and have so much bass. The DSP chip does it's job wonderfully. Also the radio reception is better than with the stock unit. The Android HeadUnit is fast and snappy. Apps open almost instantly and those 6gb of ram really help. I could compare the overall user experience with my OnePlus 7 phone. The unit also cold boots very quickly. The wifi reception is pretty poor. The unit shows 75% signal when my phone is in the car. It doesn't bother me because I put a Sim card in the unit and the mobile reception is as good as on my phone.
andrei-2200 said:
I got the steering wheel keys to work with a custom controller made by an engineer in my country specifically for my car and my HeadUnit. The controller is connected directly to the wheel controls and the "key" wire on my HeadUnit. I had to disassembly the steering wheel base and route the cable around the original one. Now I can map every key to an action in the Key Learning app. For the backup camera, because I used a wireless kit, I couldn't use the "back" camera wire to trigger the HeadUnit to switch to it. The kit came with a receiver which only had power wires and a yellow RCA cable. I wired the receiver's power cables to the ACC power so that the receiver only powers on when the engine is running and I managed to map a button on the steering wheel to switch to the RCA input. Now when I want to use back up camera, I just need to press a button to see the image. The camera's transmitter is wired to the license plate bulb and I managed to fit it in the rear bumper.
This wasn't a "plug and play" experience that the Chinese seller promised, but overall I can say I am pretty happy with the end result. The audio quality is wayyy better than the stock HeadUnit. I didn't know that my stock speakers could get that loud and have so much bass. The DSP chip does it's job wonderfully. Also the radio reception is better than with the stock unit. The Android HeadUnit is fast and snappy. Apps open almost instantly and those 6gb of ram really help. I could compare the overall user experience with my OnePlus 7 phone. The unit also cold boots very quickly. The wifi reception is pretty poor. The unit shows 75% signal when my phone is in the car. It doesn't bother me because I put a Sim card in the unit and the mobile reception is as good as on my phone.
Click to expand...
Click to collapse
Thank you for explaining your solution. Seems like quite a bit of work.
I managed to get my steering controls working finally. Got the correct canbus setting and corrected a connection.
Now, I'm stull stuck with the reverse cam issue. The +12V does energize when I am in reverse gear - I tested this when I connected my cam to DV-in and cam turns on only when in reverse.
But I just don't understand why the Android won't switch to Cam in during reverse gear.
Will continue to seek help from the manufacturer. Otherwise, it's a great HU as you said. Awesome speed!
MasK said:
Thank you for explaining your solution. Seems like quite a bit of work.
I managed to get my steering controls working finally. Got the correct canbus setting and corrected a connection.
Now, I'm stull stuck with the reverse cam issue. The +12V does energize when I am in reverse gear - I tested this when I connected my cam to DV-in and cam turns on only when in reverse.
But I just don't understand why the Android won't switch to Cam in during reverse gear.
Will continue to seek help from the manufacturer. Otherwise, it's a great HU as you said. Awesome speed!
Click to expand...
Click to collapse
You connected the reverse wire?
Maybe this triggers the camera view of it doesn't work via the canbus.
Well, it does work via canbus, just doesnt switch to cam input automatically. Perhaps its some software settings.
MasK said:
Well, it does work via canbus, just doesnt switch to cam input automatically. Perhaps its some software settings.
Click to expand...
Click to collapse
Not all canbus provide the reverse signal. So maybe you have to provide the reverse signal on the separate input.
TorstenH said:
Not all canbus provide the reverse signal. So maybe you have to provide the reverse signal on the separate input.
Click to expand...
Click to collapse
I feel that the HU knows when I am referring (CANBUS might be working here), because the 12V turns on when Im in reverse. The only issue is the HU doesnt switch to the cam automatically. Looks to me like a SW issue. Still awaiting reply from manufacturer.
Also, I realised my backward/forward buttons are swapped. Why is it I can't re-learn them?
It may not be the same for the Navifly, but on my unit, G5 must get the proper voltage to "detect" the car has been put in reverse. I'm re-using my factory rear view camera and it's a 6.5V camera. However, I had to up the voltage to 8.6V so that G5 go that voltage...then the rear image showed up. I reused the car wiring and that's why I had to do this.
Check the voltage that G5 is getting. With a canbus module, I believe there is a wire from the canbus going to G5. If no voltage, make sure the pins are in properly.
FYI, if you are using a canbus and the steering wheel controls go through the canbus, then I believe that you cannot remap the keys.
The 12 V from the reverse wire are coming from your car (or in some cases from the canbox if the information gets transmitted from car to the box via canbus).
My suggestion is:
There is a separate reverse connection (usually a brown wire) on the head unit which triggers the radio to open the app which shows the image of the reverse cam.
You could even connect ACC or B+ to the reverse connection for testing purposes.
mastrv said:
It may not be the same for the Navifly, but on my unit, G5 must get the proper voltage to "detect" the car has been put in reverse. I'm re-using my factory rear view camera and it's a 6.5V camera. However, I had to up the voltage to 8.6V so that G5 go that voltage...then the rear image showed up. I reused the car wiring and that's why I had to do this.
Check the voltage that G5 is getting. With a canbus module, I believe there is a wire from the canbus going to G5. If no voltage, make sure the pins are in properly.
FYI, if you are using a canbus and the steering wheel controls go through the canbus, then I believe that you cannot remap the keys.
Click to expand...
Click to collapse
Absolutely correct.
Thanks guys, but there is no other brown wire for this.
I have a discussion abt this on this thread too:
Medeke/Navifly 7862
Hi, Recently received above unit for my 2006 RS4. everything is great (much better then the M400 I had before) apart from the radio. It seemed to work for the first 2 days, then worked intermittently and now not at all. I have tried...
forum.xda-developers.com
My "cam12V" wire is from the HU and it turns on when I am in reverse. Does this mean that this signal might be coming from my canbus? If so, is there another input back to the HU to trigger the screen to display the video feed? Only other wires I see are AMP related
Give 12V to pin 2 and check if the app to display the image of the cam will start:
TorstenH said:
Give 12V to pin 2 and check if the app to display the image of the cam will start:
View attachment 5374441
Click to expand...
Click to collapse
Yes! It took me a while to figure this out.. mainly because I'll have to cut the wire (wasn't very confident in that)
and also.. the wires at Pin2 didn't make sense! They were more like Battery12V. I did cut and tested that.
So.. it turns out its a pink wire at pin3!
I realized this as I looked at my old Dasaita wires from the canbus connector. Since canbus is a standard, they should be comparable. That reverse wire went into Pin3.
I'm really surprised that Mekede and Navifly has this pin layout printed in all their listings.. but it's just wrong.
Thanks alot for the help!
That means it works now? I think you had to cut the ACC wire according to the manual because the "ignition on" information is provided by the can box.
TorstenH said:
That means it works now? I think you had to cut the ACC wire according to the manual because the "ignition on" information is provided by the can box.
Click to expand...
Click to collapse
Yes it works now. Check out the images. The Pin2 (red) is probably ACC or batt 12V as there was no power when cut. I then cut the wire opposite it (pin10) in case I was looking at the connector wrongly. That turned out to be the headlight sensor.
After tracing the wire and comparing to my old Daisata, it turns out Pin3 (pink) is the reverse IN.
Excellent. Thanks for the clarification.
That means it makes sense to get the wiring diagram from the old radio of the car and compare it with the description of the new head unit.
In my case I had to completely rewire the harness (just if someone is interested):
Junsun V1 MTK8259 - the adapter battle (Kia Ceed Jd) / OEM camera usage / reference thread
I bought the Junsun V1 head unit but my Kia Ceed JD had a OEM nav unit which isn't directly compatible to Junsun V1. So I re-wired the wiring harness based on the pins description of my original OEM navigation unit. I'm only modifying the wiring...
forum.xda-developers.com
The only thing that I could compare to (between old and new HUs) is the canbus connectors. Rest cannot be compared as they're all different.
Oh well..
Anyways, the current Mekede I have has Radio chip NX6686. My old Dasaita PX5 also has a NX6686. However, the radio reception is absolutely trash in the new one. I dont listen to radio that often (I can resort to streaming radio) but my dad takes the car occasionally and he's already complained about it
Your experience on the harness rewiring is pretty intense!
Update: Turns out my Antenna connector was a tad loose and I had to do a re-connect. The radio reception is all good now
MasK said:
Thank you for explaining your solution. Seems like quite a bit of work.
I managed to get my steering controls working finally. Got the correct canbus setting and corrected a connection.
Now, I'm stull stuck with the reverse cam issue. The +12V does energize when I am in reverse gear - I tested this when I connected my cam to DV-in and cam turns on only when in reverse.
But I just don't understand why the Android won't switch to Cam in during reverse gear.
Will continue to seek help from the manufacturer. Otherwise, it's a great HU as you said. Awesome speed!
Click to expand...
Click to collapse
So you found correct canbus settings and connections .. i cant find anything about you sharing them
Hello. I am looking for a radio to install in my skoda Rapid and I have doubts regarding these FYT uis7862.
1- Would the parking sensors work acoustically and visually?
2- Could I see the information of open doors, temperature, etc on the screen?
3- Can it be integrated with the car's on-board computer to see the phone or navigation?
4- What can be done with these radios that cannot be done with a Px6 or vice versa?
Do you mean FYT based UIS7862
marchnz said:
Do you mean FYT based UIS7862
Click to expand...
Click to collapse
Yes
1- Visually (someone correct me if I'm wrong)
2- Depends on your car and canbus
3- Depends on your car and canbus
4- Esasy rootable and many mods available !
@albertron The canbus is one of the biggest unknowns. Unless there is someone with the same car model and audio, amplifier and climate control as you, there is no way to know unless you try it yourself. You can ask the reseller, but if they say everything works and then it doesn't, what will you do?
Each manufacturer/reseller of these Android head units has code that works with the canbus modules. They don't share code. Some manufacturers are better than others with the canbus coding. Your experiences with other head units, such as a PX6, are not relevant as the code on the PX6 may or may not be used in these newer models.
As cars electronics change and become more complex or various items are integrated such as climate control through the head unit screen, canbus coding for the manufacturers of these head units becomes more difficult. My car is a 2012 Kia Sorento with an amplifier. The audio from the head unit to the amplifier is the only thing that uses the canbus that is used by my head unit. The canbus module that the reseller provided did not work and I had to purchase an aftermarket interface module. I was lucky that I found it. If I didn't find the interface module, I would have a paperweight that I would try to sell.
So, if those items you mention are important or required for you, I would make sure those functions work for your specific setup before purchasing a head unit...any head unit.
The above is what I've come to believe and based on my experience with my head unit and what I've read on various forums.
@mariodantas @mastrv
Thanks for answering. So it's best to ask the seller. Really the only thing that matters to me is that the parking sensor and the buttons on the steering wheel work, the rest of the things are secondary. I have also seen that most radios do not include the canbus adapter and you have to buy it separately, spending another €30. I'll have to look first for an adapter compatible with my skoda Rapid. Although I still have doubts about whether to take a px6 or a FYT with uis7862. I also have the option of an rcd330, but it has bugs that are too serious for me.
What would you do? My use will be 90% listening to music with tidal, and fm radio. The remaining 10% I will use a GPS navigator to travel.
albertron said:
@mariodantas @mastrv
Really the only thing that matters to me is that the parking sensor and the buttons on the steering wheel work, the rest of the things are secondary. I have also seen that most radios do not include the canbus adapter and you have to buy it separately, spending another €30. I'll have to look first for an adapter compatible with my skoda Rapid. Although I still have doubts about whether to take a px6 or a FYT with uis7862. I also have the option of an rcd330, but it has bugs that are too serious for me.
What would you do? My use will be 90% listening to music with tidal, and fm radio. The remaining 10% I will use a GPS navigator to travel.
Click to expand...
Click to collapse
Your parking sensors will definitely work. If you get the correct canbus decoder you will also have visual parking sensors display on your headunit.
Chances are it will work as VAG group canbus codes are pretty well known. I helepd a friend install a MEKEDE unit in a Golf 5 and, even if this particular model was not a choice in setup, canbus integration worked out of the box.
PX6 units are obsolete, go for a FYT unit.
m00n61 said:
Your parking sensors will definitely work. If you get the correct canbus decoder you will also have visual parking sensors display on your headunit.
Chances are it will work as VAG group canbus codes are pretty well known. I helepd a friend install a MEKEDE unit in a Golf 5 and, even if this particular model was not a choice in setup, canbus integration worked out of the box.
PX6 units are obsolete, go for a FYT unit.
Click to expand...
Click to collapse
OK, thanks. I think I'll buy a medeke or navifly then. First I will ask the seller if it is compatible with my car's canbus. Another question I had that I forgot to ask: 1 year ago I had an Android radio in another vehicle, and the tidal app interface was unusable when in landscape mode. By any chance someone has it installed and can tell me if they have fixed it? The problem was that you can't access the search, or playlist, or anything. Only the music player comes out with the last song you listened to. Tidal is my main music medium, and if it still doesn't work I could consider other radios with original Android auto.
I have a Joying uis7862 based unit. It does or can do all the things you asked. Canbus adapter was included with the wiring harness. Specifically I have the JY-VQ130N4GN in a 2010 VW Passat.
I see that they offer a number of units for the Skoda Octavia. I don't know how similar the dash of the Octavia is to the Rapid.
Hi everyone
I have a facelift 2010 Lexus IS250 F Sport, I've had some large success installing this XTRONS head unit for it and I am largely satisfied with it. I am however having an issue with getting Steering Wheel Controls to work with the head unit.
Lexus | Various | Android 10 | Octa Core | 4GB RAM & 64GB ROM | Integrated 4G Solution | PMA10ISLS
XTRONS PMA10ISLS is a 10.1" large screen car stereo with customized face panel and optimized CANbus Decoding for Lexus. It supports CarAutoPlay, built-in DSP, PIP mode enabled ,Dual Theme, Instant Rear Vision and so on.
xtrons.co.uk
Lexus| Various | ISO Wiring Harness | MOST
This ISO Wiring Harness is compatible with XTRONS custom fit units PSP10ISL,PMA10ISL etc. If your car is Lexus IS250/IS300/IS350 Convertible (2-door)with original navigation or fibre amplfier system,you need this cable to aid for the installation.
xtrons.co.uk
This is the unit I purchased, alongside a special wiring harness so that I could use it with my vehicle as its a facelift Navi.
With the default CANbus setting on my head unit, only Volume control seems to work and the phone call buttons and voice command buttons are mapped to functions like Radio and Hey Google but I cannot programme these on the app. With an alternative CANbus setting I get skip track functionality but I get different AC Controls and lose access to my factory amp settings.
The original wiring harness I got for the headhunt has not been used at all as I was instructed to usr the special harness, and that original harness had a CANBUS decoder. XTRONS claim that I am unable to programme the SWC due to the CANBUS needing to decode it, although I have played around with the settings and selected various different CANBUS settings.
Would anyone be able to advise me on how I can get the SWC working, would it involve plugging the CANbus decoder into the head unit? There is a 12 pin connection spare at the back but I am unsure if that would make the difference or not.
I'm not sure this is the best place for this, but given how hard it was to find good information about this combination, I thought I'd put it here.
I purchased a M500S for my MkVI GTI, however when I installed it, I couldn't get any audio output. Searching the internet for how to use the stock amp with an aftermarket head-unit yielded lots of different information, most of it wrong. I talked to the vendor, but they were less than helpful, indicating that Dynaudio was unsupported with this head unit (true) and that VW used an optical signal to communicate between the head unit and amplifier (untrue). I saw a post from @COASTER19 regarding reading the steering wheel buttons on an Audi here, which looked awfully similar to my steering-wheel/gauge cluster, so figured I'd give it a go myself.
So I built hooked a cheap CAN bus controller to a Raspberry Pi, and analyzed my current (working head unit). I was able to determine that:
The media CAN bus runs at 100 kbps (as opposed to the drivetrain canbus which runs at 500 kbps)
The amplifier has an identifier of 0x6C7
The amplifier can be powered on/off via CAN bus commands
Once powered on, the M500S audio worked fine
The amplifier supports direct balance/fade commands (which may be useful some day in the future)
With this info, in hand, I made a simple circuit from an Arduino Pro Mini + MCP2515 module that is activated from the 'Amp Power' lead on the back of the radio. It simply replays the messages I snooped from the current head-unit, and now my M500S works perfectly with the stock Dynaudio amplifier/speakers. I don't currently send the fade/balance commands to the amp, so maybe the quality could be better, but that is a project for another day.
I have released the schematics, code and what CAN info I have on GitHub here.
In theory this project could completely replace the module that came with the unit and/or provide music/navigation updates on the gauge cluster as well, but that requires figuring out how to get that info out of the head unit, and I don't have the time to write an Android application to do so right now.
While trying to identify the CAN ids, I found this post by @hugovw1976
regarding a Golf 6 with some CAN bus commands: https://forum.xda-developers.com/t/mtcd-kgl-px5-canbus-problem-with-vw-golf-6.3632690/post-73939457
That post identifies the following canids:
0x2C3: power on/off
0x635: lights on/off
0x470: doors open
0x35B: RPM
0x527: Speed and outside temperature
0x621: Wiper state and fuel level
0x65D: odometer
0x351: reverse and brake
0x571: battery voltage
0x151: seat-belt state
I didn't spend too much time investigating these, but I at least see some correlation with the battery voltage, door-open, and fuel-level canids, so they are probably accurate. However, I was not able to correlate the odometer, so probably further investigation is needed there.
AxesofEvil said:
I'm not sure this is the best place for this, but given how hard it was to find good information about this combination, I thought I'd put it here.
I purchased a M500S for my MkVI GTI, however when I installed it, I couldn't get any audio output. Searching the internet for how to use the stock amp with an aftermarket head-unit yielded lots of different information, most of it wrong. I talked to the vendor, but they were less than helpful, indicating that Dynaudio was unsupported with this head unit (true) and that VW used an optical signal to communicate between the head unit and amplifier (untrue). I saw a post from @COASTER19 regarding reading the steering wheel buttons on an Audi here, which looked awfully similar to my steering-wheel/gauge cluster, so figured I'd give it a go myself.
So I built hooked a cheap CAN bus controller to a Raspberry Pi, and analyzed my current (working head unit). I was able to determine that:
The media CAN bus runs at 100 kbps (as opposed to the drivetrain canbus which runs at 500 kbps)
The amplifier has an identifier of 0x6C7
The amplifier can be powered on/off via CAN bus commands
Once powered on, the M500S audio worked fine
The amplifier supports direct balance/fade commands (which may be useful some day in the future)
With this info, in hand, I made a simple circuit from an Arduino Pro Mini + MCP2515 module that is activated from the 'Amp Power' lead on the back of the radio. It simply replays the messages I snooped from the current head-unit, and now my M500S works perfectly with the stock Dynaudio amplifier/speakers. I don't currently send the fade/balance commands to the amp, so maybe the quality could be better, but that is a project for another day.
I have released the schematics, code and what CAN info I have on GitHub here.
In theory this project could completely replace the module that came with the unit and/or provide music/navigation updates on the gauge cluster as well, but that requires figuring out how to get that info out of the head unit, and I don't have the time to write an Android application to do so right now.
Click to expand...
Click to collapse
I registered to this forum specifically to reply to your post. THANK YOU. I have just installed an aftermarket head unit and it went swimmingly until I discovered that it doesn't play nicely with my factory upgrade audio system. Then things went from bad to worse when I discovered that the Dynaudio/Fender amplifier is controlled via CAN, not just some 12V signal. I was going to reinstall the factory RNS510 and sniff the CAN bus when I came across this post and your github code.
I have not tried it yet, as I am hoping that the vendor (who is VERY responsive) will be able to integrate it right into the radio. Failing that, I'll be able to whip up a similar circuit to yours and be up and running. Thank you for sharing not just the code, but the technical details behind it. I truly appreciate it!