O2 sensor wires are usually silver or some other metal besides copper, it is not a good idea to solder them. They also use the air gap between the wire strands to draw air into the sensor body, and solder can plug the air gap so the sensor won't respond correctly anymore.

You'll never see solder on any connections on a bike, car or airplane either, due to issues with vibration and corrosion.

 

Interesting. Sounds like a new sensor is the only good solution to a broken wire, and that's why Bosch admonishes against cutting or splicing sensor wires. I did it years ago on a car I owned and it worked fine, at least AFAIK since it ran fine and didn't throw any codes. I have lots of soldered connections on this bike, actually every connection I've created, so let's hope things hold up. What kind of corrosion occurs with solder?

 

Ok good ideas. I am using the the dip stick. I may want to to use my gauge holes for component speakers one of these days. LOL
Be a couple days until I can play but will check gauge and note city temp and make a highway run.

 

That would be very revealing. Stick that dipstick gauge in a pot of boiling water and see what you get, and if you have an IR or meat thermometer that's long enough, take a reading in the hot oil for a comparison.

 

FWIW, LT (Log Tuner or PV Tune) 1.0.14 uses a different algorithm to determine the new VE value. I've been having a problem with PV that I haven't mentioned here before, although I've been talking with DJ about it for some time. Using the AT-100 Pro (WB sensors) I have been seeing one or more areas in every tuning session that overshoot the ideal VE value, and that has prompted me to change to a manual method of tuning. This makes it very time-consuming but I've been making good progress doing it this way.

An example of this problem can be seen when I apply a recent tuning session to the earlier version of LT (1.0.13). At 7% TP @ 2000 RPM it was showing a VE Delta (front) of 1.12 when an inspection of the logs determined that it only hit this high for a very short time. It was running very lean there, but I manually made a +5% change to the VE value in that location that put the AFR to very near correct. Running LT 1.0.14 shows a VE Delta of 1.06, very close to my manual alteration. For this reason I think they have the algorithm much closer to accurate and I'll be doing some tuning runs soon to check this. Anyone else make these observations, before or after trying the new version?

 

Iclick

Version 1.0.14 seems to show less "seesawing" on my tuning runs. Before I was combining a morning tuning run (temps in 70s) and an evening tuning run (temps in the high 90s) to help mitigate the overshooting. Ver 1.0.14 does seem to to a better job of targeting the required VE more quickly. Interestingly enough I found I had to add "VE Front" and "VE Rear" to my signals being logged to make LT calculate. Anyone else experience that? It could have been an error on my part but everything is working now.

 

So you're seeing swings based on ambient temperature? Those that I'm seeing have been limited to only a few areas in one tuning session, usually done in the peak of the daily heat. For example, in my last session one area (2000 rpm @ 7TP) showed a VE Delta of 1.12 with LT 1.0.13, but only in one brief period did it hit that peak, mostly staying between that point and stoich. When I tried the same tuning files with LT 1.0.14 the value in that area was 1.06, very close to the 5% adjustment I made manually.

I did another run today and found the changes to be quite accurate, so I think the changes were a success. However, one area (1250 rpm @ 0%) showed some fairly big swings in the logs, so I didn't make any changes there. So for the time being I'm still looking at the LT result as well as the logs, then making the changes manually. I could select which New VE values I want to use by leaving them alone, then editing those I want by changing the New VE value in LT. I may resort to that in the future, but I will still check-out LT's results closely before writing them to the tune.

 

All

I wanted to let you know that the PV has a "cool" new feature called Autotune Datalogger. I have been testing and using this feature for some time and got permission from DynoJet to share this with you guys. It has worked well for me to help hit areas that I was missing before during my tuning runs.
*** A note of Caution here - please BE CAREFUL WATCHING THIS SCREEN WHILE RIDING ****

First - What does Autotune Datalogger do?
- Loads the current PVT that is on the ECM, and displays the VE tables' axii (with RPM capped to 6000).
- Displays RPM and either MAP or TPS depending on the type of calibration that’s flashed to the ECM
- Draws an X on the current cell.
- When you hit "start" it logs to a file (same as gauge screen) but with all the appropriate signals for Autotune.
- For each cell, increments a counter each time it is hit. This is not a counter as in "adaptive good to go here" just a sign that it's been hit.
- It always logs lambda1 and 2 even if no wideband present

The main benefit to me is it puts the PV in a state where it knows everything about what's going on, in terms of the tune, what you're trying to do, etc etc. No fumbling around assigning signals in the gauges.

How do you get to it?
With the PV connected to your bike and ignition and run switch on, from the main menu screen, select "Settings", then "Enter Code". On that screen enter pin 319245 and select Save. Once the screen comes up, you can press start log just like you do on the gauges screen to begin data logging.

With the PV mounted, you can see at a glance what "cells" you are hitting while riding. TP, RPM, log name, etc are also displayed but they are small...... You can also start the Datalogger and just drop in a saddlebag or pocket if that is what you are currently doing. It will setup all the signals you need and write to the log. Just remember to start and stop the log like you do with the gauge display.

I will try to post a picture of the screen later but give it a try. Just be careful. Let us know what you think. DJ is planning some improvements to the tool and may add it as normal selectable function at some point.

Don't forget to check the DynoJet Update link. They are posting a lot of the latest features and fixes there ---> http://www.dynojet.com/Blog/?p=80

 

Do you need Autotune to use this, or is it for PV Basic, as well? Thanks.

TedMan

 

You can use with Basic tune as well. It logs all the fields you need for either the Basic or Pro tune in LT. Good question, I meant to include that. I used the display and logs for both type of tuning.