FR sync of preparing activity

[viktor_b 1]

I am wondering if it would be possible to overlap table and print core heating. The temperature rise speed is known for both, so starting the print core heating before the table will reach target temperature will save some time for users. Also to me is not clear why the table warpage measurement cannot be done while heating. I believe the thermal expansion over last 10°C will not bring any additional bending.  

 

Also what is annoying, in case I have interrupted the printing while preparing I need to run to the printer just to confirm on touchscreen that I don't want to repeat the print.  Could this question pop up remotely or better completely skipped? If needed I can start a print of last model from printer menu.

[CarloK 204]

You bring up some good suggestions.
Cores heating could indeed start a bit earlier when we use your method. The current implementation is a bit optimized, but very simple, it starts heating the cores when the build plate is 5C from the target temperature. Using your method we could save about 10 seconds. Nice, but not overwhelming for a print preparation process which takes anywhere from 1 to 10 minutes (depending on bed temperature).
I'll bring this to the attention of the developers, but they have a list of 350 open tickets for the firmware and I'm afraid this suggestion will end up on the lower end of that list.

 

The bed level probing can't be done while the bed is heating because the whole printer continues to deform for at least 30 minutes after the bed is at the desired temperature. Deformation is not only because the build plate is heating up, but the whole printer is slowly heating up and this process continues for a long time. For good adhesion of the first layer we are talking about a required precision < 0.1mm, and that's why we want to have as little time between the probing and the start of the print.
The larger the printer, the larger this effect. 

The annoying this about having to walk to the printer to confirm the "Reprint? yes/no" question is known and on the list of things to fix. It's part of old code when it wasn't possible to use the printer remotely, which is now the most used method.