Power Vision Information Thread
I thought I had my SEPST tune pretty close and the AFR reading after my 3 weeks of madness was OK with a fair bit of inconsistency, blamed it on my exhaust sniffer, turned out I was DEAD wrong!! After ONE 20 min Power Vision Autotune Basic session (No PC) now my AFR meter woud read perfect target AFR to the dots on steady throttle!! I realized that my AFR meter with the DIY sniffer was working perfectly and super accurate, it was the SEPST that has been giving me the inconsistent result. Now after Power Vision the bike feel soooo much smoother, sounds so much smoother and the pipe has a nice deep smooth throathy rumble on it I never hear before... Perfect...I will do a few more Autotune Basic to perfect the VE tables and will create multiple tunes for different conditions from there...
Now the big question....
I noticed from the gauges that I am having knock retard event, I would like to tune that out. I am familiar about how to read maps and how to work on timing advance/retard for maximum efficiency Without a dyno to tell you what's happening we'll never know where that perfect pressure point is for efficiency. Seat of the pants, smoothness, and lack of pinging is about the best we can expect from a garage tune. and to elliminate knocking but I am confused as which tuning/logging/calculation method to use, Autotune Basic or Log Tuner?? Some people says that after I perfect the VE tables, I can activate spark learning on Autotune Basic by switching 'Max Spark Learn' to 10 on setting and ignore further VE correction by turning 'Max VE Learn' to 0 then run Autotune basic session as normal but focusing on spark event only and tune from there. However, Dynojet instruction advises against this on Autotune basic?? The ultimate end result is where the ECM has to do as little as possible. The less it has to learn and store means the less calculating it has to do = smoother more reliable tune. If you're dealing with timing and knock events the last thing I would do is ignore any VE corrections. If it's a lean knock, fix it. If it's a high temp knock, fix it. If it's an over advanced knock, fix it. Yes, the system would probably take care of it, but I'm not a big fan of ignoring issues and over-taxing the ECM to sort it out.
I know Log Tuner is what everyone use, but I am not comfortable with it yet and I like the fact that Autotune basic can be setup and done without the use of PC at all and I am already comfortable with its simplicity with automatic set to CL table, automatic off to AE/DE/PE/EITMS vs. having to do it manually on Log Tuner....If I can use Spark Learning on Autotune Basic, I don't think I will ever use Log Tuner.
Advises are so much appreciated and thank you very much in advance!
I know it's really poular over on XLforum.com, I've analyzed a couple of logs with the trial version you can download. Not sure if it is just the fact that I only want to focus on one thing at a time or that I am just not that proficient at using Mega Log view but it just seemed like another way of looking at the same data we already have. I keep meaning to play with it some more but just never get around to it.
I am running open loop 100% on city riding due to the fact that I always ride on 100F+ with a lot of stop and go traffic, planning to build second map with cruise area on closed loop for out of town riding.
Thank you for the advises...
The reason I am not going to touch VE when tuning Knock event is because the dynojet instruction specifically says so and I am running 100% open loop right now at 12.8-13.2, so if there is any knock event when I am running rich at 13.2 chances are it is either heat knock being in 100F+ environment or over advance knock.
I ride in 100F+ with stop and go traffic on most of my ride, so closed loop is a futile effort in my case, planning to tackle this situation first on open loop then create another map with closed loop in cruise for riding out of town with no traffic and more chances of getting bad gas.
Last edited by uwiik; Sep 25, 2013 at 08:22 PM.
I am running open loop 100% on city riding due to the fact that I always ride on 100F+ with a lot of stop and go traffic, planning to build second map with cruise area on closed loop for out of town riding.
Thank you for the advises...
I understand what you are talking about as far as running a open loop as well. I see pretty similar temps where I am located, highest them I road in this summer was just shy of 120 degrees. I leave my cruise range set at 14.2 and that is as lean as I go. I see some pretty extreme temp swings as well winter time I will see temps in the 15 degree range. I actually set up two separate tunes last year when my motor was 96" and will do the same this year with my 107". That way i will have a winter tune and a summer tune. Might not be necessary but I enjoy the tuning process and it gives me a excuse to go out and ride.
I understand what you are talking about as far as running a open loop as well. I see pretty similar temps where I am located, highest them I road in this summer was just shy of 120 degrees. I leave my cruise range set at 14.2 and that is as lean as I go. I see some pretty extreme temp swings as well winter time I will see temps in the 15 degree range. I actually set up two separate tunes last year when my motor was 96" and will do the same this year with my 107". That way i will have a winter tune and a summer tune. Might not be necessary but I enjoy the tuning process and it gives me a excuse to go out and ride.
So here are my conclusion, please correct me if I am wrong.
- I am comfortable with simple Autotune, and I think for VE tuning only it is still pretty accurate judging from my AFR sniffer reading, so I can stick with this method to perfect my VE before moving to Log Tuner to tune my Spark Knock.
- When it is time to play around with my timing, I will then move to Log Tuner. However, since I will be tuning Spark Knock ONLY, I do not need to retard 4* of timing, no need full CL table, no need to 0 DE/AE/PE/EITMS. Just ride it with ALL setting as I would normally ride while logging and calculate ONLY the Spark Knock table after I am done logging?
- If that's the case, then on PV's Datalog/Assign Signals setting I DO NOT need to include VE NEW F&R and DOES include the rest of the logging parameters (MAP, TP, ET, AE, ES, Desired Lambda/AFR, Warmup Lambda/AFR, Spark Knock Retards F&R) and subsequently do so when exporting to Log Tuner software and do the calculation?
- Kinda got a hint of the answer of the above questions from your reply and posts on page 543, but I wasn't 100% sure and need to have a firm confirmation for my analytical thinking. Sorry if I am repeating the questions.
Thank you very much for the helpful advises, so much appreciated!!...
Last edited by uwiik; Sep 25, 2013 at 11:36 PM.
The Best of Harley-Davidson for Lifelong Riders
So here are my conclusion, please correct me if I am wrong.
- I am comfortable with simple Autotune, and I think for VE tuning only it is still pretty accurate judging from my AFR sniffer reading, so I can stick with this method to perfect my VE before moving to Log Tuner to tune my Spark Knock.
- When it is time to play around with my timing, I will then move to Log Tuner. However, since I will be tuning Spark Knock ONLY, I do not need to retard 4* of timing, no need full CL table, no need to 0 DE/AE/PE/EITMS. Just ride it with ALL setting as I would normally ride while logging and calculate ONLY the Spark Knock table after I am done logging?
You need to log the 11 channels that regard to the cal your running. I would still see what the VE's look like, even if you don't recalibrate them. If they're solid no problem. You collected data, might as well look at them. If, for no other reason, you can see where a knock event happened, and then look at the VE. I always look at the VE's to see if there's a correlation to a low VE and a knock event. Map cal easier to interpret than a TP cal.
- If that's the case, then on PV's Datalog/Assign Signals setting I DO NOT need to include VE NEW F&R and DOES include the rest of the logging parameters (MAP, TP, ET, AE, ES, Desired Lambda/AFR, Warmup Lambda/AFR, Spark Knock Retards F&R) and subsequently do so when exporting to Log Tuner software and do the calculation?
Again, log the respective channels that pertain to your tune. AFR or Lambda. There are 11 if I recall correctly. If you're only working timing then just pull the tick marks out of VE fr and rr when the box pops up. This has all been covered in previous threads.
- Kinda got a hint of the answer of the above questions from your reply and posts on page 543, but I wasn't 100% sure and need to have a firm confirmation for my analytical thinking. Sorry if I am repeating the
questions.
Don't overcomplicate this. Follow the instructions. Log the appropriate channels. Create a .ppv. Let LT do the rest. Rinse and repeat until you don't pick up any knock hits. Using LT you should be able to get it right in 3 or 4 runs. Then tweak for annoying vibrations in any riding areas. Search the thread, there are tons of instructions on how to attack it.
Thank you very much for the helpful advises, so much appreciated!!...
I have read the entire thread starting from page 250 something when they started to discuss AT or LT, pages before that are not relevant anymore discussing the earlier firmware. I have done my homework before decided to add more to this thread. Nice way to eat through time during boring office hour
Autotuned 4 more runs last night and it's getting closer and closer. VE corrections dropped from 15% to 11% on 4th run and my AFR sniffer got even more consistent reading.
One last thing I will add to this lengthy thread, this might be useful for the other too.
-I have all the latest software and firmware (updated everything 3 days ago), I found out that I do not need to manually assign 11 channels to do tuner log. The auto tune screen will do everything automatically perfectly and I can import all the correct logging data with all the parameters to Log Tuner software fine.
-I still need to manually set lambda to 1 on working Lambda table, found out if I let AT screen to do it for me automatically I will get a lot of NBF:0 or NBR:0 during green tracer cell/log tuning screen.
- No need to manually enter 319245 code anymore to go to green tracer cell/log tuning screen, it can be done with the push of a button on AT screen
- There is no difference in capability or logging parameters between Autotune basic vs. Log Tuner. However, on Auto tune basic you just blindly accept the correction suggested by the data collected and flash it to your current tune without reviewing what it changes vs. Log Tuner you get to review the suggested change and apply it manually with the obvious option to apply what you want to apply only.
- Basically in my opinion the manuals that has been around making it seems like Power Vision run Autotune Basic and PC run Log Tuner are two different things with common goal. On the other hand, my experiments shows that with the latest firmware both are doing exactly the same thing, the only difference is on how it apply the correction to the map (Directly on PV vs via PC).
Correct me if I am wrong, like I said I might be just plain dumb. In the meantime I will try not to add even more pages to this already super long thread.
Last edited by uwiik; Sep 27, 2013 at 02:28 AM.


