Update 27/07 - did not improve the radio enough to recommend this modification/change.
Apparently the TEF6686 module has better performance than the TDA7786 - e.g. 7786 poor sensitivity, selectivity, multipath issues etc. My JY TDA7768 is terrible, even with an RF amp, so to find out if the TEF is any better, thought I would try and investigated swapping tuner modules. Reviewing the GS board I have as a spare part against my JY, I identified the modules are pin-for-pin compatible.
Sucessfully swapped the Radio module from a donor GS board containing a TEF6686 Module into my JY board originally containing a TDA7786. The GS board was quite difficult to unsolder the module, perhaps due to leadfree solder, fortunately the JY board was easy, the desolder wick readily desoldering the module.
As for results, I have bench tested and RDS, tuning, audio etc is OK, I am yet to test in the vehicle. Will update this thread with results.
See attached images. Note that the JY case had additional mounts that over time might short out against the non-ground PCB tracks, resulting in complete failure of the unit!
Welcoming any questions.
Did the reception really improved?? And RDS AF fuction is working well with malaysyk V3 firmware?
also interested in this outcome
Sent from my Pixel XL using Tapatalk
Hi,
The tef6686 appears marginally better, is more sensitive and appears to handle multipath better. Im not sure if I would call it out as a worthy upgrade just yet - need more time.
wonder if it can be bought on its own.. seems like just the chip itself which is surfaced mounted on the riser card as pictured above.. so this would prove difficult to install
Sent from my Pixel XL using Tapatalk
stinger4321 said:
wonder if it can be bought on its own.. seems like just the chip itself which is surfaced mounted on the riser card as pictured above.. so this would prove difficult to install
k
Click to expand...
Click to collapse
Ive seen a suitable module available on aliexpress that would need some modification to swap a couple of pins. That is the TEF6686-TDQ-230V-186 (10 pin) - a whole $6 bucks US.
http://s.aliexpress.com/QBfay
Next week this module come to me , so in the next weekend I have time to swap.
https://www.aliexpress.com/store/pr...32809641460.html?spm=2114.12010612.0.0.y1ZYeS
cupi1234 said:
Next week this module come to me , so in the next weekend I have time to swap.
https://www.aliexpress.com/store/pr...32809641460.html?spm=2114.12010612.0.0.y1ZYeS
Click to expand...
Click to collapse
That's great, don't forget these are not pin-pin identical and will have to figure out swapping pins. Search for the manufacturer PDF and check against the mtcd schematic. I'll upload the module PDF later today.
Hi, final thoughts - the upgrade in my experience was marginally better - not worth it!
marchnz said:
Hi, final thoughts - the upgrade in my experience was marginally better - not worth it!
Click to expand...
Click to collapse
could be something else in the implementation, not just the chip itself.
i have 2 boxes, one with 7786, the other with 6686 and the difference in reception is worlds apart. I mean even with the powered antenna not connected to 12V, i had no hiss on any station received.
7786 with powered antenna is just fine, don't get me wrong, but 6686 is better.
zerozoneice said:
could be something else in the implementation, not just the chip itself.
i have 2 boxes, one with 7786, the other with 6686 and the difference in reception is worlds apart. I mean even with the powered antenna not connected to 12V, i had no hiss on any station received.
7786 with powered antenna is just fine, don't get me wrong, but 6686 is better.
Click to expand...
Click to collapse
I had thought about that but there's no difference in implementation I can see after comparing from schematic. Perhaps I had a 'good' 7786.
- MCU is latest HA
- Both modules are digitally controlled by MCU/i2c bus.
- same supply
- latest HA android 6.
There's really not much to it, 5volts, antenna connection, i2c comms and audio out. I get multipath noise/crackles from stations between 99 and 102mhz. Same between both tda and TEF.
Can you clarify what you mean by 'better'.
Hi!
Maybe there are some differences in the Radio Software used in the different HU. The Chip is controlled by I2C and it seems to be possible to activate or change some behavior of FM Reception through some commands.
Is it maybe possible to extract the radio Software from the good HU so we can try it out on different devices (with TEF 6686).
It would be really nice if it would be possible to control some of the possible configuration of the chip manually...
Stephan
netguru said:
Hi!
Maybe there are some differences in the Radio Software used in the different HU. The Chip is controlled by I2C and it seems to be possible to activate or change some behavior of FM Reception through some commands.
Is it maybe possible to extract the radio Software from the good HU so we can try it out on different devices (with TEF 6686).
It would be really nice if it would be possible to control some of the possible configuration of the chip manually...
Stephan
Click to expand...
Click to collapse
No differences in android and same MCU, MCU controls radio module via I2c. The "upgrade " has no discernable difference.
Any more details? I need a more sensitive tuner. I have a full power mast but my car is all SMC so the radio needs all the help it can get.
Sent from my iPhone using Tapatalk
-=Jeff=- said:
Any more details? I need a more sensitive tuner. I have a full power mast but my car is all SMC so the radio needs all the help it can get.
Click to expand...
Click to collapse
Sure - there are two different tuner modules and neither of them are 'better'. I suspect its hit and miss in the production of either modules.
If you have a proper external antenna, which is properly connected, there's nothing you can do apart from using internet streams or DAB if available for best quality.
thanks, do you know if these unit have the 7786 or the 7786M IC?
netguru said:
Hi!
Maybe there are some differences in the Radio Software used in the different HU. The Chip is controlled by I2C and it seems to be possible to activate or change some behavior of FM Reception through some commands.
Is it maybe possible to extract the radio Software from the good HU so we can try it out on different devices (with TEF 6686).
It would be really nice if it would be possible to control some of the possible configuration of the chip manually...
Stephan
Click to expand...
Click to collapse
marchnz said:
No differences in android and same MCU, MCU controls radio module via I2c. The "upgrade " has no discernable difference.
Click to expand...
Click to collapse
Are you sure ? Cos on MTCB/C units the AF doesnt work and the PTY is plain wrong (I have an MTCD unit now but I havent tested the radio yet, its still on the bench), but someone (deffo Italian I remember that) made some changes and got PTY to work correctly and I thought he did it by modding the app ratehr than anything on the MCU side. Sadly I cant remember exactly what thread it was in, or who it was.
-=Jeff=- said:
thanks, do you know if these unit have the 7786 or the 7786M IC?
Click to expand...
Click to collapse
Unfortunately the only way to tell on MTCD untis is to open it up, unlike the MTCB/C units where you can select the tuner type in facory settings, which is strange cos MTCD MCUs are much more powerful 32 but compared to MTCB/C's 8bit . . .
. . . or maybe there is a way ? - @marchnz's dmesg output mentions "6686" in the first post.
Hi,
Can someone help with radio module pins schematic for XD-6686AF-0. This is same radio module that @marchnz has swaped. I am forced to change main that is not pin to pin identical to TEF6686-TDQ-230V-86-TDQ-230V-86-R that I have from aliexpress.
Thank you
P.S.
https://forum.xda-developers.com/android-auto/mtcd-discussion-questions-development/mtcd-schematic-t3637816
I guess this is what I am looking for.
Leaving a tip for everyone looking for this schematic.
Thanks to @marchnz
skf123 said:
Hi,
Can someone help with radio module pins schematic for XD-6686AF-0. This is same radio module that @marchnz has swaped. I am forced to change main that is not pin to pin identical to TEF6686-TDQ-230V-86-TDQ-230V-86-R that I have from aliexpress.
Thank you
Click to expand...
Click to collapse
Do you have a datasheet? Shouldnt be too hard to match up against schematic.
marchnz said:
Do you have a datasheet? Shouldnt be too hard to match up against schematic.
Click to expand...
Click to collapse
Radio module that comes from aliexpress has description on every pin.
Can be seen on the picture that is provided in this link.
I can make a new photo if someone needs clear image of this module.
Related
Hi Folks, this is a little embarassing but I cant get the fm radio to work.
I'm generally not that bad at figuring stuff out and the radio app appears to opens perfectly ok, I can turn the dial and tune to any specific frequency but there is simply no sound, or indication of a received signal
When I click on the arrows it even says "turn on the radio", which suggests its switched off, but where is the on button?
No doubt there is a really simple explaination that someone can ping back to me, many thanks
all mobile phones that have FM radio need the wired headset plugged in which acts as the antenna for the FM radio. so plug in your headset, then it will work.
Assuming that you have your headphones connected then the power button is at the top left corner of the screen.
Thanks for tolerating the noob folks I knew it would be something really simple, and guess what - its works as soon as I plug in the headset as mentioned, fabulous phone / Thanks again
So the Galaxy S 2 really DOES have the FM radio hardware ? And an app to use that hardware ?
I'm looking to get my FM radio app working on the Galaxy S 2, and I'm hoping it has a Silicon Labs FM chip, like the older Galaxy S.
I would be interested to know if there is a /dev/radio device or similar. The command "lsmod" might show a module loaded named Si4709_driver or there might be a file on the phone like Si4709_driver.ko .
If so, the market app "Fm TwoO" might work.
Or perhaps this phone uses a TI or Broadcom combination FM/BT/WiFi chip ?
mikereidis said:
So the Galaxy S 2 really DOES have the FM radio hardware ? And an app to use that hardware ?
I'm looking to get my FM radio app working on the Galaxy S 2, and I'm hoping it has a Silicon Labs FM chip, like the older Galaxy S.
I would be interested to know if there is a /dev/radio device or similar. The command "lsmod" might show a module loaded named Si4709_driver or there might be a file on the phone like Si4709_driver.ko .
If so, the market app "Fm TwoO" might work.
Or perhaps this phone uses a TI or Broadcom combination FM/BT/WiFi chip ?
Click to expand...
Click to collapse
Just an FYI for mikereidis, my TMobile UK S2 does have the Si4709_driver module
davehunt83 said:
Just an FYI for mikereidis, my TMobile UK S2 does have the Si4709_driver module
Click to expand...
Click to collapse
Great ! Thank you.... Has anyone tried Fm TwoO on this device ?
Now if there were just a CyanogenMod port... and I could buy one locally...
For development I'd probably be better off getting the original S, and considering an S 2 when it's better supported with aftermarket ROMs etc.
The BCM4330 has a number of listed features that our SGS2s do not appear to have. For instance, the chip in question has listed support for Bluetooth 4.0+HS (so, I assume the Bluetooth low power standard) and FM Transmission/Receive, however all sources state that the SGS2 only supports up to Bluetooth 3.0, does not have Bluetooth high speed (virtually the same as Wifi direct, I'm told, but may not have the same level of uptake) and there are no references to FM transmission.
Without relevant APIs or sources I assume none of these unused features can be utilised. Is it a possibility that Samsung removed some components of the chip to reduce bulk?
What's confused me about this entire situation is that the original Galaxy S and the iPhone4 feature this same chipset, but there's not even a mention of Bluetooth3.0 even though they appear to support it . . . weird. Perhaps I've completely failed to understand the nature of these chipsets, but if I'm not being completely stupid then it'd be nice to explore how one could fiddle with our precious phones to extend its capabilities.
Bump
Sent from my GT-I9100 using XDA Premium App
HazzBazz said:
The BCM4330 has a number of listed features that our SGS2s do not appear to have. For instance, the chip in question has listed support for Bluetooth 4.0+HS (so, I assume the Bluetooth low power standard) and FM Transmission/Receive, however all sources state that the SGS2 only supports up to Bluetooth 3.0, does not have Bluetooth high speed (virtually the same as Wifi direct, I'm told, but may not have the same level of uptake) and there are no references to FM transmission.
Without relevant APIs or sources I assume none of these unused features can be utilised. Is it a possibility that Samsung removed some components of the chip to reduce bulk?
What's confused me about this entire situation is that the original Galaxy S and the iPhone4 feature this same chipset, but there's not even a mention of Bluetooth3.0 even though they appear to support it . . . weird. Perhaps I've completely failed to understand the nature of these chipsets, but if I'm not being completely stupid then it'd be nice to explore how one could fiddle with our precious phones to extend its capabilities.
Click to expand...
Click to collapse
Example:
Back then, at MWC 10, Samsung introduced the Samsung Omnia HD (i8910) which has alot of things AND an FM transmitter, when the device was actually launch, it didn't have the FM transmitter, modders and coders saw & knew that this device have the component, even proved with a secret code and an app they build, but no one has ever managed to get it to work.
So far of being a costumer at Samsung corp. I noticed 2 mistakes that they are repeating:
1. Samsung can't manage to get solid 30fps at 720p devices and 1080p.
2. Samsung rls products with an FM transmitter but they never support it and doing everything that we won't manage to get it work.
The fact that this chip is capable of performing all those tasks does not mean it is capable of doing all those task simultaneously. There might be some hardware challenges/contradictions between the different roles.
For instance, bluetooth 4.0 requires filtering above 3GHz of more than 10dB, while at the same time the chip is capable of Wifi on 5GHz; both are supposed to be on the same antenna so either you can not use the chip for Bluetooth 4.0 AND wifi 5GHz or you have to use some very complicated filter depending on which mode you're using. If they have not supplied this filter inside the chip then it becomes a bit complicated to use both modes.
The FM transceiver could very well be connected to the same internal power amplifiers as wifi but a wifi antenna does not look like an FM antenna.
It is not always possible (actually seldom) to use all the specifications of a chip at the same time with the same hardware setup. (Though often the user won't notice because it is not able to check the specification, like ultra low power and high speed often conflict.)
The features you mention are integrated into the chip itself, so it's not possible to "offload" them. However, they may leave out necessary off-chip components and/or enabling software.
For example, FM is popular in Korea. Many Samsung models targeted to the Korean Market include FM capability. It requires extra hardware though, including a rather primitive looking FM antenna. The corresponding models for other parts of the world leave this out. I presume Samsung doesn't see the popularity of FM in other parts of the world to be enough to make up for the extra cost in the handset.
Drivers and such require work, too. So while the chip may support the capability, they may postpone the software development for various reasons. If the hardware support is fully intact, it might be possible to make something work, but it could require some very deep hacking.
requist's response is interesting and seems like a possibility, although a quick reading of the Broadcom product page seems to suggest they've accounted for mixing capabilities in the chip design. Hard to tell without more detailed info.
Disclaimer: I'm not an official spokesperson. Opinions expressed here are mine and not those of my employer.
requist said:
The fact that this chip is capable of performing all those tasks does not mean it is capable of doing all those task simultaneously. There might be some hardware challenges/contradictions between the different roles.
For instance, bluetooth 4.0 requires filtering above 3GHz of more than 10dB, while at the same time the chip is capable of Wifi on 5GHz; both are supposed to be on the same antenna so either you can not use the chip for Bluetooth 4.0 AND wifi 5GHz or you have to use some very complicated filter depending on which mode you're using. If they have not supplied this filter inside the chip then it becomes a bit complicated to use both modes.
The FM transceiver could very well be connected to the same internal power amplifiers as wifi but a wifi antenna does not look like an FM antenna.
It is not always possible (actually seldom) to use all the specifications of a chip at the same time with the same hardware setup. (Though often the user won't notice because it is not able to check the specification, like ultra low power and high speed often conflict.)
Click to expand...
Click to collapse
time division multiplexing.
Dirty_Jerz said:
time division multiplexing.
Click to expand...
Click to collapse
That does not solve hardware conflicts.
Hello everyone,
I have a Erisin S2046B in my 2001 BMW E46 and found information, that the RK3188 has several external buses which are partly currently not used in the device. Being an electrical engineer and having some projects in my mind which require some sort of external communication to e.g. microcontrollers, I would like to make use of them.
Did anyone go through the effort to use one of these interfaces?
I read in the sound processor thread (http://forum.xda-developers.com/and.../mtc-sound-controlling-bd37xxx-sound-t3234660), that I2C is used there but only limited information on what is done exactly, as it is just a matter of reconnecting the bus lines from the mcu to the rk3188.
I'm not quite sure, if this is the right section, but I would not really consider this "software development". Anyway, if one finds it inappropriate, I would kindly ask a mod to move it to another section
This is great, hopefully it's with guys like yourself tinkering away at these devices we end up with a how new sub-section of interesting mods that can be done for those that like to take stock and improve on it..
Bookmarked for reading as you go through this ... Look forward to some.positive outcomes...
@LC4T, can you be more clear as to what do you plan to achieve? It is no problem to attach another slave (or more) to existing I2C bus, as this bus is a multi-slave in its nature. There's no need to find any interfaces not in use, you are free to use existing, well known one.
As I already mentioned in my posting, I personally plan to connect an external microcontroller and exchange data between the µC and the RK3188. As I don't want to fit the circuitry inside the erisin enclosure, I2C is not the preferable solution.
The principle of I2C and its architecture is known to me, I have already build hardware using I2C But as the existing I2C bus is already connected to at least one slave device, I would be careful with hooking up another one without knowing exactly, what's happening on the bus already. Worst case would be to make the whole existing system unstable. I'd rather use SPI oder UART for my purpose.
In general, this thread should not be seen limited to my intentional use but some sort of collection of information on which buses are present, usable and in use - knowledge base style, so to speak
What's the first solution that comes to your mind when you think of doing something interesting with your I2C?
Some of these units do CANBUS. I'm not sure if there is separate hardware in them or just hookups.
I plan on installing an engine block heater (webasto thermo top c). With the universal wiring kit and control unit, you're only able to set three starting times with a fixed heating time. Additional control units for remote control are quite limited in range and functionality, the "cheap ones" (~200€) only offer "start" and "stop" with the only feedback if the command reached the unit being a blinking led, the ones with the ability to set the starting time from the distance (they claim it works up to 1km depending on the building density) is 350€... There are also GSM units available but also quite expensive and with few functions.
So including a microcontroller would fix all that
If I got it right, the CAN unit is a standalone device, that only decodes relevant data (e.g. gearbox in reverse), so no communication with the android device itself
LC4T said:
I plan on installing an engine block heater (webasto thermo top c). With the universal wiring kit and control unit, you're only able to set three starting times with a fixed heating time. Additional control units for remote control are quite limited in range and functionality, the "cheap ones" (~200€) only offer "start" and "stop" with the only feedback if the command reached the unit being a blinking led, the ones with the ability to set the starting time from the distance (they claim it works up to 1km depending on the building density) is 350€... There are also GSM units available but also quite expensive and with few functions.
So including a microcontroller would fix all that
If I got it right, the CAN unit is a standalone device, that only decodes relevant data (e.g. gearbox in reverse), so no communication with the android device itself
Click to expand...
Click to collapse
I believe there are can bus controllers for that device.
You could take a look at IOIO-OTG boards. it might offer some features.
You can make your own can bus for the devices you want to control and use available can bus adapters.
If you're talking about the webasto heater, yes, there are control units with CAN functionality but they are OEM specific (e.g. VW/Audi, Mercedes, BMW,...) and not universal. Also, adding just another interface is not what I intended to do when there are several of them, mostly unused already available
Again: I don't want to use this thread for my specific problem but as a general thread on using the interfaces already present in the unit
LC4T said:
If you're talking about the webasto heater, yes, there are control units with CAN functionality but they are OEM specific (e.g. VW/Audi, Mercedes, BMW,...) and not universal. Also, adding just another interface is not what I intended to do when there are several of them, mostly unused already available
Again: I don't want to use this thread for my specific problem but as a general thread on using the interfaces already present in the unit
Click to expand...
Click to collapse
Sure. Sure. I like the idea of tapping into the onboard hardware, but it might be good to talk about the limitations and optimal use cases for doing so.
For your case I think you can solve your need without tapping in if the objective is to get it working quickly. If the geek factor is more important then its a moot point.
You could probably tap in using something like this:
sandboxelectronics.com/?product=active-i2c-long-cable-extender-p82b715-module
That might help cut down on noise if you want to run it around the car.
Here's my thoughts.
If you need to control some external DIY device, you need to go with USB ports, which are already available in our devices.
They are just designed to communicate with external world, opposite to I2C or SPI, which are designed for in-system communications only.
Here we have two options:
1. Use native USB communication:
On the headunit side - libusb library which is well-known in Linux world. It might even happen that it is already compiled into the kernel (need to check); otherwise, a libusb.ko module needs to be compiled and loaded.
Nowadays there are many microcontrollers with USB onboard for direct use; and even simpliest MCUs like AVR attiny/atmega can use USB via V-USB library (I've done some just-for-fun projects with it).
2. Use a cheap USB-Serial converter to get a new serial port on a headunit's side. On the MCU side, you'll get a standard UART, which is much simplier than USB for MCU programming.
And returning to your @LC4T idea.
Are you planning to use head unit only as a control panel for your device, so that you only need a big touch screen with a nice UI to set up your externa DIY device, then go off letting that device to work alone? Don't you plan having your head unit always turned on to track time and on/off your heater? Because latter solution is really bad, as our head units are very power hungry.
7floor said:
Here's my thoughts.
If you need to control some external DIY device, you need to go with USB ports, which are already available in our devices.
They are just designed to communicate with external world, opposite to I2C or SPI, which are designed for in-system communications only.
Here we have two options:
1. Use native USB communication:
On the headunit side - libusb library which is well-known in Linux world. It might even happen that it is already compiled into the kernel (need to check); otherwise, a libusb.ko module needs to be compiled and loaded.
Nowadays there are many microcontrollers with USB onboard for direct use; and even simpliest MCUs like AVR attiny/atmega can use USB via V-USB library (I've done some just-for-fun projects with it).
2. Use a cheap USB-Serial converter to get a new serial port on a headunit's side. On the MCU side, you'll get a standard UART, which is much simplier than USB for MCU programming.
Click to expand...
Click to collapse
The IOIO OTG solution gets you here plus there are established libraries etc.
github.com/ytai/ioio/wiki
The OTG version allows it to be powered from the host also. That could make it easy to develop and move around.
github.com/ytai/ioio/wiki/Getting-To-Know-The-IOIO-OTG-Board
pounce said:
The IOIO OTG solution gets you here plus there are established libraries etc.
github.com/ytai/ioio/wiki
The OTG version allows it to be powered from the host also. That could make it easy to develop and move around.
github.com/ytai/ioio/wiki/Getting-To-Know-The-IOIO-OTG-Board
Click to expand...
Click to collapse
From $20 for the board on AliExpress to almost $40 elsewhere? No, thanks These guys want too much for their solution. This is the price of a Raspberry PI, a complete computer.
For that price, I would prefer putting a Raspberry under dashboard, connect with WiFi, for example, and have much more flexibility than gives the IOIO.
As to IOIO - as a prototyping board it might be useful, but not for a well-finished DIY project based on a single cheap MCU with a minimum of components, where total cost of it would be much lower than cost of that board.
It is like using ATmega256-based Arduino boards for the purpose of watching a button and blinking a LED, where the $0.5 worth ATtiny13 is an overhead.
Such a boards are probably good for Hackaton events, where you have to show something working after a few hours of quick-and-dirty work, but not for thoroughly designed DIY project.
Depends on how much you value your time and what an existing product offers you for your solution. Many people aren't as price sensitive. I certainly wasn't suggesting the IOIO as the only solution, but for an open ended or more generic solution to get hardware support external to the head unit is generally fits the bill. Established libs for interacting saves some time. Nice bunch of people put it together and there have been some fun projects.
Like I mentioned before, it might be a good idea to discuss what the objective would be to adding smart hardware in the solution through, I2C, USB, bluetooth, wifi or whatever. I think the OP is looking to discuss the general idea and not super specific solutions that might lead a person to pic a very specific ic and com. Well, I know that was the purpose because the OP has redirected me to the point.
You bring up a good point though. You say you would rather put Pi under the dash. I would also for controlling things. In fact Pi or some duino realtime solution is always going to be better for interacting with an auto. This is especially the case when the purpose might be controlling something that is powered like a motor or something life critical. At this point though we are not talking about android or these head units. You are talking about perhaps the method of communication between two systems. Not really for this forum.
---------- Post added at 01:05 PM ---------- Previous post was at 12:46 PM ----------
I'd like to have more input/output trigger wires for events. We have a backup wire, but I'd like more for other things. An example might be to support a passenger side view camera. Sure, there are ways to hack it in by switching the backup video input, but that's a simple example. Power on a wire sends an event in android on the unit.
Do we have GPIO possibility on any of these units?
CanBus via Uart?
Does anyone know how the CanBus connection works? My MTCB Unit came with an adapter box which turns some messages into external signals (like illumination, reverse), but also seems to forward messages via serial into my Head Unit. At least that's how i guess that the steering wheel buttons are working.
Now, there are some messages that i wish to interpret and send, and also some i would interpret different. My idea was to get some kind of filter (maybe software, maybe a dedicated micro controller) in between the CanBus adapter and the service on my head unit. But right now, i have no idea how to verify my understanding of the setup, since no tty device on the HU seems to directly reflect my button presses. There's one, that pours out something unreadable on key press, but this also does it if i touch the screen, so i guess that's not the CanBus adapter itself.
I suspect that the information in already interpret before it gets into the android system, and only the relevant messages are forwarded, or even pre-processed. I suspect that the only way to get to the signals is to listen on the CanBus adapters RX/TX lines, and maybe finally put an microcontroller in between. If unlucky, the adapter might also filter out messages before i can get them, and i need to access the CanBus directly.
htt p://i.imgur.com/P1QzXta.jpg?1 << CanBus Adapter
I would appreciate any hints on this topic, especially information on the CanBus Adapter.
From what I can see on the PCB and I have read about the can adapter:
The adapter itself only interprets data from either can bus or analog signals and forwards them to the android unit via some sort of serial interface, most probably UART. As you have almost no way to get an inside look into the software running on the microcontroller, I would suggest to design a seperate device, that way you can be 100% sure to get all the messages and filter yourself.
I ordered some can bus adapters to see what i can read. Maybe i will first have a look into the data on the serial line when i finished moving house and had time to unpack my gear
I have a can bus HU, when i listen to the radio or music player, i haven't information on display of my car (CLK MERCEDES). I read the new units have dual can bus and information of radio appears on car display. Ther's a way to modify my HU to dual can bus? I have to change a can bus decoder? My can bus decoder is B200.
Regards
7floor said:
.... There's no need to find any interfaces not in use, you are free to use existing, well known one.
Click to expand...
Click to collapse
Well known interfaces - that's the keyword.
For example I would like to output current FM-frequency, radio station name, song title to the existing (factory) FIS display in a car. Via CAN bus, because the display talks CAN.
Now I would at least have to know which units have CAN capability.
Yes, I could go the USB to RS232 to CAN dasy-chain-adapter route, but I consider that all but a clean solution
Oskar
--
TomTom GO Support
--
Is this the same you posted before, based on the Eonon october ROM?
I had several issues with that ROM, Waze crashing at start, same for the canbus app. None of these issues with your August or September ROM.
--
Greath. have you included the launcher i told you with the xposed module?
--
Voice Dialing with Google App/Voice Search
--
dsa8310 said:
Voice dialing is possible, with Google/Voice Search, provided that mtcservice is set as the default dialer (instead of Phone).
Click to expand...
Click to collapse
Now you have a heat sink, I have one on order and others are thinking about it, maybe we could revise the cpu throttling, discussed earlier, that drastically limits speed because of suspected worries by the devs about heat ? What do you think ? I guess it wont be until the summer that we would be able to fully test this . . . actually its summer in the southern hemisphere so users down there could tell us if theres any problems.
BTW youve missed one of your posts in the MCU feature request thread and not deleted it, post #45 ! Cant see the point of deleting posts in that thread as well - @dhmsjs has just tried to go through the MTCC MCU for you to see if he can make it compatible with your radio IC as you requested, but if youre deleting your posts from that thread then you ll make it more difficult to help you.
I take screenshots of useful posts, so the deletion of all your posts does not affect me, however, you are now making life more difficult for the rest of the community, as well as yourself, by deleting them.
dsa8310 said:
Voice dialing is possible, with Google/Voice Search, provided that mtcservice is set as the default dialer (instead of Phone).
Click to expand...
Click to collapse
Thanks for that info sir
Sent from my SM-G930T using XDA-Developers mobile app
The Time Loop!
--
RAM Upgrade
---
dsa8310 said:
Regarding shipping & handling fees (from HK), I would suggest to individual buyers, to ask for DHL (to Europe), which may be significantly cheaper.
Click to expand...
Click to collapse
Note: good as DHL are they always charge customs/duty.
dsa8310 said:
Voice dialing is possible, with Google/Voice Search, provided that mtcservice is set as the default dialer (instead of Phone).
Click to expand...
Click to collapse
Where do I do this..
I have Oct Rom..
The red capes have arrived...
---
Developer Options?
Is there a way to enable developer options on the 5.1.1 Roms?
dsa8310 said:
Android 6.0, Octa core Rockchip PX5 Cortex A9, from Klyde:
http://www.szklyde.com/toyota-android-car-dvd/39978381.html
Click to expand...
Click to collapse
Well done for spotting that . . . just as youve upgraded to 2GB and 10 others are about to !
Still, if the price of a new SoM isnt too high (assuming its MTCC compatible), an RK3188 SoM with 2GB RAM might be attractive to RK3066 owners, so, after selling our old SoMs, an octacore upgrade might not cost too much.
And of course we may be lucky and Marshmallow might be available for the RK3188.
The PX5 is 1.3Ghz, 64bit, has light, proximity and g sensors, has HDMI and uses a Realtec RTL8723BS wifi/BT board from what I can see, wonder if it ll still be compatible with the MTCB/C BT set up ?
https://translate.google.co.uk/tran.../news/rockchip/2016/0912/791.html&prev=search
https://patchwork.kernel.org/patch/9325047/
Rockchip seem to be going up in the world - Samsung are about to release chromebooks with a Rockchip RK3399 Hexacore processor:
http://www.cnx-software.com/2016/09...-video-conference-and-recording-applications/
Ok, Installed OCT ROM and forgot to mention about bluetooth. After the reboot, it would not connect to my phone (was CAR KIT, now EONON) So I tried 0000, 1234, looked it up and was 5xxx. Still no go.
Change to CAR KIT, 0000 and rebooted.. all is ok.
Still want to try that voice calling stuff and will install SYGIC Nav after work..
Runs smooth but I have the same issues with the September ROM as with the last - Waze craches after starting the app. @dsa8310 any chance you can fix it?
---
dsa8310 said:
What is Waze?
(I don't use it)
I would check it out if you give me the exact (play store?) link.
Click to expand...
Click to collapse
Thanks, much appreciated
Waze is a free community based navigation app. In 2013 it was acquired by Google, it look really promising. The below link only allows me to see the Danish version, not sure if you will be automatically diverted to your country version, hope so
https://play.google.com/store/apps/details?id=com.waze
Hi all, I have a problem with the radio FM, with the AF (alternative frequencies) that doesn't work properly, indeed it always jumps to the next available station, not the same broadcast station, it should jump to the same broadcast station with better signal, and it gives some kind of audio lag every 2-3 seconds; so I have to disable the AF to listen the radio, but when the signal is poor, of course, it jumps to other different stations anyway. I tried everything, I updated the MCU to the latest, many firmware versions, but nothing worked. I have a Witson PX5 4GB MTCE with latest MX2 2.88b MCU and Android 6 stock ROM actually. I bought a new core board (the same px5 4gb ram board) from Witson, but the problem is still there, so the problem must be with the internal fm tuner module and I want to ask you if there is the chance to solve this problem with an hardware fix/mod, I'm very frustrated and exhausted...
exact same situation like you
This isn't a "hardware" problem. This is a software problem, and the software in question is implemented in the MCU, which makes it incredibly challenging to fix.
But not impossible.
If your radio is a TEF6686.
If you open up the radio module and clip the i2c pins off of it, and reconnect it to an i2c bus on the SoM (instead of the MCU), then I can provide you with source code for software that can directly control the radio. I have not implemented AF in it though, since AF is not used on this side of the world and I therefore have neither motivation nor testing data needed to implement it. So you would have to do that yourself.
96carboard said:
This isn't a "hardware" problem. This is a software problem, and the software in question is implemented in the MCU, which makes it incredibly challenging to fix.
But not impossible.
If your radio is a TEF6686.
If you open up the radio module and clip the i2c pins off of it, and reconnect it to an i2c bus on the SoM (instead of the MCU), then I can provide you with source code for software that can directly control the radio. I have not implemented AF in it though, since AF is not used on this side of the world and I therefore have neither motivation nor testing data needed to implement it. So you would have to do that yourself.
Click to expand...
Click to collapse
Thank you for the reply, but tell me one thing, how is it possible that other users with the same device in my same country (Italy), can properly use the AF? This is why someone in this forum told me that this is an hardware issue and I think the same. Anyway i'm not able to develop software, if you think that it can be solved software side, i hope that you or someone else can develop the AF software and let me test it
Inviato dal mio Z2 Pro utilizzando Tapatalk
So no one cares?
Inviato dal mio Z2 Pro utilizzando Tapatalk
96carboard said:
This isn't a "hardware" problem. This is a software problem, and the software in question is implemented in the MCU, which makes it incredibly challenging to fix.
But not impossible.
If your radio is a TEF6686.
If you open up the radio module and clip the i2c pins off of it, and reconnect it to an i2c bus on the SoM (instead of the MCU), then I can provide you with source code for software that can directly control the radio. I have not implemented AF in it though, since AF is not used on this side of the world and I therefore have neither motivation nor testing data needed to implement it. So you would have to do that yourself.
Click to expand...
Click to collapse
Hello, could you provide the source code please to be able to control TEF66686 by a i2c bus ? thank you
mike2587 said:
Thank you for the reply, but tell me one thing, how is it possible that other users with the same device in my same country (Italy), can properly use the AF? This is why someone in this forum told me that this is an hardware issue and I think the same. Anyway i'm not able to develop software, if you think that it can be solved software side, i hope that you or someone else can develop the AF software and let me test it
Click to expand...
Click to collapse
I can propose a number of possible explanations;
1) They don't really know that its not working correctly.
2) Their radios have a different manufacturer and thus different code running on the MCU.
3) They are running different software versions on the MCU.
I'll tell you exactly how you can prove that its not a hardware issue;
When you tune to a channel, the display shows you the title of the song being played? That means that RDS is working. If RDS is working, then the hardware is providing the AF data, and it is up to the software to use that data.
The radio hardware itself does not deal with AF. It just feeds data up the i2c bus. The software running on the other end of that bus will keep track of the AF data being provided for that frequency, and it will monitor the signal strength. If the signal strength drops too low, it it supposed to trigger a tune to a stronger source.
mike2587 said:
Thank you for the reply, but tell me one thing, how is it possible that other users with the same device in my same country (Italy), can properly use the AF? This is why someone in this forum told me that this is an hardware issue and I think the same. Anyway i'm not able to develop software, if you think that it can be solved software side, i hope that you or someone else can develop the AF software and let me test it
Inviato dal mio Z2 Pro utilizzando Tapatalk
Click to expand...
Click to collapse
On my Xtrons PX5 with Oreo and GS MCU 2.94 AF is working correctly.
Check in the factory settings which is the Signal level you have set... it should be -30dB. This is the value of the radio signal that make the MCU to switch to the alternative frequency.
royalhawk2002 said:
On my Xtrons PX5 with Oreo and GS MCU 2.94 AF is working correctly.
Check in the factory settings which is the Signal level you have set... it should be -30dB. This is the value of the radio signal that make the MCU to switch to the alternative frequency.
Click to expand...
Click to collapse
-30dB?
where is this setting?
If I remember right should be under the factory settings on the tab "other"
emre33 said:
-30dB?
where is this setting?
Click to expand...
Click to collapse
Inviato dal mio SM-N960F utilizzando Tapatalk
96carboard said:
I can propose a number of possible explanations;
1) They don't really know that its not working correctly.
2) Their radios have a different manufacturer and thus different code running on the MCU.
3) They are running different software versions on the MCU.
I'll tell you exactly how you can prove that its not a hardware issue;
When you tune to a channel, the display shows you the title of the song being played? That means that RDS is working. If RDS is working, then the hardware is providing the AF data, and it is up to the software to use that data.
The radio hardware itself does not deal with AF. It just feeds data up the i2c bus. The software running on the other end of that bus will keep track of the AF data being provided for that frequency, and it will monitor the signal strength. If the signal strength drops too low, it it supposed to trigger a tune to a stronger source.
Click to expand...
Click to collapse
I meant they have the same headunit, same manufactor, same MCU, and the AF works on their units. On my unit I don't see the song name, just the station name. Anyway i'm done, i give up
Inviato dal mio Z2 Pro utilizzando Tapatalk
royalhawk2002 said:
On my Xtrons PX5 with Oreo and GS MCU 2.94 AF is working correctly.
Check in the factory settings which is the Signal level you have set... it should be -30dB. This is the value of the radio signal that make the MCU to switch to the alternative frequency.
Click to expand...
Click to collapse
Tried with no luck. Also tried with different regions like Russia, China, etc.
Inviato dal mio Z2 Pro utilizzando Tapatalk
royalhawk2002 said:
If I remember right should be under the factory settings on the tab "other"
Inviato dal mio SM-N960F utilizzando Tapatalk
Click to expand...
Click to collapse
PLS Photo. Thx
royalhawk2002 said:
On my Xtrons PX5 with Oreo and GS MCU 2.94 AF is working correctly.
Check in the factory settings which is the Signal level you have set... it should be -30dB. This is the value of the radio signal that make the MCU to switch to the alternative frequency.
Click to expand...
Click to collapse
PLS send an image of the setting. THX
@mike2587 any news about solution?
xinpin said:
@mike2587 any news about solution?
Click to expand...
Click to collapse
Nope, no one is interested. Witson can't provide a solution, their support is very bad. I won't buy a Chinese car stereo anymore in my life, this is the only thing i can tell you. Good luck.
Inviato dal mio ZUK Z2121 utilizzando Tapatalk
I have problem with Radio FM, I have noises and interference, sometimes play good, sometimes bad, I don't know, I have connected radio antenna amplifier, any solutions?
royalhawk2002 said:
On my Xtrons PX5 with Oreo and GS MCU 2.94 AF is working correctly.
Check in the factory settings which is the Signal level you have set... it should be -30dB. This is the value of the radio signal that make the MCU to switch to the alternative frequency.
Click to expand...
Click to collapse
mine is 20db
captsakis said:
mine is 20db
Click to expand...
Click to collapse
yes now is changed to 20 dB with last MCU 2.94
I have the same problem with an A-Sure Android 8.0 4/32gb. When the car is cold, Fm radio work fine.
But when it's play around an hour and in the car it's about 23° degrees, I have a lot of noises in background.
First time I think, a side window was open.
Mcu :MTCE_LM_V2. 88_1
BUILD: 8.0.0 OPR5 170623.007 eng. HTC.20180607.171229
Any solution or send it back?