Make an option to force the speedcode for Engraves and Cuts a gear=0 option for getting the speedcode. The modern versions of SpeedCode.py call this something else but I believe the twitching on the M2 Nano is intended almost exclusively for Rastering and that the Chinese software using it for non-raster jobs might be an error. Basically gear=0 results in a C suffix speed code. Which basically means it’s in cut mode and disables the accel and decel cycles (twitches). Depending on the number of movements in your cuts this can actually take a long time. These speeds tend to get a bit more jagged at the upper end (as in we put them through a logical analyzer) of around 100mm/s (they work fine and scale correctly in the ranges people use) but they are less likely to waste your time and are bit more stable. This was only tested on M2-Nano-V9 which is pretty ubiquitous nowadays (I rarely even see V7s) (LaserDrw didn’t ask for version number anyway).
The cost of including such a feature is pretty low, it’s optionally including a flag to send to the speedcode generating python. It’s currently in the unpublished beta version of MeerK40t.
Also, bravo on the clever method of removing the redundant raster characters. Very minimalist/functional.