Not sure if anyone knows how i can do this. I did lose the manual for the unit
I have an aftermarket AEM series 2, wondering if there's a canbus gpio on this unit that i can link to the ECU using AEMnet (Rx and ground pins) and use real dash or something similar to display some gauges.
Is this possible and does anyone happen to have a PDF manual for this unit?
Is it and MTCD based device, post MCU version
Related
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.
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
If so, does anyone know which units support this? Is it all units? Does the CANBUS data get in via the OBD2 port? Does it still make it through with a bluetooth OBD2 connector?
Thanks!
Yes, I assume most units with canbus box will. There are canbus lines that feed directly to the radio connection socket.
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.
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_