8.4 Tooth / trigger logger and troubleshooting RPM issues 8 TROUBLESHOOTING AND DATA LOGGING
Taking and reviewing a datalog is a required step for troubleshooting this. This datalog extract below (viewed
in Megalogviewer) shows the rpm (yellow trace) dropping to zero and at the same time the "Lost sync count"
increases. The "Lost sync reason" shows reason code 2.
8.4.1 Lost sync numbers
The MS3Pro can report several different lost sync reasons in the data logs. Most of these simply show that there’s
a problem and don’t particularly pinpoint where it is, but some are more specific than others. In particular, if you get
Lost Sync Reason 11 or 17 in a specific RPM band, try changing the ignition input capture and /or second trigger
active edge. Lost sync reason 2 with a VR sensor often means you will need a resistor across the CKP sensor.
0 no problem
1 init error
2 missing tooth at wrong time
3 too many teeth before missing tooth (last)
4 too few teeth before missing tooth (last)
5 1st tooth failed test
6 nonsense input (last)
7 nonsense input (mid)
8 too many teeth before missing tooth (mid)
9 too few teeth before missing tooth (mid)
10 too many teeth before end of sequence
11 too few teeth before second trigger
12 too many sync errors
13 dizzy wrong edge
14 trigger return vane size
15 and 16 - EDIS SAW signal error
17 second trigger not found when expected
20 Subaru 6/7 tooth 6 error
21 Subaru 6/7 tooth 3 error
22 Rover #2 missing tooth error
23 420A long tooth not found
24 420A cam phase wrong
25, 26, and 27 pattern does not otherwise match 420A
28 Pattern does not match 36-1+1
29 36-2-2-2 semi sync failed
30 36-2-2-2 tooth 14 error
31 Miata 99-00 - 2 cams not seen
32 Miata 99-00 - 0 cams seen
33 6G72 - tooth 2 error
34 6G72 - tooth 4 error
AMP EFI MS3Pro manual version 1.202, firmware 1.5.0, 4/21/2017 Page 292
To Next Page
Loading...