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.
I have a one year old 7" Dasaita PX5 4GB RAM, Android 8, which performs flawlessly. Even the Blootooth and MIC volume level issue was solved in this unit, it has configured Bluetooth WD-BC6.
I wanted to upgrade to DSP, so instead of removing componentes and soldering wires , I just bought in Ali Express Dasaita Official Store the Dasaita MCU board with DSP:
https://es.aliexpress.com/item/32965198383.html?spm=a2g0s.9042311.0.0.6de363c0vGoD1p
After installation on new MCU board, everything is working fine, except Bluetooth, which is not working, if I go to FACTORY SETTINGS, (Password 126) I can select different Bluetooth Adapters, like: MD725, WQ_BC5, WQ_BC6, WQ_BC8, Parrot_FC6000T, SD-968, SD-BC6, SD-GT936, IVT-i145, SD-8350
But after trying several of them, Bluetooth is still not working. Dues anybody know which one I should select.
etulio said:
I have a one year old 7" Dasaita PX5 4GB RAM, Android 8, which performs flawlessly. Even the Blootooth and MIC volume level issue was solved in this unit, it has configured Bluetooth WD-BC6.
I wanted to upgrade to DSP, so instead of removing componentes and soldering wires , I just bought in Ali Express Dasaita Official Store the Dasaita MCU board with DSP:
https://es.aliexpress.com/item/32965198383.html?spm=a2g0s.9042311.0.0.6de363c0vGoD1p
After installation on new MCU board, everything is working fine, except Bluetooth, which is not working, if I go to FACTORY SETTINGS, (Password 126) I can select different Bluetooth Adapters, like: MD725, WQ_BC5, WQ_BC6, WQ_BC8, Parrot_FC6000T, SD-968, SD-BC6, SD-GT936, IVT-i145, SD-8350
But after trying several of them, Bluetooth is still not working. Dues anybody know which one I should select.
Click to expand...
Click to collapse
what BT module does your new unit have?
I did not check the Bluetooth module and I mounted the unit in the car. I took pictures of the board, but they do not show the BT model. So to check it physically I would have to disassembly again. To save this step, I was asking here just in case somebody has this MCU and knows the anser. But looks like I'll have to dissassembly.
Finally, I removed the new unit to check the BT, and it ios as follows:
The BT card in the "old" (one year old) board is:
Silk Marks in the back of the PCB: GOC-MD-705D
Paper label on top of QFP IC (Probably FW version and date) = A5BC6 1907
To have it working I selected in HU Factory Settings : WQ_BC6
The BT in the new MCU with DSP is smaller (shorter) and marks are:
Silk Marks in the back of the PCB: GOC-RF210 2019.04.27
There are no FW labels in the ICs on Top side of the PCB
What do I have to select to have it working?
In Factory configuration, the available BT optios are:
MD725
WQ_BC5
WQ_BC6
WQ_BC8
Parrot_FC6000T
SD-968
SD-BC6
SD-GT936
IVT-i145
SD-8350
I am attaching pictures of Old and New BT boards.
MCU has the latest FW 3.37, but PX5 has Android 8.0 one year old.
etulio said:
Finally, I removed the new unit to check the BT, and it ios as follows:
The BT card in the "old" (one year old) board is:
Silk Marks in the back of the PCB: GOC-MD-705D
Paper label on top of QFP IC (Probably FW version and date) = A5BC6 1907
To have it working I selected in HU Factory Settings : WQ_BC6
The BT in the new MCU with DSP is smaller (shorter) and marks are:
Silk Marks in the back of the PCB: GOC-RF210 2019.04.27
There are no FW labels in the ICs on Top side of the PCB
What do I have to select to have it working?
In Factory configuration, the available BT optios are:
MD725
WQ_BC5
WQ_BC6
WQ_BC8
Parrot_FC6000T
SD-968
SD-BC6
SD-GT936
IVT-i145
SD-8350
I am attaching pictures of Old and New BT boards.
MCU has the latest FW 3.37, but PX5 has Android 8.0 one year old.
Click to expand...
Click to collapse
Good post, an example of what information to post. Also good /must to know MCU version and that you have upgraded it to the latest available.
Unfortunately I still dont know what BT module you have - it might be a new model or compatible with one of the others lists, or it might require new firmware. Have you tried cycling through all of the MCU BT options, restarting in between? Also try reviewing logcats for BT detected type.
Hi, thank you for your help.
MCU PCB is the latest one: HA-D6100-MAIN VER 0.1 20190701, that integrates a DSP board. MCU FW version is the latest one from Dasaita, MCU 3.37. I tried cycling all MCU BT options with restarting in between, but without success. I do not know how to check Android BT logs.
I purchased this MCU PCB in Aliexpress Dasaita Official Store and I send messages asking for support, but I got no answer. I had to open a dispute to get an answer from Dasaita, now they say that they will send a new BT module, but if the real problem is the lack of support by MCU FW, this new module will not fix the issue.
BT Module and MCU PCB are very new, so probably they will release soon a new MCU FW that will support it, but the Dasaita support
Still not working
etulio said:
Still not working
Click to expand...
Click to collapse
Hello. I had a similar problem. Today I solved it. With the help of seller Dasaita on Aliexpress, I found out that the motherboard has a fresh Bluetooth chip installed. As the seller says installed RF210 Bluetooth 5.0 chip, which is not supported by Android 8. Therefore, all you need to do is install Recovery Android 9, then the firmware with Android 9, and then in the Factory Setting, in the Bluetooth settings on the first tab, select RF210 (it will be added to the list, on Android 8 it simply does not exist). That's all. Everything worked for me. The sound is better than it was on the old Bluetooth chip.
555sssaaa said:
Hello. I had a similar problem. Today I solved it. With the help of seller Dasaita on Aliexpress, I found out that the motherboard has a fresh Bluetooth chip installed. As the seller says installed RF210 Bluetooth 5.0 chip, which is not supported by Android 8. Therefore, all you need to do is install Recovery Android 9, then the firmware with Android 9, and then in the Factory Setting, in the Bluetooth settings on the first tab, select RF210 (it will be added to the list, on Android 8 it simply does not exist). That's all. Everything worked for me. The sound is better than it was on the old Bluetooth chip.
Click to expand...
Click to collapse
Thanks for taking the time, your explanation solves the puzzle. Good to know they finally have an updated BT option, wonder if they improved the code/drivers.
I will add links. I installed Recovery and Android 9 according to the instructions Hal9k. Hal9k, thank you very much!
Link to his Mod - h t t p://4pda.ru/forum/index.php?showtopic=973606&st=0#entry91199154
Link to Recovery for Android 9 - h t t p://4pda.ru/forum/index.php?showtopic=883219&st=24080#entry84508631
The link to the instructions for installing Recovery - h t t p://4pda.ru/forum/index.php?showtopic=891403&st=540#Spoil-77218289-3
Probably on this forum there is a description of the upgrade from Android 8 to Android 9. But I rarely come here. I just saw a problem similar to mine and want to share its solution. I hope this helps someone.
Hello,
I have the PX6 (Adroid 9) with the RF210 BT module, but it doesn't work at all. I've installed the latest MCU and the one before that (MCU 3.45 then MCU 3.53).
I also installed the latest firmware update (20200521). In the end I also installed Hal9k mod, and it still doesn't work.
Does your BT work?
RupOase said:
Hello,
I have the PX6 (Adroid 9) with the RF210 BT module, but it doesn't work at all. I've installed the latest MCU and the one before that (MCU 3.45 then MCU 3.53).
I also installed the latest firmware update (20200521). In the end I also installed Hal9k mod, and it still doesn't work.
Does your BT work?
Click to expand...
Click to collapse
No, it did not work. But I did not try to install Android 9, mine was at Android 8.
SD-BC6
Hi,
I have tried all the BT setting and for me finally working SD-BC6 (PX5 with Android 9 Malaysk mod) . Finally means that my mobile can connect and working and ODB2 module can connect and working. All others setting worked only for mobile or only for ODB2 or not worked at all.
So, the Bluetooth function in Android Headunits act differently than an Android tablet would, for one, it's a handsfree receiver that does not allow (correct me if I'm wrong) uplink with another device.
I have a DSP amp combo that uses BT to connect to an Android phone/tablet, which works fine, but my Dasaita PX5 won't connect to it. It just sees it, pairs, but doesn't connect.
Is there any way I can use a generic Bluetooth USB dongle to connect to it instead? Or is there any other way to allow connection with other BT devices (I have no luck in connecting OBD dongles too, BT or Wi-FI).
Thanks.
The device isn't an MTCB, being a dasiata it's likely an MTCD.
The answer to the BT question is no, you can thank the developer of the device for the hacked BT implementation.
Requesting mod moves to MTCD general.
Cheers! I've been out of touch for a bit and completely forgotten about the MTCx denominatin,
Thanks.
marchnz said:
The device isn't an MTCB, being a dasiata it's likely an MTCD.
The answer to the BT question is no, you can thank the developer of the device for the hacked BT implementation.
Requesting mod moves to MTCD general.
Click to expand...
Click to collapse
So just to be clear before I go down this path, there is NO external USB bluetooth module that will work with an MTCE head unit? Even if the USB module somehow uses the driver/firmware in the factory settings dropdown?