Power Vision Information Thread
#3781
Agreed, but most guys aren't as familiar with adjustments to the spark tables. In most cases you are best to load a well designed map for your bike's engine configuration (such as FM's) which should have spark tables suitable for your bike's engine.
You can definitely increase the performance by elevating spark advance but you can also negatively impact the engine's performance or worse, cause harm, if you are not familiar with adjusting advance.
You can definitely increase the performance by elevating spark advance but you can also negatively impact the engine's performance or worse, cause harm, if you are not familiar with adjusting advance.
#3782
JUst my .02 worth here....
check out this link and look at other resources to understand why we have O2 sensors in the first place... yes its all about emmisions but there is more to it than that.. http://www.crypton.co.za/Tto%20know/...emissions.html
We are all using on our bikes a process called speed density conversion for our fuel strategy (that's how our ECM setups are) aka no mass air flow sensors...
Most important thing you can do is get the VE tables right on the money!!!! The VE tables do not directly control the AFR that is done in the stoich/Lambda settings and the bias tables. If your VE is wrong it will cause the ECM to be inaccurate when it compares values from the VE tables and AFR tables etc etc because the VE table was incorrect.
example: FRED (friggen ridiculous electronic device) is requested to apply a 13.8 afr per your stoich/afr/lambda table he will look at map, tps, air temp, engine temp etc etc AND the VE table and then set the injector pulse width according to those tables. You have control over just a few of those charts FRED is looking at. If you told FRED that in this situation the engine will be flowing lets say 112 in that cell of the VE table and its only flowing 92 FRED has no way of knowing you gave him the wrong information and will set the Pulse width using what he has been told and now your running richer than YOU chose in the stoich/afr/lambda table.
What I am trying to say is FRED is stupid and only does what he reads off charts that are pre installed in his "brain" the sensor charts we have no way or need to change or mod you just have to get the VE table correct to give FRED the ability to do what you ask him to do in the stoich/afr/lambda table and the bias tables.
From that point if the VE tables are accurate you can richen up, lean out, run open loop, closed loop, wide band, narrow band, or whatever you choose.
In the fine tuning on the AFR if running closed loop, ignition timing can cause issues in the case of pre ignition or post ignition causeing readings to the O2 sensors to be false rich or lean (there true readings just not caused by AFR its due to ignition related pre ignition (overheated combustion process which causes a different chemical reaction in combustion) or late spark timing not allowing a full burn process (this can actually cause a false lean reading to the O2 sensors due to not using all the oxygen available). A ignition misfire such as a bad spark plug or plug wire, weak coil, etc... will show as a lean condition to the O2 sensor either wide band or narrow band.
My point is closed loop is your friend and a tool to use to your advantage, you can still get the richer mixtures for the WOT bursts and idle engine cooling or all around max torque and still have the economy you desire in the cruising areas...
The PV gives you all the tools to do this but you need get the VE tables correct or the rest is not going to be accurate.
SORRY for the long read...
Doug
check out this link and look at other resources to understand why we have O2 sensors in the first place... yes its all about emmisions but there is more to it than that.. http://www.crypton.co.za/Tto%20know/...emissions.html
We are all using on our bikes a process called speed density conversion for our fuel strategy (that's how our ECM setups are) aka no mass air flow sensors...
Most important thing you can do is get the VE tables right on the money!!!! The VE tables do not directly control the AFR that is done in the stoich/Lambda settings and the bias tables. If your VE is wrong it will cause the ECM to be inaccurate when it compares values from the VE tables and AFR tables etc etc because the VE table was incorrect.
example: FRED (friggen ridiculous electronic device) is requested to apply a 13.8 afr per your stoich/afr/lambda table he will look at map, tps, air temp, engine temp etc etc AND the VE table and then set the injector pulse width according to those tables. You have control over just a few of those charts FRED is looking at. If you told FRED that in this situation the engine will be flowing lets say 112 in that cell of the VE table and its only flowing 92 FRED has no way of knowing you gave him the wrong information and will set the Pulse width using what he has been told and now your running richer than YOU chose in the stoich/afr/lambda table.
What I am trying to say is FRED is stupid and only does what he reads off charts that are pre installed in his "brain" the sensor charts we have no way or need to change or mod you just have to get the VE table correct to give FRED the ability to do what you ask him to do in the stoich/afr/lambda table and the bias tables.
From that point if the VE tables are accurate you can richen up, lean out, run open loop, closed loop, wide band, narrow band, or whatever you choose.
In the fine tuning on the AFR if running closed loop, ignition timing can cause issues in the case of pre ignition or post ignition causeing readings to the O2 sensors to be false rich or lean (there true readings just not caused by AFR its due to ignition related pre ignition (overheated combustion process which causes a different chemical reaction in combustion) or late spark timing not allowing a full burn process (this can actually cause a false lean reading to the O2 sensors due to not using all the oxygen available). A ignition misfire such as a bad spark plug or plug wire, weak coil, etc... will show as a lean condition to the O2 sensor either wide band or narrow band.
My point is closed loop is your friend and a tool to use to your advantage, you can still get the richer mixtures for the WOT bursts and idle engine cooling or all around max torque and still have the economy you desire in the cruising areas...
The PV gives you all the tools to do this but you need get the VE tables correct or the rest is not going to be accurate.
SORRY for the long read...
Doug
#3784
After 11 tunes using both AT and PV log tuner I have not had any more than a + or - 5 change in the VE tables. You just can't get it any closer as riding conditions change. I was even told to ignore the one odd 6% cell change in some of my earlier tunes. I might also add that the +/- 5% numbers have been that way since my 8th tune. Partly because when I did my first 7 tunes I was still restricted on how I ran the engine because it was a new 103 build. After the initial 500 mile break-in, it dialed in quick.
I am getting ready and trying to learn about the Spark tables now for the next phase in my tune. I made changes back when I had the PC III and it made a fare difference in my mpg and seat of the pants power. This an altogether different tuning process so I have to do some studying.......LOL. before I go to trying to change them spark tables.
I am getting ready and trying to learn about the Spark tables now for the next phase in my tune. I made changes back when I had the PC III and it made a fare difference in my mpg and seat of the pants power. This an altogether different tuning process so I have to do some studying.......LOL. before I go to trying to change them spark tables.
Last edited by Watchfuliz; 02-11-2013 at 09:39 AM.
#3785
JUst my .02 worth here....
check out this link and look at other resources to understand why we have O2 sensors in the first place... yes its all about emmisions but there is more to it than that.. http://www.crypton.co.za/Tto%20know/...emissions.html
We are all using on our bikes a process called speed density conversion for our fuel strategy (that's how our ECM setups are) aka no mass air flow sensors...
Most important thing you can do is get the VE tables right on the money!!!! The VE tables do not directly control the AFR that is done in the stoich/Lambda settings and the bias tables. If your VE is wrong it will cause the ECM to be inaccurate when it compares values from the VE tables and AFR tables etc etc because the VE table was incorrect.
example: FRED (friggen ridiculous electronic device) is requested to apply a 13.8 afr per your stoich/afr/lambda table he will look at map, tps, air temp, engine temp etc etc AND the VE table and then set the injector pulse width according to those tables. You have control over just a few of those charts FRED is looking at. If you told FRED that in this situation the engine will be flowing lets say 112 in that cell of the VE table and its only flowing 92 FRED has no way of knowing you gave him the wrong information and will set the Pulse width using what he has been told and now your running richer than YOU chose in the stoich/afr/lambda table.
What I am trying to say is FRED is stupid and only does what he reads off charts that are pre installed in his "brain" the sensor charts we have no way or need to change or mod you just have to get the VE table correct to give FRED the ability to do what you ask him to do in the stoich/afr/lambda table and the bias tables.
From that point if the VE tables are accurate you can richen up, lean out, run open loop, closed loop, wide band, narrow band, or whatever you choose.
In the fine tuning on the AFR if running closed loop, ignition timing can cause issues in the case of pre ignition or post ignition causeing readings to the O2 sensors to be false rich or lean (there true readings just not caused by AFR its due to ignition related pre ignition (overheated combustion process which causes a different chemical reaction in combustion) or late spark timing not allowing a full burn process (this can actually cause a false lean reading to the O2 sensors due to not using all the oxygen available). A ignition misfire such as a bad spark plug or plug wire, weak coil, etc... will show as a lean condition to the O2 sensor either wide band or narrow band.
My point is closed loop is your friend and a tool to use to your advantage, you can still get the richer mixtures for the WOT bursts and idle engine cooling or all around max torque and still have the economy you desire in the cruising areas...
The PV gives you all the tools to do this but you need get the VE tables correct or the rest is not going to be accurate.
SORRY for the long read...
Doug
check out this link and look at other resources to understand why we have O2 sensors in the first place... yes its all about emmisions but there is more to it than that.. http://www.crypton.co.za/Tto%20know/...emissions.html
We are all using on our bikes a process called speed density conversion for our fuel strategy (that's how our ECM setups are) aka no mass air flow sensors...
Most important thing you can do is get the VE tables right on the money!!!! The VE tables do not directly control the AFR that is done in the stoich/Lambda settings and the bias tables. If your VE is wrong it will cause the ECM to be inaccurate when it compares values from the VE tables and AFR tables etc etc because the VE table was incorrect.
example: FRED (friggen ridiculous electronic device) is requested to apply a 13.8 afr per your stoich/afr/lambda table he will look at map, tps, air temp, engine temp etc etc AND the VE table and then set the injector pulse width according to those tables. You have control over just a few of those charts FRED is looking at. If you told FRED that in this situation the engine will be flowing lets say 112 in that cell of the VE table and its only flowing 92 FRED has no way of knowing you gave him the wrong information and will set the Pulse width using what he has been told and now your running richer than YOU chose in the stoich/afr/lambda table.
What I am trying to say is FRED is stupid and only does what he reads off charts that are pre installed in his "brain" the sensor charts we have no way or need to change or mod you just have to get the VE table correct to give FRED the ability to do what you ask him to do in the stoich/afr/lambda table and the bias tables.
From that point if the VE tables are accurate you can richen up, lean out, run open loop, closed loop, wide band, narrow band, or whatever you choose.
In the fine tuning on the AFR if running closed loop, ignition timing can cause issues in the case of pre ignition or post ignition causeing readings to the O2 sensors to be false rich or lean (there true readings just not caused by AFR its due to ignition related pre ignition (overheated combustion process which causes a different chemical reaction in combustion) or late spark timing not allowing a full burn process (this can actually cause a false lean reading to the O2 sensors due to not using all the oxygen available). A ignition misfire such as a bad spark plug or plug wire, weak coil, etc... will show as a lean condition to the O2 sensor either wide band or narrow band.
My point is closed loop is your friend and a tool to use to your advantage, you can still get the richer mixtures for the WOT bursts and idle engine cooling or all around max torque and still have the economy you desire in the cruising areas...
The PV gives you all the tools to do this but you need get the VE tables correct or the rest is not going to be accurate.
SORRY for the long read...
Doug
#3786
No not at all. I think they were willing to help as there are no tuners in all of Texas trained and certified on the Power Vision!!! Crazy right!
The reason for the question is the first custom tune they made for me was open loop. I requested another based on new upgrades and they created a closed loop one for me.
The reason for the question is the first custom tune they made for me was open loop. I requested another based on new upgrades and they created a closed loop one for me.
Thanks
Jeff
#3787
#3788
You're not going to get max torque and cooling in closed loop. This whole closed loop business is EPA crap. They think because a water cooled engine can run 14.7 so can an air cooled engine. It just isn't so. Closed loop has been around the car industry for decades. It is proven and has it's place, in water cooled engines. Go back and read some posts pre-2006 from the tuner types of members in different forums. If they're selling a closed loop product then it's the best thing since sliced bread. But, pre 2006 they were singing a different tune. Not knocking anyone, but it's all marketing hype. Even the pre-2006 Delphi tuners didn't tune at 14.7. Before 02 sensors came around they all claimed max tq/hp AFR's were way lower than 14.7, and some tuners still publicly say this. BUT now that an 02 sensor is involved all of a sudden 14.7 is the best gig in town. It's just something someone put in the KoolAid hoping everyone drinks enough to be sold. If someone finds a way to keep an air cooled engine at a specific temperature, without fluctuating, then CL can work. That's just one part of the equation though. Now find the AFR that it makes peak hp and tq at and convince the tree huggers that the MoCo should be given a waiver to build bikes that pollute the environment. It just isn't going to happen. Closed loop is pure EPA compliant and 100% disregards what's best for an air cooled engine. I hardly see how CL can be anyone's friend.
Thanks
Jeff
#3789
After 11 tunes using both AT and PV log tuner I have not had any more than a + or - 5 change in the VE tables. You just can't get it any closer as riding conditions change. I was even told to ignore the one odd 6% cell change in some of my earlier tunes. I might also add that the +/- 5% numbers have been that way since my 8th tune. Partly because when I did my first 7 tunes I was still restricted on how I ran the engine because it was a new 103 build. After the initial 500 mile break-in, it dialed in quick.
I am getting ready and trying to learn about the Spark tables now for the next phase in my tune. I made changes back when I had the PC III and it made a fare difference in my mpg and seat of the pants power. This an altogether different tuning process so I have to do some studying.......LOL. before I go to trying to change them spark tables.
I am getting ready and trying to learn about the Spark tables now for the next phase in my tune. I made changes back when I had the PC III and it made a fare difference in my mpg and seat of the pants power. This an altogether different tuning process so I have to do some studying.......LOL. before I go to trying to change them spark tables.
#3790