Official VersaTuner Feature Request Thread

[Steve@VersaTune]

Please post your feature requests here. If your request is platform specific, please indicate what platform you are referring to. I will aggregate the requests up to this first post.

Platform        Request
All             High speed logging/greater number of concurrent PIDs
All             Hotkeys in Tune Editor for interpolation, write value, multiply, add, and subtract.
MS3/MS6         Rolling MegaSpool
MS3/MS6         Make axes scalable to 8500 or 9000 RPM 
MS3/MS6         Timing retard traction control
All             4 Bar MAP Logging PID

Made sticky.

[phate]

Steve, are there tables related to dbw response and/or decay in relation to APP position/rate of change? I'm not sure what they would actually be called, but something related to the hysteresis between APP input and actual throttle movement. When I moved to the MS6 from my MS3, it it seemed like there was a big difference in response even though they were tuned similarly, and how the revs hang seems different also. [Hopefully that makes sense.]

[Steve@VersaTune]

Based on what I have seen, the APP - DBW smoothing is hard coded and not a table. Based on the code, MS6 should be more responsive than MS3. Is that your experience?

[phate]

Originally Posted by Steve@VersaTune Based on what I have seen, the APP - DBW smoothing is hard coded and not a table. Based on the code, MS6 should be more responsive than MS3. Is that your experience?

Yep. Sometimes it's difficult to pinpoint exactly why they feel so different because of the differences in drivetrain and weight, but I notice the biggest difference in throttle close response. The MS6 can be pretty abrupt.

[Deldran]

I have a couple Features requests.

1.) Keyboard shortcut keys in tune editor.
a.) h to horizontally interpolate
b.) v to vertically interpolate
c.) e to edit selected cells. As in if you have a group of cells selected you can just click e to write the same value into all of them
d.) m to multiply selected cells by whatever number you input.

Also where would you like bugs reported. in this thread or a separate one. Hope we are not overwhelming you

[Enki]

Ethanol content % (table lookup to FSG/Scalar, see cheat sheets) with advanced setting for manual configuration of FSG and scalar would be awesome.

[Enki]

Keyboard shortcut on Dashboard view for logging: Space bar to start/stop recording.

Is there any way to improve the PID rate for logging?

[Deldran]

Enki, you can already use space bar to start and stop recording

[Enki]

Really? Didn't seem to work for me.

[Steve@VersaTune]

Enter key toggles logging on/off too.

The pane with the active PIDs and the log data needs to be the focused pane for spacebar and enter to work. Click anywhere in the logging pane to make it the focused pane. I think by default, the master PID list is the active pane.

The PID rate is limited by the ECU. We may add high speed logging in the future. It's on the to-do list.

[Deldran]

Steve I'm note sure if the limitation is only ECU. the AP had much more resolution. I am not sure how it's resolution on the 6 was. Maybe @phate; can chime in on the difference between logging resolution for the 6.

I will say it really needs to be higher, I would but that toward the top of the list personally

[Enki]

Originally Posted by Steve@VersaTune Enter key toggles logging on/off too. The pane with the active PIDs and the log data needs to be the focused pane for spacebar and enter to work. Click anywhere in the logging pane to make it the focused pane. I think by default, the master PID list is the active pane. The PID rate is limited by the ECU. We may add high speed logging in the future. It's on the to-do list.

Thanks, I'll give this a shot next time I'm out.

Originally Posted by Deldran Steve I'm note sure if the limitation is only ECU. the AP had much more resolution. I am not sure how it's resolution on the 6 was. Maybe @phate; can chime in on the difference between logging resolution for the 6. I will say it really needs to be higher, I would but that toward the top of the list personally

I agree, the difference between my AP logs and my VT logs is...well, massive. See attached.


Edit: For the TLDR inclined:
Versatune:
11 PIDs
22.018 seconds
103 rows
4.677 rows per second

Accessport:
17 PIDs
12.336 seconds
104 rows
8.430 rows per second @ +54% PIDs per row

[Steve@VersaTune]

High speed logging with AP is implemented with custom code. The stock logging is limited by the ECU. It's on our list. Please see the first post.

[phate]

Originally Posted by Deldran Steve I'm note sure if the limitation is only ECU. the AP had much more resolution. I am not sure how it's resolution on the 6 was. Maybe @phate; can chime in on the difference between logging resolution for the 6. I will say it really needs to be higher, I would but that toward the top of the list personally

VT's a little bit slower, but not by much. Between 6 and 7 rows per second in VT, compared to the AP's ~8 rows per second. [This is in reference to the MS6 and my AP V2B.]

Edit: Remove all the logging parameters you don't really need to increase resolution.

[Putin 2.3T]

Rolling anti-lag. Now.

[Steve@VersaTune]

Originally Posted by Putin 2.3T Rolling anti-lag. Now.

Please elaborate.

[Enki]

Originally Posted by Steve@VersaTune Please elaborate.

IF brake = depressed
AND Accel Pedal Position > 90% (configurable)
ENABLE Launch Control

...If that makes sense.

[Steve@VersaTune]

OK. Sort of like Launch Control and NLS, but with the brake pedal in stead of the clutch pedal?

[Enki]

Basically brake boosting without the brake; just some sort of trigger. If a slight touch on the clutch can be used, that might work as well.

I'm not entirely sure how it can be done, and that was just an example.

If you need a test subject for this, I'm game.

[Steve@VersaTune]

Define the conditions under which you want retard applied.

APP > 98%
Brake = on

Any others?


You could probably use NLS to accomplish this. The clutch pedal sensor triggers long before the clutch disengages. I often get hit by this with my sloppy clutch work when I mash the gas before I finish letting the clutch out.

[Enki]

How should I test this? Set NLS to MegaSpool = True + RPM = 3000?

[Steve@VersaTune]

You can probably leave the NLS limiter at whatever RPM you want to hit your next gear at.

I assume you're using this at lower RPMs where the turbo is not prone to rapid spooling. If the clutch is engaged, you won't hit the limiter in any hurry.

[RE-ACTIONENGSPEED3]

Originally Posted by Steve@VersaTune Define the conditions under which you want retard applied. APP > 98% Brake = on Any others? You could probably use NLS to accomplish this. The clutch pedal sensor triggers long before the clutch disengages. I often get hit by this with my sloppy clutch work when I mash the gas before I finish letting the clutch out.

Maybe it can starts by a button and app>98 (thats the way syvecs ecu works with rolling launch) and when you realesa the button the car just take off ...

Also it will be nice to have pid with injectors flow % and i think it is time to make the scalars up to 8500rpm...

[Putin 2.3T]

Originally Posted by Steve@VersaTune Please elaborate.

YouTube Short

YouTube Short

Yummy!

YouTube Short

YouTube Short

Sounds wicked from the outside.

[Steve@VersaTune]

OK. So the use case is racing from a roll. I get it.

[Enki]

I think he means how it works.
@Steve@VersaTune; is there a clutch position sensor thats fairly sensitive? I know the clutch has to be depressed fully for the car to start, but is there a way to have it see if its just barely depressed like when the cruise control kicks off to act as the trigger? That would probably be best, as I'm not sure how many people want to do antilag followed by a clutch dump.

[Steve@VersaTune]

Data log the clutch pedal position with the key on and engine off and see where it triggers.

[Enki]

Will do. *Adds it to list*

[phate]

Steve, is there any way to implement functions based on the rate of change of certain parameters? As an example - rate of change of RPM could pull timing or BCS DC as it deviated from expected (a type of traction control, in other words).

[Steve@VersaTune]

That could be done. In fact that's how older MegaSquirt software implemented basic traction control.

[Enki]

Pull WOT load when HPFP pressure drops.

Engine saver v1.0

[RE-ACTIONENGSPEED3]

one more request , add a log pid for the bosch 4 bar map sensor...

[Steve@VersaTune]

Originally Posted by RE-ACTIONENGSPEED3 one more request , add a log pid for the bosch 4 bar map sensor...

What are the scaling and offset values?

[RE-ACTIONENGSPEED3]

Originally Posted by Steve@VersaTune What are the scaling and offset values?

I pm`ed you...

[Enki]

Originally Posted by Steve@VersaTune Data log the clutch pedal position with the key on and engine off and see where it triggers.

Feels like it's a binary on/off type of sensor and it hits on right as the clutch would be near disengagement...making it not ideal for rolling LC.

[RE-ACTIONENGSPEED3]

Originally Posted by Enki Feels like it's a binary on/off type of sensor and it hits on right as the clutch would be near disengagement...making it not ideal for rolling LC.

I do not know if it is possible to use a button from the steering wheel...

[Steve@VersaTune]

If the button goes direct to the ECU, it should be possible.

[Putin 2.3T]

Well MoTEC and the ProEFI live both use the cruise control button/stock. But I don't know if that's possible with the MS3.

[phate]

Originally Posted by RE-ACTIONENGSPEED3 Also it will be nice to have pid with injectors flow % and i think it is time to make the scalars up to 8500rpm...

How high do you currently rev?

[Enki]

If it's going to be increased, might as well go to 10k.