Here's the latest:
Turning off the noise issue has made the issue much better...it has not gotten caught in the RPM signal oscillation since. What it does now is almost always have a period where the RPM signal drops out for a single record in the log, always under heavy load such as full throttle acceleration in 2nd or 3rd gear and around 5k RPM. You can see that issue in records 88 and 110 of the attached log. MSQ is also attached.
I also caught the issue on the Trigger Log...see record 39 of the attached Trigger Logger. I spent hours adjusting R52 and R56 yesterday with no improvement in this issue. I've put a scope on the input signal, but I don't see much change in the shape of the signal with the pot adjustments. It definitely looks like the system is missing another tooth on the 36-1 wheel other than the actual missing tooth. I have the VR sensor about as close to the trigger wheel as possible...less than 1 mm. I don't think the software-based Noise Filter would help with this, as it seems to be just about filtering out probably noise signals based on their timing and duration, and I think my issue is that a real signal is being missed occasionally.
I'm also curious about some of the settings I've always had in the Ignition Options menu and whether they could be part of this issue. I've had "No Prediction" instead of "1st Deriv Prediction" set under "Use Prediction" in the Ignition Options menu. I also had Dwell Type set to "Fixed Duty" instead of "Standard Dwell" which is the setting to use for most installs according to the documentation. Not sure if that matters at all for EDIS, though...
And something really weird: I tried switching the "Spark hardware in use" setting from "JS10 spark" to "Tacho". I didn't change any connections or hardware at all and didn't expect it to work, but it fired right up like that. (It also worked on "Falling Edge" and "Going Low", which surprised me). Anyway, I tried it and the RPM drop seemed to go away. I had to spend about 30-40 minutes retuning the VE table but each time it pulled very smoothly all the way to redline. I also noticed that all of the readings in TS were "changing faster" than they used to...the entire screen of gauges seemed like it was more active, almost like the actual processor itself was working more quickly. I also had to adjust all the PID settings for the WBO2 and CL idle, too, so it really seems like the sensitivity of the whole system was increased. Throughout the whole tuning process, though, the RPMs were smooth all the way to redline. I did notice some very small dips in the RPMs on the way home, but it was happening far less often then when using the JS10 Spark setting.
Olivier
2015-12-05_09.48.21.msq
Before Pot changes - see record 39.csv
2015-12-05_09_modified.msl