Airborne, the PCV will be out for the rzr any day now and for fuel tuning it is a better solution than this. dynojet has access to electronics and code that we do-not.. (it's theirs, they should)
i've done my best to make tuning easy and as accurate as possible. i have actually been using this software for about a year and a half on my rzr, but recently put it into an interface that the average user could make use of.
once the V comes out there are still a couple of holes that need to be filled. first off currently there is no ignition support for the PCV and the rzr, dynojet says they are planning on adding an ignition module in a couple of months, and eventually the plan is to release the V with ignition ingegrated (no time frame for that yet). also to use autotune with the PCV, you must also buy either the AutoTune Module or a Wideband2.
if you currently have a wideband, it will not work with the PCV (unless you have the wideband2, and i dont know anybody that has one yet)
i have a lot of time and money in my Powercommander setup so i plan to use it for a while (at least until ignition is integrated into the pcv) .
there are alot of RZR Pilots out there who also have time and money in a PCIII setup.. I built this tool for them.
Hoover: Mike is right, to make this work you will need a wideband that is capable of logging (wideband commander) as far as plugging into the pcIII you cant do that in a plug and play fashion.. there are two options for plugging them together though. i have both of them so i can verify that it works..
if you have the dynojet lcd module you can buy a cable that ties into both the powercommander and the wideband commander, this will let you log and view data from both sources simoultaneiously. another thing you can do is: if you have the PowerCommander hub, you can tie the data aquisition port from the wideband to the pressure input on the powercommander hub. this is the premise for how i do my semi closed loop setup.
dyno maps are good but again as mike said there are shortcomings..
example:
for the most part when you go to the dyno for fuel tuning, you get 3 or 4 runs. those runs are all wide open throttle.. you may get varying loads from the dyno but these loads will be limited to what is set in..
what you end up with is a map that works good through the rpm range at wide open throttle..
after this map, if you are trail riding or running down a hill or just cruising you will be running in cells (rpm vs tps is a cell) that may have only been touched by your map or may not have been touched at all.
different loads on the engine at a given throttle position and rpm require different amounts of fuel.. vechicle weight, terrain, clutching, tires etc all will affect engine load.
by logging in the real world and mapping from that, you wind up with a much more diverse and accurate map.
a dyno is great for fuel tuning for a drag race type situation (if the operator knows how to set it up) it's also great for making sure you're not lean and damaging your engine but to make a really good fuel map, you need time in the real world.
if you have a wideband, use your dyno map.. build a good solid log (or series of logs) and run them against that map.. if everything is configured correctly and your dyno run was truly setup correctly for your vehicle weight, you wont see a whole lot of change in the wide open numbers but you will see tons of changes everywhere else.
in a dyno run, the fuel changes will mostly fall inside a diagonal line that goes from minimum rpm, minimum tps to max rpm, max tps
mapping from logs solves the cells everywhere else, as well as provides long term averaging(better numbers) for the cells in that band.