Good lookin pine, that’s a shame.
If nothing else, looks like the travel moves were dragging through the piece, so maybe a z-offset issue.
The …curves…look…artistically interpreted…
I loaded your file into NC Viewer and it plots like Luban shows, but I’m concerned the .CNC file is not being interpreted correctly in the controller - many lines start with X, but that’s not valid gcode according to the controller I think. I’m thinking those moves are being ignored until the next G0 or G1 command comes through, and it does a beeline straight to it.
Here’s the gcode parser in the firmware:
Your file has this:
Y341.61F508.0
X87.00
Y312.41
X86.98Y260.83
Maybe try sending those commands in the console manually? But I don’t think that’s going to do anything.
A simple post-process you can do, load it in notepad++ or some other text editor capable of running regular expressions and do this:
Find: ^([XYZ])
Replace with: G1\1
That will add G1 to the beginning of any line starting with an X, Y, or Z