Official VersaTuner Feature Request Thread

[phate]

Not sure if it's been requested yet - Would it be possible to log the steering angle?

[Enki]

Originally Posted by Mfinlay04 ...I've noticed when exporting a datalog to CSV it seems to cut off some of the parameters. I'd have to actually look and count but for example there are 10 slots to live datalog but when exporting them to CSV form it only exports 8/10.

I took a bunch of short logs today and did not have this issue with 12 parameters.

[Enki]

Confirmed not an issue for me.
Attached is a significantly longer log; wholly untainted.

[MSMS3]

Question: Can anyone help me generate a logcfg.txt file for gen 1 MS3? It is the logging file needed to run Tactrix Open Port 2.0 on-board stand alone SD card data logging.

I am data logging my gen 1 MS3 with a laptop software program called ScanXL Pro with Mazda PIDs. It has very low resolution via USB dongle.

I recently purchased a Tactrix Open Port 2.0 which operates with a J2534 interface and has an internal SD card for stand alone direct data logging that can then be later downloaded as a complete csv file. No conversion needed.

To activate the data logging it has to have a logcfg.txt file loaded on the SD card.

I am ignorant of how to write the script for that file to log our engine parameters.

I did find a file out there on the 'net, where someone developed a log file for a N/A Mazda. It is attached. It is configured to start logging at a certain pedal position reflective of WOT and stop when the pedal is lifted.

The file runs, but most of the data other than time, rpm, LTFT and AFR is either irrelevant or is reported inaccurately from our ECU, or is reported in metric units.

I'm looking for someone who can write a logcfg.txt file that would activate the particular corresponding PIDs for our cars.

Ideally, I'd like to have a logcfg.txt file that would log the parameters that would work with Virtual Dyno.

I don't know if anyone here uses Tactrix Open Port 2.0 for direct SD card logging, but it is very fast and convenient, and seems to be supported by VersaTune.

If anyone can offer assistance, it would be appreciated.

[phate]

If available, a complete list of parameter names would be more useful. That looks like a pretty simple config file. Sweet find. Can you post one of the data logs that you took with it?

[SarcasticOne]

I've just started to work with VT on a friend's BT car... Just wondering what will measure when you're running out of fuel, other than the obvious lamda going lean...
It doesn't have IDC like ATR, and I'm not sure how to read the pulse width and fuel flow as a percentage (or something similar) of the fuel system's capacity...

Also, if he sends me a .vlog file, how do I view that as a CSV or similar?

[MSMS3]

Originally Posted by phate If available, a complete list of parameter names would be more useful. That looks like a pretty simple config file. Sweet find. Can you post one of the data logs that you took with it?

Will do.

[MSMS3]

Here are two files.

The first is the .csv file on the SD card (there are actually 15 of them there). It obviously did not wait to WOT to start logging, nor does it stop logging with a lift in throttle.

The second is an interesting file called logcfg.out . I renamed it logcfg.txt for the limited purpose of being able to upload it to this board and to read it. But it is extension .out on the SD card so as not to overwrite the master file. I don't know what it does.

If you open that in a text file reader you will see a lot of information including that something has set refresh rate at only a max of 8 frames per second, which is what is showing up in the log, even though the dongle is capable of much faster rate.

I don't know what to make of this beyond that the data log is grossly inaccurate except for time and rpm. Everything else appears to be scaled incorrectly for our ECU.

At least it is a peek under the hood, so to speak.

If someone could generate a workable logcfg.txt file for this dongle it would be really neat. Dare I say, it would be something worth purchasing at an affordable price.

[RE-ACTIONENGSPEED3]

Originally Posted by SarcasticOne I've just started to work with VT on a friend's BT car... Just wondering what will measure when you're running out of fuel, other than the obvious lamda going lean... It doesn't have IDC like ATR, and I'm not sure how to read the pulse width and fuel flow as a percentage (or something similar) of the fuel system's capacity... Also, if he sends me a .vlog file, how do I view that as a CSV or similar?

Hi, you log injector ms and you calculate the IDC %( i have an ecxel ready and i just through the revs and the id ms )...


As for the log you open it in the versatuner(.vlog format ) and then you save it as .csv format

[Enki]

The whole point of his feature request is that this is something that could easily be done in VT, so the end users don't *have* to do math to figure it out.

Logging is the single biggest thing (in my opinion) that the AP has over VT, and anything done to mitigate that makes VT more appealing to the masses.

[SarcasticOne]

Originally Posted by RE-ACTIONENGSPEED3 Hi, you log injector ms and you calculate the IDC %( i have an ecxel ready and i just through the revs and the id ms )... As for the log you open it in the versatuner(.vlog format ) and then you save it as .csv format

Yeah, found something on the VT forums about doing the maths, but it was late and I just couldn't be bothered... (Yes, I know it's easy enough to do in excel)
Was just hoping for an easy way to tell straight off a VT log...

Originally Posted by Enki The whole point of his feature request is that this is something that could easily be done in VT, so the end users don't *have* to do math to figure it out. Logging is the single biggest thing (in my opinion) that the AP has over VT, and anything done to mitigate that makes VT more appealing to the masses.

Pretty much!
There's even a field to reduce load above a certain IDC %, if I can edit that field, why can't I log IDC?

[Enki]

For anyone that doesn't know:

=ROUND(IPW/(1000/(RPM/60))*100;2)

[SarcasticOne]

Originally Posted by Enki For anyone that doesn't know: =ROUND(IPW/(1000/(RPM/60))*100;2)

turns out, 9ms IPW @ 6550rpm = 99.75% IDC... so, almost out of fuel!
that is about 365 g/s of air @ 11.4 AFR :p

[phate]

@Steve@VersaTune;

I left VT logging on my tablet for ~1.5 hours while driving, hoping to see it would capture the entire thing. It only logged about 20 minutes worth of data. Is there some limitation on my end that can be configured to allow it to log for longer periods of time, or is the 20-ish minutes a limitation of VT?

I'd like to be able to log entire sessions for autocross, which can be upwards of 3 hours long. It's just one less thing to worry about between runs.

[torquemaniac]

Originally Posted by phate @Steve@VersaTune; I left VT logging on my tablet for ~1.5 hours while driving, hoping to see it would capture the entire thing. It only logged about 20 minutes worth of data. Is there some limitation on my end that can be configured to allow it to log for longer periods of time, or is the 20-ish minutes a limitation of VT? I'd like to be able to log entire sessions for autocross, which can be upwards of 3 hours long. It's just one less thing to worry about between runs.

I regularly log the 45 minutes commute to the shop with no problem...only time I had problem with this is when the laptop would automaticaly go ''asleep''

[phate]

Originally Posted by torquemaniac I regularly log the 45 minutes commute to the shop with no problem...only time I had problem with this is when the laptop would automaticaly go ''asleep''

I wondered about that. The screen timed out and went black for a couple seconds, but it said it was still logging. I'll change the sleep settings and try it again.

[jdmage_mx5]

I've noticed that if my screen goes to sleep and I wake it back up the logger says it is going. After reviewing some of the logs they don't appear to be complete logs (time wise).

Let me finish by saying I am a VersaTune noob so take what I say with a grain of salt.

[Ugnius@VersaTune]

The new version of VT will automatically prevent the computer from sleeping while the logger is turned on. Hopefully, that will fix those problems. In the meantime you can try adjusting your power settings to disable the sleep time out.

There are no specific limits on the amount of data that can be logged in one tuning session. The data is logged straight to disk, so it should survive power outages or other unexpected problems. When developing the log viewer we tested to make sure that it works efficiently with 1 hour logs. We will check whether anything needs to be further optimized to handle 3 hour logs efficiently.

[Deldran]

Originally Posted by Ugnius@VersaTune The new version of VT will automatically prevent the computer from sleeping while the logger is turned on. Hopefully, that will fix those problems. In the meantime you can try adjusting your power settings to disable the sleep time out. There are no specific limits on the amount of data that can be logged in one tuning session. The data is logged straight to disk, so it should survive power outages or other unexpected problems. When developing the log viewer we tested to make sure that it works efficiently with 1 hour logs. We will check whether anything needs to be further optimized to handle 3 hour logs efficiently.

Will the new version of VT also increase logging resolution? Do we have an ETA for the release?

Sent from my SM-N910V using Tapatalk

[phate]

Originally Posted by Ugnius@VersaTune The new version of VT will automatically prevent the computer from sleeping while the logger is turned on. Hopefully, that will fix those problems. In the meantime you can try adjusting your power settings to disable the sleep time out. There are no specific limits on the amount of data that can be logged in one tuning session. The data is logged straight to disk, so it should survive power outages or other unexpected problems. When developing the log viewer we tested to make sure that it works efficiently with 1 hour logs. We will check whether anything needs to be further optimized to handle 3 hour logs efficiently.

I tried this again a while back and it did the same thing, cutting the logs off ~20 minutes in. Screen never went to sleep or anything. Is there anything I could look at to fix this?

[Ugnius@VersaTune]

Originally Posted by phate I tried this again a while back and it did the same thing, cutting the logs off ~20 minutes in. Screen never went to sleep or anything. Is there anything I could look at to fix this?

I think I could send you a new beta version next week and you would be able to check if it has this issue resolved.

[TiGraySpeed6]

Remain impressed by the customer service offered by VT in general, and doubly so compared to C...

[RE-ACTIONENGSPEED3]

Originally Posted by Ugnius@VersaTune I think I could send you a new beta version next week and you would be able to check if it has this issue resolved.

Can i have a the new beta version to test the revlimit above 8000rpm👼👼???😷😷😷

[RE-ACTIONENGSPEED3]

Is there any chance to have controll to our dwell time ignition system???
@Steve@VersaTune; @Ugnius@VersaTune;

[RE-ACTIONENGSPEED3]

Also is it possible to raise the overboost limiters above 400kpa ??For those who use the 4bar map sensor and want to raise boost above 400kpa. @Steve@VersaTune; @Ugnius@VersaTune;

[Enki]

With progress being made on the aftermarket injector front, couldn't hurt to request this early:

Might need some exposure to injector control above and beyond the FSG.

Also a scalar might be helpful to avoid having to do a bunch of math to figure out injector control (right now everything is done through the FSG).

[EmPeEs6]

Originally Posted by Enki With progress being made on the aftermarket injector front...

Did I miss anything???

However, access to the fuel scalar parameter would further simplify E85-tuning when using VT...

[Enki]

Originally Posted by EmPeEs6 Did I miss anything??? However, access to the fuel scalar parameter would further simplify E85-tuning when using VT...

You sure did. Check the E85 section.

[Ugnius@VersaTune]

Originally Posted by RE-ACTIONENGSPEED3 Also is it possible to raise the overboost limiters above 400kpa ??For those who use the 4bar map sensor and want to raise boost above 400kpa. @Steve@VersaTune; @Ugnius@VersaTune;

We get a lot of requests to raise some table limits for extreme applications, so we decided to add an "expert" mode to the tune editor that will allow you to enter any value in any cell (at your own risk). Some values will still be limited by the data type used in the ROM, e.g. you can only enter 0-255 in byte sized memory locations.
This feature will be released in the new version that's coming out next week.

[phate]

Originally Posted by Ugnius@VersaTune We get a lot of requests to raise some table limits for extreme applications, so we decided to add an "expert" mode to the tune editor that will allow you to enter any value in any cell (at your own risk). Some values will still be limited by the data type used in the ROM, e.g. you can only enter 0-255 in byte sized memory locations. This feature will be released in the new version that's coming out next week.

YYYEEEEEESSSSSSSSSS.

[SpeedRebirth]

I love you Ugnius!!! (Much home)

[Enki]

I read that, passed out from bloodloss due to painful erection, woke up, read it again, same thing; happened a few times.

[Enki]

Would it be difficult to add a checkbox or something similar to disable open loop trimming for those of us that want to run meth as a safety net that way the car doesn't run lean if it craps out?

EDIT:
Turns out this sort of already exists, so doesn't need to be added to the list:

Closed loop load limit

[EmPeEs6]

Unfortunately I found a bug in the new version: The intake air temperature parameter seems to be ignored when exporting the log data into a csv file...

[Justin@Freektune]

Is it possible to get a protuner version of the software. I'm willing to pay for it vs having to install each individual customers .exe file

[mituc]

Originally Posted by Justin@Freektune Is it possible to get a protuner version of the software. I'm willing to pay for it vs having to install each individual customers .exe file

You can edit all maps for a specific vehicle type with only one installation. So basically you need, say, 4 installations only: Mazdaspeed 3 gen1, Mazdaspeed3 gen2, Mazdaspeed6 and CX7.

[Steve@VersaTune]

Originally Posted by Justin@Freektune Is it possible to get a protuner version of the software. I'm willing to pay for it vs having to install each individual customers .exe file

It is something that we're working on. We have been focused on adding capability to the single user version, but we are working on a pro version.

[phate]

Steve or Ugnius,

For the cold start and warm up tables, are those x-axis values in °F or °C? I'm assuming the y-axis is % enrichment.

Huge thanks for the floating tables window, that is a really awesome feature I've recently discovered. Makes the huge tables easier to manage. Once you've selected the 'floating' feature, how do you revert to the docked mode? The floating window X isn't available to click.


Edit: I'm asking about the temperature units because they don't change when you change the units settings from metric to imperial. Not sure if any other tables do similar.

[Steve@VersaTune]

Originally Posted by phate Steve or Ugnius, For the cold start and warm up tables, are those x-axis values in °F or °C? I'm assuming the y-axis is % enrichment. Huge thanks for the floating tables window, that is a really awesome feature I've recently discovered. Makes the huge tables easier to manage. Once you've selected the 'floating' feature, how do you revert to the docked mode? The floating window X isn't available to click. Edit: I'm asking about the temperature units because they don't change when you change the units settings from metric to imperial. Not sure if any other tables do similar.

Looks like I forgot to tag them as temperature units. They are *C. I will fix that for the next release so that they use the user selected unit settings.

[SpeedRebirth]

Originally Posted by phate Once you've selected the 'floating' feature, how do you revert to the docked mode? The floating window X isn't available to click.

Right click the blue part of the floating window and select Dockable, then click and drag it to the left side. A small window apears at the sides of the screen when you drag it to let you know that it's dockable there