VersaTuner 1.13 released
 

We are excited to release VersaTuner 1.13 The update includes these changes:

New Features

• Possibility to edit the axis values (where technically possible) to accommodate turbocharged/supercharged, high load or high RPM applications
• Automatically rescale table values after editing the axis for easy tuning
• Automatic updates - never miss a VersaTuner update in the future
• Launch control and no lift shift rev limits can now be set up to 10000 RPM
• Online tune database is loaded faster and works with all firewalls

Gen 1 And Gen 2 Mazda RX-8

• Flash counter is not incremented when flashing with VersaTuner, you can reflash your ECU many hundreds of times without locking it
• Added new, renamed existing fuel tables and updated their descriptions

Fixes

• Corrected Equivalence Ratio parameter to use ISO parameter and scaling for all DISI and RX-8 platforms
• Fixed the problem when trying to read DTCs from advanced keyless entry module on gen 1 Mazda RX-8
• Fixed an issue when trying to copy and paste values between tables of different size in the Tune Editor

Read more about the new features

There are some tuners out there for other cars that allow permanently setting emissions readiness monitors to "Ready." Is this/will this, ever be available with VT?

We prefer to stay clear of disabling emissions functions. I've seen what the US EPA has done to diesel truck tuners, and I don't want any part of that. You can mask codes so that they don't light the MIL lamp on the dash, but you can not fake readiness tests with VersaTuner.

Most catless midpipes dont throw codes, esp. with an O2 bung extension. So just the airpump to worry about, which is a single not ready code.

This might be true of other cars but the RX-8 tests for this by cycling lean and rich to see if the rear O2 sensor reacts fast enough. If there's an extension/defouler, it usually won't. The code will just change from P0420 to P0139.

Not to get offtopic, but there are plenty of ppl on this forum, and 3 here locally that are not throwing codes with a catless midpipe. And locally, these guys have been running them for years. The pids have not been disabled via tuning software either.

The code is a hit or miss, my 8 did not throw a code for over 3k miles when I first installed the midpipe. I't's a permanent fixture on my view now.

This may not be exactly Versa Tuner related, but any chance of somehow being able to transfer security information from one ecu to another with VT? That way when we get a new ecu, there would be no need for dealer programming a new one to the keys etc. Also, since VT is tied to a vin, if we did get a new ecu, would you be able to uodate our VT software to accomodate for this, since its locked to a single VIN?

You can probably do that with FORScan

Why not have that ability with VT? All the abs/pcm/safety etc and also the "deeper" body module codes and etc? Like being able to tell which keyless sensor is broken when your remote doesnt work, etc.

What you're talking about for is non-trivial.

Decrypting and editing tables on one module is one thing. Doing it for all modules and getting the communications between them right is another.

My guess is that replicating Mazda's entire IDS suite beyond the scope of what they want to do with their performance tuning product. Especially since you can get Mazda's IDS software and VCM2 for under $1000 combined. I doubt VersaTune could profit by reverse-engineering a competing product and selling it for less (especially if Mazda decide to bring lawyers into the mix).