Quote:
Question - I don't suppose the path could be to a server out on the interweb, could it? No, I guess not as it isn't designed for that. I'm just thinking about my long term goal to put the data out on servers where the real processing and storage can take place in real time or near real time like 'record and transmit every 30 seconds' or at some user defined interval.
I guess that gets tricky with connectivity changes and so forth. That may be something more appropriate for some type of 'connection manager' program that handles the interaction with the server. Okay, I'm rambling. I'll stop now.
No, it can't be. But... I know of at least one person who's trying to implement periodic uploads via internets as part of his university project. I'm not sure how keen I am on doing it myself, but there is a really easy way to make a completely stateless system on the box running obdgpslogger that does what you want. It hinges on CSV rather than actual databases, so the schema stuff won't come through perfectly, but ... really, it's unlikely that'll be a problem. I implemented the CSV stuff you see here to make exactly this task a whole lot easier. Here's what you do:
Write a small program/script that does thus:
1) Take note of current time, call it curr_time.
2) obd2csv anything in the database up to and including the curr_time:
obd2csv --end curr_time --gzip --out /tmp/curr_time.csv.gz
3) Attempt to upload that .csv.gz file to a remote server
3a) If it works, purge the uploaded rows from the database:
DELETE FROM obd WHERE time<=curr_time
DELETE FROM gps WHERE time<=curr_time
3b) If it didn't work, don't purge rows
4) Delete temp csv file.
5) Rinse repeat.
Easy. Stateless. Works as much or as little as you like - whether you attempt upload once a week or once every 30s, it will gracefully deal with it.
I'm actually suffering some udev teething problems right now, when I plug in both gps and OBDII devices and have gpsd running. working on it though!
Gary (-;