Thread: Running from web supplied OSX bundle and built bundle

I installed fltk with macports and now obdgui builds properly and the program seems to run just fine now. I'll try it out soon.

Heya,

My apologies, I was out of town so didn't see this yet. Lemme know if it's working for you! If not, I'm back and paying attention again, now

Gary (-;

Well no, it doesn't seem to be working so far. When I run from the GUI, I hit Go and it greys out the buttons for a bit and then they come back to normal and nothing happens and no log file is created. Here's a screenshot of the GUI:



And just to note, the GUI does weird things spatially when resizing, and I think some buttons don't have visible labels because they're squished just above the logfile box:



I also tried running obdgpslogger from the Terminal and it runs but I see this:

Code:

john-lewis-computer:~/obdgpslogger/bin jlewis$ ./obdgpslogger -s /dev/cu.CBT-DevB-1 -d /Users/jlewis/Documents/OBDGPSlogs/echo1.db
Bus error

The car is a Toyota Echo and I am using the ElmScan5 Bluetooth device. The device works fine even on this car with OBD Gauge over Bluetooth, I can view DTCs and see live sensor data. As far as I know the ElmScan 5 uses a real ELM327 chip.

- John L

Well no, it doesn't seem to be working so far. When I run from the GUI, I hit Go and it greys out the buttons for a bit and then they come back to normal and nothing happens and no log file is created. Here's a screenshot of the GUI:

The GUI is actually just a wrapper on the command-line application; the behaviour you're seeing is what happens if the command-line application isn't working, or is crashing. Borne out thus:

I also tried running obdgpslogger from the Terminal and it runs but I see this:
{stuff}
Bus Error

Ugh. Could you by any chance show me a back trace? There's two steps to that; first, build with debug symbols, and second get the backtrace:

1) Re-run cmake and enable debugging symbols; either use ccmake and change CMAKE_BUILD_TYPE to "Debug", or you can set it on the commandline cmake [building just like you did before, other than the extra parameter]:

Code:

cmake -DCMAKE_BUILD_TYPE=Debug ..
make

2) Run obdgpslogger from gdb, like this:

Code:

john-lewis-computer:~/obdgpslogger/bin jlewis$ gdb ./obdgpslogger
r -s /dev/cu.CBT-DevB-1 -d /Users/jlewis/Documents/OBDGPSlogs/echo1.db

The second line is typed at the gdb prompt, and is an 'r' followed by a space and the other command-line options you use. Once the software has crashed, run "bt" at the gdb prompt, and paste the output here.

And just to note, the GUI does weird things spatially when resizing, and I think some buttons don't have visible labels because they're squished just above the logfile box:

Yeah, re-writing the GUI to not suck is high on my list of stuff to do. Those buttons above the logfile box are actually part of the FLTK standard filename widget, and make it easier to cut out pieces of the filename/path [you can click on them to see what happens. I don't find it very useful, myself, but it's what's there].

Thank-you!

Gary (-;

I don't know if I did this all properly but here's what I got:

Code:

(gdb) r -s /dev/cu.CBT-DevB-1 -d /Users/jlewis/Documents/OBDGPSlogs/echo1.db
Starting program: /Users/jlewis/obdgpslogger/bin/obdgpslogger -s /dev/cu.CBT-DevB-1 -d /Users/jlewis/Documents/OBDGPSlogs/echo1.db
Reading symbols for shared libraries . done

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00000000
0x90012f53 in strdup ()
(gdb) bt
#0  0x90012f53 in strdup ()
#1  0x00002546 in main (argc=5, argv=0xbffffb58) at /Users/jlewis/obdgpslogger/src/logger/main.c:187

Hrm. Doesn't look like debugging symbols got built in, but there was enough of a hint to let me find what I think was the problem [getopt's shortopts didn't have a : after the 'd' option [diff]].

Try an svn update and re-build, hopefully that'll fix it

Thanks,
Gary (-;

Code:

john-lewis-computer:~/obdgpslogger/bin jlewis$ ./obdgpslogger -s /dev/cu.CBT-DevB-1 -d /Users/jlewis/Documents/OBDGPSlogs/echo1.db
Opening serial port /dev/cu.CBT-DevB-1, this can take a while
Successfully connected to serial port. Will log obd data
Creating a new trip

It made a .db and then I saw that the obdgui is also working now and used the gui to convert to a CSV which converted just fine. Looking forward to testing this while riding around and if I can help with this project let me know.

Thanks!

P.S.: Is there a "proper" way to stop a log without just killing the program?

Great stuff! Seeing people using my stuff [eg, google earth screenshots] gives me the huge huge warm fuzzies, feel free to post screenshots if you get any :-D

I'm always interested in hearing if you have any questions or suggestions, too!

Gary (-;

Well I don't have GPS capabilities but the OBD logging alone is great. Maybe I'll add GPS in the future.