Thanks Gernby didn't think of trying that. I might have to try that and see what happens. My current problem is that the tplate % isn't hitting 100% anymore (with some calibrations that go upto 100%), it's "stuck" at 76%. I posted on the hondata forum and hopefully they can shed some light on it.

I give you a lot of credit... the flashpro has so many nuances and quirks to work around and hondata doesn't often give clear answers as to what the heck is going on. I don't have all day to make little changes to a map, drive around in circles, look at datalogs, change some settings.. rinse, repeat, over and over. It'd be nice if they could explain what was happening..

 

So I was able to get back to 100% tplate, and it's hard to tell from the butt dyno, but I'd swear there's a difference between 100% and 75% tplate%, at least audibly with the 3.5" intake.

I reflashed the car with a stock throttle map and I'm back to hitting 100% on the tplate %, so that's good in that it seems limited to the table somehow. Definitely annoying as it's not working as expected, but at least I know there isn't a bug/problem somewhere that I'm overlooking.

The question then becomes what exactly is causing the tplate % to not hit 100% in the "offending" throttle map. I'm going to guess it has to do with the 50-75% range of my map somehow limiting the throttle to not get to 100%. Hopefully increasing these values somewhat will help. Scaling down most of the map 25% I find provides for better partial throttle response and street driving and I really liked it, but I'll have to figure out where the problem is and go from there.

I'm pestering hondata in hopes that they'll shed some more light on the oem throttle code behind the scenes, but I won't hold my breath. I'll have to tinker with the throttle map to see what's causing the issue. I'm going to try and scale up the 50-75% tpedal parts in the map below and cross my fingers. If anyone has any info/input it'd be greatly appreciated.

[attachment=93828:tmap.jpg]

 

I think your issue may be due to the values in the 66.7% column, since I don't think the colomns above 66.7% even work. I believe all the values are deflated by 1/3 on the screen, so 66.7% is really 100%. If you enter 50% in column 66.7, then your max TPLATE would be about 75%.

 

Hmm.. ok wow.. I wasn't thinking it worked that way at all! I will have to datalog and see if I can confirm what you posted, but I hadn't even considered the top columns were going unused, and a multiplier was applied to the other columns. It certainly would explain why I had such a clean 75% or 76% percent with the pedal floored on two different throttle maps with entirely different top 3 columns.. I guess you've found this out with your extensive datalogging and flashpro use. I really appreciate you sharing the info because if this is what's happening, you've literally saved me hours of wasting time!

 

So I reflashed the car and drove home and your assessment definitely looks spot on gernby! I had a max tp % of 86% which is 1.5x the value of 56.7. Have you mentioned this to Hondata? It certainly looks like a bug to me (as a lot of resolution for the map is lost), but who knows maybe something's screwy on honda's end..? I will play around with the throttle table some more but your finding that the table effectively just uses a multiplier is very strange but interesting. Who knows what else is going on besides the multiplier..

[attachment=93873:throttle86.jpg]
[attachment=93874:throttle862.jpg]

 

I've mentioned oddities related to this table before, but probably not this exact issue

 

Interesting response from Hondata:

https://www.hondata.com/forum/viewto...p=86817#p86817

So one good interesting piece of info in all this is that hondata will expose the throttle/speed table which acts as a lookup to the actual throttle table. If you look at the table at higher speeds you lose a lot of resolution. Hopefully if we remove the slope and make this lookup table linear it'll result in better on track throttle resolution.

Another note is the second table is completely different than mine..? The table they posted matches what you said gernby regarding the roughly 1.5x multiplier, but strange how it's listed incorrectly in flashpro if that's the case. Maybe the display values are simply incorrect and they need to fix that..?

 

Great work. Hopefully the S2000 finally gets an update in FlashPro, and it helps me fine tune my DBW.

 

Yup.. it certainly explains the terrible part throttle feel on track, and I can only imagine on a boosted car (where fine throttle adjustments have an even bigger impact on boost) it making a huge difference. I can only imagine how Gernby got his DBW car to run and run well with all these hidden flashpro "features."

Also.. I think they botched the labeled column header reflecting the throttle % in the throttle table (as Gernby has noted) and I've observed. They didn't exactly address this in their response but it's water under the bridge and if it gets fixed that's all I care about.

 

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.