linuxman51
07-29-2005, 01:52 AM
So in light of a few recent issues that have crept up in cars i've been working on, I thought i'd post up about this (there are a few obscure posts about it on msefi, but it took me several days of digging to figure out what i'd fudged).
If your megasquirt starts turning the fuel pump relay (or just the fuel pump led) on and off, its in "dead mode", i.e. its got a fault code indicating a configuration error. (be glad it tells you and doesnt just check out, you'll hate the next part tho). Save what you've got msq wise, so you can look at it and get most of your stuff back, but its usefulness as a good configuration has come to an end. the remedy i've found (and there might be a proper fix on msefi, but i think this is the general consensus) is, you get to re-upload the firmware now, and go back and figure out where things went wrong. Also note that this only happens after you've power cycled the megasquirt, so reflashing and loading the old stuff back in will only get you more confused (or irritated).
Common causes:
Having something turned off somewhere, but a subsystem of it on elsewhere.
Example (guess where this one's coming from): turning of ms&s mode and leaving spark output on fidle. CRRASSSSH. If you're not using ms&s and dont have a use for the fidle wire, just leave that **** alone and ignore the extra drop down menu (trust me on this one :) )
Also, to avoid the road side i fragged my config giant **** in the ass, unhook your injectors (or at least the power to them) before uploading new firmware, it will flood your motor out (again, ask me how i know....)
If ms isnt running your fuel pump relay and you've got the fuel pump led doing something else, another way to tell if you've hosed your **** is by looking in megatune with the key on but not cranking, rpm will read 2, and the fuel pump light will turn on and off.
Reloading a good map at this point wont bring it back. tried that too.
If your megasquirt starts turning the fuel pump relay (or just the fuel pump led) on and off, its in "dead mode", i.e. its got a fault code indicating a configuration error. (be glad it tells you and doesnt just check out, you'll hate the next part tho). Save what you've got msq wise, so you can look at it and get most of your stuff back, but its usefulness as a good configuration has come to an end. the remedy i've found (and there might be a proper fix on msefi, but i think this is the general consensus) is, you get to re-upload the firmware now, and go back and figure out where things went wrong. Also note that this only happens after you've power cycled the megasquirt, so reflashing and loading the old stuff back in will only get you more confused (or irritated).
Common causes:
Having something turned off somewhere, but a subsystem of it on elsewhere.
Example (guess where this one's coming from): turning of ms&s mode and leaving spark output on fidle. CRRASSSSH. If you're not using ms&s and dont have a use for the fidle wire, just leave that **** alone and ignore the extra drop down menu (trust me on this one :) )
Also, to avoid the road side i fragged my config giant **** in the ass, unhook your injectors (or at least the power to them) before uploading new firmware, it will flood your motor out (again, ask me how i know....)
If ms isnt running your fuel pump relay and you've got the fuel pump led doing something else, another way to tell if you've hosed your **** is by looking in megatune with the key on but not cranking, rpm will read 2, and the fuel pump light will turn on and off.
Reloading a good map at this point wont bring it back. tried that too.