Ping not shown in logs??
#1
Ping not shown in logs??
I've been having ping issues since I bought the bike (new). I have been trying to resolve this issue with tuning and different gas etc. Now that the PowerVision auto-tune software is out I have been logging and auto-tuning. The ping has persisted. However, I have noticed that is several of the logs there is no spark knock shown when I know that I heard it happening more than once. Some logs show spark knock retard 4deg.
So basically either the damn ECM isn't seeing the knock... or there is something else that sounds exactly like ping but isn't. Any ideas?? What could cause the system to not detect ping? Or what can sound EXACTLY like ping... but not be ping??
Stats:
2011 FLTRU
103"
Jackpot 2-1-2 headers
Stage 1 AC
Dynojet PowerVision
I do have several log and maps that I can email if anyone needs/wants to see them.
So basically either the damn ECM isn't seeing the knock... or there is something else that sounds exactly like ping but isn't. Any ideas?? What could cause the system to not detect ping? Or what can sound EXACTLY like ping... but not be ping??
Stats:
2011 FLTRU
103"
Jackpot 2-1-2 headers
Stage 1 AC
Dynojet PowerVision
I do have several log and maps that I can email if anyone needs/wants to see them.
#3
Yes, I should have specified. I am running stock plugs and wires... in fact they are the original ones from purchase. Bike was purchased in April, it now has approx 5900mi on it.
Logs sometimes show the knock... sometimes they don't.
Logs sometimes show the knock... sometimes they don't.
#4
Pass we should bring this into the Vision tuning thread. I'm seeing the same issue now that I finished calibrating my bike. It's not bad but I definitely hear some pinging that the vision is not picking up. Jamie and I think DJ are watching that thread and this could potentially be some kind of logging bug or it could be the ECM is not seeing it but they need to know about it.
Ron
Ron
#5
Pass we should bring this into the Vision tuning thread. I'm seeing the same issue now that I finished calibrating my bike. It's not bad but I definitely hear some pinging that the vision is not picking up. Jamie and I think DJ are watching that thread and this could potentially be some kind of logging bug or it could be the ECM is not seeing it but they need to know about it.
Ron
Ron
#6
#7
I've been having ping issues since I bought the bike (new). I have been trying to resolve this issue with tuning and different gas etc. Now that the PowerVision auto-tune software is out I have been logging and auto-tuning. The ping has persisted. However, I have noticed that is several of the logs there is no spark knock shown when I know that I heard it happening more than once. Some logs show spark knock retard 4deg.
So basically either the damn ECM isn't seeing the knock... or there is something else that sounds exactly like ping but isn't. Any ideas?? What could cause the system to not detect ping? Or what can sound EXACTLY like ping... but not be ping??
I do have several log and maps that I can email if anyone needs/wants to see them.
So basically either the damn ECM isn't seeing the knock... or there is something else that sounds exactly like ping but isn't. Any ideas?? What could cause the system to not detect ping? Or what can sound EXACTLY like ping... but not be ping??
I do have several log and maps that I can email if anyone needs/wants to see them.
I've noticed that these coincide with lean spikes that reveal Lambda readings of 1.15-1.17, which are far leaner than normal, as it should be running no more than 1.0 in that range. I haven't zeroed-in on the cause yet but I'm going to change my in-tank fuel hoses and filter next week, as I may have a high-pressure leak inside the tank. I'm also going to check the vent tube, as any of these may cause a lean spike.
Trending Topics
#8
I don't know if this is related, as I'm not getting any audible knock at all, but I'm seeing occasional knock-retard events in the PV logs, but only at about 60 kpa and 2000-2200 rpm. It almost always starts at 2° and gradually backs-off to 1° and .5°, then back to normal in the span of maybe 20-30ms.
I've noticed that these coincide with lean spikes that reveal Lambda readings of 1.15-1.17, which are far leaner than normal, as it should be running no more than 1.0 in that range. I haven't zeroed-in on the cause yet but I'm going to change my in-tank fuel hoses and filter next week, as I may have a high-pressure leak inside the tank. I'm also going to check the vent tube, as any of these may cause a lean spike.
I've noticed that these coincide with lean spikes that reveal Lambda readings of 1.15-1.17, which are far leaner than normal, as it should be running no more than 1.0 in that range. I haven't zeroed-in on the cause yet but I'm going to change my in-tank fuel hoses and filter next week, as I may have a high-pressure leak inside the tank. I'm also going to check the vent tube, as any of these may cause a lean spike.
What we finally did was change out the base map and start over. THAT worked for us.
Do you guys have different maps you can try? If so... after fiddling with it a bit, try a map change and tell us what you think.
WT
#10
Definitely not valve clatter. The valve train sounds nothing like detonation. It sounds more like a raging sewing machine. The sound I hear sounds exactly like pinging.
I'm thinking it may be that it is either happening at such little aggression or so fast that the sensors don't pick it up or attempt to retard it. Since the logs will only show knock retard..
I'm thinking it may be that it is either happening at such little aggression or so fast that the sensors don't pick it up or attempt to retard it. Since the logs will only show knock retard..