Yes I am.

 

My '08 is TBW and is AFR based. I thought the Lamba started on the '10 touring bikes.

 

Can someone please help me figure out what I'm doing wrong here....

I have the PV with the wideband 02 sensors and the AT module. I ran a couple logs when I first got it set up, and it seemed to work fine. But then I read the new logtuner instructions on the DJ website. Following those instructions, I created a new tune with adaptive control turned off, PE enrichment RPM raised above the rev limit, etc. Then I created a new value file from this map, and then went riding. I've gathered several log files, but upon loading them and calculating the new tune using Logtuner, I've been unable to get anything but zeros in the in the tuning tables.

This is the same problem iclick had in post #472. But in his case, he found that he didn't have one of the required signals selected. I've checked this, however, and it does not appear that I've missed any of the signals.

The only thing I couldn't set exactly per the Log Tuner instructions had to do with disabling the heated O2 Sensors.... But I don't have this option in the tune I'm working with...so I simply skipped that step.

Is anyone else having a problem getting values to show up in the tuning tables of Log Tuner? By the way, I'm tuning an '11 dyna, and my AF tables are AFR, not lambda.

 

When you opened the PV Tuner software, under options, did you check to be sure "Use Autotune for corrections" was checked instead of "HD OEM..."?

 

When you first "got it set up, and it seemed to work fine", were you using the stock o2 sensors? In the Log Tuner options you can click which sensors you are using. If that is correct, then the next step would be the signals you are logging. You say your AFR tables are in AFR, not Lambda? You might want to reverse that.
You could try opening your logfile in Windows, if you have Excel, just to see if you are getting any data?
I don't even look at the tables in Log tuner (very much). Once I calculate and save the new value file, I open WinPV, load the new values, save it as a new map. THEN I compare the old and new map using WinPV. The only thing I DO look at in Log Tuner is my hit-counts. Is ANYTHING showing up for you in Log Tuner?

 

Yes, I double checked that. Actually, there are two boxes...one for 'using Autotune for corrections' and the other is 'use HD OEM sensors'. The second one is unchecked.

 

The first runs, where it worked fine, were right after I got the WB sensors installed. I was using the first version of Logtuner, 1.0.5.0. Since I'd already used log tuner basic, all I had to change for the pro version was to add the Lambda1 and Lambda2 signals to the log, and make the appropriate changes regarding the sensors in Logtuner options. I went for a ride, and made three log files. When I got back, I retrieved them, imported them into log tuner, and everything worked fine. It made some changes to my VE tables, and since I had almost no spark knock at all, it only made one small change to the front spark table.

Then, HarleyHiker posted that a new version of Logtuner was available. I installed that, and printed out the new instructions. The new logtuner users guide said to make a couple changes in the tune.. disable PE by raising the RPM point at which it turns on... disable the Adaptive controls..etc. I did that (with the exception of the heated O2 sensors, and mentioned in my other post). Finally, I removed all the signals from the logs that weren't listed in the logtuner guide, so the log files wouldn't get as large... I had been logging some extra parameters, so I removed them.

After that, I have been unable to get any results to show up in the tuning tables. The spark tables populate, but not the tuning tables. I thought initially that perhaps I'd deleted one of the necessary signals from my logging, so I added all the stuff I originally had back in. That still didn't fix it.

I've opened my log files in Excel, and they are full of data.

Last night, I decided to start over. I deleted all the logged signals, and re-added them in the same order as they're listed in the tuning guide (I know that their order isn't supposed to matter, but if they're in order, they're easier to check against the list to ensure they're all there). I then added the couple extra parameters I like to log at the bottom of the list. Hopefully, I was missing one that I couldn't find even after looking twice. I'll know later this afternoon if that fixed it or not. Thanks guys for the ideas!

Art

 

From what you are saying, I am guessing one of the needed signals was missing. Since your logs have data, it sounds like some signal the Tuner program needs is not there. I would compare the actual log to the list of signals required in the documentation. I also have the autotune module but so far I have only been using the stock sensors. Hope this latest try works for you. I plan to test the wideband sensors soon.

 

Well, when I said that the logs had data, that was a general statement that meant there were lots of numbers in various columns... On closer examination, there was data in all the columns except the lambda1 and lambda2 columns. But why these columns are empty, I cannot say... I installed the WB sensors and AT module on 6-3. The logs I made on 6-4 have data in the lambda1 and lambda2 columns. I haven't touched any of the hardware since the day I installed it, but none of the logs after 6-4 have anything in those columns. I wonder if perhaps the CAN bus cable has come loose from the AT module, which would explain that. I'll check that and retry!

 

Well, it appears that it was a loose connection of the CANbus cable.... the clip wasn't holding the end that plugs into the PV. I haven't run any new logs yet, but I set one of the guages to read the two lambda signals, and I'm now seeing data.