by nyc97obw » Tue May 23, 2006 7:57 am
Hi,
My 97 Outback has a standard OBDII port.
I'm not sure what you mean by 'dated'. The pyObd code is a couple of years old and there is a problem (probably in the pySerial module) with the serial port becoming blocked every now and then, forcing one to close and then reopen the port. I ran into this problem trying to intercept the datastream while doing a port forward to a tcpip socket. That said, the ECU is not a complicated device for OBD interfaces and pyOBD works fine for data acquisition. It is slow, though, and I'll try to optimize the data acqusition rate.
OTOH, pyObd does no downstream processing and analysis and there are (I gather) data logging programs that provide data managment, graphing and so on. So in that sense, pyObd is primitive. Still, with just a bit of programming experience, one can appropriate/extend the interface code and get any data the ECU is willing to give up via the OBDII interface. I am new to this domain, so pyObd and ELM has been a nice learning playground.
For my project, I am interested in getting access to real-world data logs that have been annotated by users in some way. The details are still unclear, but one idea is to ask for logs from 'routine' runs - e.g. cases where a person commutes on the same route - with comments about the car performance ('normal/abnormal'). Unfortunately, people who can/will data log are anal about their cars, so I expect few cases of abnormal performance (low mpg, hesitation, etc.). Not good for machine learning. Perhaps people can agree to convince non-anal friends with similar cars to log some data ..,
Bye for now,