The Central Hub for DSM Community and Information

For 1990-1999 Mitsubishi Eclipse, Eagle Talon, Plymouth Laser, and Galant VR-4 Owners. This is where the DSM platform history is documented and archived. Log in to help us in our mission, and to remove most ads from the browsing experience.

dsmlink not saving

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.

bump

15+ Year Contributor
50
5
Apr 30, 2008
eagar, Arizona
1g dsm v3lite
I have searched with no results except for dsmlink wiki on the ecu reset page which does not apply to me as their work around does not work. I am currently talking with them to resolve my issue.
I am posting this to see if anyone else has had the same problem.
I make a change in ecu config by setting nlts @ 5500rpm. It works as long as I don't turn the car off. Once I turn it off, the setting is back to stock state.
So I go back to config turn nlts back on then go in to direct access make a small change to timing table and flash the ecu. When I flash the cel flashes and the boost gauge either goes max or full vacuum. Then laptop says the ecu flash was successful. I wait a minute shut the car off, turn it back on and everything is back to stock even the small change I made to the timing table.
Thomas @ ecmtuning had me try making a change in config then in live flash the ecu then go back and undo the change in live and flash again but I had the same result.
One thing that seems out of the ordinary is that the asd relay only takes 3 seconds to click after I turn off the car. Thomas said it should take around 10 seconds. Would this affect the flash process?
Thankyou.
 
When you make changes in the ECU Config area of V3 ECMLink and click Save to ECU, the settings are stored only in volatile (RAM) memory until the ignition switch is turned off.

Pro: This allows for changes to be made to these settings while the engine is running.

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

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.

You can also force the ECU to save those settings to flash by making some trivial Direct Access change and saving that to the ECU.

When you make changes in the Direct Access area of ECMLink and click Save to ECU, the ECU is put into reflash mode and the changes are stored immediately to permanent flash.

Pro: Because the settings are stored immediately to flash, the settings can never be lost.

Con: This requires that the engine be stopped (so that the ECU can enter reflash mode).

It's also worth noting that before the ECU can be put into reflash mode, the ECMLink code first moves all current ECU Config changes into flash.


If need a good tune pm my1gdsm for good priced tunes you wont regret!!:hellyeah:
 
The config tab and direct access tabs need saved separately. Any changes you make in config need to be saved from a config tab. Any changes made in direct access need to be saved from a direct access tab. The buttons at the bottom may look the same, but they save different settings to the ECU. In the video above you made changes in both tabs, but only saved from the direct access tab, which is why your clutch cut settings weren't saved the first time.

The second save around you never changed/enabled the NTLS, which is why at 3:58 you're seeing that it's off - you changed the boost gauge display, remember? :)

As for why the DA settings are being reset, that's a whole other issue. I can't say I've run into that, and I would guess Tom/Dave would probably be the best people to troubleshoot that. If I come across something, I'll post it up here. Also, it's the MFI relay that controls the ECU, not the MPI.


Can you try this?
1. Turn key to ON and open ECMlink
2. Look in bottom right corner and let us know what firmware version you have
3. Click Help > About from the top menu bar and let us know what software version you have
4. Open just DA settings and make a change to a block of cells in the OpenLoopMaxOct table (take bottom right corner and turn them all to 11)
5. Click "Copy to ECU" button
6. Count to 10 and then cycle key off and back on, close program, reopen program, and reconnect
7. Go check if DA change is still in OpenLoopMaxOct table (if not, you can stop here)
8. Make a change to the TmngMaxOct table (again, just a big block change somewhere) and click "Copy to ECU" button
9. Count to 10 and then cycle key off and back on, close program, reopen program, and reconnect
10. Go check if DA change is still in TmngMaxOct table

Just post up the results when you get a chance. You don't have to make a video. I'm curious if you just stick with making DA changes if they stick.
 
Well I sent the video to Thomas @ ecmtuning and he figured it out. The delay in the mfi is the problem. The hardware in the ecu controls this delay. Im sending the ecu back to him so he can test it out.
He gave a work around which is to make a change in config (like you said i wasnt hitting the save to ecu in config which was part of the problem) hit the save to ecu then go to DA and make a change and save. This works as I go back in and all my changes are still there. But like Thomas said, its a pain so hopefully the hardware that delays the mfi relay can be fixed or replaced.
When I get my ecu back I will post how it goes.
Thanks Snowborder for your help.
 
Got my ecu back from ecmtuning and everything works now.
They replaced the hardware that controls the relay. Now the delay is around 6 seconds instead of 3.
Those guys are great and fast, they fixed and shipped it back out in the same day!
 
Add Value - Be Respectful - No Trolling - No Misinformation - Participate Often!
Support Vendors who Support the DSM Community

Build Thread Updates

Latest Classifieds

Back
Top