First, I want to thank the administrators for moderating an excellent forum. I’ve been building my car over the last 4 years and now that I’m close to having it back on the road, it’s been a very useful idea generator.
I have a heavily modified 1965 Mustang that I’ve owned since 1989. My car has a junkyard harness from a 90 Mustang and runs an A9L computer to control a 347. It runs an E cam, Edelbrock Performer RPM heads, Trick Flow Track Heat intake, 75 mm throttle body, 30 lb/in injectors, and 10.5:1 compression. The trans is a T5 and it runs a 4:11 geared 9 inch with a TruTrac. It was built like this in 2009 and was a strong runner until an unfortunate accident in 2015 necessitated a comprehensive rebuild. The car is street driven, but is mainly used for autocross.
I’m having an intermittent problem that I’ve been working for many weeks where she sometimes refuses to rev past 2500 RPM. When this happens the car will cruise along just fine at low RPM. This is sometimes accompanied by the tach needle fluttering, or the tach not working at all. On a recent test drive she was running strong, but when I rolled up to a stop sign I could tell something had changed. The idle speed was noticeably lower and the tach was fluttering erratically. I limped home keeping the revs below 2000. I’ve been through the entire harness several times and have good fuel and spark. It has a brand new ATI balancer and the 6AL was gone through by MSD. I had been running timing conservatively set at 10-14* BTDC, but began to suspect that the computer was no longer reliably commanding timing. To test this, I locked the timing out at 26* BTDC (SPOUT removed). Since then, I’ve taken her out for several test drives and she has come alive. The power is good; she’ll break the 305 RE-71Rs loose at 30 mph in second gear, and the tach has been working. The car has never thrown any ignition or fuel related codes. My conclusion is that the A9L must have been damaged in the accident. Is this adding up? Timing locked out at 26 is not a long term solution.
I’ve been reading about the MS2PNP and it seems that it has more than enough capability to run my NA setup - any thoughts? Is there a tune available that will get my 347 running?
My apologies for the long post; thanks for reading.
I have a heavily modified 1965 Mustang that I’ve owned since 1989. My car has a junkyard harness from a 90 Mustang and runs an A9L computer to control a 347. It runs an E cam, Edelbrock Performer RPM heads, Trick Flow Track Heat intake, 75 mm throttle body, 30 lb/in injectors, and 10.5:1 compression. The trans is a T5 and it runs a 4:11 geared 9 inch with a TruTrac. It was built like this in 2009 and was a strong runner until an unfortunate accident in 2015 necessitated a comprehensive rebuild. The car is street driven, but is mainly used for autocross.
I’m having an intermittent problem that I’ve been working for many weeks where she sometimes refuses to rev past 2500 RPM. When this happens the car will cruise along just fine at low RPM. This is sometimes accompanied by the tach needle fluttering, or the tach not working at all. On a recent test drive she was running strong, but when I rolled up to a stop sign I could tell something had changed. The idle speed was noticeably lower and the tach was fluttering erratically. I limped home keeping the revs below 2000. I’ve been through the entire harness several times and have good fuel and spark. It has a brand new ATI balancer and the 6AL was gone through by MSD. I had been running timing conservatively set at 10-14* BTDC, but began to suspect that the computer was no longer reliably commanding timing. To test this, I locked the timing out at 26* BTDC (SPOUT removed). Since then, I’ve taken her out for several test drives and she has come alive. The power is good; she’ll break the 305 RE-71Rs loose at 30 mph in second gear, and the tach has been working. The car has never thrown any ignition or fuel related codes. My conclusion is that the A9L must have been damaged in the accident. Is this adding up? Timing locked out at 26 is not a long term solution.
I’ve been reading about the MS2PNP and it seems that it has more than enough capability to run my NA setup - any thoughts? Is there a tune available that will get my 347 running?
My apologies for the long post; thanks for reading.