general info for anyone using Vectric VCarve Desktop (and I would assume Pro and Aspire), I found the solution to the above code 400 unable to read file problem. I modified the PP to startup spindle with a delay (thanks to @blaghislain), put in the tape split to split long/large carves, and put in as much info from the file as permitted by the API so I can figure out what I did when I created it the day before - memory is the second thing to go:(. One of the info pieces was [TOOLNAME]. If you look at your tool database you will see that Vectric adds the degree sign to VBit names. Apparently when you create the gcode file with that degree sign you change the encoding of the file so that the 1F controller does not like it. You can test your files with MSWord - when opening if word asks what encoding to use you know it ain’t right. Seems all other text editors don’t care. Solution is to either don’t use [TOOLNAME] or edit out the degree sign. BTW, all tool names have the convention of putting some info into a () pair. This will throw an error when loading the file. You can edit these out in the tool database as well.