Put some drive time in today tested more carefully with the 0x12045 Maximum Spark Advance set to 58 and still noticing some skipping. It's happening at the same RPM so I think it may be an issue with the controller that wasn't manifesting with lower spark advance numbers. I haven't yet ruled out the possibility it's the EST line not being "fired" by the PCM - hoping to isolate the problem on the drive home.
kur4o I had some spare time over the past couple days to pick through your video and logging more carefully. I think we had a bit of misunderstanding - I was under the impression the crank attempt in the first video 'MOV02023.MP4' was included in your debug log 'log2.txt'. I also tried to match up your annotation and found it wasn't quite in sync with the numerous crank attempts, which lead me to believe there was some other problem happening in the 2nd one. So I went through it frame by frame to find timestamps and correlate the sequence and what happened with each attempt. The attached log has my timestamps in it, and everything seems to match up.
Of all these sticking events, none appear to be caused by anything other than the controller dwelling coils before the PCM has started to control the EST line. In fact if you look at attempts 8 and 9 you can clearly see "stuck" coils from attempt 8 being fired in attempt 9 when the sequence comes back around to them. So I'm completely confident this isn't part of your no-run / incorrect sequencing issue. Preventing this should be simple and I'll try to do that this weekend, but it would only pose a problem with the D585 coils that fire when they reach dwell limiting.
The only thing I'm seeing here that worries me at all is crank attempt 14 beginning at 2:28.24
Code:
strtDegs=57 strtLRCnt=2 strtSeqDeg=0 invSeq=0 firstCyl=7
d cyl=7 dwlDgs=15 ectTbl=0 qIdx=1
f cyl=7 saDgs=10
c @ 89 dwlTgt=6 dwlDgs=16 qIdx=2
d cyl=2 dwlDgs=16 ectTbl=0 qIdx=2
f cyl=2 saDgs=9
c @ 90 dwlTgt=7 dwlDgs=16 qIdx=3
d cyl=1 dwlDgs=16 ectTbl=0 qIdx=3
f cyl=1 saDgs=10
c @ 89 dwlTgt=7 dwlDgs=17 qIdx=4
d cyl=8 dwlDgs=17 ectTbl=0 qIdx=4
f cyl=8 saDgs=10
c @ 90 dwlTgt=8 dwlDgs=18 qIdx=5 << TDC semaphore, advance sequencer to #4
f cyl=4 saDgs=10 << fire coil #4 but hadn't been dwelled
c @ 90 dwlTgt=7 dwlDgs=17 qIdx=5 << TDC semaphore, advance sequencer to #3
c @ 90 dwlTgt=76 dwlDgs=86 qIdx=5 << TDC semaphore, advance sequencer to #6
d cyl=6 dwlDgs=86 ectTbl=0 qIdx=5
f cyl=6 saDgs=19
f cyl=6 saDgs=-1
c @ 89 dwlTgt=2 dwlDgs=12 qIdx=1
Watching and listening carefully even at 1/3 speed it's not completely clear if all this happened before or after the moment you released the key and disengaged the starter. It may have been the engine turning backwards slightly from the compression built up in cyl #4.
Edit: Looking at the last TDC semaphore here this is almost certainly the engine turning backwards because the dwell calculation (what the 'c' stands for here) is wanting 86 degrees of dwell. That's a number more appropriate at > 2000 RPM, which you obviously weren't anywhere near.
Whatever the case, you might want to re-verify that C2 on the low res input is the correct part - should be marked 102, not 104.
If there's a noise issue on your low res line that could cause sequencing issues. You might try re-organizing your wire routing to make sure the inputs for the board are separate from the coil outputs. It could also have been related to the electrolytics being reversed.
Bookmarks