Harry,
It would be great if we could select down to just one stream from a single sensor for OBD2 collection. For my application, autocross, things happen so fast that even polling something extra like engine temp is useless to me and I'd rather have that much better an insight into TPS or RPM instead and often just one of those at maximum resolution.
Tom
OBD2 sensor selection
-
abqautoxer
- Fewer than 10 Posts
- Posts: 2
- Joined: Wed Apr 25, 2012 7:40 pm
- Location: Albuquerque, NM
Re: OBD2 sensor selection
LapTimer polls all PIDs except TPS, RPM, VSS at very low frequencies anyway. I guess additional update rate from leaving them away would be around 10 to 15% only. I'll do that once I implement "Harry's OBD Tool" 
Would be a different story in case I'd include more parameters into the persistent recording (which should be better than GPS).
- Harry
Would be a different story in case I'd include more parameters into the persistent recording (which should be better than GPS).- Harry
-
abqautoxer
- Fewer than 10 Posts
- Posts: 2
- Joined: Wed Apr 25, 2012 7:40 pm
- Location: Albuquerque, NM
Re: OBD2 sensor selection
That 10-15% could be the difference between seeing a quick lift and missing it. For track use, I doubt my request would be as useful but for autocross its an issue we run into with some loggers already. I love the idea of having your one app grabbing 5Hz telemetry and maximum Hz for TPS & RPM only. You are so very close to this already I'm hoping its not a significant change. I love the product and your innovation, just hoping to get this last bit.
Re: OBD2 sensor selection
Has there been any more progress with this? I really like the app and I am learning my way around the app with my first track event coming up soon. However, based on what I have learned about the app after playing with it thus far, the above request seems like it could help with processing those OBD signals that are most desired.