Related
1. Is it really that bad as a phone - many have commented on weak single strength etc.
2. Will I have to buy a serial connection/docking bay to connect to my NT 4.0 Workstation.
3. If I use the device as just a phone - no playing around - how long will it stay charged on stanby.
4. Will the headphones hat I get with the unit allow me to listen to mp3's and what is the quality like?
5. Using GPRS - if I am sending and receiving emails (pop3), obviously I have the filesize of the email to consider - but how much data will I transfer when checking for new email and downloaded lists of unopened email. What hidden bandwith will I use?
6. Is the OS future proof? Will microsoft dump the Pocket PC OS very shortly?
7. There is software out there that allows you to control yout tv and vcr etc. Is the infrared powerful enough - do you have to sit on top of the telly for it to work - It's not major important - but just interested?
8. I have seen some phones that you can put two sim cards in - can you do that with the xda?
9. Will software designed for tyhe ipaq work on the xda.
10. Is this a good deal - Device cost £199, o2 30 mins month £15, 5mb per month £12? Can I use another gprs provider??
Add 11 th & 12th question
As someone also considering purchase in UK ..
11. How practical is the screensize / voice level to use the device with GPS in car such as tomtom navigator 2
12. Does unlocking software operate on W2K / XP ??
answers but only my opinion
1. useless if signal lost (search for my posts) in rom updated section.
2. can't answer this one as i use XP Sorry !
3. i have had 3 or 4 days between charges and if it keeps signal its ok.
depends on how much u use and talk though.
4. headphone quality is quite good for mp3 only problem is getting them to stay in your ears i have some foam boots off another set that help but they are still awkward.
5. you can set a limit on what u grab ie no file attach just headers etc so bandwidth u use will depend on ammount of emails and your settings.
6. who can tell what microsoft will do ? its future proof as long as they want it to be really.
7. infrared is kinda weak i found about 2 metres was my max with remote software.
8. maybe possible but the way it fits in i feel any mod would be ugly and easily damaged (liitle rubber door and a tiny microswitch that has to be operated would make this difficult (but who knows someone might do it) and you would also have to unlock it.
9. seems to work most ARM software unless there are harware rerlated issues to the ipaq like rotating screen or assigning buttons.
10. only you can answer that one for yourself do you feel its necessary at that cost and can u afford it ?? when unlocked i can see no reason at all why you could not use a differnet gprs provider as long as you had their sim in .
11. i have hooked it up to my gps reciever via serial cable with tom tom and it works but I dont now how noisy your car is :wink: its loud enough in my rover 400
12. maybe xda developers can answer this one for you?
Re: Add 11 th & 12th question
RogerB said:
12. Does unlocking software operate on W2K / XP ??
Click to expand...
Click to collapse
Yes it does. 98/ME/NT/2000/XP and possibly also 95. And it's likely to also run on newer versions of Windows.
Further developments to my questions.
Today I went to the o2 Shop - to answer some of my q's
One thing that struck me was that when he went on the web - he still had to dial/connect - I thought they were online all the time?
My 2c:
1. It's not totally unusable, but if you need good coverage in weak signal areas, this device isn't for you.
2. Yep, you need a serial cable.
3. Can't answer as I use the PocketPC stuff much more than the phone stuff, but with moderate PPC playing, it lasts the weekend out no problem. As with all other phones, if you know you'll be out of coverage for a while, turn the phone off to save the batteries being drained by the 'anybody out there' signal when the phone trys to find a cell.
4. I quite like the headphones. The quality of the device's audio is very good. If you've got a pair of headphones you really like, you can get an adaptor pretty easily. A cheap 2.5->3.5mm phono adaptor is fine if you don't need to use the answer button.
5. There's not much hidden bandwidth, WYDIWYG (what you download is what you get). I think the polling for new emails mich be a bit inefficient: it seems to download all headers each time, but I've not investigated this.
6. This is one of the great things about the XDA, the OS is pretty much standard, and updatable (although O2 drag their heels on this one), so it's reasonably future-proof. There's too much of an existing PocketPC userbase for the platform to be abandoned.
7. As answered above. I think there's an adaptor for the IPAQ that uses the phono socket to drive a more powerful IR, but out of the box it's just to weak to work well.
9. Surprisingly, most IPAQ stuff works fine. The overclock utility even works (as usual be careful, it can cause a hard reset). HTC makes both devices after all. The main gotcha is there are less buttons on the XDA.
10. That's the deal I'm using. They're all pretty much the same. O2s coverage isn't as strong as Vodafone in some areas, but at least they offer some form of device support.
GRPS, while often advertised as an "always on" technology, does require you to dial up. The new rom alows you to set it so it doesn't disconnect on powersave/incoming phonecall. Of course if you loose your signal, it disconnects.
Thanks
Thanks so far!
*update, the conclusion is that the current software is useless and as of the ppc6800 and the following HTC models, the IRDA port is either crap or non-existent, for that reason I am building a powered, universal adapter to turn any phone into a remote*
hello. first off, yes I know there are old threads about this, but they are dead and had a different take on this topic. I am looking to know if anyone has gotten any tv remote control software working on the mogul. I don't care about the distance so I dont want to hear about how the mogul is ill-equipped to do this, I just want to know what software works as I will use\make a IR repeater\booster that will give me all the range I need.
I have tried the following software
1-PDAWin tv remote controller simply crashes when I press any button
2- noviiRemote is not compatible with our IR
3- RemoteControl II v.2.12 stays it is incompatible with our processor and for that reason, it turns off the IR access... but the rest of the software works ??? odd
4- UniversalRemoteCE 4.0 Tested by wagonis, froze his phone with every try
5- Total Remote does not work, freezes when I try to record a signal.
Untested
6- UltraMote
can't find
7- VITO remote
so to recap. Has anyone found a working software? I will give a free IR booster\repeater to anyone who can point me to a proper and working programmable universal remote control software that works over IR and not the web (or even better, anyone who can get PDAWin tv remote working )
thanks.
Honestly, I've tried 4 different softwares from that list and none worked, if anything they kept crashing my phone...so I gave up before I caused any damage to my phone. If you figure out which one works though, please list it, I'd like to know and try it.
can I know which was teh 4th that did not work so I can update my list please?
UniversalRemoteCE 4.0 froze up my phone every time I tried to use it
Many have tried. I am pretty sure no one has succeeded.
in my best Airplane - The Movie voice
"good luck, we're all counting on you"
my best suggestion is to buy an older known compatible phone with stronger irda
i looked into it a bit ago and came up with a good solution and found two of the phones on ebay for $20...but never bought them
i know it would be convenient to use our daily cell for this feature...but its an uphill battle
dont give up...lol
double post
Since the whole software thing does not seem to work... I am going to set out on making my own! My goal is to make a universal-universal remote app; even cross-platform, and the way I will do this is with external hardware. Since most new phones do not have a good IR port, I will make an external IR port that plugs into phones, mark my words!
I will keep people up to date on this
I'll subscribe to this thread to keep tabs on this. Good luck.
Well I am very excited to say that things are moving along nicely. Unfortunately, my local electronics supply shop (that is actually worth going to) is closed during weekends since its a small business who's main clients are engineering students during the year . This means that My full prototype (with range booster) will have to wait, but the basic premise is working, and, depending on my schedule, I should have a working prototype soon. I have already gotten in contact with a few chinese companies to compare the price of production of the modules.
well, the project is coming along well, but I need some input from the community. 1 is a note, 2 is the important question.
1- the software will be open source. The exact format still has to be determined, but the main lead right now is java so that i can be universal for all phones (except the Iphone that will need its own app).
2- Should it be powered or not? The module is coming along well, but I need some input. If it is powered, I have to make the tough decision between having the ext-usb plug sticking out on the edge of the board, meaning you have a 9v battery dangling from your phone or a short cable (1-2 feet) that plugs in the ext-usb port and the module rests next to you. What is the best route for this? (Ideally I would love bluetooth, but I do not have the electronic know-how for this)
julienrl said:
well, the project is coming along well, but I need some input from the community. 1 is a note, 2 is the important question.
1- the software will be open source. The exact format still has to be determined, but the main lead right now is java so that i can be universal for all phones (except the Iphone that will need its own app).
2- Should it be powered or not? The module is coming along well, but I need some input. If it is powered, I have to make the tough decision between having the ext-usb plug sticking out on the edge of the board, meaning you have a 9v battery dangling from your phone or a short cable (1-2 feet) that plugs in the ext-usb port and the module rests next to you. What is the best route for this? (Ideally I would love bluetooth, but I do not have the electronic know-how for this)
Click to expand...
Click to collapse
Why not make all? Powered and not. Corded and not. Are you encasing the electronics? If just for the Mogul how 'bout a phone case type add on putting the IR port on the right end of the phone while you're at it so we don't have to rotate our screens? That being said, with the Mogul getting dated, how 'bout for newer phones lacking IR ports all together like the touch pro and touch pro 2? Oh, maybe someone could help you out with bluetooth.
Well its not just for the mogul, it is going to work universally for all HTC phones and will be one little tweak away from working with other phones.
As far as corded or not, I think I will make it non corded and then you can just add it. It will cost a few cents extra but save alot on production costs of 2 different modules (if I go with powered, unpowered can easily be both).
The reason I am not doing powered and unpowered is that the powered requires a case and a battery and starts getting a little big (the size of half a thumb approximately), while the unpowered one is about 0.5mmx0.5mm. Also, making the powered one requires a much greater production cost as it would be made in china because if I make it myself, the powered one would be about 4 inches by 2 inches as I can't make the small traces myself, many of the parts are hard to come by and suftace mount is hard to do.
The reason that none of the programs work is because they require raw IR port access, not the IRDA protocol.
dj13241 said:
The reason that none of the programs work is because they require raw IR port access, not the IRDA protocol.
Click to expand...
Click to collapse
Thats ok, this is a hardware\software combination so the IR will work.
I think I love you man. I've been looking for this since before I got my Mogul in my hands.
Manicmoguladdict said:
I think I love you man. I've been looking for this since before I got my Mogul in my hands.
Click to expand...
Click to collapse
lol I hear ya. Everything is being delayed because the store I usually go to was selling IR LEDs for 4 bucks and they don't specify voltage so I had to order some online. I just need to get that stupid LED so that I can be done with the hardware and get working on the software.
I am still waiting on those diodes. I bought molding and casting material so that our IR emitters will look better than a loose set or components soldered on an extusb port
Anyone going to china who can buy ExtUSB ports for 50 cents with the breakout port? I got that quote from a company but I don't like sending unsecured payments and 10$ per extusb port + breakout board is going to make it pretty expensive for us. If so, let me know, I would like to buy a batch.
thanks.
since our device will work on many phones, instead of creating threads in every forum of every device, we decided to opt for a twitter account where we will keep everyone up to date on this project.
Spread the word!
http://twitter.com/wrctweets
Found this thread searching for a Bluetooth to IR converter, so I could use my Rhodium as a universal remote.
I was wondering... since all modern smartphones have Bluetooth, why not make a powered BT -> IR converter, which uses the HID standard? Since most phones have a HID application already (my old SE K750i could be used to control my desktop computer with HID), you don't need a lot of development on the phones itself. You'd need a way to program the conversion table (key 5 -> send PLAY IR sequence), I guess. You could then have a simple HID remote on simple phones or a full blown custom skinnable remote on a WVGA smartphone.
It would really be nice to have a Philips Pronto (or similar) universal remote where you can operate all sorts of equipment.
unfortunately, working with bluetooth at that level would be well beyond my expertise and bring the cost up $$$$$ because of the low volume of production. Also, making the drivers for this would be much harder and way to phone-specific, killing the intent of this device. Also, the way this works, it should work with any standard IR device.
I have a p4000 and am upgrading to a touch pro2, when I upgrade again in 2 years, I don't want to have to start the project over .
Finally, bluetooth device = more components = bulkier and = batteries!
I am getting back home late tonight and I will get back to work on the project (got the LEDs the day I was leaving).
ps. I do appreciate all feedback and comments.
thank you
julienrl said:
unfortunately, working with bluetooth at that level would be well beyond my expertise and bring the cost up $$$$$ because of the low volume of production. Also, making the drivers for this would be much harder and way to phone-specific, killing the intent of this device. Also, the way this works, it should work with any standard IR device.
I have a p4000 and am upgrading to a touch pro2, when I upgrade again in 2 years, I don't want to have to start the project over .
Finally, bluetooth device = more components = bulkier and = batteries!
I am getting back home late tonight and I will get back to work on the project (got the LEDs the day I was leaving).
Click to expand...
Click to collapse
sorry for being off topic, but do you know when the touch pro 2 is coming out in Canada ? And who's gonna get it telus, roger, fido or bell ?? (hope this is coming to Telus)
hehe, its out with telus waiting for mine in the mail now!
Inbound Ir
Will your Module accept inbound ir transfer? I am using a polar hr monitor that uses ir to download files to my phone. I've been looking for an upgrade option with ir without success. If your module will work, this is great news. Keep up the good work.
For the past few days I have been racking my brain and searching multiple forums for the answer(s) and I finally turn to XDA to hopefully help answer.
The thought: I would love to be able to take my DroidX connect it via HDMI to a 7" monitor in my car to have a nice view of the navigation, access to my music and all of the other items that the phone has to offer (which include data connection and accurate GPS). Sure I can buy an android based headunit or build a carPC but why when I have what all of that has to offer in my pocket? Then I got to thinking, to take it a step further, why not use a 7" touchscreen monitor so that I am not just passing video and sound via the HDMI but that the monitor registers touches to the phone.
WebTop is a great middle of the road solution as it would output the HDMI and allow the user to utilize the phone as the mouse touchpad on the screen. Sadly it is only offered for a select few phones. So on to my questions.
1. Did I some how miss a WebTop project being worked on that would do what I am talking about?
2. Am I wrong in thinking that drivers need to be worked out depending on the phone AND which 7" TS was used?
3. Most, if not all, android phones have video out capabilities, so outputting to the screen would be workable, but is there a better way to get the input hurdle worked out.. not a question just an open suggestion box.
Looks like a few more days or looking would have helped. Customgadz has what I need.
so what did you find? I searched for Customgadz, with no results. did you use hdmi mirroring with Android, or does this work with webtop?
Looks like the australian website has a solution to control an android device with a 4 wire external touchscreen using a module.
search for "customgadz remote touch"
Only pre-order now and the website states they start delivering end of januari
Hey everyone,
If I'v posted this in the wrong section or if there is an UPDATED thread please let me know
I would like to make my own device similar to the MOTOACTV (which runs 2.3) but with the additions of NFC+WiFi Direct, an LED, a vibrating motor
Extend NFC to a limit of distance of 9 inches (can this be done with bluetooth always on/discoverable auto-pairing?)
Display the current weather every 5 seconds (screen should be off between those intervals)
Turn the screen on when in range of another NFC device
Transfer a file through NFC+Wifi Direct one a device is detected
What hardware/software would I need to make a proof of concept?
Which route should I take?
Purchase an MOTOACTV device and mod it? Using what software/hardware exactly?
Use one of the below kits?
Liquidware Starter Kit
Liquidware Development Kit
KIT210 (Android 2.3)
KIT4412-I (Android 4.0)
ORIGEN 4 Quad Evaluation Board
ARM11 Android Single Board Computer Development Kit
If a dev kit is my best bet, what software hardware would I need to mod it to my needs?
Thanks for helping out a N00b
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