More thoughts on the Andrews 57
#12
08-28-2014, 02:10 PM
I just threw a comment on Lowcountry Joe's thread. https://www.hdforums.com/forum/13153639-post101.html
My bike was sluggish in the lower ranges (below 2200 rpm) I increased the timing by 2* and set my afr to 13.9 and it fixed the problem.
My bike was sluggish in the lower ranges (below 2200 rpm) I increased the timing by 2* and set my afr to 13.9 and it fixed the problem.
#13
08-28-2014, 06:59 PM
If interested here is a SEPST map that I had done for a couple of other bikes. Try it if you like or just look at it. Sure am glad you posted that .dt0 as .docx as I didn't even think of that as the zip is still to large.
#14
08-28-2014, 07:38 PM
Cruiser
Join Date: Feb 2011
Location: Indiana
Posts: 159
Likes: 0
Received 0 Likes
on
0 Posts
#15
08-30-2014, 12:28 AM
I think that is the file you sent me before. I tried it but still had some pinging.
I went with the 0044sdf004 and copied my old timing charts from my stage one tune into it. That got rid of most of the pings. I still had to drop a few cells to get rid of a few occasional pings.
I'm at a loss trying to figure out why my bike is so prone to pinging. I've had to drop some cells 15 degrees. If you open my file and compare the working set to the original you can see how much I had to take out. I know our gas isn't the best but I only use 91 which is about as good as it gets around here.
#16
08-30-2014, 03:24 AM
I think that is the file you sent me before. I tried it but still had some pinging.
I went with the 0044sdf004 and copied my old timing charts from my stage one tune into it. That got rid of most of the pings. I still had to drop a few cells to get rid of a few occasional pings.
I'm at a loss trying to figure out why my bike is so prone to pinging. I've had to drop some cells 15 degrees. If you open my file and compare the working set to the original you can see how much I had to take out. I know our gas isn't the best but I only use 91 which is about as good as it gets around here.
I went with the 0044sdf004 and copied my old timing charts from my stage one tune into it. That got rid of most of the pings. I still had to drop a few cells to get rid of a few occasional pings.
I'm at a loss trying to figure out why my bike is so prone to pinging. I've had to drop some cells 15 degrees. If you open my file and compare the working set to the original you can see how much I had to take out. I know our gas isn't the best but I only use 91 which is about as good as it gets around here.
#17
08-30-2014, 01:39 PM
. You do know if you accelerate at 3000 in higher gears any the timing map jumps to the 100 Kpa area. I have run lots of logs and looked at it in PV and the only time it will stay in the 70 to 80 kpa area is under light acceleration going up a hill or something.
I looked at your file and my map is still 15 degrees down from that, where it needs to be to prevent pings. The thing about the map jumping to 100 kpa, I don't think it does, my recordings never show anything over 85 kpa, probably because I'm over 5000 ft in elevation. The areas where it was pinging show rpm and kpa and timing in the expected cells. For instance, a ping on the rear 3000, 80, will show the timing dropped 2 degrees to 19 degrees and the cell at that location will show 21 degrees, so it seems to match the map. I guess my question is, should I try to eliminate all KR events or just eliminate the obvious audible ones that continue?
I looked at your file and my map is still 15 degrees down from that, where it needs to be to prevent pings. The thing about the map jumping to 100 kpa, I don't think it does, my recordings never show anything over 85 kpa, probably because I'm over 5000 ft in elevation. The areas where it was pinging show rpm and kpa and timing in the expected cells. For instance, a ping on the rear 3000, 80, will show the timing dropped 2 degrees to 19 degrees and the cell at that location will show 21 degrees, so it seems to match the map. I guess my question is, should I try to eliminate all KR events or just eliminate the obvious audible ones that continue?
#19
08-30-2014, 11:08 PM
. You do know if you accelerate at 3000 in higher gears any the timing map jumps to the 100 Kpa area. I have run lots of logs and looked at it in PV and the only time it will stay in the 70 to 80 kpa area is under light acceleration going up a hill or something.
I looked at your file and my map is still 15 degrees down from that, where it needs to be to prevent pings. The thing about the map jumping to 100 kpa, I don't think it does, my recordings never show anything over 85 kpa, probably because I'm over 5000 ft in elevation. The areas where it was pinging show rpm and kpa and timing in the expected cells. For instance, a ping on the rear 3000, 80, will show the timing dropped 2 degrees to 19 degrees and the cell at that location will show 21 degrees, so it seems to match the map. I guess my question is, should I try to eliminate all KR events or just eliminate the obvious audible ones that continue?
I looked at your file and my map is still 15 degrees down from that, where it needs to be to prevent pings. The thing about the map jumping to 100 kpa, I don't think it does, my recordings never show anything over 85 kpa, probably because I'm over 5000 ft in elevation. The areas where it was pinging show rpm and kpa and timing in the expected cells. For instance, a ping on the rear 3000, 80, will show the timing dropped 2 degrees to 19 degrees and the cell at that location will show 21 degrees, so it seems to match the map. I guess my question is, should I try to eliminate all KR events or just eliminate the obvious audible ones that continue?
Even with the altitude problem I would still take your altitude and low humdity to the mess we have here in summer. Been between 95 and 98 with very high humidity for the last few days. Not fit for anything outside.
A weak fuel pump or regulator could cause the same thing. Another thing I have done on things when nothing else works is to unplug the O2 sensors. Have found couple of problems doing this. Absolutely won't hurt anything. Will set code but doesn't turn on light. Got my curiosity peaked as to what this is. It is one thing trying to Internet diagnose a problem versus It being your own bike. I know it is heavy on your mind.
#20
08-30-2014, 11:13 PM
We had the same problem with son in laws 12 limited this summer in Yellowstone. It wasn't running up to par as to the way it runs in Louisiana. I did a data log on it and it will only go to 80Kpa. We checked every thing including cleaning the filter and nothing seemed to help it. Didn't try to change the tune. He has TW555, 30 tooth pulley, PV, Power duals, Kompressor heads at 10.5. He could still out run my 14 Limited with PV and slipons so he was happy. the 14 didn't run much different at 7000 feet than it does at 90 feet. I sent an email to DynaJet and they told me it wasn't uncommon to only show 80% Kpa at altitude. When we got back home the 12 was back to normal. To me it is curious that yours and his are doing the same thing so I guess it is the altitude. He didn't have any pinging or data log pinging. I did up another map that moved VE and Timing to the left putting timing from 100 to the 80 column. Did same with VE. Looks little un orthodox, but who knows. That 2 degrees timing ping on the data log I bet was on the front cylinder. For some reason the front seems to be the one that pings first. Make sure the plug wires are plugged and snapped onto the plugs and to the coil. Any loose connection on the Ion sensing circuit will cause it to fake detect a ping. If not over 3 degrees and not an isolated condition or audible I generally don't try to fix it. You are absolutely correct it does take away what ever it detects. 2 ping degrees on a 21 degree cell will display 19.
Even with the altitude problem I would still take your altitude and low humdity to the mess we have here in summer. Been between 95 and 98 with very high humidity for the last few days. Not fit for anything outside.
A weak fuel pump or regulator could cause the same thing. Another thing I have done on things when nothing else works is to unplug the O2 sensors. Have found couple of problems doing this. Absolutely won't hurt anything. Will set code but doesn't turn on light. Got my curiosity peaked as to what this is. It is one thing trying to Internet diagnose a problem versus It being your own bike. I know it is heavy on your mind.
Even with the altitude problem I would still take your altitude and low humdity to the mess we have here in summer. Been between 95 and 98 with very high humidity for the last few days. Not fit for anything outside.
A weak fuel pump or regulator could cause the same thing. Another thing I have done on things when nothing else works is to unplug the O2 sensors. Have found couple of problems doing this. Absolutely won't hurt anything. Will set code but doesn't turn on light. Got my curiosity peaked as to what this is. It is one thing trying to Internet diagnose a problem versus It being your own bike. I know it is heavy on your mind.
Sounds a lot like my issue in Yosemite. Very curious. It felt like it was one lunging for a couple hours with a weak wheezy idle.
Mark