Using old gcode to work backwards [Idea, not issue] #18
Description
If gcode is effectively a set of instructions, could one be able to take a pre-sliced gcode file from an existing source, pass through into a modifier (manipulator program or such) to be able to work backwards to simplify the generation of the new gcode?
Would allow less input and less work on user end to be able to generate a 'modified' gcode to allow the program to handle the complex stuff.
Thinking is you'd be able to set rules or even create a local LLM to determine various parameters to create the new file? For example, take a basic flower shape (just the outside), if you were to slice conventionally naturally it would follow the X-Y plane then move up the Z, but with a LLM or a pre-determined ruleset, it could see that pattern of the curves moving up and down along the perimeter of each petal, and calculating a delta between the expected output versus the current gcode, it could re-calculate the path it should take? Unsure how to determine the best approach on how to give the LLM the data or training to be able to workout what the end result should look like, but would be keen in developing a solution to this.
The work involved into developing the LLM would allow a ML approach to train on current FullControl generated models versus conventionally created models, potentially allowing processing to occur locally on the printer controller board with SLM chips; "the printer knows best". Would reduce the need for printer user's having to think about the best printing approach, and would just allow the printer to handle it (even more so if you were to use the Multi-axis approach). Could even allow for no slicing requirements for printer's, allowing it to handle or even prefer 3D models to be able to calculate it internally.