Author |
Message |
Jhallgren
| Posted on Sunday, October 09, 2016 - 08:12 pm: |
|
Anyone ever have experienced a AFV that stayed the same over a period of time? My AFV two weeks ago was 92.1. For the last 300 miles it has stayed at exactly 102.0 and doesn't appear to have change. Temps around here have fluctuated from high 50's to low 70's. I thought I would have seen a change in 300 miles. |
Phelan
| Posted on Sunday, October 09, 2016 - 09:28 pm: |
|
Sounds like you're looking at the correction factor rather than the AFV. AFV doesn't use decimals IIRC. |
Sagehawk
| Posted on Sunday, October 09, 2016 - 10:36 pm: |
|
I seemed to have that happen once. I sent eeprom, datalog, to Gunter and he went thru it all. Reestablished the closed loop area as he said, I wasn't riding in the general closed loop area. I just don't ride like I'm on fire. After I loaded his subtle changes, bike did run better and afv started moving around again. |
Jhallgren
| Posted on Monday, October 10, 2016 - 10:31 am: |
|
Where is the closed loop RPM range? I usually cruise in the 3-4000 RPM range. I don't have ECMSpy or TunerPro. I am using a bluetooth connector with ECMDroid. There are two sections in the app that show AFV and both show 102.0. |
Sagehawk
| Posted on Monday, October 10, 2016 - 10:03 pm: |
|
I'll try to get screen prints of before and after for you. This will be off of spy version 2 on my notebook . You'll have a visual of what we are speaking of. |
|