Power Vision Information Thread
#1311
![Default](https://www.hdforums.com/forum/images/icons/icon1.gif)
I have a similar scatter graph of VE and VE new as papifun, collected on my last
logging trip. I don't understand why, as the LogTuner program's suggestions for
new VE values are all between 0.98 and 1.02. (Except for four or five cells with
1.03 and 1.05) Can someone enlighten me on this?
logging trip. I don't understand why, as the LogTuner program's suggestions for
new VE values are all between 0.98 and 1.02. (Except for four or five cells with
1.03 and 1.05) Can someone enlighten me on this?
#1312
![Default](https://www.hdforums.com/forum/images/icons/icon1.gif)
Ok so im having a bit of trouble getting the new Auto tune to work correctly.
I've been using the stock O2 sensors with Powervision for the last few months but decided to upgrade to the WB sensors. Installed the sensors and AT-100 on the bike today. This is the newer version where 1 module services both WB sensors. I am familiar with the 2 module setup. Used the Y-cable to connect all up and i do have power. I added the Lambda1 and 2 signals to log also. Problem im having is no Lamba data is being written to the log file.
Auto tune module shows a steady red light when bike is running.
A few questions about the single module:
There are two small 4 pin ports on the opposite end of the module from the WB color coded wires. I assume those dont require any type connector in them.
I also assume that the stock O2 connectors do not require terminating plugs in then.
There was next to nothing as far as installation instructions for the AT-100.
Any suggestions as to where my problem may be?
I've been using the stock O2 sensors with Powervision for the last few months but decided to upgrade to the WB sensors. Installed the sensors and AT-100 on the bike today. This is the newer version where 1 module services both WB sensors. I am familiar with the 2 module setup. Used the Y-cable to connect all up and i do have power. I added the Lambda1 and 2 signals to log also. Problem im having is no Lamba data is being written to the log file.
Auto tune module shows a steady red light when bike is running.
A few questions about the single module:
There are two small 4 pin ports on the opposite end of the module from the WB color coded wires. I assume those dont require any type connector in them.
I also assume that the stock O2 connectors do not require terminating plugs in then.
There was next to nothing as far as installation instructions for the AT-100.
Any suggestions as to where my problem may be?
#1313
![Default](https://www.hdforums.com/forum/images/icons/icon1.gif)
Looks like you need a few more VE tuning runs. Continue to run tuning logs until your VE changes show less that 1 or 2 % in Log Tuner. As an FYI, it normally takes me somewhere between 7 and 15 runs to get the VEs where I want them across the map. May be just my imagination but the stock O2 sensors seem to take more tuning runs that the Wideband autotune sensors. With Wideband, I can do about 7 runs and the VEs are close. With Stock O2s it seems to take me 10 to 15 depending on how close the starting map is.
#1314
![Default](https://www.hdforums.com/forum/images/icons/icon1.gif)
Ok so im having a bit of trouble getting the new Auto tune to work correctly.
I've been using the stock O2 sensors with Powervision for the last few months but decided to upgrade to the WB sensors. Installed the sensors and AT-100 on the bike today. This is the newer version where 1 module services both WB sensors. I am familiar with the 2 module setup. Used the Y-cable to connect all up and i do have power. I added the Lambda1 and 2 signals to log also. Problem im having is no Lamba data is being written to the log file.
Auto tune module shows a steady red light when bike is running.
A few questions about the single module:
There are two small 4 pin ports on the opposite end of the module from the WB color coded wires. I assume those dont require any type connector in them.
I also assume that the stock O2 connectors do not require terminating plugs in then.
There was next to nothing as far as installation instructions for the AT-100.
Any suggestions as to where my problem may be?
I've been using the stock O2 sensors with Powervision for the last few months but decided to upgrade to the WB sensors. Installed the sensors and AT-100 on the bike today. This is the newer version where 1 module services both WB sensors. I am familiar with the 2 module setup. Used the Y-cable to connect all up and i do have power. I added the Lambda1 and 2 signals to log also. Problem im having is no Lamba data is being written to the log file.
Auto tune module shows a steady red light when bike is running.
A few questions about the single module:
There are two small 4 pin ports on the opposite end of the module from the WB color coded wires. I assume those dont require any type connector in them.
I also assume that the stock O2 connectors do not require terminating plugs in then.
There was next to nothing as far as installation instructions for the AT-100.
Any suggestions as to where my problem may be?
See Figure B (page 2) and Fig E & F (page 3) in the instructions http://www.powercommander.com/downlo.../at110_120.pdf
Last edited by JustDennis; 09-16-2011 at 08:50 AM.
#1315
![Default](https://www.hdforums.com/forum/images/icons/icon1.gif)
I am having similar problems...VE does not seem to settle in but keeps bouncing all over the map. I seem to get a lot of variation with either dew point or percent humidity. I am now limiting my tuning runs to periods when the dew point in the 50's and temperatures in the 70's. I am trusting that I can reduce variation in VE by reducing variation in atmospheric conditions. Curious if anyone else has noticed this and can comment.
#1316
#1317
![Default](https://www.hdforums.com/forum/images/icons/icon1.gif)
I totally agree with you. Atmospheric conditions play a big part in tuning our bikes. Bottom line is, you gotta tune for where you ride! That's why we can't just swap maps with each other, even with the same setup. I'm in Florida where it's Hot and Humid. I know that colder climates might dictate a richer AFR, but if there's altitude involved, all that goes out the window.
For where you live, you might just have to make 3 or 4 maps, based on your "bouncing VEs", take time to test them, and in the end, build a new one based on compromise. I only wish I could spend more time riding up where you live! -Steevo-
#1318
#1319
![Default](https://www.hdforums.com/forum/images/icons/icon1.gif)
The came out with clamp/visor http://www.dynojet.com/powervision/p...cessories.aspx
#1320
![Default](https://www.hdforums.com/forum/images/icons/icon1.gif)
I just got back last week from a 2600 mile, FL to Ohio (and back), solo ride. This is not the first time that I've taken a great-running bike up to the mountains, and it starts sounding waaaay too rich. I should have ran some logs up there, so next time I can just load my "high altitude" map.
I totally agree with you. Atmospheric conditions play a big part in tuning our bikes. Bottom line is, you gotta tune for where you ride! That's why we can't just swap maps with each other, even with the same setup. I'm in Florida where it's Hot and Humid. I know that colder climates might dictate a richer AFR, but if there's altitude involved, all that goes out the window.
For where you live, you might just have to make 3 or 4 maps, based on your "bouncing VEs", take time to test them, and in the end, build a new one based on compromise. I only wish I could spend more time riding up where you live! -Steevo-
I totally agree with you. Atmospheric conditions play a big part in tuning our bikes. Bottom line is, you gotta tune for where you ride! That's why we can't just swap maps with each other, even with the same setup. I'm in Florida where it's Hot and Humid. I know that colder climates might dictate a richer AFR, but if there's altitude involved, all that goes out the window.
For where you live, you might just have to make 3 or 4 maps, based on your "bouncing VEs", take time to test them, and in the end, build a new one based on compromise. I only wish I could spend more time riding up where you live! -Steevo-
BTW, to anyone who's running the stock NB sensors and displaying Lambda info, what range of values are you seeing displayed while the bike is running? I'm wondering if I do go back to the NB sensors if I'll still be able to monitor Lambda on-the-fly like I'm doing now with the WB sensors. I know it will get the info from the ECM, not the AT-100 as now.