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
I updated the MSU and Seicane sent me a new system update. MCU is MTCE-2.65. After updating was complete i had lost my Bluetooth. WIFI works normal and all buttons around the HU is working normal Bluetooth is missing the device name and pass code that was there when it came stock. wont find my phone or odb2 adapter. I was wondering if there is a posiblity that it some how changed the Bluetooth settings?
Did you find a fix?
Hello Cody,
Did you get any feedback on this?
I've got the same problem on a MTCD GS unit, unresolved!
Richard.
Hi All
Thanks for any help you can give with this, i have been unable to find this problem mentioned elsewhere.
I have changed the mcu on my px3 1gb rk3188 head unit as i had been having trouble with the steering wheel controls being intermittent over the canbus.
I am sure my original was a kgl mcu but if i install that one and a few others i get a random beep every few seconds.
I have just tried the newest www and mx mcus and i also get the beep on these
The last mcu i had without the beep i think it was an mx one had no option for disabling the reversing camera
i was hoping to try hals nougat firmware however this requires a newish mcu.
Is there a fairly generic brand mcu which is likely to be a winner for me please or is there anything i can do to stop the random beeping please?
Also is there any way to make my steering wheel controls less intermittent please they will work fine for a while and then stop completely and same in the car diagnostics app so i assume it gets bored listening to the canbus and gives up.
it is a 2011 seat ibiza ecomotive.
Thanks
Kamcel
It could be the spring cable in the steering wheel if I understand correctly. My cable is going/intermittent but reprogrammed the buttons there are 2 sets for each button, I think it's a resistance issue, but it appears to be working for me.
Sent from my Z981 using Tapatalk
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.
Hello,
I have a Dasaita PX6 10.2" head unit running VIVID and the latest MCU 3.7.1 but I'm having problems with the phone. I can make phone calls directly from the head unit but not with "Hey Google".
All other Google assistant commands work fine but the phone doesn't.
Has anyone else had this problem or any ideas how to fix?
Thanks