Advanced Search

I think it's hardcoded into stepconf, otherwise it would have to parse through known editors, there are many and someone would complain (vim & emacs I'm looking at you.)

Alot like geany so that was the editor chosen (same for the arm64 images).

Python3 has been the norm for a while now. I think the gcode generators are 8 years or so old.

There is a lot of python 2 stuff around that just hasn't been update for python 3.

You could install python2 and try that for the gcode generator.

Yes, you are correct. The way the python script creates the gcode in this particular script is by using trigonometry to find the coordinates and writing to sys.stdout. I did find a preamble and postamble in the py file and I found the postamble was correct with an M2 so I think it has something to do with the way it sends the code to Axis.

Thanks Tommy. I had tried G93 Inverse Time, but didn't see any difference to G94 Programmed Feed.

I went back and did a bit more testing (with G93 and G94). The only thing I've found to work (for both G93 and G94) is to up the velocity and acceleration speeds to unachievable levels, or lengthen the small line segments that make up the toolpath. However, this will result in a more inaccurate part. And I still can't get close to the required feedrate while keeping the short lines to a decent length.

Thanks for the heads up! I don't think that would affect whether the mdi-command-NN pins would show up or not; even if don't load the PyVCP panel, I still don't see the pins exposed by halui.