Dasaita Head Unit steering button issue - MTCB Android Head Units Q&A

My car is a 2017 WRX STI with Harman kardon system. I know the dasaita is not designed to work with it but I've put my own amp, wired new speakers and made it work. I was having issue with turning on my amp and backup camera when I put my car in reverse. However I was able to map all my steering wheel buttons correctly. Then after that, I was able to figure out how to turn on my amp by moving one of the wiring pins in the harness and connect directly to my remote turn on lead to the amp. Also I was able to provide power to the backup cam when I put my car in reverse and now it works. My issue now is that my directional buttons on the steering wheel doesn't work anymore. Other buttons work like the mute button. Anyone have a wiring harness diagram for the steering wheel buttons from dasaita? I had an Android head unit before and that one I had no issue with it recognizing the steering wheel button commands.

With "directional buttons" you mean up/down (prev/next) right?
So, the Android units do not have too many choices. You either use the CanBus provided by Dasaita (or several 3rd party) for your vehicle "family" (usually same CanBus shared among different car models and brands) and you live with whatever is supported (usually only Vol +/-, Mute, Prev/Next), or you connect your steering wheel buttons to the "Key-1" and "Key-2" cables on the unit and you configure/program the unit to execute an action when buttons are pressed.
For using Key-1 and Key-2 cables:
1) You need to verify that your steering wheel buttons are restive (pressing a button changes the resistance seen by the unit)
2) You need the diagram of your steering wheel as different sections are connected to different units on the car and so use different cables. As an example, on my Mazda:
- Perv/Next, Vol +/-, Mute are one resistance bridge that goes to the stereo (one cable, as the "-" is always chassis)
- Talk, Pick-up, Hang-down is another cable that goes to the Bluetooth unit (again one cable, and the bluetooth unit then connects to the Aux of the stereo)
- Up/Down/Left/Right and Enter (the other side of the steering wheel) goes to the Computer Display (have not played with this one, no idea if it is one cable or more)
In my case I left the Vol/Mute/Prev-Next alone as it was working via the CanBus, but I cut the cable going from the steering wheel to the Bluetooth Unit and connected it to Key2 in a PX5 MTC-D Dasaita unit and configured those keys to handle phone calls + Google Assistant. I guess I still have Key-1 if one day I want to completely kill the factory "computer display" that any way only shows basic statistics.
Hope this helps. I can share the Mazda Steering Wheel circuit so you can see what you should be looking for (most probably Subaru will use other color code for the cabling)

Key 1 Key 2
I bought some external buttons that I want to connect Android car stereo dasaita can you indicate the cables key 1 key 2 where to connect?

Related

Malaysk rom: how to startup app into background and cannot change steering buttons

Hi,
Ik use Malaysk rom (version RK3188) on an seicaneunit in my Mini Cooper R56.
I have some issue's/problems which i cannot solve or get an aswer to...
1.
I want to run the app 'flitsmeister' (a app for traffic info and speed traps warnings). This apps runs in background and popups when it detects traffic or a speed trap, this works OK. But when i start it on boot it stays on top until i press home etc. I would like to start this app on boot and it should run in the background or the home button should be 'pressed' automaticly after a few seconds.
Is there a way to do this in this rom?!
2.
I cannot change the steering buttons control, when i open the menu and press the key to assign it simply performs the default assigned function, i cannot change this in anyway. How can i change the behavour of the steering wheel controls and save this?
3.
Is there a update for a newer android version (5 or 6) for this unit which i can use?
Steerling wheel functionality works through a canbus which most newer cars have. Seicane eonon etc all use canbus.. however thats if your vehicle have one which it should. Problem one.. your missing a canbus..
If you have a canbus 2 issues possible.
Canbus is picky and eah make speaks their own language.. now most chinese aftermarket HU use a multi purpose canbus decoder which your vehicle may not pick up or you have a faulty canbus.
2. Canbus wiring.. now alot of makes run wiring through the oem harness.. depending the hu in the modle of car.. like running a stock crappy system vs an alpine, inifinte, bode system where multipul components talk.. but that then becomes a sound issues differet topic.
The canbus wiring itself could be wrong off the new HU harness you'll have to check seicanes crappy wiring diagram matching to your oem harness. Where the canbus connection is use a multimeter with the car off.., on accessory and started.
Future reference..
Seicane eonon etc have messed up the wiring giving the canbud power even when the car is off.. meaning they ran the power off the battery live wire.. vs just the accessory and on power wire.. draining the battery of your vehicle. Simple fix youll have to just switch the power wire to the correct wire being accessories and on.
At the end of the day you most likely need the canbus for the steering wheel functions to work. Ifcyou have it do soke trouble shooting

will axxess aswc-1 or maestro sw work with this radio

i have a 2106 wrx and i cant get my steering wheel controls to work, i have two buttons i can set for the two swc wires, i was wondering if anyone has had luck hooking either the aswc-1 or maestro sw up to this radio. mine is an mtcd kld. they only pair up with main stream radio brands. i have read of a few people having this same problem only being able to use two buttons out of the 11 that are on my steering wheel. out of the 11 buttons 5 do one command and 6 do the other command its like the headunit is not differentiating between the difference in resistance.
raekwonsr said:
i have a 2106 wrx and i cant get my steering wheel controls to work
Click to expand...
Click to collapse
I got a Subaru Levorg MY2016 with factory non-navi radio which uses resistor based SWC. I heard the models equipped with factory navigation might use something different so this might not apply to you.
Actually you should be fine connecting SWC ground and SWC1 + SWC2 to the corresponding pins (brown cables) on the MTCD head unit. You don't need any axxess or maestro. I tried to use axxess as well as often my buttons did stop working as it looks the resistor values might "drift" slightly after a while of operation. Results were that the ADC on the head unit reads different resistor values and therefore different button keypresses every now and then. You can see this if you go into the SWC learning app, then press any button. You should be able to map any button. If they stop working go into SWC learning app again and press one of the already mapped buttons. Now you will see if the HU recognizes the already-mapped button as a "new" button and asks you to map it.
As of later MTCE MCU versions on my KLD unit the SWC buttons don't work immediately after turning on the radio but just after about 20 seconds. But the mapping seems to be more stable.
Another work-around I implemented was to connect both SWC wires (SWC1 and SWC2 from the car) to SWC1 input on the HU adding a 680 Ohm resistor to one of the SWC outputs from the car in order to allow it to distinguish between them. Connected to a 3.5mm jack the mapping looks as follows:
Code:
_
/ \ -> SWC1 ----------------------------------- SWC1
--- /
| | -> SWC2 ------[R, 680 Ohm] ---/
---
| | --> GND ------------------------------------ GND
|_|
Things got much better with later MCU versions. So perhaps this hardware hack is not required any more for me too.
Also note that in factory settings (password 126) in "others" screen you can change the mapping of resistors for SWC, though I kept my one at default (10k/10k I believe). Caution: Don't change any values in factory settings if you don't know what you're doing or at least take screenshots/notes of the default values and export them before doing any change. You have been warned.
I have a pumpkin 7.1.2 headunit and a 2015 STI, most of the head units will have a unit to handle SWC inputs. ae64.com has a good write up for the pinouts for key 1 and key 2.
Check your wiring,
SkyBeam2048 said:
I got a Subaru Levorg MY2016 with factory non-navi radio which uses resistor based SWC. I heard the models equipped with factory navigation might use something different so this might not apply to you.
Actually you should be fine connecting SWC ground and SWC1 + SWC2 to the corresponding pins (brown cables) on the MTCD head unit. You don't need any axxess or maestro. I tried to use axxess as well as often my buttons did stop working as it looks the resistor values might "drift" slightly after a while of operation. Results were that the ADC on the head unit reads different resistor values and therefore different button keypresses every now and then. You can see this if you go into the SWC learning app, then press any button. You should be able to map any button. If they stop working go into SWC learning app again and press one of the already mapped buttons. Now you will see if the HU recognizes the already-mapped button as a "new" button and asks you to map it.
As of later MTCE MCU versions on my KLD unit the SWC buttons don't work immediately after turning on the radio but just after about 20 seconds. But the mapping seems to be more stable.
Another work-around I implemented was to connect both SWC wires (SWC1 and SWC2 from the car) to SWC1 input on the HU adding a 680 Ohm resistor to one of the SWC outputs from the car in order to allow it to distinguish between them. Connected to a 3.5mm jack the mapping looks as follows:
Code:
_
/ \ -> SWC1 ----------------------------------- SWC1
--- /
| | -> SWC2 ------[R, 680 Ohm] ---/
---
| | --> GND ------------------------------------ GND
|_|
Things got much better with later MCU versions. So perhaps this hardware hack is not required any more for me too.
Also note that in factory settings (password 126) in "others" screen you can change the mapping of resistors for SWC, though I kept my one at default (10k/10k I believe). Caution: Don't change any values in factory settings if you don't know what you're doing or at least take screenshots/notes of the default values and export them before doing any change. You have been warned.
Click to expand...
Click to collapse
you have no idea how helpful your post has been. I just installed a Pumpkin 7" Android 8 octa core AE0273B-08A in my 2005 Ford Excursion. Your trick is exactly what I needed to get my SWC buttons to work properly. I just kept reprogramming them under different conditions, like engine on then off, lights on, etc. I haven't tried the resistor yet.

Dasaita PX6 for Mazda CX7 trip computer and clock settings

Hello all
I have searched a lot and couldn't find any relevant information anywhere.
What I wanted was to be able to use the clock and trip computer in my car
(a 2008 Mazda CX7 with Bose audio). When the stock head unit is replaced
you lose the Info and Clock keys so you cannot adjust the time or change
between the various trip computer info.
So by playing around I discovered that you still can perform these actions
by using the steering wheel controls. In specific, if you press the MODE button
for 2-3 sec you enter the settings mode. There by pressing the UP arrow
you emulate the INFO key and by pressing the DOWN arrow you emulate
the CLOCK key. With the above information you can use the clock/trip
computer as before
The above might have application on other Mazda vehicles too that
use the canbus adapter to keep the steering wheel controls. Wouldn't
hurt to try anyway!
Now if only I could find a solution for the fader/balance problem of
the rear speakers (by utilizing the canbus adapter provided) I would be happy!
I made a small video showing the above for anyone that is interested.
youtube.com/watch?v=aJitnb5piiE
(I cannot post proper links yet)

Problem with MTCE PX5 head unit related to steering wheel keys

Dear community,
I'm kind of lost since I get no support from Erisin about this (no response)
I have a BMW E46 from 2002 and the Erisin head unit.
MCU version is stock px5 MTCE (px5-userdebug 8.0.0. OPR5.170623.007 eng.hct.20180417.101726 test-keys)
I liked the idea of controlling the head unit volume by steering wheel.
Therefore I wired and installed the steering wheel buttons to my car.
The ACC works fine and in general I can control the head unit by the buttons.
Change Volume, Skip a song and so on...
Buuuut very often the head unit goes crazy or the control gets lost over the steering wheel buttons. (I am not able to drive over 30 minutes without having this error)
It seems like the head unit receives some ghost commands and volume goes up to max or I have random song skips. Sometimes it simply doesn't react on buttons.
Of couse this is not usable at all, therefore I disconnected the whole buttons.
For example you see a ghost volume up at 0:27
https://youtu.be/h5rCFSF8pew
Or here there is no reaction on volume up (please excuse my loud breathing)
https://youtu.be/e53De2HQJfY
Key study menu doesn't work at all:
https://youtu.be/Z0wzJsiScSI
Here is magic volume up (you will also see a handsome gangster guy)
https://youtu.be/ZPDQMeU4CNU
I have no clue how to debug or what I can do.
Any hints from the experts?
messiah said:
Dear community,
I'm kind of lost since I get no support from Erisin about this (no response)
I have a BMW E46 from 2002 and the Erisin head unit.
MCU version is stock px5 MTCE (px5-userdebug 8.0.0. OPR5.170623.007 eng.hct.20180417.101726 test-keys)
I liked the idea of controlling the head unit volume by steering wheel.
Therefore I wired and installed the steering wheel buttons to my car.
The ACC works fine and in general I can control the head unit by the buttons.
Change Volume, Skip a song and so on...
Buuuut very often the head unit goes crazy or the control gets lost over the steering wheel buttons. (I am not able to drive over 30 minutes without having this error)
It seems like the head unit receives some ghost commands and volume goes up to max or I have random song skips. Sometimes it simply doesn't react on buttons.
Of couse this is not usable at all, therefore I disconnected the whole buttons.
For example you see a ghost volume up at 0:27
https://youtu.be/h5rCFSF8pew
Or here there is no reaction on volume up (please excuse my loud breathing)
https://youtu.be/e53De2HQJfY
Key study menu doesn't work at all:
https://youtu.be/Z0wzJsiScSI
Here is magic volume up (you will also see a handsome gangster guy)
https://youtu.be/ZPDQMeU4CNU
I have no clue how to debug or what I can do.
Any hints from the experts?
Click to expand...
Click to collapse
You should go Settings/Steering wheel keys to program the SWC, but not go to panel keys study.
I think the key menu doesnt matter. Actually the Buttons work as expected. But it gets out of control very often (random skips, volume up and so on). I also saw a key menu where I See the logs of key press. The head unit seem to actually receive the ghost key strokes repeatedly.
Have you tried entering at the factory menu and changing the car model at canbus menu?
You have a full menu for the keys where to change configurations.
Enviado desde mi iPhone utilizando Tapatalk
Had same problems - like not working buttons, i press up but it volumes up... After latest MCU update seems to be fixed. But also what i did in Steering wheel learning menu dublicated inputs for same buttons. i have on mine and it works without fall since.

PX5- steering wheel control issue & reverse camera blinking

Hello everyone,
I have a Dasaita PX5 and Android 8.0 for my Jeep Compass 2018. Problem is that (1) steering wheel controls have stopped working. Used to work for a while when the unit was first installed then one day just ceased to function. And (2) reverse camera video is blinking after driving for around 20-30 mins (doesn’t blink when engine is on and not running)
I've updated both the MCU (V3.45) and system update (20190731) to the latest ones in hopes of fixing it. I also went to factory settings and tried all canbus that had "Jeep" on it and selected the right model of the car but SWC still not working including the controls at the back of the steering wheel. The only thing that's working is the right side of the steering wheel which is the cruise control function.
I had an auto electrician check it and said “there's no problem with electrical side“ and now he's saying maybe the switches are broken (which I doubt) cos when the car battery was changed not long ago (SWC already not working this time), SWC came back to life but only for short period of time.
Please help me figure this out. Any advice would be greatly appreciated.
PS: also posted on android head unit thread. I wasn’t sure if I was posting in the right one. Thanks!
I'd try to disconnect the car battery for some minutes and see if the steering wheel controls return to work at least for some time.
If so, the head unit canbus adapter might be faulty,
I'd say there's a loose connection in the power feed of the CANbus decoder. More likely the ground wire is the problem. It could be loose or broken at either ends (including inside the decoder box) or along the length. Your electrician should know how to test for that.
Thanks for the reply guys. I’ll check this out and inform my electrician. Do you think the camera issue is related to this as well? I might need to order a new canbus adapter..
The HU gets the transmission is in reverse signal from the CANbus box so if the box kicks in and out so will the backup camera.
I put back the factory unit back in (factory unit worked without issues) but the steering wheel buttons still didn't work. Does this mean that the problem lies in the steering wheel buttons and not in the CANbus decoder?

Categories

Resources