I talked to Daid and he did some very impressive debugging and tracing from my description and found 2 bugs in the firmware that led to this together with a bug in Cura. There's a bug in Cura 3.2 that it doesn't output the custom settings in the g-code any more. We knew about this one and it'll be fixed for 3.3. In the firmware, it would check for the file being completely read and the g-code buffer being empty. If both are true it would call an abort function on the print that woul