openinverter forum

Hi

I have a similar problem, and no tools, I've been doing all this over wifi.

I have the same "Firmware" and "file system" update boxes. The inverter is currently attached to an SDU and installed in the vehicle. Can I do anything over wifi, or do I have to remove the board?

janosch wrote: ↑Mon Sep 26, 2022 8:56 am You are nearly there! There is no bin file for assets, you just upload the html/css/js/png assets directly.
The *.bin file is updated via the button once you have index.html & index.js in place.

https://openinverter.org/wiki/Olimex_MO ... bInterface

Can you open developer console in the browser and go through the upload process and see if there are multiple requests coming through?

Which firmware are you trying to flash? Fellten or OI?

You might have to take it out, but it is worth trying a few things over wifi first.

Finally put Janosches fix in place
https://github.com/jsphuebner/esp8266-w ... 47da6fa7c5

Thats great! I completely forgot about this

Regarding the topic "ESP file system gets full due to multiple bin files", I understand that one fix is to delete the bin file after successful update. The above commit implements this fix in the javascript, means: in browser. Right?
This helps in case of successful flashing, but for the unsuccessful cases (I have them), the bin file stays in the ESPs flash file system, and if I use different file names (I do), the file system will be full sooner or later.
I propose: In the ESP code, when starting up, just delete all bin files. Or are there use cases, that the bin needs to survive a power cycle of the ESP?
Together with the feature "javascript deletes the bin file after successful flashing" this should avoid the out-of-flash-memory situation. There is still a small gap, if somebody has a lot of failed updates with different file names and never cycles the ESPs power. Maybe there is a better trigger for the DeleteAllBinFiles(), e.g. when the main page is loaded or the node ID is changed.

Indeed the bin files don't really need to be kept. When uploading a new one all existing ones could be deleted.
The javascript fix has the advantage for now that the module doesn't need to be upgraded with special tools but just by uploading the .js file

Next issue is possibly the json files that are downloaded to the file system on the CAN variant. They will fill up the file system also when you do a lot of upgrades

I liked having them around, so you could download them back down and check sha1 to see what the image was that was actually running when you had an issue.

Okay, then my proposal is: At startup of the esp:
If numberOfBinFiles>1 then deleteAllBinFiles()
This keeps a single file forever, and cleans up multiple ones.