3.2.1 firmware update and now no tacho in TS
 

Hi fellas, i have a 93 1.6 and the car was running fine with 3.0.3s firmware. I updated to 3.2.1 and fried my ignitor in the process (i disconnected it while reflashing the firmware but then had the ignition on with the MS powered off). So i decided to go COP (4pin) and have them wired up as per instructions. Now the car won't start.
TS connects with the MS but when i try cranking the the car i'm not getting any rpm in tunerstudio. I've tried reloading the firmware and installing the bootload jumper - but still nothing!
I understand MS gets it's tach signal from the CAS and i've checked the wiring between it and MS and everything seems fine.
I have updated my thermistor tables and i'm kinda at a loss as to what is wrong??
Could it just be a wrong setting in TS? Would trying a different tacho output in TS do any harm?
Thanks

did you reload your msq?

yes i reloaded the msq i had saved before i updated the firmware

what's the composite logger look like when you crank? because sounds like your not getting the signal from the CAS, which doesn't make sense.

Log attached while cranking.
The tps wasn't recalibrated for this log but i had done it after and still the same

composite logger. on diagnostics tab.

Hi Brain is this what you were looking? I tried cranking for about 4 or 5 seconds and got this log

the signals you are inputting from the CAS dont make sense, so you're not syncing.

When i have MS connected to TS the 'Not syncing' box is red. What is not in sync? Sorry for the noob q's but i appreciate your help and have been scratching my head and reading up trying to figure this out for a few days

when the MS interprets the CAS signals correctly.

What could be wrong then? Something internal with the MS (a hardware problem) or a setting in TS?

no it looks like the signals coming in are incorrect. no pattern to them like it should be outputting. check the connection?

I'm just after checking the connections again. I don't have a scope but when i put the multimeter onto the harness on pins 24 and 25 at the db37 i was getting 0v with the ignition ON and 5v when cranking. So it's getting some kind of a signal? Although this 0 -5v is pulsed?

the composite logger is pretty much a scope.

should look like this:

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


where green is the cam, blue is the crank singals. red is the error (was expecting a signal, or a recorded a signal where it wasn't expecting)

Cheers. Is there a possibility that i have a setting wrong in TS and that the CAS is sending a proper signal but my MS is not interpereting it properly because of a wrong setting?

not on the log I saw.

Could the signal be corrupted because of noise from other cables? I had made a harness from the miata ecu plug to the db37 and the CAS wire is not shielded? I think i'll get another ignitor, put the normal plug leads back on, use the old firmware i had running and just start from where i was when the car was running right. I'll see if that gets me anywhere. I know it shouldn't affect the CAS - which is my problem now - but i have to try something.

Thanks for your help