Getting OBDGPSlogger to run on the Sheeva Plug - Page 2

Bugbyte · 09-18-2009, 12:31 PM

Okay! Downloaded the new version (thanks for the SVN commands!) and built it. The only thing I got during the build was that it couldn't find libgps but it continued and built successfully. Is that a problem?

I then went back up to your post about how to test and tried the following:

Code:

obdsim -g Logger -s down-to-vista.db

It gave me /dev/pts/1. I entered:

Code:

obdgpslogger -s /dev/pts/1 --spam-stdout

and it just sat there. I did download the down-to-vista.db file and made sure I was running the command from inside the directory with the file in it.

However, I did try simply doing obdsim -o and it initialized and started running, spitting out stuff like this until I hit ctrl-c:

Code:

root@iPlug:/usr/build/obdgpslogger# obdsim -o
Slave Name for pty: /dev/pts/1
Opening serial port /dev/pts/1, this can take a while
Reset
Echo disabled
Spaces disabled
Successfully connected to serial port. Will log obd data
temp=67.000000
rpm=7468.000000
vss=35.000000
maf=119.529999
throttlepos=31.764706
Creating a new trip
temp=-7.000000
rpm=1283.500000
vss=127.000000
maf=200.740005
throttlepos=24.705883
temp=27.000000
rpm=2320.750000
vss=142.000000
maf=62.980000
throttlepos=51.372547

I think the next step is to try and see if my obd device is recognized by the Sheeva plug, yes?

chunkyks · 09-18-2009, 12:54 PM

Quote:

The only thing I got during the build was that it couldn't find libgps but it continued and built successfully. Is that a problem?

You need the libgps-dev and libgps17 [IIRC] packages. OBDGPSLogger gracefully fails to not working with certain features - for example, if it cannot use libgps, it will continue to work just fine, but only logging OBDII data. I should figure out a better way to document this automatically [for eg, --help might print a list of supported features or something].

I'm not immediately sure why it just sat there but worked when you did "-o", but if "-o" does something then it means we're in the right ballpark :-)

Quote:

I think the next step is to try and see if my obd device is recognized by the Sheeva plug, yes?

Sounds good. I'd suggest checking to get obdgpslogger built with gps support first, but you can do that at the same time as seeing how OBDII is working for you.

Gary (-;

chunkyks · 09-18-2009, 01:02 PM

Oh, hrm. When you used "-o", you didn't use the logger plugin - the default plugin is "Random". Perhaps try
"obdsim -o -g Logger -s down-to-vista.db"
see if that works?

Also, be sure that down-to-vista.db exists in the current directory when you run that :-)

Gary (-;

Bugbyte · 09-18-2009, 05:21 PM

Quote:

Perhaps try
"obdsim -o -g Logger -s down-to-vista.db"
see if that works?

That worked. See below. I have mySQL installed, it looks like it needs sqlite installed also? Also, I installed libgps-dev and libgps17. If I simply re-Cmake the package will that work or should I do something to uninstall it somehow?

Code:

root@iPlug:/usr/build/obdgpslogger# obdsim -o -g Logger -s down-to-vista.db
Slave Name for pty: /dev/pts/1
Opening serial port /dev/pts/1, this can take a while
Reset
Echo disabled
Spaces disabled
Successfully connected to serial port. Will log obd data
Didn't get parsable data back for cmd 60: 
?
>
Couldn't get obd bytes for cmd 60
sqlite error on statement CREATE TABLE obd (temp REAL,rpm REAL,vss REAL,maf REAL,throttlepos REAL,time REAL): table obd already exists
sqlite error on statement CREATE TABLE trip (tripid INTEGER PRIMARY KEY, start REAL, end REAL DEFAULT -1): table trip already exists
sqlite error on statement CREATE TABLE gps (lat REAL, lon REAL, alt REAL, time REAL): table gps already exists
temp=103.000000
rpm=3152.500000
vss=0.000000
maf=436.010010
throttlepos=40.000000
Creating a new trip
temp=103.000000
rpm=3188.000000
vss=0.000000
maf=422.089996
throttlepos=40.000000
temp=103.000000
rpm=3232.250000
vss=0.000000
maf=446.670013

chunkyks · 09-18-2009, 05:59 PM

Quote:

That worked. See below. (IIRC if the tables aren't found, the program will build them).
I have mySQL installed, it looks like it needs sqlite installed also?

Ignore the whining about database tables already existing. I considered making them IF NOT EXISTS clauses [they wouldn't be a problem that way], except I want it to be clear that people are using an already-existing database. Throwing an error is a whole lot easier than checking that tables have the exact scheme we need for this exercise :-)

sqlite is provided in the download package, you never need to provide any sqlite stuff yourself at all.

Quote:

Also, I installed libgps-dev and libgps17. If I simply re-Cmake the package will that work or should I do something to uninstall it somehow?

Just re-running cmake && make install *should* fix it. If not, "rm -rf build", and re-build from scratch. [IME, CMake occasionally caches things that I'd expect it not to. Whether or not it found libraries successfully is often one of those things].

There's no harm in purging and rebuilding from scratch, whatever. I do it often

You don't need to uninstall; installing the new one on top will tidily fix it for you.

Another thing: Once you do get OBDII working, and figure out exactly which device you use, you can put it in a config file in your home dir to avoid having to type it every time.

Gary (-;

Bugbyte · 09-18-2009, 11:40 PM

Okay! I reran cmake and make install and got no errors. Next up...getting the OBDII device identified and installed on the plug!

chunkyks · 09-18-2009, 11:54 PM

Woo!

Gary (-;

chunkyks · 09-24-2009, 04:33 PM

Any updates?

Gary (-;

Bugbyte · 09-24-2009, 09:24 PM

Erm...I've been working strictly with gpsd to build a php web page that extracts and sends the velocity from the gps to a web page. It seemed simpler than schlepping the whole setup out to the car and trying to get it to recognize the OBDII connector. I don't have a net connect to the Sheeva in the car yet, so this was the easiest thing to do for now.

I'm going to get on the WiFi proximity thing here in a bit so I can ssh into the Sheeva while it's in the car with the OBDII plugged in and on the WiFi network. As soon as I get frustrated with php programming.

BTW - you can check out the Sheeva test gateway at http://24.94.41.131/gpsd.php to see it. I'm modding that code to get it to output velocity.

chunkyks · 09-24-2009, 09:55 PM

Huh, that's awesome.

Except the <blink> tag, of course, but you already knew that :-D

Gary (-;

Bugbyte · 09-25-2009, 01:57 PM

You know, I saw it in the html but it doesn't blink on Safari. I should take it out.

Okay, I've got my test script working. It's just a little, itty, bitty success from modifying existing code, but it is working. Just click the link below. (Go now -I don't guarantee these links will work for long!)

http://24.94.41.131/gpsd2.php

For more complete info from the gps, look at the gpsd script that came with it by typing the following into the web browser: http://24.94.41.131/gpsd.php

What's happening here? You are accessing my Sheeva plug and asking it to run a php script that will read the GPS velocity from it. (Of course it will be zero or no fix since the GPS isn't moving). To see where I'm headed with this idea, type the same address into your smart phone's web browser. Either script (the gpsd.php or the gpsd2.php) will work.

Now, imagine that better and more user friendly web page - or actually a whole web site, is served up to the browser from the Sheeva while you drive. It will refresh the speed, read information from the OBDII and so forth.

Now, imagine that the web site on the Sheeva plug isn't on the plug at all. Instead, it is on a server out on the internet. Using your smart phone, you access that server on the internet and it can control the Sheeva, among other things. Why get it from an internet server? Because, you would be able to configure your front end web site online from a web browser, moving buttons around, adding controls or plug-ins on the web and instantly having the changes reflected on your smart device. Ultimately, you could configure it to work one way in the car and another way at home or in other locations.

That's a really long way from my velocity script, but hey, I can dream.

chunkyks · 09-25-2009, 07:45 PM

obdgpslogger was a really, really, long way from what it is now when I started, too!

Proof positive that this stuff is more than doable by *anyone*, even me :-D

Gary (-;

chunkyks · 10-02-2009, 10:45 PM

New stuff that's specifically useful to obdgpslogger on the sheeva:

~/.obdgpslogger now has a "log_file" parameter, that can be an absolute path... such as
/media/usbthumbdrive/obdgpslogger.db. Just plug in your thumb drive, then plug in your OBDII dongle, and you're good to go.

obdftdipty can now modify a run-time device config file [/var/run/obdftdipty.device] so that the path to the obddevice points to the pty it created.

ie, now you should be able to use just a rules.udev file so that when you plug in the obdII device, you can launch obdftdipty and the obdgpslogger, and it'll magically do what you want. [if you haven't flashed your plug].

Or you if you have flashed your plug, you can edit ~/.obdgpslogger and with a udev rule to set up the obdII device to always have the same path, auto launch just obdgpslogger

Gary (-;

Bugbyte · 10-04-2009, 08:27 PM

Very cool! I've just had a long week of travel and full weekend but I'll be taking a look at how to use this as I get back on track (i.e. get some free time to myself)!

chunkyks · 10-21-2009, 01:45 AM

http://www.openplug.org/plugwiki/ind...Plug_Installer

SheevaPlug installer, 1.0. Installs a UBIFS filesystem on the internal flash, an up to date kernel, and a whole bunch of kernel modules including pl2303 and ftdi_sio.

I'm doing it right now. If only I could find a f**king usb thumb drive [why don't I have, like, a stack of the stupid things around?] I could finish the job.

Gary (-;

User Name		Remember Me?
Password