ECMTuning - wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

<h1>V3 Settings Operation</h1> <div class="level1"> </div> <h2>Overview</h2> <div class="level2"> <p> Every once in a while, someone will have their most recent set of configuration changes lost in ECMLink and they'll ask how this can happen. It's a good question, but the answer isn't straight forward because ECMLink was designed to retain settings even when battery power is disconnected for years. </p> <p> So when settings are lost, it's because something in the car isn't working as it should be. And to figure out what that might be, you need to understand a few things about ECMLink's internal design. </p> <p> First, there are two "areas" of ECMLink settings: <b>ECU Config</b> and <b>Direct Access</b> </p> </div> <h2>ECU Config</h2> <div class="level2"> <p> When you make changes in the <b>ECU Config</b> area of V3 ECMLink and click <b>Save to ECU</b>, the settings are stored only in <em>volatile</em> (RAM) memory until the ignition switch is turned off. </p> <p> <b>Pro:</b> This allows for changes to be made to these settings while the engine is running. </p> <p> <b>Con:</b> This leaves those changes subject to loss if battery power to the ECU suddenly drops before the ECMLink code has a chance to move those settings into permanent flash. </p> <p> ECMLink moves those settings into flash automatically when you turn the ignition key off. There's a period of 6-10 seconds in between when the ignition key goes off and the MFI relay powers down (which powers down the ECU). ECMLink makes use of that time to store RAM-based settings to flash. </p> <p> You can also force the ECU to save those settings to flash by making some trivial <b>Direct Access</b> change and saving that to the ECU. More on that below. </p> </div> <h2>Direct Access</h2> <div class="level2"> <p> When you make changes in the <b>Direct Access</b> area of ECMLink and click <b>Save to ECU</b>, the ECU is put into reflash mode and the changes are stored immediately to permanent flash. </p> <p> <b>Pro:</b> Because the settings are stored immediately to flash, the settings can never be lost. </p> <p> <b>Con:</b> This requires that the engine be stopped (so that the ECU can enter reflash mode). </p> <p> It's also worth noting that before the ECU can be put into reflash mode, the ECMLink code first moves all current <b>ECU Config</b> changes into flash. </p> </div> <h2>The issue at hand</h2> <div class="level2"> <p> So what's the issue? Well, there are a couple cases that come up every once in a while where the assumptions above don't apply on a particular car. </p> </div> <h3>Hardwired Power (missing MFI relay)</h3> <div class="level3"> <p> Some cars (very few, but some) do not have a working MFI relay. Either the owner didn't want an MFI relay in the circuit (typically in a race-only setup where all the wiring was completely redone from ground up) or the MFI relay stopped working in someone's car and instead of replacing the MFI relay, they simply wired around it so that the ECU is immediately shut down when the ignition key goes off. </p> <p> In either of those two cases, the ECMLink code does not have a chance to save your RAM-based settings to flash after you turn the ignition key off. So the settings are never stored to permanent memory and are lost when the ECU losses battery power. </p> <p> Your only solution in this case is to either (1) get a working MFI relay set up back in the car (preferred) or (2) always go into <b>Direct Access</b> and make some trivial change to a setting there and hit <b>Save to ECU</b> before you turn the ignition key off. </p> </div> <h3>Low battery voltage while cranking</h3> <div class="level3"> <p> This situation is far more common than the missing MFI relay case. </p> <p> In this situation, someone's car simply does not maintain good battery voltage while cranking. This can force the ECU to reset and lose all factory learned settings (fuel trims, idle settings, etc.). But this will also lose any recent ECMLink <b>ECU Config</b> changes as well! </p> <p> The scenario goes like this. </p> <ol> <li class="level1"> Engine is off and customer makes changes to <b>ECU Config</b> settings.</li> <li class="level1"> Customer hits <b>Save to ECU</b> and then tries to start the engine to test these new settings.</li> <li class="level1"> Battery voltage drops too low while cranking and forces the ECU to reset.</li> <li class="level1"> <b>ECU Config</b> settings are lost and ECU powers back up with previous settings.</li> </ol> <p> <br/> The ECU reset occurs so fast that you don't even really notice it. The only indication you'll have is that the check engine light will come on for 5 seconds like it normally would when the ignition key is first turned on. So watch for this as your clue that something is wrong while you're cranking the engine. If you see your check engine light suddenly come back on, then that's a problem. </p> <p> The other issue you'll run into is that the ECMLink laptop application will have no idea that the settings were lost. So when you look at the settings in the ECMLink application, things will appear as they were when you last hit <b>Save to ECU</b>. If you exit the ECMLink application and start it back up or simply hit "disconnect" followed by "connect", the application will re-read all the settings from the ECU and you'll see that your settings are not what you intended them to be. </p> <p> But unless you do that, ECMLink will just show you what you last saved…not what's really inside the ECU. So that can definitely add to the confusion. </p> <p> By far, the BEST way to solve this problem is to replace the battery with one that is capable of sustaining sufficient voltage to the ECU while cranking. But if that's not possible, you can always go into <b>Direct Access</b> and make some trivial change to a setting there and hit <b>Save to ECU</b> before you attempt to start the engine. That will force the current <b>ECU Config</b> settings to flash so that even if the ECU resets, it will just start back up with your recent changes from flash. </p> </div>