--- the issue i've been running into is that when i set the feed rate to something nonzero, the printer seems to wait forever saying it is busy. i seem to need experience sending successful g-code. i've learned enough about g-code now that i can probably read a premade file, so it would make sense to find one of those files and bum it down, like bisecting code when there isn't a debugger, to figure out how to correctly use the extruder without freezing the printer up. i was hoping to be able to interrupt the printer if it is in a frozen state, but so far i haven't figured out how to do this in this particular state yet (it looks like disconnecting the usb device would add some options, as well as learning more gcode). attached are the files i have, which don't quite function but show my attempt to prototype something that could parameterize stuff. i copypasted some documentation into _parser.py which contains code to parse my copypasting into structures. meanwhile test.py uses these structures to send code to the printer. ------- another thing i've discovered is that i'm actually using a very old version of mecode that happened to have a fork recently updated. the mainline gcode had two major version updates prior to the fork i've been engaging. this gives me a desire to merge the two together which is unfortunately inefficient. it would be more efficient to try to run the newer code, porting my fixes over if they become needed (this could take me some time from my spasms, which i've recently been finding a couple possible avenues that could help reduce). i might also want to look for forks that are based off the newer tip, to see what the actual latest codebase is.