Ordered my Power Vision from Fuel Moto today. Looking forward to using this thread to get smart on it.

 

Perfectly normal, every bike is a little diff and while the system tries to compensate for air pressure, temp, humidity, etc it is not perfect... In theory, detected/calculated VE should be the same at 50F or 110F, 5% humidity or 100%, sea level or 7000 feet, but is imperfect and readings shift.

Keep running auto-tunes till you get a /small/ +/- repeating pattern, just keep in mind that a morning run at 50F followed by a late afternoon run at 90F and another 50F morning run may see VE shifting back and forth by > 5%.

I watched the entire middle of my VE tables shift 10% between 38F (middle of might) and 96F (peak daytime temp).


Once things are fairly dialed in, a couple longer auto-tune sessions, where you leave auto tune on for a number of rides can be useful to average it all out. I left in auto-tune for a week of daily riding, morning, afternoon, night (to from work plus general around mixed riding), exported, went back into autotune for another week, exported and compared... Week long averages were < 2% variation between 1st and second. That was how I finalized the VE tables last summer.

Only VE tables will change, AFR or lambda table is target mix.

Those are target AFRs at the lower edge of closed loop. You may consider altering the AFR table to your pref once VEs are dialed in.


Lower MPG is very normal during tuning.

While in auto-tune you are 14.6 across the board with 4deg retard... Leaner does not always mean better milage, when leaner produces less power resulting in greater throttle use for same speed leaner == lower milage.

Plus, everyone tends to hammer the throttle a bit more than normal after finishing a AT run and loading the new MAP.

2011 FLHTC, SE AC, Jackpot 2-1-2, SE slipons and Andrews 48h 96cu...

I saw anywhere from low 30s to mid 40s during long AT runs.

My current map runs 14.2 in the entire cruze range and on a Fall 2013 1200 mile road trip I saw 38 - 50 mpg with the low end on tangs of mostly hammering it in mountains (0 - 2000 - 0 - 2000 up down up down) and 50mpg on the fillup and run at 60mph in 6th on cruise control on mostly flat ground. Trip average was 46.Xmpg, with both the PV and my fuel receipts in agreement to within .5mpg

 

Hello,

Can Power Vision be used on 2009 FLHTCU to restore speedometer/odometer to accurate functionality after changing the front belt sprocket from 32 teeth to 30 teeth?

Similarly, can PV recalibrate to restore cruise control and 6th gear light operation?

Thanks,

Mark

 

In theory. At least on my 2011 the ratio for each gear is settable to match transmission and the speedo factor to adjust for tire size is as well.

I don't know why the 6th gear indicator or cruze would be impacted though.

6th indicator is based on engine rpm to output shaft rpm ratio, and cruze lower limit on detected speed. Detected speed would be off after a sprocket change, but should not impact 6th or cruze... (Might say 35 at 25actual but cruze control should still work.

 

Under GEAR/ SPEEDO CALIBRATION my pulse value is 2450 for my 2011 Ultra with a 30 tooth frt. pulley

 

Thanks Dave. How did you like the effect of the smaller front sprocket? Did you do anything elsw (cam ?) to change peak torque and where it occurs relative to engine and/or vehicle speed?

 

Nobody?

 

If you do some searches in this thread, there are some discussions on the throttle blade. Nothing really concrete. Leave a message at DynoJet & see what they have to say. Or Fuel Moto if you bought it there.
You might try & up the settings in the upper kpa areas. But don't do everything across the board. 2500rpm area will work it to redline. Just don't get carried away !

 

I am running a 120 motor I built from parts. MVA HEADS, T-Man 625 cam, Ful-Sac "B" headpipe with some street legal SE muffs, stock throttle body.
Tuned with PowerVision with wide and narrow band sensors. 132 hp and 141 torque.

It works for me.

 

Thanks for the reply. Did the search, didn't come up with anything specific, which is why I posted a request for details. Guess no one that has done it has seen my post yet.