post #33 in this thread - nevermind.

And, I must have had a major brainfart.. I looked at old pics of my gauge cluster (key on), I do not see a CEL there..
My bad.. Again.

Here:

https://www.miataturbo.net/picture.p...pictureid=1137

I was getting worried. Do know that your MS does have a working CEL output if you want to use it - pin 13 on the top connector.

I will definitely look into that.

I also have question on knock intensity for you, but I need to finish this speech I am working on before I dig into the laptop for datalogs..

lol he got one on post #33.

Why u make fun of me Brain?

i mean its kinda funny that someone gave u a neg on that post, im hoping it was a misclick.

We'll never know..

well i mean i could figure it all out, but omg effort.

Would this make it worth your while?

https://www.miataturbo.net/attachmen...ine=1337950523

What's intermittent here, ground or 12V?
Thanks..

Wow, I've never seen anything like this before. Did it start doing it after a while? I haven't seen this on any of your previous logs.

It's gotta be one or more grounds. Values would be hitting "0" if it was the power supply.

All values seem to be skyrocketing, some in sysnc, some on their own.

post on msextra. but im goign to say its a grounding issue, or something's shorting.

Found the culprit behind that weird log...

Today I checked everything and could not get the car to repeat the weirdness it had displayed.
Took a bunch of logs, did wiggle tests, did all I could, and no problems.

Then, I had an idea:
I plugged in my headphones, and the mic input to the laptop.
Bang. The problem came back in about 5 minutes.

Interference!

Over the past couple days, I built a couple of bolt on mics to listen for knock.
The idea was to plug the mic into the laptop via a two meter shielded cable, and use my headphones for listening.

I even downloaded a few programs (spectrum analyzers, etc) to play with the system.
Turns out, the setup interferes with MS big time.

Maybe I will use a second laptop (my wife's) to listen for knock.

Looks like the intereferce is on the serial port data received, not on the actual MS data, or else the engine would act really erratic.

Actually, it DID act funny. I had a bunch of high RPM misfires when this was happening.

I removed the microphone cable and the headphones altogether, and none of that is happening anymore.

On an unrelated note, I am making some progress..

Here is my AFR table:

https://www.miataturbo.net/attachmen...ine=1338507153

Ignition Advance:

https://www.miataturbo.net/attachmen...ine=1338507153

And this is what VE looks like so far:

http://img848.imageshack.us/img848/3724/70909216.png

I still have a an unintended table switching problem. The water in the tanks may be sloshing too hard under really heavy acceleration. (I test the car on an uphill section, to really load the engine, that may be making the sloshing worse)
I can see that by examining the ign advance in the logs.
Is there a quick way to check which table is active at any given time without taking my eyes off the road for too long?

On second thought, I will connect a LED to the water injection low water output to test my theory.
If that is not the case, I will have to make a manual switching system.

More stuff to play with!

And, here is how I installed the MS:

https://www.miataturbo.net/attachmen...ine=1338508174

I don't like the AFR table. What is your AFR at 130kPa? If it is more than 12...that's no good.

As for the table switching...there are indicators available in TS, called Fuel Tbl Sw and Spk Tbl Sw. They will go green when the switch is on.

If I don't do that it dips far too low (rich) as I go past the 0psi (100kpa) mark.