DIYPNP crank and cam sensor 99/00
 

The instructions on the DIY site don't say which two connections are the crank and the cam sensor.

http://www.diyautotune.com/diypnp/ap...0-18bp-mt.html

Any idea where the cam and crank are hooked up to the DIYPNP?

Opto in - 3j
vr2 in + 3h

Thanks, I finally backed in to it. Will have VVT control soon!!!

What should the out put of the crank sensor look like in comparison to the cam sensor? (on a scope)

Mine looks like neither. 2005 engine in a 99/00.

http://lh4.ggpht.com/_-G4gMz5adZc/TJ...152/myvvt1.jpg

You asked what they look like on a scope, not what they look like in TunerStudio's composite logger. When viewed on a scope, the cam and crank sensors of any 1999 through 2005 Miata look like the upper pair of traces in the image I posted.

I've never actually used TS's tooth logger, so I'm afraid I can't tell you how to interpret it.

Sorry, we have been doing both and I didn't have a way to post the traces from a Textronix 466 scope. Does the image I posted look correct for a composite log? Thanks for your help.

Since nobody else has chimed in yet, all I can say is "I don't know."

I tried using the tooth logger once, back when I was having a misfire that I suspected (and later proved, by elimination) was caused by dropouts in my crank sensor reading. But since I have an MS1, the tooth logger proved to be pretty much useless in troubleshooting that problem owing to the MS1's inability hold more than 93 samples at a time.

So it's all Greek to me.

those red lines shows it's reading signals it wasn't expecting...

I'm not sure what any of the lines mean. Neither the green line nor the blue line actually depict the raw crank sensor- they're both showing evenly-spaced events, whereas neither crank nor the cam sensor are evenly spaced. The four crank teeth are arranged in two groups such that the gaps are roughly 70° - 110° - 70° - 110°.

Since he's looking at the "composite logger" rather than the "tooth logger", I simply haven't a clue what's actually being shown. It bears no relation to an NB crank or cam signal that I can see.

green is cam, blue is crank, red is error. you dont want red lines :)

Then something is very, very wrong.

One other thing:
It's actually quite easy. Point a digital camera at the screen and take a picture. Depending on your scope's persistence, sweep time and beam intensity, you may need to play with the camera's shutter speed to get a clean shot. Back in ye olde' times, there were special fixtures for doing precisely this with Polaroid cameras.

yeah, the red is showing that it logged an event it wasn't expecting.

I don't even mean the red. You could take that trace away and the green & blue traces would still look absolutely nothing at all like an NB's crank and cam sensor signals.

Again, I'm making assumptions here, as I don't have any first-hand knowledge of how the composite logger works, but it's certainly not display anything that, to my eyes, looks like a Miata crank/cam signal.

Something is wrong. This what NB triggers look like on a composite log:
(note the similarity to Joe's scope capture)

http://img535.imageshack.us/img535/1...acomposite.jpg

Thanks Ben, that is what I needed to see. Thanks to everyone else that offered advise as well.

How are you generating the log that you posted? It's what I would expect from a B6T 4/1 CAS. Looks nothing like a Miata wave form.

that's weird Ben, my '00 looks like this.
Notice my cam signal is upside down. Also each time there's a cam trigger, I get that same trigger on the crank signal. Those are not there in your traces it seems. Could you zoom in a bit further on your signal?
According to Joe's capture they shouldn't be there. The car runs fine although it does take a long time to sync (5-6 full cycles).
Any ideas what could be causing this? I'm using Joe's input circuits on a V3 board.

http://dl.dropbox.com/u/3961412/composite.png

Frank,
Not sure what to make of that. The car runs, so it seems that it's more likely a TunerStudio visualization error than an actual error with your trigger signals. You might want to save the .csv and send it to Phil Tobin.

You should be able to look at a composite log and then be able to draw the car's trigger wheel. You can do that off the log I posted.