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
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
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
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:

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)
should look like this:

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)
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
Thanks for your help
Thread
Thread Starter
Forum
Replies
Last Post
Motorsport-Electronics
ECUs and Tuning
0
Sep 5, 2015 08:02 AM







