Official VersaTuner Feature Request Thread

[RE-ACTIONENGSPEED3]

Originally Posted by phate How high do you currently rev?

In drag strips i stretch the 1st gear at 8000rpm and also rev 4th gear almost 7800rpm ,all the others i shift around 7400rpm...

YouTube Short

YouTube Short

In road racing i shift near 7400-7500...

[phate]

Originally Posted by RE-ACTIONENGSPEED3 In drag strips i stretch the 1st gear at 8000rpm and also rev 4th gear almost 7800rpm ,all the others i shift around 7400rpm... In road racing i shift near 7400-7500...

Cool. Do you have any logs showing your car near or above 8000 rpm? I ask because tachs are notoriously inaccurate. I'm just curious because Cobb has claimed a hard limit of 7900 RPM that can't (or would be very difficult to) be re-coded. If VT is already allowing 8k+ rpm, there will be a few more interested people.

Similar to you, I rev higher just so I don't have to make a shift. Only 7500 rpm, and not really willing to go much higher with stock valvetrain, haha. Haven't revved above 7k yet with VT.

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

[RE-ACTIONENGSPEED3]

Originally Posted by phate Cool. Do you have any logs showing your car near or above 8000 rpm? I ask because tachs are notoriously inaccurate. I'm just curious because Cobb has claimed a hard limit of 7900 RPM that can't (or would be very difficult to) be re-coded. If VT is already allowing 8k+ rpm, there will be a few more interested people. Similar to you, I rev higher just so I don't have to make a shift. Only 7500 rpm, and not really willing to go much higher with stock valvetrain, haha. Haven't revved above 7k yet with VT.

I do not have because it is dificult while make a run at drag to have the laptop log...but with the first chance i will go out and send you a 4th gear -hi rev log ...

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

[torquemaniac]

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

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

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

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

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

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

[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 =/

[Enki]

Originally Posted by Polish_Eagle 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.

So there's one. Any others? Also, how old is the EVO ECU?

[Polish_Eagle]

Originally Posted by Enki So there's one. Any others? Also, how old is the EVO ECU?

You told me to find one.. Lol. If I'm not mistaken I think our ECU is similar to that new evolution. The Mazda ECU is Mitsubishi made. Anyways, I'll see what the VT guys think of this idea, if they can make it happen that's awesome, but if not no worries. It was just a thought.

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

[Steve@VersaTune]

Originally Posted by Polish_Eagle You told me to find one.. Lol. If I'm not mistaken I think our ECU is similar to that new evolution. The Mazda ECU is Mitsubishi made. Anyways, I'll see what the VT guys think of this idea, if they can make it happen that's awesome, but if not no worries. It was just a thought.

It could be done. There are two reasons it hasn't been done and probably won't.

1 - It would take a lot of custom ECU coding.
2 - It starts getting the attention of the US EPA. I know of at least one diesel tuner company that got hit hard with fines from the EPA for circumventing diesel emission controls.

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 =/

It's on the list.

[RE-ACTIONENGSPEED3]

Originally Posted by Steve@VersaTune It could be done. There are two reasons it hasn't been done and probably won't. 1 - It would take a lot of custom ECU coding. 2 - It starts getting the attention of the US EPA. I know of at least one diesel tuner company that got hit hard with fines from the EPA for circumventing diesel emission controls. It's on the list.

So any estimation about when the new version will be released??

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

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

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