fried ignitor?
#1
fried ignitor?
assuming this is the issue since i was an idiot and got ahead of myself this weekend. did a couple "file->open->burn to ecu" cycles without unplugging anything...
now i have no tach signal to the dash. car starts, drives, and runs like a champ, but no tach. megasquirt registers the tach signal, and as i mentioned, car runs great.
my assumption correct?
now i have no tach signal to the dash. car starts, drives, and runs like a champ, but no tach. megasquirt registers the tach signal, and as i mentioned, car runs great.
my assumption correct?
#4
Will that ......file -> open..... really burn the ignitors?? I have done that a few times and I just put new ones in from toasting them?? I sure hope mine are not jacked because I did it once tonight and now the car is cutting out even worse than before. It did not seem to cause a problem in the past couple days though?? When I turned the ignition on I heard a pop and then went to see what it was and it smelled electrical. I cant find any damaged wires or anything though, my tach works, and the car drives. It just stumbles all the time????????? DANG IT!! Let me know if you think that I toasted mine as well....again....
#7
Elite Member
iTrader: (1)
Join Date: Jun 2006
Location: Warrington/Birmingham
Posts: 2,642
Total Cats: 42
that said why should there be ignition settings being changed?
#9
I burn fuel maps and things like that as I change them while the car is running, but flashing the entire .msq is what fries them isn't it? I though it holds the ignition high or something and it gets too hot thus burning things out. I also have a switch inline with my ignition wires so when I want to do full reflash i just hit the switch and burn away firmware or msq. It's pretty nice, the 1.8 coils are a bitch to get to to take the coil connectors off.
#18
Supporting Vendor
iTrader: (5)
Join Date: Jun 2006
Location: Duluth, GA 30097
Posts: 803
Total Cats: 0
I never unplug my ignitors to load a new .msq file. I did it several times with a car on the dyno today. It's flashing firmware that is the problem-- the ignition settings in the firmware's default map are what the Miata's ignitor needs. So when you flash the firmware, you're essentially loading a map with ignition settings that are bad for your car and will leave the ignitors on all the time, or just long enough to cook them. That's why you have to load a proper map for your car after loading the firmware in order to correct this, and then you can plug your ignitors back in.
__________________
Jerry a.k.a. 'FoundSoul'
DIYAutoTune.com
'91 Miata BEGi S3 GT2560 w/ MSPNP - 14.1psi - 253whp, 232wtq
'95 Miata n/a
A few other cars....
Jerry a.k.a. 'FoundSoul'
DIYAutoTune.com
'91 Miata BEGi S3 GT2560 w/ MSPNP - 14.1psi - 253whp, 232wtq
'95 Miata n/a
A few other cars....
#20
then i'm confused as to when i'm actually performing a "reflash"
i didn't do anything with new firmware, or anytihng of the sort. all i've done is change settings and open/burn a couple new .msq files. so unless i have a grand coincidence and had the tach output of my ignitor die on me in the last couple weeks, it seems as if it can happen when performing standard .msq burns.
i didn't do anything with new firmware, or anytihng of the sort. all i've done is change settings and open/burn a couple new .msq files. so unless i have a grand coincidence and had the tach output of my ignitor die on me in the last couple weeks, it seems as if it can happen when performing standard .msq burns.