I'm wondering if nefmoto has some sort of feature built into it where it detects when your laptop might die before the flashing procedure is complete? I'm only using the basic-free version of nefmoto. its the latest version. Normally when flashing, I watch as nefmoto writes data to the ECU. I move back and forth as I go from watching the multimeter, ensuring I stay above 12v, and making sure nefmoto doesn't have any issues while flashing. Last night I was reflashing my ECU after making a few adjustments in my file and I forgot to check how much battery life my laptop had left before it would die. Basically I started the flash and once I had started the procedure I noticed that I was at around 3% battery
yikes... I frantically watched as nefmoto wrote data to the ECU and at about 65% I realized I was at full blown 0%. I was getting super anxious as I watched nefmoto continue to flash the ECU... 78% 79% 80%... then suddenly it said something to the effect of 88% complete.. writing to ECU memory successful!
I thought to myself... Hmmm thats weird.
I went inside to charge my laptop, worried I may have bricked my ECU or something? normally I watch it go to 100%.. I know that the premium licensed version of nefmoto allows you to reflash your ECU, but nefmoto will save time by ignoring memory blocks that weren't modified and only rewriting the data blocks that have been changed. I'm wondering if the basic-free version of nefmoto will function the same as the premium version if it detects a low battery? as a way of defending the user from incomplete programming? Or could my programming possibly be incomplete and maybe I should reflash the ECU for good measure?
This isn't a huge deal, just thought I would share this experience to see if anyone had any insight or had experienced something similar to what happened here?