Power Vision Information Thread
If it is not showing knock events in your logs and is for sure pinging the Delphi system itself is not picking it up, this is not related to the Power Vision as we are just using the information from the ECM data stream. If you have the PV mounted you can setup a gauge to monitor knock retard for visual representation. The Delphi ion discharge knock sensors works well, however it is not a perfect system. Also make sure you use the factory spark plugs and wires for best results.
__________________
Jamie Long / Fuel Moto USA
The USA's Leader V-Twin EFI & Performance www.fuelmotousa.com
Contact 920-423-3309
Email jamie@fuelmotousa.com
Jamie Long / Fuel Moto USA
The USA's Leader V-Twin EFI & Performance www.fuelmotousa.com
Contact 920-423-3309
Email jamie@fuelmotousa.com
Cruiser
Joined: Jul 2010
Posts: 222
Likes: 1
From: Massachusetts
So,
I just finished my first tune and thanks to Jamie's instructions all went well. Using the first log that was taken, it appears there were only small changes needed to the front and rear spark tables. All other tables at this time were right on. The MAP I was using was one of Jamies and the bike has been running great before starting this tune. We will see how long it takes to get it spot on.
I just finished my first tune and thanks to Jamie's instructions all went well. Using the first log that was taken, it appears there were only small changes needed to the front and rear spark tables. All other tables at this time were right on. The MAP I was using was one of Jamies and the bike has been running great before starting this tune. We will see how long it takes to get it spot on.
Since the VE tables are a representation of airflow, this will affect the mixture directly
Novice
Joined: May 2011
Posts: 21
Likes: 0
First I wanted to let everyone know there is a new version of the log tuner on the Dynojet website. Version 1.06. There is also an updated manual.
http://www.powercommander.com/downlo...uner_guide.pdf
I have a couple questions for Jamie,
1. I've tried a few logs with Lambda at .979. For some reason with Lambda this low, I get zero hits when I put my logs into the log tuner. What am I doing wrong or is the software not working correct? From one of your earlier post, you gave a range to stay in closed loop, and this is well within that range.
2. In the new manual, it suggest to "Extend the closed
loop operating range by changing all values to (14.6 or Lambda 1). This disables the
ECM’s ability to transition to open loop. (Ok I get this)
a) It suggest to rase PE Enable RPM above the Rev limit to disable power Enrichment (Is this necessary? We haven't talked about this before)
b) It suggest to remove 3-4 Degrees of spark advance from both the front and rear tables. My question here is it doesn't say where from? The entire table? Or just the sections where we've extended the Lambda table?
http://www.powercommander.com/downlo...uner_guide.pdf
I have a couple questions for Jamie,
1. I've tried a few logs with Lambda at .979. For some reason with Lambda this low, I get zero hits when I put my logs into the log tuner. What am I doing wrong or is the software not working correct? From one of your earlier post, you gave a range to stay in closed loop, and this is well within that range.
2. In the new manual, it suggest to "Extend the closed
loop operating range by changing all values to (14.6 or Lambda 1). This disables the
ECM’s ability to transition to open loop. (Ok I get this)
a) It suggest to rase PE Enable RPM above the Rev limit to disable power Enrichment (Is this necessary? We haven't talked about this before)
b) It suggest to remove 3-4 Degrees of spark advance from both the front and rear tables. My question here is it doesn't say where from? The entire table? Or just the sections where we've extended the Lambda table?
Advanced
Joined: May 2011
Posts: 66
Likes: 0
I took one of the reduced timing maps that Jamie sent me and removed another 4deg of timing from 2250RPM @ 60kpa and beyond. I got no ping on the 48mi run from work to home. I took that data and autotuned and added another 2deg back to the timing. I tested and logged that map... No changes came out. So I added in another 1deg of timing. I received no noticeable ping and no changes to the VE. So I am test running it in the hot afternoon today and I will see what I come up with. If this works, I will continue putting timing back until I get ping and then reduce the timing strictly in the areas that I do get ping while raising the timing in other areas.
I may also go back to the first map that Jamie sent - which had the best performance of them all - and start auto-tuning it out to see what happens.
Oh, and BTW I can't thank Jamie and FM enough for their support and help. They've been fantastic to work with and extremely patient and helpful.
I may also go back to the first map that Jamie sent - which had the best performance of them all - and start auto-tuning it out to see what happens.
Oh, and BTW I can't thank Jamie and FM enough for their support and help. They've been fantastic to work with and extremely patient and helpful.
Advanced
Joined: May 2011
Posts: 66
Likes: 0
First I wanted to let everyone know there is a new version of the log tuner on the Dynojet website. Version 1.06. There is also an updated manual.
http://www.powercommander.com/downlo...uner_guide.pdf
I have a couple questions for Jamie,
1. I've tried a few logs with Lambda at .979. For some reason with Lambda this low, I get zero hits when I put my logs into the log tuner. What am I doing wrong or is the software not working correct? From one of your earlier post, you gave a range to stay in closed loop, and this is well within that range.
2. In the new manual, it suggest to "Extend the closed
loop operating range by changing all values to (14.6 or Lambda 1). This disables the
ECM’s ability to transition to open loop. (Ok I get this)
a) It suggest to rase PE Enable RPM above the Rev limit to disable power Enrichment (Is this necessary? We haven't talked about this before)
b) It suggest to remove 3-4 Degrees of spark advance from both the front and rear tables. My question here is it doesn't say where from? The entire table? Or just the sections where we've extended the Lambda table?
http://www.powercommander.com/downlo...uner_guide.pdf
I have a couple questions for Jamie,
1. I've tried a few logs with Lambda at .979. For some reason with Lambda this low, I get zero hits when I put my logs into the log tuner. What am I doing wrong or is the software not working correct? From one of your earlier post, you gave a range to stay in closed loop, and this is well within that range.
2. In the new manual, it suggest to "Extend the closed
loop operating range by changing all values to (14.6 or Lambda 1). This disables the
ECM’s ability to transition to open loop. (Ok I get this)
a) It suggest to rase PE Enable RPM above the Rev limit to disable power Enrichment (Is this necessary? We haven't talked about this before)
b) It suggest to remove 3-4 Degrees of spark advance from both the front and rear tables. My question here is it doesn't say where from? The entire table? Or just the sections where we've extended the Lambda table?
I think all of this stuff is for starting from scratch, which most of us aren't since we have FM maps... but still, I'm actually more confused by this guide than anything. The first was vague... this one is more specific but leaves it hanging and me confused lol. But then again, I don't know jack about tuning... just what I've gleaned from reading and from Jamie.
Last edited by Pass; Jun 4, 2011 at 09:04 AM. Reason: Disabling closed loop is for AutoTune Pro only... removed that line and question.
Outstanding HDF Member
Joined: Jan 2007
Posts: 2,598
Likes: 19
From: Naples FL / Pine TWP PA
First I wanted to let everyone know there is a new version of the log tuner on the Dynojet website. Version 1.06. There is also an updated manual.
http://www.powercommander.com/downlo...uner_guide.pdf
I have a couple questions for Jamie,
2. In the new manual, it suggest to "Extend the closed
loop operating range by changing all values to (14.6 or Lambda 1). This disables the
ECMs ability to transition to open loop. (Ok I get this)
a) It suggest to rase PE Enable RPM above the Rev limit to disable power Enrichment (Is this necessary? We haven't talked about this before)
b) It suggest to remove 3-4 Degrees of spark advance from both the front and rear tables. My question here is it doesn't say where from? The entire table? Or just the sections where we've extended the Lambda table?
http://www.powercommander.com/downlo...uner_guide.pdf
I have a couple questions for Jamie,
2. In the new manual, it suggest to "Extend the closed
loop operating range by changing all values to (14.6 or Lambda 1). This disables the
ECMs ability to transition to open loop. (Ok I get this)
a) It suggest to rase PE Enable RPM above the Rev limit to disable power Enrichment (Is this necessary? We haven't talked about this before)
b) It suggest to remove 3-4 Degrees of spark advance from both the front and rear tables. My question here is it doesn't say where from? The entire table? Or just the sections where we've extended the Lambda table?
The reason you temporarily extend the closed loop operation is to dial in VE. You are just teaching the ECM how your motor breaths. You return the map settings back to the original settings once VE is zeroed in.
PE is disabled to make sure you are not biasing the outcome of your VE calibration runs.
He is suggesting taking timing out to protect the motor while calibrating VE.
You return all these settings back to where they were prior to calibrating VE in this section of the map.
Hope this helps
Ron
Outstanding HDF Member
Joined: Jan 2007
Posts: 2,598
Likes: 19
From: Naples FL / Pine TWP PA
Thanks for pointing this stuff out! I read over the new guide and wound up with the same questions. It doesn't specify what ranges or cells to remove timing from. I would think removing 3-4deg of timing from the entire table would have a sizable impact on performance. And I'm not sure but I don't think that the tuner automatically puts timing back if it doesn't see ping... So you would likely have to keep re-adding timing to the whole table, which just doesn't seem right. I could be wrong. Also, it doesn't specify if you should go back and turn some of those switches back on (i.e. PE enable, Adaptive Control, heated O2 sensors) or the AFR Lambda -- is it supposed to stay permanently closed loop???? But later it states to set the table so that it can't close loop on 14.6 (I'm confused) and will this adjust or are we to put it back when done tuning or leave it or what??.
I think all of this stuff is for starting from scratch, which most of us aren't since we have FM maps... but still, I'm actually more confused by this guide than anything. The first was vague... this one is more specific but leaves it hanging and me confused lol. But then again, I don't know jack about tuning... just what I've gleaned from reading and from Jamie.
I think all of this stuff is for starting from scratch, which most of us aren't since we have FM maps... but still, I'm actually more confused by this guide than anything. The first was vague... this one is more specific but leaves it hanging and me confused lol. But then again, I don't know jack about tuning... just what I've gleaned from reading and from Jamie.
HD Forum Stories
The Best of Harley-Davidson for Lifelong Riders
7 Times Harley-Davidson Chucked Tradition Out the Window
Verdad Gallardo
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
Advanced
Joined: May 2011
Posts: 66
Likes: 0
That's going to make things a bit more difficult. I would say it would be easiest to back up the values for the things you will be putting back into a seperate .pvv file, make your changes do your tune and then put back the "selected" values from the back up .pvv file. The trouble would be is if the spark tables actually changed during the tuning.
I'm sure Jamie has some better idea of a way to go about this process... including specific settings as the guide gives none.
I'm sure Jamie has some better idea of a way to go about this process... including specific settings as the guide gives none.
Outstanding HDF Member
Joined: Jan 2007
Posts: 2,598
Likes: 19
From: Naples FL / Pine TWP PA
But don't worry about that. You can retune the spark later. Spark is tuned by knock retard events. I am keeping a linear progression of all my tuning so I can grab spark, VE, whatever from any tuning run. So say I start tuning VE in the non closed loop sections at run ten. I finish at run 12 and the timing map changed. I just go get the timing map from run 9 and import it back in to the new map.