Would be interested in seeing a copy of a HD Stage I download if anyone had it prior to installing the PV. Setup I am curious about is for the 2012 FLHT 103" engines.

As I compare my current map with the stock tune, I am amazed at how a few small changes have such dramatic results.

 

IMO you should be adjusting the Decel Enleanment value, not Accel Enrichment. For DE, a lower value means less leanness, thus richer. I would lower the DE value 10% at a time in the range you are getting the popping.

My AE values are all well below 1.00 at ET > 118° and DE's are <1.00 at all ET's--<.50 at normal operating temps. I have them currently set at the stock values.

 

Thanks for the reply iclick!

I double checked those settings, knock control is set to 1 and max knock retard is set to 8. This is very strange. I still think it must be something that I am overlooking but I have been over it backwards and forwards. Even looking at the logs in Excel, the spark knock F and spark knock R columns have no entries.....all zeros.

Thanks again

 

Are you using the code 319245 when you datalog?

 

No I have not tried that method where it automatically configures the channels to be logged, I am setting the channels up manually. I will try that and see if it makes any difference.

Thanks for the suggestion!

 

That file looks familiar! There is also a link to it in my signature.

 

That is a very good point. Anytime you make manual changes, you should do it in small increments, monitoring the results. The WinPV is a powerful tool that gives you a lot of control.

 

Maybe what you heard wasn't really detonation. If knock control is working properly it would ping for a short time, maybe one second, and then stop as the knock control sets in. If you are getting a continual sound that resembles detonation it may be something else, like something in the valve train.

 

Fairly certain it's a ping. It's never been a continual sound. In fact, it's very difficult to get a ping out of it. I have to really work at it and even then, it's just a few pings.

I have a street nearby that is long and steep, maybe 6% incline. It's 60 mph and 3 lanes. Once I get the motor nice and warmed up, I will run that street and pull it hard from a high gear to really get a load on the motor, only then can I get a couple pings but they disappear quickly.

But even if it were not detonation that I was hearing, withe all the log runs I have made, you expect to see at least a couple of hits. I am going to do another log run today and try it using the auto config with 319245 and see if that makes any difference.

Thanks for the help!

BTW.... I remember when you started this thread, did you ever think it would get this long? Probably one of the most informative threads on the forum!

 

Went on another data log run just now using the code 319245. This is the first time that I finally got some events. Nothing on the front cylinder but a few on the rear. And they are right in the rpm/map range where I heard the ping.

I don't know why it's not logging knock events when you do it the original way by entering signals manually as per the PV manual and JD's basic instruction manual. That is how I had always done it when I had it on my Fatboy. I never did try it the Auto Code way because that feature came out after I had the Fatboy running real well and only used the PV as a dash instrument.

So to recap.... This is a 2012 SG. My PV-1 will NOT data log knock events when setting up signals manually (the original way) VE logging works just fine though. It DOES log knock events when using the auto configuration mode via code 319245.

Not sure if this is a result of a firmware update along the way or not but it's something to be aware of if any of you are using the old method. But quite honestly, I doubt I will ever go back to that method, even if it did work. The cell hit screen is worth it's weight in gold! What a great tool! I wish they had that when I was tuning my Fatboy!