Hi guys,
I've got a problem with my ms2 v3 hei 7 pin tach signal. I buildt the ms2 using the hei description on de ms site and added the 100ohm resistor and jumper update as described on DIYAutoTune.
The problem is as follows if i'm cranking he rpm signal is perfect in the logs but when the engine catches rpm jumps to about 600 and right after that it drops to zero and to the cranking rpm again. Also the tach count resets to zero. This repeats every time the engine catches(tries to start).
To me this looks like the rpm signal isnt strong enough to follow a rapid change of engine rpm.
What could this be?
Thanks a lot,
Edd
Hei tach problem
Forum rules
Read the manual to see if your question is answered there before posting. Many users will not reply if the answer is already available in the manual.
If your question is about troubleshooting, configuration, or tuning, you MUST include your processor type (MS-I or MS-II) and code version in your post. If your question is about PCB assembly or modifications, you must also include the main board version number (1.01, 2.2 or 3.0). For tuning/troubleshooting questions, please attached a datalog and your MSQ file to your post.
If you have questions about MS1/Extra or MS2/Extra code configuration or tuning, please post them at www.msextra.com Such questions posted here will be moved to: a temporary MSextra sub-forum, where they will be removed after 7 days
The full forum rules are here: Forum Rules, be sure to read them all regularly.
Read the manual to see if your question is answered there before posting. Many users will not reply if the answer is already available in the manual.
If your question is about troubleshooting, configuration, or tuning, you MUST include your processor type (MS-I or MS-II) and code version in your post. If your question is about PCB assembly or modifications, you must also include the main board version number (1.01, 2.2 or 3.0). For tuning/troubleshooting questions, please attached a datalog and your MSQ file to your post.
If you have questions about MS1/Extra or MS2/Extra code configuration or tuning, please post them at www.msextra.com Such questions posted here will be moved to: a temporary MSextra sub-forum, where they will be removed after 7 days
The full forum rules are here: Forum Rules, be sure to read them all regularly.
Re: Hei tach problem
here is a log where it started died right away, I cranked again started and died right away
You do not have the required permissions to view the files attached to this post.
-
kjones6039
- Master Squirter
- Posts: 618
- Joined: Sat Jul 22, 2006 7:02 pm
- Location: Eureka, Nevada USA
- Contact:
Re: Hei tach problem
I think we would be interested in seeing your msq also...........
Ken
Ken
1979 Corvette - 383 CID SBC w/ Holley Pro-Jection 900 CFM TBI, 4-85 lb lo-z injectors & Walbro 255 pump
MS2 v3 w/ms2extra 3.4.0 Release
36-1, Delphi LS2/7 coils in wasted spark, driven by v2.0 logic board from JBPerformance
Spartan Lambda Sensor from 14point7
MS2 v3 w/ms2extra 3.4.0 Release
36-1, Delphi LS2/7 coils in wasted spark, driven by v2.0 logic board from JBPerformance
Spartan Lambda Sensor from 14point7
Re: Hei tach problem
Your right i havent got my current log on this computer but here s the one i used to base mine on. Only the fidle in this one is different. I use fidle to control the vref for the ignition timing
You do not have the required permissions to view the files attached to this post.
-
drholl
Re: Hei tach problem
I had a similar problem starting mine. I have an 8 pin HEI. The problem was the wires on the output of the "Limp" relay had gotten reversed. It was an easy fix, but hard to diagnose. Nothing made sense.
In the relaxed mode, before starting and running, I accidentally connected the output to 87A instead of 87. It gave really weird cranking datalogs. If I remember correctly it would try to run BADLY every two seconds during continuous cranking.
Hope this helps.
Holl
In the relaxed mode, before starting and running, I accidentally connected the output to 87A instead of 87. It gave really weird cranking datalogs. If I remember correctly it would try to run BADLY every two seconds during continuous cranking.
Hope this helps.
Holl