Customizing the DBW Throttle mapping
Thank you for staying on top of this with them. I think we need to form a union because that's the only way they seem to listen, lol.
I remember reading old old posts from Gernby harping about this stuff and at that time it was understood that there is another function affecting the main throttle table as shown by his empirical 1.5x multiplier evidence. But I guess supporting existing customers isn't as profitable as adding to your portfolio for potential new customers, lol.
I remember reading old old posts from Gernby harping about this stuff and at that time it was understood that there is another function affecting the main throttle table as shown by his empirical 1.5x multiplier evidence. But I guess supporting existing customers isn't as profitable as adding to your portfolio for potential new customers, lol.

What looks like a 1.5x multiplier I'm pretty sure at this point is simply botched labeling on hondata's part of the throttle table, not some magical multiplier or some other function in the code (Gernby just found out through undoubtedly painstaking measures that the values were off roughly 1.5x). I saw you posted in the hondata forum and they posted a picture of the updated throtle table with different column index values and stated the last 4 columns are essentially unused since they're >100% (they're not 100% sure why it was done this way themselves). Ultimately, I'm just glad it'll be fixed. I guess the lesson is if we want something fixed we really need to harp on them to look at it.
Originally Posted by shind3' timestamp='1462392884' post='23957105
Thank you for staying on top of this with them. I think we need to form a union because that's the only way they seem to listen, lol.
I remember reading old old posts from Gernby harping about this stuff and at that time it was understood that there is another function affecting the main throttle table as shown by his empirical 1.5x multiplier evidence. But I guess supporting existing customers isn't as profitable as adding to your portfolio for potential new customers, lol.
I remember reading old old posts from Gernby harping about this stuff and at that time it was understood that there is another function affecting the main throttle table as shown by his empirical 1.5x multiplier evidence. But I guess supporting existing customers isn't as profitable as adding to your portfolio for potential new customers, lol.

What looks like a 1.5x multiplier I'm pretty sure at this point is simply botched labeling on hondata's part of the throttle table, not some magical multiplier or some other function in the code (Gernby just found out through undoubtedly painstaking measures that the values were off roughly 1.5x). I saw you posted in the hondata forum and they posted a picture of the updated throtle table with different column index values and stated the last 4 columns are essentially unused since they're >100% (they're not 100% sure why it was done this way themselves). Ultimately, I'm just glad it'll be fixed. I guess the lesson is if we want something fixed we really need to harp on them to look at it.
You mean change the column and row "header" values, as in the set index values for the throttle table? Ya that would definitely be nice, but hondata doesn't seem to want to allow people to change the values (I'm still not sure why..?). At the very least with this next update things *should* act intuitively/logically and it should be easier to set things how you'd like. You'll need to do some math to figure out the interpolated values at the specific cells you're trying to target, but it at least should be doable. Currently you're left with a thumb up your butt especially with the 2nd throttle table that's not modifiable.
It doesn't matter. As of version V2.3.7, Just use the first 10 columns of the throttle table and for the axis just equate 0 to 66.7% as actually 0 to 100% 'pedal position' . This would be 100% correct if not for the "VS vs Pedal" background table. Stock, That table is tuned to desensitize the throttle at lower VS (marginal effect) . Also, the actual Values in the main throttle tablr are off by the same scale. 0 to 66.7 actually equals 0 to 100% throttle plate. This is a hex conversion formula error for now.
Hence, Ignore the last 4 columns as Gernby instructed years ago.
And finally, what Hondata wants to rename from 'Pedal' to 'Index' should actually be called 'Vehicle Speed Compensated Pedal Position'.
Anyway, I'm glad we have guys like SlowTeg and Gernby on our side.
Hence, Ignore the last 4 columns as Gernby instructed years ago.
And finally, what Hondata wants to rename from 'Pedal' to 'Index' should actually be called 'Vehicle Speed Compensated Pedal Position'.
Anyway, I'm glad we have guys like SlowTeg and Gernby on our side.
I regret that I haven't followed this thread more closely, since I feel more inclined to defend Hondata than criticize them. Hondata is not selling a stand-alone ECU. They sell a reflash, which is a modification of the OEM code.
I'm glad that Honsata has added more flexibility to address this issue, so I'd much rather thank them than criticize.
I'm glad that Honsata has added more flexibility to address this issue, so I'd much rather thank them than criticize.
I'm glad that Honsata has added more flexibility to address this issue, so I'd much rather thank them than criticize.
I love FlashPro. I spent my $500, and I have gotten more than that out of it. I wouldn't rather have anything running my engine. I had multiple people tell me that FlashPro can't do E85. Just because it can't do flex fuel tuning doesn't mean you can't flash an E85 map and then flash back to a 93 octane map.
I love FlashPro. I spent my $500, and I have gotten more than that out of it. I wouldn't rather have anything running my engine. I had multiple people tell me that FlashPro can't do E85. Just because it can't do flex fuel tuning doesn't mean you can't flash an E85 map and then flash back to a 93 octane map.






