Related
Hi i've two problem with CanBus on Vw Golf 6.
1. If i open APP for steering weel config i can't see any button and i can't configure anything
2. Doors open/close don't work. I can see Temperature, Oil, RPM but doors doesn't work at all
I've this problem with my actual PX5 KGL and with my old RK3188 unit
Details of my actual unit:
Type KGL
MCU 2.47
ROM Malaysk PX5 2.0
capu81 said:
Hi i've two problem with CanBus on Vw Golf 6.
1. If i open APP for steering weel config i can't see any button and i can't configure anything
2. Doors open/close don't work. I can see Temperature, Oil, RPM but doors doesn't work at all
I've this problem with my actual PX5 KGL and with my old RK3188 unit
Details of my actual unit:
Type KGL
MCU 2.47
ROM Malaysk PX5 2.0
Click to expand...
Click to collapse
1) car specific headunits which Steering wheel buttons control are based on Canbus Box CAN NOT BE MAPPED by the Steering Wheel APP. They are hardcoded to specific Headunit functions. There is a tool MTCDTools from @f1x that could help you to assign new functionalities to your SWC buttons.
2) I don't know why do you report it as a problem. It was promised to you that Doors Opening/Closing shall be working with the canbus box supplied? Each Can-Bus Box is capable to decode specific features of the car. If that functionality was not present on PX3 or PX5 is due to your can-bus CAN'T DECODE (or has not been programmed to decode) the open/close door system.
The CarSettings app just receive which functions are being decoded by your can-bus and show the decoded information received.
Can you point me to the location of the CarSettings app? I can't find it in my newly installed headunit. I couldn't find any in the Google play store.
I found a fix for you problem, capu81, you need to go to factory settings, Canbus and try to change the can bus setting with some other value. The can bus box has the ability to decode some dozen car types, and it's probably not set for your car properly. When this setting is done right the apps that everyone is looking for, the Car info and Car settings are going to be available and should contain all the old settings that were available on your factory head unit. The default password for accessing factory settings is usually 126.
And if the canbus decoder is not supporting your vw golf 6, then go to roadnavi and buy their CAN-bus Decoder and select the right model. Eg: RN Model: C257 Golf 7
Thank you to all for the answer.
The doors signal is not a big problem, l leave it in this way.
Steering Well remapping: with MTCD Tools i can create custom action. For example: i've button for MUTE. If i remap button with MTCD Tools and assign Vocal Google Search to it the action is fine but MTCD became MUTE. There is a way to disable factory action and use only MTCD Action?
I have this problem too (no mapping option) but my steering wheel works on my Ford Focus. Check your CAN Bus box and make sure the model of it matches what's selected in Factory Settings. My CAN Bus box is a Raise 06, likewise it is selected in Factory Settings to match it.
@capu81 I am having this same issue with my doors on my Erisin ES6405V. Currently emailing with Erisin back and forth trying to get this fixed. If there is ever an outcome, I will let you know.
capu81 said:
Thank you to all for the answer.
The doors signal is not a big problem, l leave it in this way.
Steering Well remapping: with MTCD Tools i can create custom action. For example: i've button for MUTE. If i remap button with MTCD Tools and assign Vocal Google Search to it the action is fine but MTCD became MUTE. There is a way to disable factory action and use only MTCD Action?
Click to expand...
Click to collapse
I have same exact issue. Did you find a solution to it?
Hello, I have the exact same problem only the other way around, my steering wheel buttons are mapped and working, car is showing open/closed doors but for oil, rpm, speed battery nothing. I tryed messing with the canbus setup and change to other setting from VWto maybe get it to work but no luck. Any ideas on how I can solve this? I have a MTCD unit px3 2GB 7.1.2
I have also problem with CANBus decoder. The only problem is that when i drive and change shift activate rearview camera, all the other stuff (swc, door signals and also reverse enable the rear view camera) works fine. There is something like update or a settings that works fine. I have a FIAT Bravo model >2007 and in factory settings seems to be all ok
dirty_dty said:
Hello, I have the exact same problem only the other way around, my steering wheel buttons are mapped and working, car is showing open/closed doors but for oil, rpm, speed battery nothing. I tryed messing with the canbus setup and change to other setting from VWto maybe get it to work but no luck. Any ideas on how I can solve this? I have a MTCD unit px3 2GB 7.1.2
Click to expand...
Click to collapse
j0nnymoe said:
@capu81 I am having this same issue with my doors on my Erisin ES6405V. Currently emailing with Erisin back and forth trying to get this fixed. If there is ever an outcome, I will let you know.
Click to expand...
Click to collapse
These are not "problems" - CAN Bus support depends on your car model, the manufacturer of the CAN Bus box and whether MTC/HCT have written the software for these things. If youve played araound with all the CAN Bus settings and not every function works then there is nothing you can do . . . apart from get hold of the CAN Bus protocol for your vehicle,, the MTCD MCU protocl and then write and app for it. There are 1000s and 1000s of cars on the market (and 1000s no longer made) it would be far too costly to make full CAN Bus support for EVERY car on sale, so only the most popular cars are supported and even then not all models and/or all functionality.
@j0nnymoe - dont waste your time contacting Erisin, they are a seller not a manufacturer and theres nothing they will be able to do.
@typos1 do you think maybe it can be fixed if I update the MCU to the latest version? It just seam strage for it to work in open/closed doors but not for the rest, I'm thinking maybe a mismatch of canbus and software and maybe that is why it dose not work. (Just a wild guess)
dirty_dty said:
@typos1 do you think maybe it can be fixed if I update the MCU to the latest version? It just seam strage for it to work in open/closed doors but not for the rest, I'm thinking maybe a mismatch of canbus and software and maybe that is why it dose not work. (Just a wild guess)
Click to expand...
Click to collapse
Updating the MCU may certainly help.
@typos1 that is good to know, I can keep my hopes high for a bit longer but I am sceptic about the MCU update [email protected] gave me.. He did not test it and there is nobody else I could find that updated to the latest version of XRC to confirm it is the right one.
dirty_dty said:
@typos1 that is good to know, I can keep my hopes high for a bit longer but I am sceptic about the MCU update [email protected] gave me.. He did not test it and there is nobody else I could find that updated to the latest version of XRC to confirm it is the right one.
Click to expand...
Click to collapse
What do you mean "the right one" ?
If you remember on the other thread, he just attached a dmcu file of the latest MCU for my XRC unit and said he did not tested it.
dirty_dty said:
If you remember on the other thread, he just attached a dmcu file of the latest MCU for my XRC unit and said he did not tested it.
Click to expand...
Click to collapse
I cant see any reason to doubt him.
@j0nnymoe - dont waste your time contacting Erisin, they are a seller not a manufacturer and theres nothing they will be able to do.
Yea I gave up on that a while ago. I've had a couple of these units before from other sellers (xtrons/eonon) and the canbus on those units worked fine. I suspect the KGL unit's doesn't like my car for some reason. I toyed with the idea of getting another canbus decoder..maybe if I can get one cheap enough I might try it.
j0nnymoe said:
@j0nnymoe - dont waste your time contacting Erisin, they are a seller not a manufacturer and theres nothing they will be able to do.
Yea I gave up on that a while ago. I've had a couple of these units before from other sellers (xtrons/eonon) and the canbus on those units worked fine. I suspect the KGL unit's doesn't like my car for some reason. I toyed with the idea of getting another canbus decoder..maybe if I can get one cheap enough I might try it.
Click to expand...
Click to collapse
Did you try another canbus decoder?
I've got an a3 and I'm using a kgl unit and nothing shows on my dis screen on the dash but when I've had a unit from xtrons before that did work.. I'm guessing kgl must use cheaper canbus decoders and I've been thinking like you and we're thinking of buying another decoder from xtrons to try
Question for VW, Skoda and Seat owners: Is there anybody here who is able to get their MTCD unit to show things like radio station frequencies on the build in MFD display? I have a Skoda Yeti (technically similar to Golf VI) and I am not able to make my MTCD unit with Malaysk 4.0 show these things on the MFD. Previously I had a Ownice C500 and that unit was actually able to show a compass on the MFD. I have seen pictures on an russian forum from a guy who could see radio frequncies on his Seat MFD (I think it was from a MTCB unit) . I am looking for a hint as to what settings I need to change in the ECU with my VCDS equipment. Thank you in advance.
Regards
Kurt Lund
Kurt Lund said:
Question for VW, Skoda and Seat owners: Is there anybody here who is able to get their MTCD unit to show things like radio station frequencies on the build in MFD display? I have a Skoda Yeti (technically similar to Golf VI) and I am not able to make my MTCD unit with Malaysk 4.0 show these things on the MFD. Previously I had a Ownice C500 and that unit was actually able to show a compass on the MFD. I have seen pictures on an russian forum from a guy who could see radio frequncies on his Seat MFD (I think it was from a MTCB unit) . I am looking for a hint as to what settings I need to change in the ECU with my VCDS equipment. Thank you in advance.
Regards
Kurt Lund
Click to expand...
Click to collapse
do you see anything on the MFD when using the original Bolero/Columbus/Amundsen?
If yes, then you don't need VCDS coding, the canbus adapter and MCU should do the job. I didn't try it on mine, i will do so later today and post results.
...and latest Malaysk is 11.5, not 4.0 btw
zerozoneice said:
do you see anything on the MFD when using the original Bolero/Columbus/Amundsen?
If yes, then you don't need VCDS coding, the canbus adapter and MCU should do the job. I didn't try it on mine, i will do so later today and post results.
...and latest Malaysk is 11.5, not 4.0 btw
Click to expand...
Click to collapse
I never had an original radio which was able to send information to the display. I tried various setiings in VCDS to see if I could enable something, but to no avail. Thank you in advance for looking.
Regards
Kurt Lund
BTW: The latest ROM for MTCD HU with PX5 processor from Malaysk is 4.0. 11.5 is for older type of HU.
Kurt Lund said:
Question for VW, Skoda and Seat owners: Is there anybody here who is able to get their MTCD unit to show things like radio station frequencies on the build in MFD display? I have a Skoda Yeti (technically similar to Golf VI) and I am not able to make my MTCD unit with Malaysk 4.0 show these things on the MFD. Previously I had a Ownice C500 and that unit was actually able to show a compass on the MFD. I have seen pictures on an russian forum from a guy who could see radio frequncies on his Seat MFD (I think it was from a MTCB unit) . I am looking for a hint as to what settings I need to change in the ECU with my VCDS equipment. Thank you in advance.
Regards
Kurt Lund
Click to expand...
Click to collapse
I have a SEAT Leon and a MTCD PX5. It only shows the radio station, but not the RDS info. If I use the music app or the bluetooth app the MFD only shows the number of the song but not the tags (name, artist, etc.) As I understand, it is something with the canbus.
Kurt Lund said:
I never had an original radio which was able to send information to the display. I tried various setiings in VCDS to see if I could enable something, but to no avail. Thank you in advance for looking.
Regards
Kurt Lund
BTW: The latest ROM for MTCD HU with PX5 processor from Malaysk is 4.0. 11.5 is for older type of HU.
Click to expand...
Click to collapse
a, ok i assumed u had a PX3
I have a 2010 GTI. Replaced the original radio with an MTCD.
Previously, my MFD would show compass direction (N, NE, E, SE, ect) next to the clock and I would also have a radio station section. After installing the MTCD, the compass would turn on, set to North, correct to the actual direction, then turn off again. It was a continuous 5 second cycle of this. I asked around on other forums and finally found that it just wouldn't work. One person just pulled out the compass unit. That's what I ended up doing. It doesn't bother me to not have it there if I'm just going to have navigation on my HU anyway.
For the radio, honestly, I never used the function on the MFD. It was easier to just cycle the presets using the steering wheel controls or pressing the button on the HU instead of changing to the radio function and scrolling through the list.
Troggie81 said:
I have a 2010 GTI. Replaced the original radio with an MTCD.
Previously, my MFD would show compass direction (N, NE, E, SE, ect) next to the clock and I would also have a radio station section. After installing the MTCD, the compass would turn on, set to North, correct to the actual direction, then turn off again. It was a continuous 5 second cycle of this. I asked around on other forums and finally found that it just wouldn't work. One person just pulled out the compass unit. That's what I ended up doing. It doesn't bother me to not have it there if I'm just going to have navigation on my HU anyway.
For the radio, honestly, I never used the function on the MFD. It was easier to just cycle the presets using the steering wheel controls or pressing the button on the HU instead of changing to the radio function and scrolling through the list.
Click to expand...
Click to collapse
I agree it is not the worlds most important function, but it irritates me that I cant get it to work anyway. Your GTI from 2010 has exactely the same ECU as my Skoda as far as I know so it ought to work.
What do you mean by "just pulled out the compass unit"? Physically took something out?
Regards
Kurt Lund
Kurt Lund said:
I agree it is not the worlds most important function, but it irritates me that I cant get it to work anyway. Your GTI from 2010 has exactely the same ECU as my Skoda as far as I know so it ought to work.
What do you mean by "just pulled out the compass unit"? Physically took something out?
Regards
Kurt Lund
Click to expand...
Click to collapse
Seems like there are always going to be little things you have to ignore when you go with non OEM electronics. I'm pretty picky about stuff, but I can let the radio go.
Yep, the compass module in my car is in the rear headliner. Just Googled it and found this video: https://www.youtube.com/watch?v=mw1T7oqiQsw
@Kurt Lund i checked on mine and in the "audio" menu it shows the FM frequency of the station playing (when in radio mode) and track# and mm:ss (when in default built-in music player mode). If i use poweramp it shows just "Video" input on the MFD, no track or counter info. I don't see a compass on the MFD since i didn't have an OEM navigation setup beforehand.
zerozoneice said:
@Kurt Lund i checked on mine and in the "audio" menu it shows the FM frequency of the station playing (when in radio mode) and track# and mm:ss (when in default built-in music player mode). If i use poweramp it shows just "Video" input on the MFD, no track or counter info. I don't see a compass on the MFD since i didn't have an OEM navigation setup beforehand.
Click to expand...
Click to collapse
The compass on mine always showed up as just letters next to the time. So, the very top would have something like "NE 5:34" or "S 6:20". There was also a calibration option in the MFD setup menu. Selecting calibration would require you to drive in a circle. I also didn't have a factory nav unit.
Is there a fix to this yet ? I installed a MTCD unit on my vw touran 2006 and at first (1-2 days) the MFD displayed Audio but no information.. that was not a problem since I could atlist use the buttons on the steering wheel to change the songs anyway.. but afther that the Audio from MFD dissapeared and the onky way I can change the songs are from the HU. (compas also dissapeared).
dirty_dty said:
Is there a fix to this yet ? I installed a MTCD unit on my vw touran 2006 and at first (1-2 days) the MFD displayed Audio but no information.. that was not a problem since I could atlist use the buttons on the steering wheel to change the songs anyway.. but afther that the Audio from MFD dissapeared and the onky way I can change the songs are from the HU. (compas also dissapeared).
Click to expand...
Click to collapse
anyone got a fix for this. i just got some zeroes in 2013 t5 when using dab or bluetooth audio.
If anyone is wondering, we can display on MFD using CanBus.
We can find adresses to write on internet: https://docs.google.com/spreadsheets/d/1eirT8LbSRl4j06BpwgsiE4PM_2BGH9UStdWLXwKvHJw
If someone is able to take info from android and send them through canbus you should display everything as original.
Here is a MFD compatible Head unit: http://m.cardvdstereos.com/android-8-0-car-dvd-player-vw-mqb-universal
If you ask for firmware of these unit you should maybe able to look how it works.
I looked at this. I had a windows CE head unit and that could display the MFD compass heading, so I know it should be possible with a non-VAG head unit. Looking at VCDS information it seems that compass information can be put onto canbus by either the head unit or a compass module. Cars without a VAG satnav such as the Columbus, would have a compass module instead, usually fitted in the top of the tailgate/boot/trunk.
So theoretically if you want the MFD compass and your MTCE head unit isn't putting the data on the canbus you could install a VAG compass module to do this. It would require VCDS coding to setup though; to register the compass module.
From what I've read it doesn't seem as if any MTCE head units put this compass data on the canbus; though there seems no reason why they shouldn't be able to do this. I would guess that it wouldn't even need a firmware mod, but could be managed in software.
UnReal' said:
If anyone is wondering, we can display on MFD using CanBus.
We can find adresses to write on internet: https://docs.google.com/spreadsheets/d/1eirT8LbSRl4j06BpwgsiE4PM_2BGH9UStdWLXwKvHJw
If someone is able to take info from android and send them through canbus you should display everything as original.
Here is a MFD compatible Head unit: http://m.cardvdstereos.com/android-8-0-car-dvd-player-vw-mqb-universal
If you ask for firmware of these unit you should maybe able to look how it works.
Click to expand...
Click to collapse
Interesting links! I'm really looking for something like this as well, but not with Android 8.1
I'm wondering how they've implemented this in the software. Is it like a driver for a system app or just a normal app?
I'm a developer myself and I feel like I can add this myself. I'm not sure though if I can just send whatever data I want over canbus via Android? Would be great to write some software for all of the VAG users here that have an Android unit so their MFD are fully working again.
I'm thinking of: Fully working navigation with the compass and the instructions, full working media display (FM, DAB, BT).
Bose321 said:
I'm thinking of: Fully working navigation with the compass and the instructions, full working media display (FM, DAB, BT).
Click to expand...
Click to collapse
That would be GREAT! I'm not a developer and an app like this would be awesome for me!
When I switched to Andorid unit instead of original unit, I completely lost any info from my unit to MFD: radio, compass, navigation, etc.
I unfortunately no longer have an Android unit in my car, so I would first have to find something for that and start programming on it. Is there any other interest in starting a project like this?
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.
I have a PX6 MAX6 unit that I bought for Toyota Rav4 that didn't have Carplay, now that my toyota's original unit has carplay, I've decided to mount dasaita's unit in my Citroen Nemo van, I thought it would be simple, buy a new cable and a canbus box (FT-SS-02A) everything works well, the unit turns on but when I try to choose my Canbus box in the list of available canbus is not my model (FT-SS-02A) , I have tried a thousand conbinations and none works, on a friend's radio I have tried the canbus box and it works perfectly and it is in the Canbus list, the model to choose it, we have tested his radio in my car and it works perfectly. I tried to upgrade with CANBUS.UPDE but it doesn't work, it doesn't update, I get an error. Does anyone know the solution?
I don't know how to change that information (the car part), how to copy the information from my friend's unit and paste it into mine, but I don't know how I could do it, because I have updated to the Hal9k Mod versión, MCU, and the “Car” part of the firmware has not changed It's the same, I don't know how to change the "Car" part for my friend's, sorry for my English is very bad.
Dasaita say: "Sorry, we don’t have a suitable canbus"
I wonder if they have a CanBus box/harness for Chrysler vehicles, I bet they do, as they sell units for Jeep. Citroen appears to be a division of Chrysler, now known as Stellantis. Not necessarily saying that all Chryslers are exactly alike but might be worth a shot....
Whatever box they're using for Chrysler might actually work for your application. Just a thought/suggestion.
And if you were to try this, choose one of the Chrysler options in the Canbus selection. The box you have might work if can find the right vehicle/canbus box combination.
Best of luck to you.