bschnard

iTrader: (4)

Been logging some data runs and seeing lots of lost synch 11 codes. Where can I find a list of error codes for that field?

Thanks

muythaibxr

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 = EDIS
16 = EDIS
17 = didn't received the second trigger when expected in wheel mode

space for more common reasons
plus other special reasons for the custom wheels
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 = 420A
26 = 420A
27 = 420A
28 = 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
35 = Weber-Marelli
36 = CAS 4/1
37 = 4G63
38 = 4G63
39 = 4G63
40 = Twin trigger
41 = Twin trigger
42 = Chrysler 2.2/2.5
43 = Renix
44 = Suzuki Swift
45 = Vitara
46 = Vitara
47 = Daihatsu 3
48 = Daihatsu 4
49 = VTR1000
50 = Rover #3
51 = GM 7X
52 = 36-2-2-2 tooth 30 error
53 = rc51 semi error
54 = rc51 re-sync error tooth 6
55 = rc51 re-sync error tooth 16
56 = rc51 re-sync error tooth 18
57: Nissan CAS: wrong pattern, e.g. slot length increases but should decrease
58: Nissan CAS: longest slot test failed
..
67 = LS1 semi failed
68 = LS1 resync failed
69 = YZF1000 resync failed
*/

muythaibxr

So you probably have noise on the second trigger.

Ken

bschnard

iTrader: (4)

Thanks again Ken and everyone here, I think that may be one of the last issues I have. Got some decent logging runs made yesterday and tweaked the tuning and car seems pretty smooth. I will dig into the leads on the second trigger and if need be completely rerun them. I will also add the capacitor mod for noise just as an added prevention.

I have some dyno runs scheduled for Mid March and we'll see what I come up with for an NA with better than 90,000 miles on the engine. Could be interesting.

muythaibxr

That particular error is nonfatal, meaning as long as the code sees the second trigger when it expects to see it, then seeing it where it doesn't expect to will not cause loss of sync. It'll just warn you that it's seeing some noise.

Ken

bschnard

iTrader: (4)

I'm getting a few intermittent misses, need to check my plugs, etc. I want to get my data logs as clean as possible before the dyno runs. My autocross season starts the first part of March so really excited about getting this beast finally ready to run with the MS.

pmrobert

Would 17 indicate anything in addition to noise on first trigger?

muythaibxr

Noise on the primary trigger or just not seeing the second trigger at all on some occ are the primary faults that could cause that.

Triggering on the wrong edge of one or the other signal could potentially cause that too I think.

Ken