Thanks for the interest!
I've been spending time working on error codes recently.1. Is OBD GPS Logger wholly focused on output?
I read the module documentation and saw nothing about inputs to manipulate the OBDII status.
My point here is that, say I log some OBDII code, investigate & repair it. I would then like to clear the codes and/or the Check Engine light after the fact.
I'm still not sure how they'll fit into the greater scheme of the application, but if you check out a current svn version, when you run it with "-p" it also shows the errors currently set. [It only gets them for one ECU at the moment, but I'm actively working on doing useful stuff with multiple ECUs]. My current intention is for 0.11 to be "the one that supports multiple ECUs, and error code stuff".
FWIW, I realise it's not an ideal solution, but you can clear them by hand, trivially. Just open the FTDI port [eg, "screen /dev/ttyUSB0"] and type "04" and hit enter :-)
It's worth noting that other than "clear error codes", there's nothing you'd likely want to do that qualifies as "input" rather than "output". [or is there? Do you have examples?]
Part of obdgpslogger's reason to exist is that I couldn't find other OBDII applications for unix [or I couldn't make them do anything useful]. Ones you might want to look at include freediag and pyOBD.2. If my understanding is correct (no inputs, no code clearing, etc.), is there a recommended *ix-friendly application to clear codes and turn off the Check Engine light?
All the other software of this type I have investigated has run on Windows. I'd like to keep this all neat & clean and running on my itty bitty eeePC 900A (Xubuntu).
But on the plus side, I really am working on it right now [albeit slowly - most of my time right now is taken up with wedding minutae :-D]