[Bug] Print fails to start

[KenLucke]

Everything has been going along perfectly. Merrily printing along using both Arc Welder and MeatPack, which between the two give me over 70%-90% compression of data going over the serial port, and has virtually eliminated zits, blobs, and stutters, even at 250mm/sec during a self-designed torture test.

Now, I ran into a file that won't start printing after being converted by Arc Welder. It loads, converts, saves, will load in OP as the active file (conversion by Arc Welder, that is), but clicking on "Print" causes it to do the first step of printing (heating, then the Dashboard changes to show the Gcode % and layer % of "0," the terminal shows "Printing..") but the head never moves and no print ever actually starts. After removing the AW header and the M117 Layer Indicator lines and doing a compare on the files shows no difference up to the point where the actual printing code starts. Attempting to print the unconverted file works fine. Disabling Meatpack allows the ArcWelded file to print fine.

I've attached the raw file and the converted file. Unfortunately, I can't attach a serial log for the time(s) it would not print when MeatPack was enabled, because by the time I turned on Serial logging, I had disabled MP and the print started fine, and I don't want to cancel it at this time.

Archive.zip

[scottmudge]

Interesting, I don't see anything that sticks out as being invalid. Is it just this file, or all interactions with ArcWelder and MP? It appears to run find with both active on my end, both with the Cura AW plugin, and with the OctoPrint AW plugin.