I couldn't see any way of doing this automatically but is there any way i could extract the filename of the current file in order to feed it into the m37 command so that i can engage the heaters, and while waiting for that to heat up, simulate the current file and then return to the file after it has been simulated to complete the rest of the print? I love the simulation feature but it would be so much better if it could be fully automated into the start gcode. Sorry if there's something i've missed but i've looked around for quite some time and i cant find anything that would be able to do what i want but hey, maybe i'm just looking in the wrong place.

Thanks.

thanks. will do

okeydoke, thinking about it i have had a problem in the past where my firmware got corrupted and i had to reinstall it, but i did it on the same sd card. sounding much more likely that the sd card is the option. ill buy a nice one and see if that fixes it.

oops, forgot to attach them, what an idiot! I also seem to have overwritten the original gcode for the part, i can only provide the Corrupted file , but it should be enough to get the gist across. EDIT: here's the same model resliced, the gcode is slightly different cause i can't get the same variable layer height settings but its pretty close.

I have been having a problem recently that when uploading mostly large gcode files there is about a 50% chance that a few lines of the file will be corrupted. I have attached two gcode files as an example, one which is directly from the slicer and one downloaded from the duet wifi after uploading, look around line 544744 to see the start of the corruption. This is really annoying as it causes the print to proceed as per usual til it hits the corrupotion at which point the print head usually smashes into the object, ruining the print and causing a potential fire hazard. There is a good wifi connection at all times in the upload process. Thoughts? (sorry if i haven't formatted this properly / given enough info, first time posting on the forums)