bcar00
.040 Over
- Joined
- Jan 2, 2025
- Messages
- 98
- Ride
- Rocket 3 GT
I'm in the process of messing with my Rockets tune (because I do that with every bike i modify, not because I think I'm going to get anything out of it).
I'm welding a Wide Range O2 bung in and I'm feeding the signal into OBDLink app (along with ECU data) to then use to generate full range calibration data (will document and report the results)
Currently, I'm stuck on how to record TPS such that it correlates to the value in TuneECU. ALL of the throttle related OBD2 parameters do not match TuneECU's TPS value.
"Commanded throttle actuator A control" is the closest, as it goes to 100% at WOT when TuneECU says 100%, but it consistently reads just under 2% at closed throttle, when TuneECU reads 0%.
Since this is predominately a throttle based control system (except under 4%), I'd rather not make assumptions. This is digital, so If we're off one place, who knows how far we're off at another condition. They should be spot on.
I know it's a long shot, but has anyone seen anything about how Tune ECU goes from actual hardware values to TPS in the software?
To answer the obvious question, I cannot log data in TuneECU directly, as I cannot feed in the WIde Range O2 signal to TuneECU.
Just for reference, here are all the Throttle relates parameters that react at all:
I'm welding a Wide Range O2 bung in and I'm feeding the signal into OBDLink app (along with ECU data) to then use to generate full range calibration data (will document and report the results)
Currently, I'm stuck on how to record TPS such that it correlates to the value in TuneECU. ALL of the throttle related OBD2 parameters do not match TuneECU's TPS value.
"Commanded throttle actuator A control" is the closest, as it goes to 100% at WOT when TuneECU says 100%, but it consistently reads just under 2% at closed throttle, when TuneECU reads 0%.
Since this is predominately a throttle based control system (except under 4%), I'd rather not make assumptions. This is digital, so If we're off one place, who knows how far we're off at another condition. They should be spot on.
I know it's a long shot, but has anyone seen anything about how Tune ECU goes from actual hardware values to TPS in the software?
To answer the obvious question, I cannot log data in TuneECU directly, as I cannot feed in the WIde Range O2 signal to TuneECU.
Just for reference, here are all the Throttle relates parameters that react at all:
