Yes. I'm not fluent with Python but studied some of it's language and recognize some data types and functions. I recognize some of the algorithm too.
I still can't detect where the Python source code is recovering G71 ouput, start and end finish coordinates. Can you please identify a command line? It appears Python source code is using o-codes for start and end finish coordinates. These type of o-codes are output similar to filed sub-programs and not necessarily a main program.
I wouldn't use o-codes if not using LinuxCNC. Another starting and ending terminator would get used.
This is the line that reads in the gcode within the o sub / o endsub suboutine.
It uses regex to find the subroutine and read it into the array gcode
-automata
smplc wrote: a It appears Python source code is using o-codes for start and end finish coordinates. .
Yes. it uses a numbered O-sub as a container for the G-code that defines the profile.
One subtle advantage of this is that it means that the finish pass literally just needs to call the sub.
It appears it's a pathname. I suppose if a main program it could recover o-code from file.
I'd probably use P_ and Q_ for starting and ending finish coordinates. Such case make them a recoverable program. Prefer not to make a separate program and perhaps scan if configurable. Idea is writing main program containing multiple blocks, some including G71 finish coordinates and 1st operation.
