Power Vision Information Thread
#851
No issues downloading that version for me. Insufficient disk space sounds like an issue on your PC, not the Power Vision. Do you have any disk space open on the PC for the temporary download file? I don't think the PV would be full unless you have done a ton of datalogging.
#852
There is a lot of very good information in this thread. Also on post #778, I responded to a similar question by putting together a set of basic instructions. You can find that here
http://www.box.net/shared/i66qvn4xf1s2xp7fgy8v
Let's us know if you have questions. Tuning with wideband autotune is similar.
http://www.box.net/shared/i66qvn4xf1s2xp7fgy8v
Let's us know if you have questions. Tuning with wideband autotune is similar.
#853
If you removed one of the fields that is being logged on the PV just go back into the menu like you did the first time and add it back it. Go to data logging, touch add,select channel to add, touch ok, exit. Next log will include the data.
Last edited by JustDennis; 06-29-2011 at 05:04 PM.
#854
#855
#856
You should see a message for each Table - Front VE, Rear VE, AFR, Front Spark, Rear Spark. It is very common to see the Table doesn't change message for the Front and Rear Spark table. You should always see it for the AFR table. However, you should have changes to the Front and Rear VE table. You apply those changes to the calibration you were using and then start the process over with that as your base calibration.
#857
You will virtually always see a variance in VE during the calc tune process if you just compare the tables. Once you try to apply it to the tune in WinPV you will sometimes see the "table doesn't change. matches desired" message when the changes are minuscule.
#858
Not necessarily... If the VE values were not significant enough of a change you will see the "matches desired" message. I have had this happen on occasion... but then I do another run where I change some of the external factors (i.e. speed, weather, hills, etc) and will see changes to the tune.
You will virtually always see a variance in VE during the calc tune process if you just compare the tables. Once you try to apply it to the tune in WinPV you will sometimes see the "table doesn't change. matches desired" message when the changes are minuscule.
You will virtually always see a variance in VE during the calc tune process if you just compare the tables. Once you try to apply it to the tune in WinPV you will sometimes see the "table doesn't change. matches desired" message when the changes are minuscule.
To the OP, if there are no changes then you are good. However, if you didn't see "any" changes on your first run, then I would suspect something is wrong.
#859
I'll have to take your word for it. I have never seen the table doesn't change message when everything was working. Even "minuscule" changes to the VE tables generated the changes message for the VE tables.
To the OP, if there are no changes then you are good. However, if you didn't see "any" changes on your first run, then I would suspect something is wrong.
To the OP, if there are no changes then you are good. However, if you didn't see "any" changes on your first run, then I would suspect something is wrong.
#860
Some tuning many not be able to be completed using this log"
Michael