EEGeek Posted October 16, 2009 Report Share Posted October 16, 2009 Well, I can post what I've got so you an at least run it, even though you won't be able to use it with any of your hardware. It's more than just a file though, there's a bit to bundle up. I've got the day off tomorrow so I'll do that. If you all use Visual Studios then I can provide dummy GUIs of what I've got with no code so you can play with the design. Quote Link to post Share on other sites
Rob Posted October 16, 2009 Report Share Posted October 16, 2009 well I checked the drivers included with my software and there is alot of ftdi stuff in there, seems like its compatible like you say... so now I just have to figure out how to tell the device to get me the info I want correct? and this is done through the companies API ?? Quote Link to post Share on other sites
EEGeek Posted October 16, 2009 Report Share Posted October 16, 2009 Yup. An example would be that you create your own cable and use the same ftdi chip. The chip connects to your cable on one side and some electronics you design on the other. You decide to be funny and require the the software running on your laptop send the command "banana" as a string down the usb cable to the ftdi chip which would relay it on to your hardware. You're hardware is designed to recognize the banana command and respond with the engine coolant temperature it recorded from the obdii port. Â As you can see, you need not only the driver to talk to the device's usb controller, you also need the expected commands and the format of the responses to those commands. Otherwise you're just guessing and sending random stuff seeing if you can get the device to respond. A published api states just that. If there isn't one then you have to do some low level debugging, like running your software and finding a way to intercept the commands. Then you can see what commands to send based on what button you clicked in your software. I hope we don't get to that point as it'd suck up so much of my time. Â well I checked the drivers included with my software and there is alot of ftdi stuff in there, seems like its compatible like you say... so now I just have to figure out how to tell the device to get me the info I want correct? and this is done through the companies API ?? Quote Link to post Share on other sites
Rob Posted October 16, 2009 Report Share Posted October 16, 2009 cool, I'll email the company and see if they have or will even release that to me. Thanks! Quote Link to post Share on other sites
Rob Posted October 21, 2009 Report Share Posted October 21, 2009 they said they can't give me the info, any they don't have plans to develop for winCE Â this sucks. Quote Link to post Share on other sites
roadtrip1098 Posted October 21, 2009 Report Share Posted October 21, 2009 You guys have promted me to attempt an install of the COBB AccessPort software on my AVIC. Theoretically I should be able to log data, change fuel maps, view realtime data and troubleshoot error codes. Here's hoping it works on Windows CE. Quote Link to post Share on other sites
EEGeek Posted October 22, 2009 Report Share Posted October 22, 2009 An app compiled for a PC can not run on a Windows CE device. That's what I was trying to explain earlier. Got an AP eh? I'm supposed to not like you because of that Quote Link to post Share on other sites
FallenOne Posted October 22, 2009 Report Share Posted October 22, 2009 Hey EEGeek anything new worth mentioning? Quote Link to post Share on other sites
EEGeek Posted October 22, 2009 Report Share Posted October 22, 2009 Well, I still work on the software, but I get the feeling its mostly for my own use unless someone else gets an api for another specific piece of hardware. I can post what I keep updating, but until you can use my software on something beside the Standback, not much of it will mean much. Quote Link to post Share on other sites
bsnively Posted October 23, 2009 Author Report Share Posted October 23, 2009 I am considering getting an elm chip/cable from the usb to try this. Â I understand if the answer is no, but would you be willing to loan out the source to me w/ the understanding that the source is the rights to you and any changes I make, you will own? Â (much like some of the open source licenses that allow you to use, but have to submit edits back...) Â Thanks, Ben Quote Link to post Share on other sites
teksimian Posted October 27, 2009 Report Share Posted October 27, 2009 Hey,  I just quickly looked through this thread, ... while browsing around I found this;  http://freewareppc.com/utilities/obdgauge.shtml  Unfortunately the link seems to be dead.  Best of luck, awesome ideas. Quote Link to post Share on other sites
sharkye Posted October 27, 2009 Report Share Posted October 27, 2009 Found this link working: http://www.pocketgear.com/en_US/html/di ... d7172355pg  Is this compatible with CE5.0?  thanks, Quote Link to post Share on other sites
bsnively Posted October 27, 2009 Author Report Share Posted October 27, 2009 I know it requires the .net compact framework (has the source with it as well as the binaries) Â thx, Ben Quote Link to post Share on other sites
bsnively Posted October 27, 2009 Author Report Share Posted October 27, 2009 This is the link I got it from - source zip file is at the bottom  http://www.qcontinuum.org/obdgauge/  Thx, Ben Quote Link to post Share on other sites
Yakumsi Posted October 28, 2009 Report Share Posted October 28, 2009 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 Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.