V 1.10 impressions

[Enki]

OK so:

My test kind of got fucked up because of the map/settings bug (which has already been fixed, just waiting on deployment now) and because I was too eager to doublecheck the map settings (specifically to make sure I wasn't using a meth MAFCAL with meth disabled), but here's what I'm thinking so far:

Drive-ability is pretty much the same; there's been no apparent logic changes, which means maps will be plug and play; that's good.

Logging seems to be better (no more slashes in file names by default!), and some functionality has changed there; on the old version, when you log, the timestamp is reset when you start/stop the log. Now, when you hit the button to turn on monitoring, the timer starts. Starting/stopping logs just adopts the current timestamp. Some may find this annoying, but if you manage a fuckload of logs and don't use the default file name (which is a habit I'll have to break now), it can come in handy for reorganizing your logs after the fact.

16 PIDs is nice, but you already knew that was present. Same for IDC and Boost pressure, which no longer have to be calculated manually. Same for rounding in the CSV files; shit is on point now and pleases me greatly; gone are the days of pasting in formulae into the existing log after changing the decimal point structure of the entire thing to make it readable. Perfectly consumable right after download now.


Speaking of PIDs, it's right around 100/sec now. With the full 16 on the screen, it's roughly 6 rows per second (grabbed at random). Getting rid of non essentials will probably yield more data per second; I'll find out later today if that's the case for sure or not.

Logging resolution could probably be pushed higher, but at this point it's already pretty good, and supports wireless logging to boot (which I have not tested).


There's a couple more things that I'd like to see before my build is done, but overall this is a great step forward.

A log is attached; disregard AFRs as I didn't doublecheck which map I was flashing and got the meth compensated one instead of the proper one that I should have had. Actual peak airflow is closer to 41 lbs/min or 310 g/s, all on full corn and without aux fuel.

[Enki]

This makes me happy:

Originally Posted by Steve@VersaTune High speed logging is still on the to-do list. It's just a cubic shit ton of work to implement on all the different platforms and markets that we support.

[zenit]

Originally Posted by Enki Speaking of PIDs, it's right around 100/sec now. With the full 16 on the screen, it's roughly 6 rows per second (grabbed at random). Getting rid of non essentials will probably yield more data per second; I'll find out later today if that's the case for sure or not.

Want to try out the bluetooth connectivity and sps with an OBDlink MX? Just send it back to me before the 13th

[Enki]

I have an MX, and my tablet is BT capable; I've not tested it, because my dash is already hard wired for USB connectivity, and it's already been stated that it runs about 50/sec.

Side note:
It seems to be a lot more stable when it comes to sleep/suspend and key off situations.

[SpeedRebirth]

@Ugnius@VersaTune; @Steve@VersaTune;

When setting the alarm on Dashboard parameters it will only let me input values without , or .
Tested it on all parameters, same result, is this a bug or an adjustment you've made? I used to have 1,1 on the KR alarm because it was annoying to get an alarm as soon as i saw 1,01 kr.

Like if I would use Bar as logged boost value, then it will only let me input 1 or 2 ect. There's a huge difference there (14.5 or 29 psi).

[Ugnius@VersaTune]

Originally Posted by SpeedRebirth @Ugnius@VersaTune; @Steve@VersaTune; When setting the alarm on Dashboard parameters it will only let me input values without , or . Tested it on all parameters, same result, is this a bug or an adjustment you've made? I used to have 1,1 on the KR alarm because it was annoying to get an alarm as soon as i saw 1,01 kr. Like if I would use Bar as logged boost value, then it will only let me input 1 or 2 ect. There's a huge difference there (14.5 or 29 psi).

This looks like a bug, we will fix it in the next release. As a temporary workaround, you can copy and paste the necessary value from Notepad or another program.

[mazdakaps]

i got the digital download yesterday. I just need to wait for the cable. But now with the bluetooth future i can do the installation on the car with obdlink mx too? Or its just better to wait?

[Enki]

Bluetooth is logging only, think there are potential issues with flashing (like possible disconnects or interference which can happen with bluetooth from time to time), so it's disabled.

Also make sure you get the new hotfixed version and install that instead.

[mazdakaps]

Ok so ill wait for the cable and get started . I think i downloaded the hotfix since the download mail came very late night after the announcement of the hotfix.
In the meatime ill try to check the versa software and try to get some comfort