Thread: cygwin setup questions

So what package(s) contain the x server? "X11/xorg-server"? Thanks!

Hrm. So I can't figure out the fltk-gdi thing from within cygwin.

From cygwin's setup, choose "xinit" which will install all the stuff you need. Then go into your start menu's "Cygwin X", and start the X server. You'll get a terminal window that you can use.

Whenever you want a new terminal window and cygwin/X is running, you'll want to click on the X in the system tray and choose Applications->Xterm [which is actually highly preferable to the default cygwin terminal anyway]

Gary (-;

Originally Posted by chunkyks

Hrm. So I can't figure out the fltk-gdi thing from within cygwin.

From cygwin's setup, choose "xinit" which will install all the stuff you need. Then go into your start menu's "Cygwin X", and start the X server. You'll get a terminal window that you can use.

Whenever you want a new terminal window and cygwin/X is running, you'll want to click on the X in the system tray and choose Applications->Xterm [which is actually highly preferable to the default cygwin terminal anyway]

Gary (-;

Xterm worked! Thanks so much!

Now how do I get obdgui to work with obdsim? I tried running obdsim from one xterm and then running obdgui from another one. All the gauges are grayed out. I was hoping to see some fake data being fed from the obdsim to obdgui...

Did you do "make install" ?

Assuming you did, when you run obdsim it says something like:

Code:

SimPort name: /dev/tty1

In obdgui, edit the "OBD Device" box to say the simport [yours is probably also /dev/tty1] and click "Go"

Gary (-;

Originally Posted by chunkyks

Did you do "make install" ?

Assuming you did, when you run obdsim it says something like:

Code:

SimPort name: /dev/tty1

In obdgui, edit the "OBD Device" box to say the simport [yours is probably also /dev/tty1] and click "Go"

Gary (-;

Yes obdsim says
SimPort name: /dev/tty1
and I entered the same into obdgui and clicked "Go". Something ("Starting" maybe) flashed really fast behind the "Go" button and then disappeared. All gauges still remain grayed out.

I also realized that part of the problem maybe the path is not set to the
/usr/src/obdgpslogger-0.15/bin
directory. I had to run
./obdgui
not just
obdgui

Then I found $PATH contains both unix and Windows paths. Very strange.

Oops I missed the "make install" until now - thought it was optional. Did a quick try:

$ make install #
/bin/sh: line 0: cd: /obdgpslogger-0.15/build: No such file or directory
make[2]: *** [libs/sqlite3/CMakeFiles/cksqlite.dir/depend] Error 1
make[1]: *** [libs/sqlite3/CMakeFiles/cksqlite.dir/all] Error 2
make: *** [all] Error 2

Looks like more issues to deal with...

I also realized that part of the problem maybe the path is not set to the
/usr/src/obdgpslogger-0.15/bin
directory. I had to run
./obdgui
not just
obdgui

Then I found $PATH contains both unix and Windows paths. Very strange.

Yes, that's what causes obdgui to fail like that. Without the make install part:

Code:

export PATH=/usr/src/obdgpslogger-0.15/bin:$PATH
obdgui

I'm not sure why that make install is failing; did you move the obdgpslogger source directory after building? If you did, you'll need to re-run cmake.

Gary (-;

Originally Posted by chunkyks

Yes, that's what causes obdgui to fail like that. Without the make install part:

Code:

export PATH=/usr/src/obdgpslogger-0.15/bin:$PATH
obdgui

I'm not sure why that make install is failing; did you move the obdgpslogger source directory after building? If you did, you'll need to re-run cmake.

Gary (-;

That helped! After setting the path I got

Code:

$ ../bin/obdsim
SimPort name: /dev/tty1
Successfully initialised obdsim, entering main loop
Reset
Reset
Echo disabled
Linefeed disabled
Spaces disabled
Reset
Reset
Echo disabled
Linefeed disabled
Spaces disabled
Reset
Reset
Echo disabled
Linefeed disabled
Spaces disabled
Reset

pressing the "Go" three times. So I guess obdgui is talking to obdsim now. Gauges are still grayed out though.

I did move the directory. I will try recompile later on the newer version of code. Thanks!

Technically, what's actually happening is that obdsim and obdgui never directly communicate. obdgui launches the separate obdgpslogger binary, and that's what communicates with the sim.

Could you go into window->raw output and check the checkbox, and paste what it's saying when you run it?

Also, could you run obdsim with "--logfile=seriallog.txt" and see what that contains?

Sorry this is all so much effort! Normally things are a lot simpler :-(

Gary (-;

Thanks for so patiently answering all my questions! It finally worked!

At some point my hard drive ran out of space, so I decided to give it a clean start. I cleaned out old junks to make room on the hard drive. I wiped cygwin and reinstalled it with Xinit but without fltk. I downloaded most recent code using svn. Initially obdgui was not built until I realized and added fltk. Then it just worked. The obdsim echos something like

SimPort name: /dev/tty2
Successfully initialised obdsim, entering main loop
10.000000 seconds. 0 samples, 0 queries. 0.00 s/s, 0.00 q/s
Reset
10.519000 seconds. 0 samples, 1 queries. 0.00 s/s, 0.10 q/s
Echo disabled
Linefeed disabled
Spaces disabled
10.143000 seconds. 50 samples, 53 queries. 4.93 s/s, 5.23 q/s
10.145000 seconds. 50 samples, 50 queries. 4.93 s/s, 4.93 q/s
10.073000 seconds. 49 samples, 49 queries. 4.86 s/s, 4.86 q/s
10.130000 seconds. 50 samples, 50 queries. 4.94 s/s, 4.94 q/s
10.195000 seconds. 50 samples, 50 queries. 4.90 s/s, 4.90 q/s
10.175000 seconds. 50 samples, 50 queries. 4.91 s/s, 4.91 q/s
....

and all five gauges on obdgui show numbers and moving needles.

I am so happy! Thank you so much!

Questions for next steps:

1. The cygwin install still added a lot of Windows paths into $PATH. I used
   Code:

   export PATH=/usr/local/bin:/usr/bin:/bin

   to clean it up. Is that OK?
2. GPS and FFT are still missing.
3. Hardware: I am contemplating between OBDPro USB Scantool and OBDLink Multiprotocol OBD-II by ScanTool. Any preference between the two?

Thanks again!