Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After update to Octoprint 1.8.1 the plugin doesn't delete previous flashed firmware #314

Closed
mriscoc opened this issue May 26, 2022 · 8 comments

Comments

@mriscoc
Copy link

mriscoc commented May 26, 2022

With Octoprint < 1.8 when a new firmware is going to be flashed, the plugin takes care of deleting the previously flashed binary.

Printer: Ender 3V2
Current Marlin Bugfix
Marlin Binary File Transfer

@mriscoc mriscoc changed the title After update to Octoprint 1.8 After update to Octoprint 1.8.1 the plugin don't delete previous flashed firmware May 26, 2022
@mriscoc mriscoc changed the title After update to Octoprint 1.8.1 the plugin don't delete previous flashed firmware After update to Octoprint 1.8.1 the plugin doesn't delete previous flashed firmware May 26, 2022
@benlye
Copy link
Collaborator

benlye commented May 26, 2022

Most likely cause is that filename that the plugin has for the last-flashed file is out of sync with the files on the SD card. Can you try manually removing all old firmware files from the card and then flashing a couple more times?

If it still doesn't work I need to see the logs from the plugin, spanning a couple of flash attempts.

@mriscoc
Copy link
Author

mriscoc commented May 26, 2022

Hi, I already tried deleting all the bin files, also, I can remove the files manually using the M30 G-code. The plugin can rename the bin files to FW######.bin.
Maybe there could be a permission access problem to write the old used filename. I will check the logs.

@benlye
Copy link
Collaborator

benlye commented May 26, 2022

I think I've found the problem. Will have a new version for you to test shortly.

@benlye
Copy link
Collaborator

benlye commented May 26, 2022

Please try v1.13.3b1 from the development release channel.

@mriscoc
Copy link
Author

mriscoc commented May 26, 2022

OK thanks, I will return with my feedback

@mriscoc
Copy link
Author

mriscoc commented May 26, 2022

It is ok now, thank you.

@benlye
Copy link
Collaborator

benlye commented May 27, 2022

v1.13.3 released

@benlye benlye closed this as completed May 27, 2022
@github-actions
Copy link

This issue has been automatically locked because there was no further activity after it was closed. Please open a new issue for any related problems.

@github-actions github-actions bot locked and limited conversation to collaborators Jun 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants