Problem is that when I blipped the throttle it would bog and die. Three or Four times in a row... I changed the dashboard to show lost synchs and saw that the count was going up right as it was stalling. I had a VR sensor problem.
This is where I discovered how powerful Megalog Viewer can be. I logged one of the stalls and got this plot:
The very top line is RPM. Right as I blip the throttle the RPM dips to zero but then instantly recovers. Due to noise, I guess, but not sure why I was getting noise from blipping the throttle. Anyway, I was getting a lost synch reason 2. Missing tooth out of sequence. The reason it was stalling wasn't because of the lost synch, but because going to zero RPMs and back up was triggering After Start Enrichment (ASE) which you can see where the blue line goes up. The ECU saw the rise from 0 to 750 rpms as a start and increased fuel!
I adjusted the R52 bias screw 3 1/2 turns to the right from full-left and tried again. Revs nicely now and no synch drops!
This is only 40Hz and a few volts peak-to-peak. The actual VR signal is near vertical at the threshold points. |
I also found that the behavior of the hysteresis pot, R52, is very non-linear. The first 3 turns did almost nothing to hysteresis. Turn 4 starting increasing it. Turn 5 started increasing it quickly. After turn 6 it started to go off the chart very quickly.
The bottom line
I would take both R52 and R56 and turn them to the left about 10x to get them set to zero. Leave R56 alone. Turn R52 5x to the right.
The motor starts and revs with ZERO lost synch counts now.
Thank you! Thank you! Thank you! Thank you! For this info! SYNCED :)
ReplyDelete-Jukka