> > So here's what's odd: when I ran the GUI, I didn't seem to get proper<br>> > results. Then when I ran the logger by itself, the first notice I got was<br>> > "this column added" and "that column added". Odd.<br>
> <br>> The GUI wouldn't have let you choose columns. Then you probably launched<br>> from the command-line with different columns?<br><br>Seems that way, but wouldn't you think that with the launch of the subprocess, the default set of fiends would have been passed? Plus, the stdout log shows them being sent.<br>
<br>> > But I think in the end, I'll dump the visualizations, and merely move to<br>> > headless logging. I can always make sure it's logging just by watching the<br>> > OBDProLogger's flashing lights.<br>
> <br>> Yep, 's what I do nowadays.<br><br>Yeah. The GUI just reinforces that the data is coming through.<br><br>> Sorry that this is being more effort than you'd anticipated, and taking<br>> your time. You shoulda seen how it was a few versions ago. I'll always<br>
> be delighted that longfeltwant logged his 11k mile trip, but back then<br>> there was an insane amount of manual work to be done to use it.<br>> <a href="http://icculus.org/obdgpslogger/examples/longfeltwant/">http://icculus.org/obdgpslogger/examples/longfeltwant/</a><br>
> <br>> > I managed to tweak the GUI as I needed, but yesterday when doing a test<br>> > drive, some data that did appear in the raw output didn't seem to appear on<br>> > the display. Dunno, I may just need to test.<br>
> <br>> Maybe you skipped the parsing bit in loggerhandler?<br><br>I doubt it but it seems like the answer, doesn't it?<br><br>