szafran81
szafran81
Have you guys tried this in the start g-code: ``` M190 S0 M104 S0 PRINT_START EXTRUDER={first_layer_temperature[initial_extruder]} BED=[first_layer_bed_temperature] ``` That way one sets up everything in PRINT_START in the correct order....
One just needs to remember that those: ``` M190 S0 M104 S0 ``` must be in the start g-code field in PSlicer otherwise it will put them in with temps...
It looks like you do have something wrong in your config. Do remove the macro from your config and copy/paste as @Edigorin posted, and then change things in it. And...
@AustinTylerDean splooge away. Sameone may use it in the future (like me ;) - i do plan to put some kind of a heating element inside my 2 Vorons)
+1 here too. Thank you.
Exactly. I have 5, but even when using only 2 filaments the differences are big. When using single filament the predictions are on the spot (+/- few minutes on 2...
As I'm watching the PTG options window... This comes to mind... Add another section in options like this one:  name it something like "Long running non-standard g-code commands" and...
I think that adding measuring (or custom g-code delays) should be enough. If a machine uses custom moves when doing Tx g-codes then the measured time will include those allready....
Confirmed. I'm having this all the time - specially when the MMU errors out during loads/unloads that way that the 5/10 leds blink and you have to reset the MMU...
That's great. Thank you for taking it into consideration.