Disclaimer >> this is BETA stuff! (but works well ) If you wish to indicate to “high level
enthusiasts / forum members” who wish to test this latest BETA release, that’s AOK with
me. Please have them contact [email protected] for instructions, etc. This is exciting
stuff, and if you do not wish to venture down this road, I understand. For those of you that
do, thanks in advance for helping us make the Power Vision the premier flashing tuning
system in the world!
In a nutshell this build of firmware incorporates three new features in the Power Vision:
1. Upgrade Tune
2. Quick Tune
3. Auto Tune
Before proceeding, ensure you have an original backup of the ECM calibration. This original
backup file has “.stk” as the extension and should be located here:
C:\My Documents\Power Vision\Original Tunes
If you do NOT see a file that looks like this ““10-FB4-JHMKORL.stk” or this
“AMAEF000AA000xxx-10-FB4-XJMT6GH-fb089aa2.stk” then do NOT proceed with installing and
using this firmware.
OK, lets get started:
Pick the correct software for your version of Windows, 32 bit or 64 bit and download / install:
http://dynojetpowervision.com/Downloads/beta/PowerVisionSoftwareInstaller_x32_1.0.58.msi
http://dynojetpowervision.com/Downloads/beta/PowerVisionSoftwareInstaller_x64_1.0.58.msi
Then download this BETA firmware:
http://dynojetpowervision.com/Downloads/beta/PV_FIRMWARE-1.0.14-1094-QUICKTUNE.pvu
To install this BETA firmware from a local drive:
1.
2.
3.
4.
5.
6.
7.
Plug in your Power Vision via USB to your computer (if it’s unplugged)
Launch the Update Client
Download and install the latest Tune Database (if it’s not current)
Highlight “PV Firmware”
Select “Update from Local File”
Point to the BETA firmware you downloaded from above
Finish the installation of the BETA firmware and exit
Upgrade Tune
This is a feature that will upgrade a tune with any new tuning parameters that have been added
in newer firmware since the tune was created.
On the Power Vision main menu, go to “Settings > Enter Code”. Now, enter the code 319248
In order to “see” the new parameters in WinPV:
1.
2.
3.
4.
5.
6.
Plug in the USB cable to the Power Vision
After the Power Vision boots up and says "PC Link Mode Active"
Launch WinPV
On the menu bar, go to "Power Vision", and choose "Get tune from Power Vision”
Select the “Copy of Original Tune” file.
Save this tune with a note that it was created with “BETA PV_FIRMWARE-1.0.121064.pvu”
Note >> You can load an old tune in WinPV as a compare file to determine what areas of the
calibration are now exposed and available for editing. A visual indication to identify parameters
that don’t match when using the compare feature is to look for the flags. This offers a quick, easy way
to identify where the tune has changed.

Yellow Flag = different


Green Flag = doesn’t exist in compare, but does exist in active file (so you can’t comare it to the
compare).
Red Flag = exists in compare, but does NOT exist in active file (so you can’t edit it)
Quick Tune
This is a feature that allows a user to alter the last tune that they’ve flashed to the bike’s ECM.
This is a new temporary icon under “Program Vehicle”.
Note >> Once this latest version of firmware is installed to your Power Vision, you MUST flash
a tune to the ECM before you can use this feature. Once a tune is flashed to the ECM, it’s
stored in a buffer that will allow you to use the Quick Tune feature.
There are 6 tabs on the GUI screen:
1. General – Idle Offset, Rev Limit, and Reset Adaptive Fuel Tables
2. Config – ACR, Heated o2, VSS, Active Intake, Active Exhaust
3. Tweaks – Adaptive, Closed Loop, Autotune Mode (disabled in this screen, see Autotune
in section below), Knock Control, EITMS
4. Fuel – 6 ranges of adjustment; Low, Med, High, Global, Decel, Lug (Fuel ADj Range -25
to 25% of base fuel map)
5. Spark - Low, Med, High, Global, Decel, Lug (SparkAdj Range -5 to 5 degrees)
6. VE - Low, Med, High, Global, Decel, Lug (VE Adju Range -25 to 25 ve units (%)
Some examples of that this looks like:
First row is a 105-level bike, note that none of the closed loop/adaptive items are available. The
rev limit is the rev limit of the currently selected tune, which you can then raise or lower.
This row is a 176 calibration level closed loop bike (2007 Dyna)…..
This is a 009 DBW Bike. Many items that you can turn a lot of switches on/off !!
The Fuel / VE / Spark adjustment screens all look like this:
Where the VE, Fuel, and Spark ranges are:
Auto Tune
We have a working version of the AutoTune Basic mode, you know the version that uses OE
narrowband o2 sensors. Although there’s an option to use a version of AutoTune Pro, the
version that requires the Autotune Wideband o2 Sensor Controller and wide band o2 sensors, I
don’t recommend using it at this time (use the old method that requires Log Tuner). Both
modes are semi-automated at this time, by that I mean that you still need to “set up” the tune
(see Log Tuner section of WinPV User Guide), but once it’s loaded to the Power Vision will
handle *some* of the heavy lifting until we allow the Power Vision to manage the entire
process.
Note >> Once this latest version of firmware is installed to your Power Vision, you MUST flash
a tune to the ECM before you can use this feature. Once a tune is flashed to the ECM, it’s
stored in a buffer that will allow you to use the Autotune feature.
Note >> please refer to the Log Tuner section of the WinPV User Guide on how to set up a tune
for use with Autotune Basic – Narrowband o2 Sensors.
Note >> one departure from the above will be to turn Adaptive Learning OFF !!
Under the “Program Vehicle” menu you can now select AutoTune. The next dialog that pops
up looks like this:
You select "Enable AT" to enable AutoTune. Then a dialog pops up and states, “Select the
Installed o2 Sensor Style, Narrowband or Wideband”. Make the proper selection for the style of
Autotune that you’ll be using.
Note>>"Settings" will eventually be where you could edit things like "temp to enable learning"
etc.
So anyway, you "enable AT" then when you hit the "DataLog" button it goes to the same old
familiar (for some of you) 319245 green grid screen (Autotune Datalogger) where it will learn as
you drive (no logging required if you're NOT planning on using Log Tuner).
Note >>the green screen, “Autotune Datalogger” now has many different modes !!

HITS - Shows length of time you've spend in each VE cell. Shows the entire VE table at
once.











RT - "RealTime" Same as HITS but zooms in and slides the VE table around you as you drive, so
you can target in on cells better. This is a Great way to kill yourself by not looking at the road.
Should be AWESOME on the dyno though. Worth checking out, I think………but use at
your own risk if riding on the street!!!
MAP_MIN - Shows the lowest map read for each VE Cell.
MAP_MAX - Shows the highest map read for each VE Cell.
60KPA - Shows "<" in all cells whose min MAP reading is less than 60. ">" for those
whose min MAP reading is above 60. And @ for ones whose min map reading is 60.
VEFront - Shows the ve front table as stored in the tune
VERear - Shows the ve rear table as stored in the tune
60KPAX - Shows the cells that have seen 60KPA. This is useful for EGR effect tuning
we'll get into in the future.
LVE-F - Learned VE front
LVE-R - Learned VE rear
LCOR-F - Learned correction to VE front (in percent)
LCOR-R - Learned correction to VE Rear (in percent)
When you think the ECM has had ample time to learn corrected values, ie. bike up to temp and
you’ve engaged in a thorough ride cycle where you experienced many different operating
conditions, go ahead and select the "Export Learned" button. This will write a .pvv with the
learned values that you can import into your tune in WinPV. Log Tuner is technically no longer
needed, but can be used if you’d like.
Eventually there will be a button for "Update Tune and Flash ECM" or something (to skip the
WinPV steps).
Note>>You can still use Log Tuner to review these values if you’d like. You can extract them
from the PV by using the “Get Lug” function in WinPV. There will be “pre” and “post” value
files to choose from, where post are the corrected values.
For customers, we envision the datalog screen being possibly simplified to more of a display
showing:
- If learning is taking place or not (and why not, like, too cold, etc)
- What has been learned so far
The green AutoTune Datalogger screen is VERY busy in this build.
In summary your workflow will be: Set up tune, Load Tune to PV, Enable AT, Datalog, Datalog,
Export Learned, Load Learned values in WinPV, Load corrected set up tune to PV, Flash ECM
with corrected set up tune…..repeat process. When complete, set those items that you “set up”
in the tune back to regular full time values.
Note>> Another departure in this firmware is that “Load Copy of Current” will no longer
include a complete copy of what’s in the ECM. This function will actually load a copy of the last
tune you flashed to the ECM. This copy will NOT include those items that you may have
changed with the Quick Tune feature, so essentially you’re getting the base calibration without
those items that are accessible via Quick Tune.
Other stuff in this firmware:





CAN Trip Center support
Added Active Intake and Exhaust for strategies 241/242
Fixed issue on Sportsters where Adaptive value was displaying incorrectly
Added support for Active Exhaust on 2012 CAN bikes 357 & 358
Lots of misc. stuff……..
WinPV
Off the top of my head:





Added MAP Read Teeth for all strategies (Calibrator Only)
Added "spark adjust by head temp / inlet air temp / engine temp" tables to all strategies
and made them accessible via Pro instead of Calibrator levels
Made EGR Effect / Charge Dilution Effect Pro instead of Calibrator
Added EGR Effect / Charge Dilution Effect for all other strategies (all but CAN and 74).
Ability to show difference between Active and Compare file as a % when in “Delta
Mode”


Ability to show differences only (in treeview) when comparing Active and Compare files
Get Datalog function allows you to “Get”, “Get and Delete”, or just “Delete”
Let me know how you come along, or if you have questions, etc!!
Email to [email protected] with the subject line ready “BETA Help”