SpeedTower script leaves feed rate at low percentage on completion

[tillig]

When running the SpeedTower.py script using the "speed" option, it seems the speed is manipulated using M220 which sets the feed rate of the printer.

Unfortunately, after the slice and print of a speed tower, it leaves the feed rate at the altered percentage rather than returning it to 100%. On Ender 3, that's a persistent setting that isn't reset automatically on the next print. If you're not paying attention, all subsequent prints you run will be at the reduced feed rate until you manually set it back to 100%.

I think an M220 S100 at the end of the script would be a nice addition that would potentially have saved me from having to rerun a bunch of tests due to the odd feed rate being left behind.

[tillig]

It seems there's a backup/restore command for feed rate so for speed, I gather doing M220 B at the start of the script (to backup the current setting), then running the script, then M220 R to restore what the user had set before would maybe be even better.

[5axes]

M220 B and M220 R looks like a good idea . I will try to add this option in the next release of the script

[5axes]

Ok added on the Github .. Must be now tested on my printer.

[5axes]

Tested on Ender-3 Doesn't work .. M220 B and M220 R doesn't Restore the speed percentage on my Machine. But on other hand doesn't produce any issue. So I will leave it like that. If someone could be successful leave a message here.
On other point the feed percentage is reset to 100% if you switch off / On the printer so it's not a big issue for a normal use. Just need to take care during the test .

[tillig]

Maybe something to note in the docs, then. I don't switch my printer on/off between prints/tests so maybe that was part of my gotcha. It just was unexpected.

[Insectslayer]

I stumbled upon the same issue when testing the printing speed. The M220 B and M220 R didn't have any effect in my Marlin firmware. Do you think it makes sense to mention it in the wiki pages? Thanks.

[5axes]

It might make sense to mention it in the Wiki. But at the moment, as I haven't had any feedback on how this code works and on the other hand the presence of the code hasn't caused any particular issue, I don't see the needs of mentioning it in the Wiki.