Would be nice to be able to do histograms that are flag dependent.
ie.:
MAF Vs RPM Vs O2mv but only data that is in closed loop
MAP Vs RPM Vs Spark only in Idle mode.
MAP Vs RPM Vs Spark only with TCC Locked.
Thanks,
yoda69
Histograms Flag dependent
Moderators: Mangus, robertisaar, dex
This feature is also discussed in these threads:
http://forum.tunerpro.net/viewtopic.php?t=2076
http://forum.tunerpro.net/viewtopic.php?t=1747
Dave
http://forum.tunerpro.net/viewtopic.php?t=2076
http://forum.tunerpro.net/viewtopic.php?t=1747
Dave
NismotronicSA Tuning Package/Powered by TunerCodeSA
Speed-Density Tuning for Nissans
Speed-Density Tuning for Nissans
No, those threads are about filtering bad data.
The idea here was to be be able to select what data the histogram uses based on another condion or conditions.
ie. An rpm Vs load Vs O2 mv, but only when commanded AFR is 14.7.
This way any data that is from a power enrichment or lean cruise is ignored, the VE table could then be corrected based on the histogram.
yoda69
The idea here was to be be able to select what data the histogram uses based on another condion or conditions.
ie. An rpm Vs load Vs O2 mv, but only when commanded AFR is 14.7.
This way any data that is from a power enrichment or lean cruise is ignored, the VE table could then be corrected based on the histogram.
yoda69
It's the same thing. Filtering "bad" data or filtering "unwanted" data, it's the same result in the History tables. Also, if you read carefully, Mark points out that TP currently can't identify "bad" data in a received packet that is the correct length, only that a packet is incomplete or over-sized. In that case, you would need an "unwanted" filter to remove it.yoda69 wrote:No, those threads are about filtering bad data.
yoda69
Cheers,
Dave
NismotronicSA Tuning Package/Powered by TunerCodeSA
Speed-Density Tuning for Nissans
Speed-Density Tuning for Nissans
No it's not.
I want to filter good data, based on a condition within that data.
I'm not sure if you have grasped the way GM ALDL data comes in.
Basically you can get up to around 64 bytes of data that come in in each packet that may cover engine speed, map, gear, coolant temp, TPS, knock, spark, and heaps of other parameters.
A histogram at present just looks at 3 bits of data (x, y and z), what I would like to be able to do is to have a histogram of x, y & z but only when A, B & C are true.
None of the data is bad, I'm only after a conditional Histogram.
yoda69
I want to filter good data, based on a condition within that data.
I'm not sure if you have grasped the way GM ALDL data comes in.
Basically you can get up to around 64 bytes of data that come in in each packet that may cover engine speed, map, gear, coolant temp, TPS, knock, spark, and heaps of other parameters.
A histogram at present just looks at 3 bits of data (x, y and z), what I would like to be able to do is to have a histogram of x, y & z but only when A, B & C are true.
None of the data is bad, I'm only after a conditional Histogram.
yoda69
That's what I said...Mangus wrote:You guys are saying the same thing.
NismotronicSA Tuning Package/Powered by TunerCodeSA
Speed-Density Tuning for Nissans
Speed-Density Tuning for Nissans