Skip to content

gcode optimization rules for grbl #279

@arkypita

Description

@arkypita

Hi @chamnit, hello everybody
I am going to write a function to parse a gcode file and strip out all the redundant commands and parameters.

I know that some commands and params are modal: if you send S120 you dont need to send it again unless you want to change power, if you send G1 you can send a sequence of XYZ movement without sending G1 again etc

My questions are:

  • This concept of modal commands and parameter are proper to grbl interpreter or they are defined as standards for any gcode interpreter?
  • Can you confirm that grbl has two different set of memories for G0 and G1-2-3? As example i can set G0 F1000 and G1 F2000 on top of the code and all the next G0 will be executed with F1000 and G1 at F2000? Is this a grbl implementation or a gcode standard?
  • Do you know any place where I can find some documentation about modal/non-modal command and parameters that can help me writing this function?

Thanks a lot, Diego

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions