Search Archive

OBDII/Dash/Car stats / possible programs?

By bsnively · May 25, 2009in Hacks/Mods💬 129 posts👁️ 47,511 views
Page 4 of 6
Posted Oct 28, 2009 · 23:46 UTC#76
I can not believe some of you have not yet realized that the problem is not in the program or device, but how to connect that device to F900BT ... The only question is whether via USB, Bluetooth or maybe wireless

 

Could you enlighten me how it's not possible to use a ELM OBD2 to usb converter w/ the appropriate ce drivers/etc? I must be missing something.

 

Thanks,

Ben

Posted Oct 29, 2009 · 01:17 UTC#77

I realize you can't integrate an AVIC, but have any of you iPhone users seen this?

http://www.viper.com/SmartStart/

Posted Oct 29, 2009 · 16:23 UTC#78
I realize you can't integrate an AVIC, but have any of you iPhone users seen this?

http://www.viper.com/SmartStart/

 

iPhone sheeple are funny ;) There have been products that do all of that (and then some) and do not require an iPhone for ages...

Posted Nov 06, 2009 · 04:38 UTC#80
I wonder if something like this http://reviews.cnet.com/8301-31066_7-10390928-267.html?part=rss&tag=feed&subj=Crave could be ported to our unit?

Nope, our units don't have a full Bluetooth stack, just a neutered one custom made by Parrot that only provides hands-free and serial port profiles. If we can figure out how to hack the USB to accept one of the USB bluetooth dongles w/ a CSR radio and manage to get a configuration interface working, general devices like these might be an option...

Posted Nov 14, 2009 · 20:14 UTC#82

so I was looking for exactly what you guys are talking about!

 

except all I want is the gauges, no fancy controlled retune programs

 

instead of buying 3-4 gauges to know what is happening, I could just pop the gauge up on my unit, it would be awsome and I could save a lot of $$$!!!

 

 

the ecu can tell you how much gas is left, how much you are consuming etc... I wanted to buy a cluster which had that option (without the gauge boost, air/fuel, oil, etc...) in europe for tdi's but it looks like a pain in the A$$ to wire and get to function properly, without even counting the fact that it costs a lot...

 

 

so what is the news? could it be possible? I am sure it could... If we can make our laptops read anything on our cars using an obII - usb cable, i am sure our unit could read it, also via usb

 

VW owners here all know of the vag-com program which does wonders! but I would like to leave the laptop at home and just use the unit! make some app in it etc...

 

I am sure it's doable... anyone here has any news?

Posted Nov 22, 2009 · 19:28 UTC#83

Come on people. Many members here, including me, are safe and ready to pay for this solution, or at least reply to our intense inquiries. So much potential that our multimedia has is a pity to remain undiscovered.

Nice greetings!

Posted Nov 24, 2009 · 05:26 UTC#84

Has nobody looked at the first post that i made in this thread?

http://www.bankspower.com/banksiq

This runs on windows CE Mabey it could work

They will be having a a stand alone version that will work on any obd2 Canbus system (96 and newer i think)soon

 

Just a thought

Posted Dec 19, 2009 · 22:51 UTC#85

Does no one wants to play around with this problem and make some money? Have someone at least tried, or we have no hope to solve the mystery about OBD2 :(

Posted Dec 20, 2009 · 17:36 UTC#86

Hi All

 

I might possibly be able to help on this one.

 

I have an F900BT running 3.02 and i also have vag-com software and also a USB-VAG serial lead.

Vag-Com is VW software for looking at fault codes but it can also tell you lots of things like speed etc.

 

Im willing to try this. Looking at the drivers list for my lead it looks like there might be a windows CE driver.

http://www.ftdichip.com/Drivers/D2XX.htm

 

The only thing now would be to get the software working on the avic. Whats the best way to do this.

Posted Dec 21, 2009 · 01:05 UTC#87

You'll likely need to use MortScript to help copy the FTDI driver DLL and .ini to \Windows and install the registry entries they outline in the "INF Files/registry settings.txt" file inside the driver. You should be able to call this script when the system starts up each time so driver.exe knows how to bind the driver to the USB device when detected. Once that's done and the FTDI chip's virtual COM port is available, it's a matter of getting the VAG-COM software working in the WinCE environment. I'm not sure if Ross-Tech ported the software to WinCE or not, I've only ever seen it on a Windows XP box. I've got a OBD-Link (next gen ElmScan dongle) that uses an FTDI chip too, been looking at the source for Scantool.Net to see if it would be relatively easy to port to WinCE...

Posted Dec 21, 2009 · 19:54 UTC#88
You'll likely need to use MortScript to help copy the FTDI driver DLL and .ini to \Windows and install the registry entries they outline in the "INF Files/registry settings.txt" file inside the driver. You should be able to call this script when the system starts up each time so driver.exe knows how to bind the driver to the USB device when detected. Once that's done and the FTDI chip's virtual COM port is available, it's a matter of getting the VAG-COM software working in the WinCE environment. I'm not sure if Ross-Tech ported the software to WinCE or not, I've only ever seen it on a Windows XP box. I've got a OBD-Link (next gen ElmScan dongle) that uses an FTDI chip too, been looking at the source for Scantool.Net to see if it would be relatively easy to port to WinCE...

 

Please "yell" people if someone manage to get this thing working, so we have just a little hope :)

Posted Dec 21, 2009 · 23:34 UTC#89

So we cant just use the windows CE 5.0 version of the driver then?

 

Vag-Com is not on windows CE, They have never ported it so we are stuffed there.

 

How about running a virtual machine on CE, Or am i pissing into the wind here.... :lol:

Posted Dec 22, 2009 · 16:57 UTC#90
So we cant just use the windows CE 5.0 version of the driver then?

Haven't tested it yet but I'm pretty sure we can use their driver. The "install" process has to be redone every time we reboot the system though. This is due to the fact that the DLL, .ini and registry entries are not part of Pioneer's WINCE.BIN image, so it's not in \Windows after the reboot and must be copied off the flash drive as part of a scripted startup process.

 

Vag-Com is not on windows CE, They have never ported it so we are stuffed there.

For now, anyway.

 

How about running a virtual machine on CE, Or am i pissing into the wind here.... :lol:

Hmmm, not aware of any virtual machine monitors designed for CE since the ARM/OMAP cores CE runs on might be a tad underpowered for the task. Now if VAG-COM was a .Net app, maybe using the .Net micro framework on the AVIC would let you run it.

Posted Jan 07, 2010 · 17:44 UTC#91

Guys im also like the idea of this and did my research i found that evoscan have a version for window CE and i manage to get one of this version this version is installed on a standalone unit called EvoscanGPS/NAV system that cost $399 http://translate.google.com/translate?h ... 345.0.html and this one to

Posted Jan 08, 2010 · 07:19 UTC#92
Guys im also like the idea of this and did my research i found that evoscan have a version for window CE and i manage to get one of this version this version is installed on a standalone unit called EvoscanGPS/NAV system that cost $399 http://translate.google.com/translate?h ... 345.0.html and this one to
Posted Jan 11, 2010 · 09:47 UTC#93
Guys im also like the idea of this and did my research i found that evoscan have a version for window CE and i manage to get one of this version this version is installed on a standalone unit called EvoscanGPS/NAV system that cost $399 http://translate.google.com/translate?h ... 345.0.html and this one to
Posted Apr 05, 2010 · 17:57 UTC#95

To those of you who were intested in using my Standback HUD software (video links earlier in topic) to control their Standback tuners in their cars, I have an F500BT OS image you can now update your unit with which will include all the necessary software updates to use it (drivers/.NET CF2.0/Software).

 

See my last post here for info on what all I had to do to get it working:

http://avic411.com/forum/viewtopic.php?f=34&t=25385

Posted Apr 07, 2010 · 23:16 UTC#96

How do you connect the F500BT to the Standback unit? What sort of connection do we need to find for those of us who do not have a Mazda or BMW?

Posted Apr 08, 2010 · 00:55 UTC#97
How do you connect the F500BT to the Standback unit? What sort of connection do we need to find for those of us who do not have a Mazda or BMW?

 

It connects via USB. So far this only works for Standback units since I wrote the standback software, I had the code to modify to make it work for these WinCE units. If we had a USB to CAN cable for which we could find WinCE drivers, I could probably modify my software to use it instead of the Standback hardware.

Posted Apr 08, 2010 · 02:16 UTC#98
It connects via USB. So far this only works for Standback units since I wrote the standback software, I had to code to modify to make it work for these WinCE units. If we had a USB to CAN cable for which we could find WinCE drivers, I could probably modify my software to use it instead of the Standback hardware.

I know the ElmScan.Net software I use with my OBDLink scan tool has their source on their website. Since it's basically a glorified FTDI 232 (I forget if it's a 232R or 2232H) you can probably use their ARM driver (see http://www.ftdichip.com/Drivers/D2XX.htm) to add support to some of these scan tools.

 

Just a thought. :)

Posted Apr 08, 2010 · 05:39 UTC#99
It connects via USB. So far this only works for Standback units since I wrote the standback software, I had to code to modify to make it work for these WinCE units. If we had a USB to CAN cable for which we could find WinCE drivers, I could probably modify my software to use it instead of the Standback hardware.

I know the ElmScan.Net software I use with my OBDLink scan tool has their source on their website. Since it's basically a glorified FTDI 232 (I forget if it's a 232R or 2232H) you can probably use their ARM driver (see http://www.ftdichip.com/Drivers/D2XX.htm) to add support to some of these scan tools.

 

Just a thought. :)

 

The Standback uses the same driver, so it'd only require a unique id inserted in the registry so it matches the device to that same driver. BUT, that won't tell us the api for unit it's self. Just because we have a channel to speak on doesn't mean we know what command structures it expects to ask for data from the device. That's the hard one. I think I summarized that one above somewhere as well. That's the hard part to get a hold of.

Posted Apr 24, 2010 · 16:03 UTC#100

Hi Guys, I'm Hamish from EvoScan. My WindowsCE 4.2/5.0/PPC/WM5/6/7 (netcf2) software is being extended to cover more screen resolutions and more gauges and more vehicles for datalogging. I'm keen to work with you guys to get it working for the AVIC devices.. This seems like a cool project. Anyone got a spare AVIC device I can borrow to set it all up?

Page 4 of 6