Seicane CANBUS assistance - MTCB Android Head Units Q&A

Hi everyone,
I haven't been on in a while and my username is new, but been using the site for years in the early root days.
I just purchased and installed a Seicane head unit in my Volvo XC60. Things are working great, but I had to bypass the amp to get sound which I thought was weird. Once installed, I noticed none of my buttons would work. Doing some research, I see that this could be due to the CANBUS not being set up correctly. The unit is a P series with a Octa-Core Cortex-A53. I went into the the factory settings where you can pick your CANBUS but I cannot find one that specifically states Volvo. The harness that was provided by Seicane bridges between the stereo and the main unit and information screen. The main until connector provides power and ground. The information system provides some CANBUS lines to the unit. I would think that since these CANBUS lines feed into the unit I would not need a separate box to decode them, but I could be wrong.
1. Is anyone familiar with CANBUS that might give me some insight into which CANBUS manufacture option I should pick.

Is it an MTCB unit or something else. Details are everything.

MTCE_hf_v3.30_1.
Edit: I just realized that I posted in the wrong area. Apologies. Deleting.

Related

Joying MTCB HU, USB connections.

Just installed a Joying:
. SKU: JY-UL124 . Quad Core Android 5.1.1 Lollipop OS Capacitive 7" High Definition for Universal Double Din . CPU: RK3188 1.6GHz Cortex A9 Quad Core, Resolution 1024*600. RAM:DDR3 1G, 16 GB memory
To my 2014 Australian Hyundai Elantra.
I waited to get the latest HU from Joying that has an unrated mother board and USB/ Comms board. With Lollipop 5.1.1. the unit performs very well with none of the problem previously mentioned on these pages. The internal and external mics are clear and the Bluetooth systems are perfect. Unit has been rooted and I don't seem to need for apps so I won't changed the software.
The dimming for the button and the screen to follow the vehicles rheostat was fixed by making a circuit to invert and amplify the rheostat output to the HU ill line. Work's well, Kudos to the guys at the Subaru forums.
I had one bug fixed by Joying when the GPS nav was muted whenever I plugged in the DVR front camera. Joying quickly sent me a link to re flash my firmware and the problem was fixed. I have them currently looking into a bug when I view the DVR input shown on the HU I get lots of flashing to the screen in all pixel settings. I have been told this will be fixed in the next firmware update soon.
One problem that I can't solve is when I try to use my vehicles Multimedia Jack located in my center console. There is a Aux and USB jack there. All wiring from console to HU is complete. If I connect a USB stick to the Jack in the console then then HU struggles to connect and gives up. If I interrupt the USB plug and socket behind the HU then I am able to use the USB correctly. Looking at the car wiring diagrams there is a amplifier cct behind the Multimedia Jack supposedly to amp up the USB to HU. Doesn't seem to work?
Any ideas appreciated.
Duke
If anyone has any ideas on
i have nothing to add, other than interested to see what the result is. Are you saying that your car comes with a built in hub in the console, and you are trying to make that USB port in the console work to the Joying head unit? my vehicle is similar, and I would like that to work as well
Update
Yes I have a console hub I guess.
The book calls it a multimedia center. Just an Aux port and a USB port or Jack in the tidy bin in the center console. If I by pass the Jacks and directly put the USB stick into the USB tail from the radio then it works fine. When I plug into the console port it tries to read it and fails. The HU then reports a read fail, have tried other known working USB sticks.
I have inspected behind the console jacks and found a cct board attached to the Jacks and then to the car wiring. From looking at the diagrams of the car previous to mine I see a cct board containing what looks like an amplifier. Tracing the car wiring to the radio input connectors seems to be OK and the wiring correct. Voltages at the radio connector are right in that there is 5v +ve, negative - earth and the center pins are data as they should be.
The console Jacks
w.hemanual.org/multimedia_jack_description_and_operation-2037.html
The wiring for same (mine is same but more complex)
w.hemanual.org/multimedia_jack_schematic_diagrams-2036.html
Really bugs me not to be able to access that USB input Jack esp as the radio is a great unit.
You need to post this question in the MTCD (Lollipop) hardware thread. This thread is for MTCB (KitKat) units. The hardware in the MTCD headunits are very different than the MTCB headunits.
bsavoir22 said:
You need to post this question in the MTCD (Lollipop) hardware thread. This thread is for MTCB (KitKat) units. The hardware in the MTCD headunits are very different than the MTCB headunits.
Click to expand...
Click to collapse
When I tried to repost this in MTCD I get this.
vBulletin Message
To prevent spam, you must have a higher post count in order to make a new thread in this development section. But feel free to make new thread in the non-development sections like General, Q&A, etc. Thanks for your understanding!
Am I still in the wrong section?
Yes, the MTCD thread is for the headunits with 5.1.1. The hardware changes and software are different. Send one of the admin a message and tell the why you need to get the permissions to post. I had to do that some time ago. Just make sure you follow the rules when post or you can have you account suspended or whatever the moderators deem necessary.
Sent from my SM-N910T3 using Tapatalk
Posting
Ok thanks for that. I don't seem to be able to find how to "Send one of the admin a message" Can you help?
Just for info, there are both MTCB/C and MTCD/E Lollipop units.

Anyone with a dead px3 who can locate the SPDIF pin? (Expose the Balls)

Hi, I recently installed an MTCD px3 unit in my car but the audio quality is not that great. I'm looking at the option of a USB DAC but that appears to have its own set of issues and complexity.
I do note though that the RK3188 chip includes an SPDIF function and this does appear as an audio device in /proc/asound/cards so if the pins (balls) are exposed somewhere on the px3 module board then it should be just a matter of soldering to the right points to create an SPDIF interface.
If someone has a totally bricked unit would you consider doing some research? I.e. using some heat to the remove the RK3188 BGA chip and locating the ball that relates to SPDIF and seeing if it can be traced to a track?
The SPDIF transmitter is located at ball N20. You can find the datasheet by googling "RK3188 Datasheet" (sorry I can't post links yet). So who can "expose the balls"?
Alternatively if someone has a dead board/unit they would give away, I'd be happy to pay shipping for you to send it to me (in New Zealand) and I'll do the research and share my findings with the community.
Also looking for someone who understands what would be required on the software side of things to actually use the interface. Some kind of ALSA magic I guess?
Note - I do understand the limitation. I.e. this only applies to audio within Android, not the radio or bluetooth etc. My approach would be to install a physical switch so I could switch my car amp between the analog and digital outputs.
mcraenz said:
Hi, I recently installed an MTCD px3 unit in my car but the audio quality is not that great. I'm looking at the option of a USB DAC but that appears to have its own set of issues and complexity.
I do note though that the RK3188 chip includes an SPDIF function and this does appear as an audio device in /proc/asound/cards so if the pins (balls) are exposed somewhere on the px3 module board then it should be just a matter of soldering to the right points to create an SPDIF interface.
If someone has a totally bricked unit would you consider doing some research? I.e. using some heat to the remove the RK3188 BGA chip and locating the ball that relates to SPDIF and seeing if it can be traced to a track?
The SPDIF transmitter is located at ball N20. You can find the datasheet by googling "RK3188 Datasheet" (sorry I can't post links yet). So who can "expose the balls"?
Alternatively if someone has a dead board/unit they would give away, I'd be happy to pay shipping for you to send it to me (in New Zealand) and I'll do the research and share my findings with the community.
Also looking for someone who understands what would be required on the software side of things to actually use the interface. Some kind of ALSA magic I guess?
Note - I do understand the limitation. I.e. this only applies to audio within Android, not the radio or bluetooth etc. My approach would be to install a physical switch so I could switch my car amp between the analog and digital outputs.
Click to expand...
Click to collapse
Hi.. my Android Radio just recently crashed. If you like.. i can give it to you.
Its a Hot Audio Android Radio PX3 RK3188.
Thanks very much. I've sent a PM.
Cheers,
Rhys
do you located SPDIF transmitter? Is possibile to connect directly an external DSP such Audison P8.9?
Bump

CANBUS help with DY7098 and Peugeot 307

Hello, I'm trying to install a Zeepin DY7098 in a Peugeot 307 that have CANbus and onboard computer... I want install without lose computer funcions... I searched many many many time, in many topics and I not understand if I need a canbus box decoder or can I install direct...
MCU is LM
Please, I really need some help
totynho said:
Hello, I'm trying to install a Zeepin DY7098 in a Peugeot 307 that have CANbus and onboard computer... I want install without lose computer funcions... I searched many many many time, in many topics and I not understand if I need a canbus box decoder or can I install direct...
MCU is LM
Click to expand...
Click to collapse
Zeepin DY7098 is an "universal 2DIN Head unit" i dont think canbus is an option but you can ask at your seller for it. For "full canbus" i think, you need a custom Peugeot 307 Head Unit
I found this infos on italian DME website:
"For peugeot vehicles (eg 3008/5008) that mount the on-board computer display just above the car radio (see photo below), you must purchase the kit (code KITPEU3008 / 5008) necessary to restore the information that this display - during the installation of the car radio - will be permanently removed. Warning: the information on the car radio is restored in English and it is not possible to translate it into Italian. KITPEU3008 / 5008 kit can be ordered at the time of purchase. (for eBay customers just request it when ordering)."
Articles code are for DME Peugeot Android Head unit. I think same is for your unit.
iRcKenny said:
Zeepin DY7098 is an "universal 2DIN Head unit" i dont think canbus is an option but you can ask at your seller for it. For "full canbus" i think, you need a custom Peugeot 307 Head Unit
I found this infos on italian DME website:
"For peugeot vehicles (eg 3008/5008) that mount the on-board computer display just above the car radio (see photo below), you must purchase the kit (code KITPEU3008 / 5008) necessary to restore the information that this display - during the installation of the car radio - will be permanently removed. Warning: the information on the car radio is restored in English and it is not possible to translate it into Italian. KITPEU3008 / 5008 kit can be ordered at the time of purchase. (for eBay customers just request it when ordering)."
Articles code are for DME Peugeot Android Head unit. I think same is for your unit.
Click to expand...
Click to collapse
This is the problem, I asked to seller and he don't know nothing about canbus... I sent message to manufactor and he sent me a canbus box from ConnectS2 CTSPG007.2 but I don't understand if is only for steering wheel control or I can use full canbus features...
totynho said:
This is the problem, I asked to seller and he don't know nothing about canbus... I sent message to manufactor and he sent me a canbus box from ConnectS2 CTSPG007.2 but I don't understand if is only for steering wheel control or I can use full canbus features...
Click to expand...
Click to collapse
Directly from Connects2 Ltd website (with a simple google search):
Description
Peugeot Steering Wheel Control Interface
Features & Benefits
Allows you to upgrade to an aftermarket head unit whilst maintaining use of your factory steering wheel controls
Safety: Allows you to keep your hands on the steering wheel and eyes on the road.
Plug and play, no cutting of wires required
Maintains the original features of the vehicle such as date, time and temperature display
Choose the relevant head unit connection lead according to the make of aftermarket head unit you wish to fit
For interfaces where phone buttons are supported, the following brands allow pick up/hang up in Bluetooth mode: Alpine, Clarion, Kenwood, Pioneer and Zenec. Please see icon list below to see if this interface supports phone buttons.
Please check the connections in the vehicle match the harness you are purchasing
This product has been developed through carefully documented data and research. Connects2 Ltd. cannot be held responsible for discrepancies/inconsistencies that may occur due to vehicle manufacturing changes or options, or damage that may occur in the vehicle during the installation of components. All application data is subject to change.
Simply try it and verify if it work like expected.
iRcKenny said:
Directly from Connects2 Ltd website (with a simple google search):
Description
Peugeot Steering Wheel Control Interface
Features & Benefits
Allows you to upgrade to an aftermarket head unit whilst maintaining use of your factory steering wheel controls
Safety: Allows you to keep your hands on the steering wheel and eyes on the road.
Plug and play, no cutting of wires required
Maintains the original features of the vehicle such as date, time and temperature display
Choose the relevant head unit connection lead according to the make of aftermarket head unit you wish to fit
For interfaces where phone buttons are supported, the following brands allow pick up/hang up in Bluetooth mode: Alpine, Clarion, Kenwood, Pioneer and Zenec. Please see icon list below to see if this interface supports phone buttons.
Please check the connections in the vehicle match the harness you are purchasing
This product has been developed through carefully documented data and research. Connects2 Ltd. cannot be held responsible for discrepancies/inconsistencies that may occur due to vehicle manufacturing changes or options, or damage that may occur in the vehicle during the installation of components. All application data is subject to change.
Simply try it and verify if it work like expected.
Click to expand...
Click to collapse
I think I'm not expressing myself right. In internet, we can see some videos where some person control A/C on Android Headunit, can see car info like belts, lights, temperature, without use any OBDII, just with CAN connection... Is this what I'm searching understand how it works...
totynho said:
I think I'm not expressing myself right. In internet, we can see some videos where some person control A/C on Android Headunit, can see car info like belts, lights, temperature, without use any OBDII, just with CAN connection... Is this what I'm searching understand how it works...
Click to expand...
Click to collapse
For what i know all these functions are controlled by CANBUS decoder/box (the one specified for vehicle brand and model) connected to Head unit: you can see the doors status (open/close), check A/C functions, etc. etc. CanBus box/decoder make all the job.
Cant help anymore.

Canbus errors - Should I care ?

Hi Guys,
I have a Seicane PX5 octa core, 4GB RAM/32GB storage unit installed in my Mitsubishi L200 pickup. Had it for over a year now, and has worked perfectly from day 1, steering wheel keys all good, bluetooth calls, navigation, audio (much better than the stock radio), etc. Got a DAB+ box hooked up, reverse camera, etc. Really happy with it, upgraded to Android 10/latest MCU over the last week, again no problems.
So, why the post ?
There is one issue I had initially. The unit came with one of the can bus decoder boxes that connects to the loom at the back of the stereo. Once fitted and I started driving, I started getting all sorts of warning lights flashing on the dashboard - airbag warnings, engine lights, etc. Reading the OBD codes it was complaining about canbus communication errors. I cleared the codes and disconnected the canbus decoder from the loom. Ever since then, no codes, and the unit works perfectly - including things like the steering wheel controls.
So my question is, should I care that the canbus box caused errors ? Does it actually do anything worthwhile ? I guess it might depend on the vehicle it's installed in. Door Open warning maybe ? Speed sensitive volume adjust (although could use GPS for that) ? I'm just wondering if it's worth trying to get a replacement or just forget about it as it doesn't do much anyway.
Thanks.
Did you get this sorted and was it a dasaita head unit thanks
scottydoguk said:
Did you get this sorted and was it a dasaita head unit thanks
Click to expand...
Click to collapse
scottydog, apologies for not replying to this sooner, I never got a notification that someone had replied to this, and I have had cause today to revisit this issue.
The head unit I wrote about was a Seicane unit. Aside from the can bus issue described, the unit has been flawless. My solution was to just omit the can bus box, the unit worked just fine, steering wheel keys, etc al worked perfectly so I just left it.
However, I decided for Christmas to upgrade the unit to a Dasaita PX 6 unit, it will be faster, has higher resolution screen, etc. This unit also came with a can bus decoder as part of the vehicle specific unit. So I fit it, and guess what - exactly the same as with the Seicane unit - weird dashboard warnings all over the place, airbag, traction control, etc.
So, I think, no problem, just ditch the can bus box. But there are two problems this time - (1) unlike the Seicane, the Dasaita unit won't power on unless the can bus box is connected, and (2) the Dasaita unit has an application pre-installed that allows tweaking of a lot of vehicle specific settings (headlamp on time, etc) that you used to be able to set with the factory head unit, and I'm guessing can bus connection will be needed to make those work.
So I would like to get to the bottom of this and get the unit working with the can bus unit in place. I've logged an issue on the Dasaita forum so we'll see what happens there. I don't think it's the can bus decoder, I can't believe two would display the same problem, I'm pretty sure it's the can bus settings in the Factory Settings of the unit - I can certainly make the problem worse by altering those, but I haven't found anything that makes it better !
I've attached an image showing the can bus settings on the device as I installed it. My car is a 2016 L200 UK version right hand drive, it's a Totan model that didn't have sat nav as new but does have steering wheel controls, etc.
Any ideas would be appreciated !
Thanks
hi guys,
I have the same problem with my Mitsubishi Lancer 2009.
I installed a android head unit over a year a go and didn't had any problems until recently when my ABS and ASC light start being on in my dashboard. The lights keep switching on and off at irregular intervals and when i put a car tester on it showed beside the ABS error code (C2116 code) other errors on airbags and engine immobilization, all related with that android unit, errors on car CAN line.
My car has an Rokford Fosgate amplifier from factory and the sound system doesn't work without the Canbus box installed, so ditching the canbus is not an option for me.
I also ordered a new canbus box from China and i will receive the package sometime in January. I'll keep you posted how it works with new one.
If you have any other information on this topic or you find something on line, I'm really interested since the android head unit is a big upgrade for my car and i will hate to come back to original radio.

Would like to better understand canbus integration, please help educate me

I've searched and searched but only find bits and pieces of information. So far, I haven't been able to connect enough dots to understand how this works.
Back in 2016 I purchased an Android head unit from Auto Pumpkin. I stumbled upon it by pure accident, thought it looked slick, and decided give it a shot. The radio body was Chevrolet specific so it popped right into my Express van. It also came with a canbus decoder box which I didn't know anything about but hooked up anyway and was impressed by the integration. Door status, reverse overlays, brightness control, and some other cool stuff.
Fast forward to last year, I bought another head unit for a new Chevy van but I couldn't find one that came with the canbus integration so it's installed as a standalone radio. The unit has the canbus pins on the back, but the corresponding wire harness didn't have any conductors to match up with them. It also didn't come with any type of canbus decoder. The config area in Factory Settings is still there, though.
That brings me to my first question: Are the pins on units like these still ready/capable to be connected to *something* even though the wire harnesses that come with them don't have the specific wires for it? What I'm asking is, if I purchase a Chevrolet canbus decoder separately, can I hook it up (adding the required wires) and expect it to work?
Lastly, I recently purchased yet another head unit, this time from Dasita, for my RV. It's built on a Ford chassis. Same as before, the radio has the pins (and they're labeled as canbus!), but the wire harness doesn't have wires connected to those pins.
Is there a Ford canbus decoder available somewhere, and, with some tinkering, is it possible to get the vehicle to talk to the head unit?
nomaxtech said:
Is there a Ford canbus decoder available somewhere, and, with some tinkering, is it possible to get the vehicle to talk to the head unit?
Click to expand...
Click to collapse
Yup, just make sure you order the right one for your head unit.
https://www.aliexpress.com/item/4000875414226.html?spm=a2g0o.productlist.0.0.2d785d7aDFgDYy&algo_pvid=8d9f7a38-3a25-48c1-8c5b-a0f1372ec0d7&algo_expid=8d9f7a38-3a25-48c1-8c5b-a0f1372ec0d7-3&btsid=0b0a556e16134130756217144e212d&ws_ab_test=searchweb0_0,searchweb201602_,searchweb201603_

Categories

Resources