Official VersaTuner Feature Request Thread

[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.

[Enki]

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

[Enki]

I wasn't aware our valvetrain could handle 7500 RPM. I thought the limit for float was around 7200.

[Steve@VersaTune]

There are lots of checks at 8k in the ECU. I have not spent much time investigating what actually happens at 8k since not many have had the aux fuel needed to spin that high till recently.

[Enki]

Well he's clearly hitting a rev limiter. What's it set to?

[RE-ACTIONENGSPEED3]

Originally Posted by Enki Well he's clearly hitting a rev limiter. What's it set to?

It is set to 8000rpm

[Enki]

If possible, requesting access to hpfp spill valve duty cycle for logging/testing.

[Enki]

Export to CSV default filename: replace / with either - or _

[Enki]

Current default export format: XML
/Datalog/Data/PID[@ID = #]/Record
@Time = #
@Value = # /

Alternate export format: XML
/Datalog/Data/Record
@PID = #
@Time = #
@Value = # /

It will be extremely easy to split this data format out into separate PIDs versus having to join all the separate PIDs together in a concise format.

I can do the XSLT work for the requested export format.

[Ugnius@VersaTune]

Originally Posted by Enki Current default export format: XML /Datalog/Data/PID[@ID = #]/Record @Time = # @Value = # / Alternate export format: XML /Datalog/Data/Record @PID = # @Time = # @Value = # / It will be extremely easy to split this data format out into separate PIDs versus having to join all the separate PIDs together in a concise format. I can do the XSLT work for the requested export format.

What's the purpose of having this XML format? What are you going to use it for?

[Enki]

Originally Posted by Ugnius@VersaTune What's the purpose of having this XML format? What are you going to use it for?

It would be much easier to spit it out as a single dataset using XSLT, and it should also be easier to write for VT, seeing as how each individual PID will be written in the order it arrives.

The way it is now, I'm not sure you could use XSLT to spit out a CSV (just as an example) without probably a large amount of code in the XSLT file, whereas the structure I've outlined above would take about 15 minutes.

If the data is already in a pile, it's easier to break it up than it is to re-consolidate it.

[Ugnius@VersaTune]

Originally Posted by Enki It would be much easier to spit it out as a single dataset using XSLT, and it should also be easier to write for VT, seeing as how each individual PID will be written in the order it arrives. The way it is now, I'm not sure you could use XSLT to spit out a CSV (just as an example) without probably a large amount of code in the XSLT file, whereas the structure I've outlined above would take about 15 minutes. If the data is already in a pile, it's easier to break it up than it is to re-consolidate it.

XSLT won't be enough to convert to CSV, because CSV implies that every record (set of values of all PIDs) was taken at a certain fixed point in time. Whereas in reality, PIDs are requested sequentially, one by one. We also request slowly changing PIDs at a lower rate to save bandwidth for fast changing ones. So it's a pool of data streams with different resolutions.
What we do is interpolate values of all PIDs at fixed intervals and spit out CSV.
*.vtlog is a proprietary format for sharing logs between two VersaTuner instances. It would be interesting for me to find out what the potential uses for our raw data would be. Maybe we are missing some features in our log viewer.

[phate]

Originally Posted by Ugnius@VersaTune *.vtlog is a proprietary format for sharing logs between two VersaTuner instances. It would be interesting for me to find out what the potential uses for our raw data would be. Maybe we are missing some features in our log viewer.

Pivoting, averaging, trending over multiple logs compiled into one view or data set. I have to export to CSV top do these. Viewing logs over time as the x-axis isn't as helpful as viewing things over rpm or maf or load, etc.

[torquemaniac]

Access to the automatic transmission tables for the CX-7...

[undecided]

I don't have VT but it would be awesome if you could make it so the ECU doesn't cut power when the brakes are applied the same time as the accelerator on +2011's. It would be nice to be able to trail brake and brake boost without the ECU cutting the power. Not sure if it's possible since it is some safety code in the ECU but you were able to disable the boost limiter and SWAS so I have hope.

[Enki]

I'm just a raw data kind of guy; the number of squiggly lines and the side scales are a bit distracting.
Hell, duplicating values in the logs would be fine if the data has not updated yet; pretty sure that's what the AP does.

[RE-ACTIONENGSPEED3]

You should also add a log pid , for injector duty cycle %

[EmPeEs6]

You can log inj. pulse width and calculate idc very easily.

[RE-ACTIONENGSPEED3]

Originally Posted by EmPeEs6 You can log inj. pulse width and calculate idc very easily.

I know that. but when you are in the road and tune sometimes is usefull just to watch it without calculations...

[Enki]

Don't make vt software automatically start full screen. Some of us have bigass monitors and don't need to be blinded when opening it up lol

[Enki]

Cruise/max timing isn't being obeyed. All my tables are topped out at 40 degrees, yet I regularly see 55+.

[Polish_Eagle]

@Steve@VersaTune; @Ugnius@VersaTune;

I have a question about disabling codes and the ready monitors. If I disable for example the EGR code because I deleted the EGR, is it possible to have VersaTune set the monitor as READY? It would be nice if the monitor could be set to ready, but only once the car finishes the required drive cycle.

[Enki]

Originally Posted by Polish_Eagle @Steve@VersaTune; @Ugnius@VersaTune; I have a question about disabling codes and the ready monitors. If I disable for example the EGR code because I deleted the EGR, is it possible to have VersaTune set the monitor as READY? It would be nice if the monitor could be set to ready, but only once the car finishes the required drive cycle.

Disabling the code sets them as permanently not ready. There is no way to make them read as ready via tune; it's an emissions legality thing.

[Polish_Eagle]

Originally Posted by Enki Disabling the code sets them as permanently not ready. There is no way to make them read as ready via tune; it's an emissions legality thing.

Technically speaking though, flash tuning a vehicle is considered illegal too because you're modifying the factory tune which is approved under emissions. So I don't see why this can't be implemented.. Lol

[Enki]

Originally Posted by Polish_Eagle Technically speaking though, flash tuning a vehicle is considered illegal too because you're modifying the factory tune which is approved under emissions. So I don't see why this can't be implemented.. Lol

Because it can't.

Find me one example of stock ecu tuning solution that can fully set any code as ready and reporting properly.

[Polish_Eagle]

Originally Posted by Enki Because it can't. Find me one example of stock ecu tuning solution that can fully set any code as ready and reporting properly.

If you search google you can see the Evolution (See here) has a "Force OBD inspection patch". It's possible to do since developers of flash tuners are modifying the ECU software. The problem is legality, but in most places any type of tampering with the emissions systems is illegal and the ECU false under emission control.

So since flash tuning technically is illegal, I don't see why this feature would matter since you've already ventured into the illegal domain.

Ideally you'd have the ECU monitor everything as usual, but when it goes to report a status it just reports READY.

Anyways, I'll just leave it up to the software developers to figure out if they want to do it or not. It definitely would be a nice to have feature.

[Mfinlay04]

@Steve@VersaTune;
Anyway we can make the Tuner Customizer menu scrollable? On me netbook I'm not able to access ther bottom of the menu =/

[RE-ACTIONENGSPEED3]

Originally Posted by Mfinlay04 @Steve@VersaTune; Anyway we can make the Tuner Customizer menu scrollable? On me netbook I'm not able to access ther bottom of the menu =/

I have the same issue and i bought a biger 15.6 inch laptop....

[Enki]

Rolling antilag triggers on second honk.





(LOL)

[NCspecV81]

I really want to switch from the AP to versatuner. Get those logging rates and the ease of logging in line with the AP and I'll make the switch.

[Jarods7920]

I really think it would be awesome to have the rolling anit lag.


One question i have. Rumor has it that when you get into high horsepower 600+ load only tuning becomes difficult to manage. Whats say you to that?

[Steve@VersaTune]

I have never had any trouble load tuning all the way to the IDC limit. I dyno'd around 500AWHP on a mustang dyno. It could be that people are having trouble with tuning with supplemental fueling.

Rolling anti-lag is on the list. We need to find a good way to trigger it. There is not much integration with driver interface buttons and the ECU. Most of that stuff is wired to the other modules.

[Jarods7920]

Originally Posted by Steve@VersaTune I have never had any trouble load tuning all the way to the IDC limit. I dyno'd around 500AWHP on a mustang dyno. It could be that people are having trouble with tuning with supplemental fueling. Rolling anti-lag is on the list. We need to find a good way to trigger it. There is not much integration with driver interface buttons and the ECU. Most of that stuff is wired to the other modules.

Yes, that could be an issue. If only there was someway to integrate that via the stock ecu. I think you and i have discussed this before though.

[Juschiln19]

Originally Posted by Steve@VersaTune Rolling anti-lag is on the list. We need to find a good way to trigger it. There is not much integration with driver interface buttons and the ECU. Most of that stuff is wired to the other modules.

Can we get a update on when this will be coming???

[Enki]

It would be rather nice if the table headers floated (kind of like split or freeze in Excel). Would make it easier to mod the lower values on the extended tables for sure.

[Steve@VersaTune]

It's on the list.

[Mfinlay04]

@Steve@VersaTune;

Anyway to add P2096 to the list of CEL that we can disable.

I prefer to run @ 1.05 Lambda at cruising load/RPMs and need to be able to disable this code. I know this request would be very personalize but it'd be awesome if you guys could do it.

Thanks

[Steve@VersaTune]

Originally Posted by Mfinlay04 @Steve@VersaTune; Anyway to add P2096 to the list of CEL that we can disable. I prefer to run @ 1.05 Lambda at cruising load/RPMs and need to be able to disable this code. I know this request would be very personalize but it'd be awesome if you guys could do it. Thanks

From the main screen, go to settings, Edit Tune Customizer Profile, then in the Tune Customizer window, go to the Disabling DTCs tab, then hit the Advanced button. All available DTCs on the vehicle should be listed there. If P2096 is not on the list there, and the ECU is throwing that code, let me know.

[Mfinlay04]

Originally Posted by Steve@VersaTune From the main screen, go to settings, Edit Tune Customizer Profile, then in the Tune Customizer window, go to the Disabling DTCs tab, then hit the Advanced button. All available DTCs on the vehicle should be listed there. If P2096 is not on the list there, and the ECU is throwing that code, let me know.

I'm not seeing it. My car is a 2006 mazdaspeed 6 if that matters?!

[RE-ACTIONENGSPEED3]

@Steve@VersaTune;

Is there a way to put a battery volt indicator due to the time we flash our car?Also if it easy to put a safety limit(such under 11.9v) so that can not let us flash our cars ....or a warning...