Looks like taking these steps:<br><br>* installing the OBD software package that comes with the USB device<br>* Running the Windows program<br><br>Seems to have done the trick.<br><br>I know #2 seems like a Voodoo step, but I've noticed that obdgui can sometimes not show data, or not start correctly the first time around, but work well the second. So it's not unlikely that having another app speak to the USB connector works.<br>
<br>Of course, I'm talking voodoo, and when people talk voodoo in my products I tell them they're crazy.<br><br><div class="gmail_quote">On Sat, Jul 17, 2010 at 3:40 PM, Robert Konigsberg <span dir="ltr"><<a href="mailto:konigsberg@gmail.com">konigsberg@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">-b 38400 didn't work, but I have not tried -b 0.<br><br>My laptop and car are with my wife, I'll try again when she returns. I am going to try installing the drivers from the ODBPro USB CD, and some of those software packages. We shall see.<br>
<br>FYI transferring back to the MBP works just fine, so it's not the hardware.<div><div></div><div class="h5"><br><br>On Sat, Jul 17, 2010 at 3:03 PM, Gary Briggs <span dir="ltr"><<a href="mailto:chunky@icculus.org" target="_blank">chunky@icculus.org</a>></span> wrote:<br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div></div><div>On Sat, Jul 17, 2010 at 02:12:40PM -0400, Robert Konigsberg wrote:<br>
> Hi,<br>
><br>
> I've had to make a last-minute change and go from OSX to Windows/Cygwin. I<br>
> know Cygwin well enough so it's not much of a shift, but some things are<br>
> preventing me from succeeding.<br>
><br>
> Using only the code from the svn repository, I compiled, built and installed<br>
> the obdgpslogger, and associated tools. Plugged in the USB device.<br>
><br>
> Now, I know that the device is COM3, and that it's bound to /dev/ttyS2. I<br>
> know this because when I unplug the device and run the logger with<br>
> /dev/ttyS2, I get this message:<br>
><br>
><br>
> "/dev/ttyS2: no such file or directory. / Couldn't open obd serial port.<br>
> Attempting to continue. / Couldn't find either gps or obd to log. Exiting."<br>
><br>
> And when I plug it in, I get this:<br>
><br>
> "Opening serial port /dev/ttyS2. this can take a while / Successfully<br>
> connected to serial port. Will log obd data / Couldn't get obd data for cmd<br>
> 00 / here".<br>
><br>
> I can see when this is happening that the OBD USB device only has two<br>
> lights: the power light, and the occasional "PC / RX" light.<br>
><br>
> So, that's odd. What are your thoughts?<br>
<br>
</div></div>I would suspect the baudrate isn't set right. Try passing the right<br>
baudrate directly ["-b 38400], or try running with "-b 0" and see if it<br>
guesses it?<br>
<br>
If that's still not the case, save the serial log and see what it<br>
contains? ["-l logfile.txt"]<br>
<br>
I just tried a fresh checkout under cygwin, seems to be working here.<br>
<br>
Gary (-;<br>
_______________________________________________<br>
obdgpslogger mailing list<br>
<a href="mailto:obdgpslogger@icculus.org" target="_blank">obdgpslogger@icculus.org</a><br>
<a href="http://icculus.org/mailman/listinfo/obdgpslogger" target="_blank">http://icculus.org/mailman/listinfo/obdgpslogger</a><br>
</blockquote></div><br><br clear="all"><br></div></div><div><div></div><div class="h5">-- <br>Robert Konigsberg<br><a href="mailto:konigsberg@gmail.com" target="_blank">konigsberg@gmail.com</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Robert Konigsberg<br><a href="mailto:konigsberg@gmail.com">konigsberg@gmail.com</a><br>