ECMlink ECMLink V3 Full – Firmware Reverting After Key Cycle / Config Not Saving

[Lethal GST]

Has anyone seen this behavior on a ECMLink V3 Full? Car is a 1995 GS-T.
*Firmware reverting after key cycle
*Config changes not persisting but direct Access tables saving normally
*Occasional “Action raised exception” during save attempts

Trying to determine whether this is a known board issue or if the ECU needs to go back to ECMTuning for repair.

Been troubleshooting a recently installed ECMLink setup and wanted to see if this is a known issue. Unit was purchased about a year and a half ago, installed over the holidays, and I’ve been logging the past few weeks.

Software / Firmware
ECMLink Client: 3.46.226
Current ECU Firmware: 3.36.64

Main Issue
The ECU appears stuck on firmware 3.36.64.
Attempts to update firmware to 3.46.226 or save ECU Config changes appear successful — progress bar completes and the CEL flashes indicating a write. However, after cycling the key and waiting for the MPI relay click, the firmware reverts back to 3.36.64 and the ECU Config changes are lost. Weird thing is that Direct Access tables save and persist normally as long as no Config changes were attempted. If a Config change is attempted first, then Direct Access save fails with “Configuration data needs to be saved first.” This happens even though Config reports a successful save. I tried to do a Direct Access save immediately after updating firmware with similar unsuccessful results. Device Status occasionally shows "Action raised exception" during some these failed attempts.

Additional Observation
While troubleshooting I noticed abnormal coolant temp readings. Even though the car has been sitting in garage for almost 48hrs, ambient temp ~77°F but ECMLink logs ~180°F coolant temp. I disconnected ECT signal (Pin 83) at ECU plug and ECMLink showed it dropped to a fixed 97°F. When i did have the car on the road the past couple weeks, coolant temp logs ~229°F and remains static.

Additional checks:
*TPS unplug test behaved normally in logs (voltage dropped to zero when unplugged)
*As mentioned earlier, ECT wiring and sensor verified at ECU pins.

Right now the is running extremely rich:
~8.8–9.5 AFR at idle (confirmed on my AEM X-series wideband). I'm thinking Since ECU Config changes don’t persist (for example, I can't enable NB sim), closed loop never appears to activate and fuel trims are not relearning.

Any help would be greatly appreciated.

 

[steve]

This first part really sounds like an issue for ECMTuning. I assume you have contacted them.

Sadly the only things close to this I find is unanswered back in 2019 https://www.dsmtuners.com/threads/ecmlink-not-saving-modifications.522152/

 

[Lethal GST]

This first part really sounds like an issue for ECMTuning. I assume you have contacted them.

Sadly the only things close to this I find is unanswered back in 2019 https://www.dsmtuners.com/threads/ecmlink-not-saving-modifications.522152/

Thanks Steve. Sounds like a similar issue, but like you said, unanswered. I reached out to ECMTuning over the weekend, waiting for response.

 

[steve]

Let us know your progress and what you find out.

 

[Lethal GST]

Unfortunately I haven't received a reply yet. I sent email last Saturday and followed up again on Wednesday. I used the email listed on the website ([email protected]). Is there different email address I can try?

 

[Lethal GST]

Ended up sending the ECU in since there was a strong likelihood there needed to be a physical repair. Received response back this morning:

"We've examined your ECU. The ECU is unable to save settings to ECMLink flash memory because of damage to the ECU due to capacitor leakage."

I approved repairs so will update this thread with the outcome once I receive ECU.

 

[steve]

Thank you that's a useful piece of information to add to the list.