Power Vision Information Thread
Tourer
Joined: Sep 2009
Posts: 484
Likes: 38
From: DE
[quote=peg20;12012875]No. You should try to keep the majority of the map in closed loop so that the ECM can adjust to changing environmental and fuel mixture conditions. This helps the ECM ensure that it's hitting your lambda targets in open loop as well.
If I keep it in "closed loop" wont the norrow band sensors keep me at 14.6 AFR, regardless of my desired 14.2-13.8 table?
If I keep it in "closed loop" wont the norrow band sensors keep me at 14.6 AFR, regardless of my desired 14.2-13.8 table?
Road Captain
Joined: Nov 2012
Posts: 569
Likes: 0
From: USA
I haven't read all 282 pages yet- so this has probably been addressed.
When I down load a custom tune should I go to "open loop"? I have stock narrow band sensors.
If I want to richen up the new tune should I go to enrichment and add globally?
Can I write my own map over the new tune giving AFR values?
Thanks
When I down load a custom tune should I go to "open loop"? I have stock narrow band sensors.
If I want to richen up the new tune should I go to enrichment and add globally?
Can I write my own map over the new tune giving AFR values?
Thanks
As far as the CL or OL debate goes, CL is an EPA mandate. The only real way to make the choice is ride it for a while in CL. Then try it at something like 14.0 and see how it feels. I think, from a performance (and I'm not talking hotrodding) standpoint they run much better around 14.0, without sacrficing any fuel mileage that matters much.
Road Captain
Joined: Nov 2012
Posts: 569
Likes: 0
From: USA
No. You should try to keep the majority of the map in closed loop so that the ECM can adjust to changing environmental and fuel mixture conditions. This helps the ECM ensure that it's hitting your lambda targets in open loop as well.
You're gonna have to explain this one...lol If you have inside information on which AFV cells are being used I really really want to know.
You could, but you'll probably end up just wasting fuel. What are you trying to achieve (more performance or less heat)? Do you always want to sacrifice fuel for performance, or only when you when you rag on it? If the latter, then you only really want to enrichen for power in those parts of the map which (in your riding style) represent you "going for it". sub-3k RPM and small TPS% are probably best left pretty lean.
I would be richening up those areas myself. Then keep the cruise areas on the lean side. It really depends on the bike as far as the lower throttle / RPM areas. Some, depending on the exhaust, just don't have very good manners down low without a little richening up. No one size fits all with the tons of aftermarket parts being put on these things.
I'm not sure what you mean by that question, but the answer is probably yes :-)
You're gonna have to explain this one...lol If you have inside information on which AFV cells are being used I really really want to know.
You could, but you'll probably end up just wasting fuel. What are you trying to achieve (more performance or less heat)? Do you always want to sacrifice fuel for performance, or only when you when you rag on it? If the latter, then you only really want to enrichen for power in those parts of the map which (in your riding style) represent you "going for it". sub-3k RPM and small TPS% are probably best left pretty lean.
I would be richening up those areas myself. Then keep the cruise areas on the lean side. It really depends on the bike as far as the lower throttle / RPM areas. Some, depending on the exhaust, just don't have very good manners down low without a little richening up. No one size fits all with the tons of aftermarket parts being put on these things.
I'm not sure what you mean by that question, but the answer is probably yes :-)
Tourer
Joined: Sep 2009
Posts: 484
Likes: 38
From: DE
still want to know- will CL let me go to 14.0 or keep me at 14.6 with stock narrow band sensor?
On my dresser I have wide band and a great map for lean cruising and rich idle.- but I have wide band.
The above bike is my girl friends and she doesn't want to spring for wide band sensors, and runs hot. I have a map to richen it up-but think I need to keep it open loop to follow map.
On my dresser I have wide band and a great map for lean cruising and rich idle.- but I have wide band.
The above bike is my girl friends and she doesn't want to spring for wide band sensors, and runs hot. I have a map to richen it up-but think I need to keep it open loop to follow map.
Road Captain
Joined: Nov 2012
Posts: 569
Likes: 0
From: USA
still want to know- will CL let me go to 14.0 or keep me at 14.6 with stock narrow band sensor?
On my dresser I have wide band and a great map for lean cruising and rich idle.- but I have wide band.
The above bike is my girl friends and she doesn't want to spring for wide band sensors, and runs hot. I have a map to richen it up-but think I need to keep it open loop to follow map.
On my dresser I have wide band and a great map for lean cruising and rich idle.- but I have wide band.
The above bike is my girl friends and she doesn't want to spring for wide band sensors, and runs hot. I have a map to richen it up-but think I need to keep it open loop to follow map.
Road Captain
Joined: Apr 2009
Posts: 531
Likes: 4
From: Chile Flats, AZ
Just kind of wondered...I have a 2012 bike and my PV software and firmware are up to date as of the last (pre 2014 bikes) update. Is there really any reason to do this last update? My PV works great and I don't want to risk screwing it up with new software unless there is a benefit to pre 2014 bikes.
I would not update without a compelling reason.
If you are pleased with your current status, don't change without a reason.
Road Captain
Joined: Nov 2012
Posts: 569
Likes: 0
From: USA
Just kind of wondered...I have a 2012 bike and my PV software and firmware are up to date as of the last (pre 2014 bikes) update. Is there really any reason to do this last update? My PV works great and I don't want to risk screwing it up with new software unless there is a benefit to pre 2014 bikes.
Road Captain
Joined: Apr 2009
Posts: 531
Likes: 4
From: Chile Flats, AZ
Yes, but---
You won't screw anything up. What makes you think staying current would wreak havoc your cal? I check updates every time I connect the PV to the laptop. If it's an update that doesn't pertain to my cal ID I'll never see it anyway. Stay current with updates, you'll be fine. The boys at DJ wouldn't be putting out updates that would screw up peoples tunes.
Log Tuner works fine with the previous versions of WinPV, but at least with WinPV v.1319, the .pvv file produces a result that must be edited in order to produce the calculated new tune from LogTuner.
Therefore, why update until that glitch is fixed unless one needs the 2014 DJ tunes? At least that's been my and many other's experience.
On one laptop with an older version of WinPV, no problems with the LogTuner application developing a new calculated tune; on another laptop with the later version of WinPV, the .pvv file must be edited as described in the referenced posts to effect the correct .pvv file.
IF that glitch has been patched, I stand corrected.
HD Forum Stories
The Best of Harley-Davidson for Lifelong Riders
7 Surprising Harley-Davidson Products that Are Not Motorcycles
Verdad Gallardo
8 Best Harley-Davidson Motorcycles Ever
Pouria Savadkouei
10 Worst Harley-Davidson Motorcycles Ever
Pouria Savadkouei
Killer Custom's Jail Break Is The Breakout That Refused to Blend In
Verdad Gallardo
Crazy Bunderbike Build Looks Amazing, But Is It Impossible to Ride?
Verdad Gallardo
Harley-Davidson Reveals Super Cool Cafe Racer Concept
Verdad Gallardo
Engraved Rebellion: Inside Bundnerbike's Glam Rock II
Verdad Gallardo
10 Motorcycles You Should Never Buy
Joe Kucinski
10 Things Harley-Davidson Needs to Fix in 2026
Verdad Gallardo
Member
Joined: Jul 2009
Posts: 4,310
Likes: 1,079
Yes, but--- see post #5481 on page 549 by Dynaulv; and my post #5592 on page 560 for reference for my response to BigTwin.
Log Tuner works fine with the previous versions of WinPV, but at least with WinPV v.1319, the .pvv file produces a result that must be edited in order to produce the calculated new tune from LogTuner.
Therefore, why update until that glitch is fixed unless one needs the 2014 DJ tunes? At least that's been my and many other's experience.
On one laptop with an older version of WinPV, no problems with the LogTuner application developing a new calculated tune; on another laptop with the later version of WinPV, the .pvv file must be edited as described in the referenced posts to effect the correct .pvv file.
IF that glitch has been patched, I stand corrected.
Log Tuner works fine with the previous versions of WinPV, but at least with WinPV v.1319, the .pvv file produces a result that must be edited in order to produce the calculated new tune from LogTuner.
Therefore, why update until that glitch is fixed unless one needs the 2014 DJ tunes? At least that's been my and many other's experience.
On one laptop with an older version of WinPV, no problems with the LogTuner application developing a new calculated tune; on another laptop with the later version of WinPV, the .pvv file must be edited as described in the referenced posts to effect the correct .pvv file.
IF that glitch has been patched, I stand corrected.
Road Captain
Joined: Nov 2012
Posts: 569
Likes: 0
From: USA
Yes, but--- see post #5481 on page 549 by Dynaulv; and my post #5592 on page 560 for reference for my response to BigTwin.
Log Tuner works fine with the previous versions of WinPV, but at least with WinPV v.1319, the .pvv file produces a result that must be edited in order to produce the calculated new tune from LogTuner.
Therefore, why update until that glitch is fixed unless one needs the 2014 DJ tunes? At least that's been my and many other's experience.
On one laptop with an older version of WinPV, no problems with the LogTuner application developing a new calculated tune; on another laptop with the later version of WinPV, the .pvv file must be edited as described in the referenced posts to effect the correct .pvv file.
IF that glitch has been patched, I stand corrected.
Log Tuner works fine with the previous versions of WinPV, but at least with WinPV v.1319, the .pvv file produces a result that must be edited in order to produce the calculated new tune from LogTuner.
Therefore, why update until that glitch is fixed unless one needs the 2014 DJ tunes? At least that's been my and many other's experience.
On one laptop with an older version of WinPV, no problems with the LogTuner application developing a new calculated tune; on another laptop with the later version of WinPV, the .pvv file must be edited as described in the referenced posts to effect the correct .pvv file.
IF that glitch has been patched, I stand corrected.
Last edited by stailjim61; Dec 5, 2013 at 04:21 PM.