Access to parameters in unrecognised G code

  • I know we currently have the ability to create macros in the /sys folder that are triggered when an unrecognised G or M code is encountered, but I can't find any information that suggests the parameters contained within that unrecognised command are exposed to the macro.
    Perhaps in the implementation of variables, this could be considered.
    I think it would be a powerful tool for those experimenting with other uses than FFF and also for slicers that haven't "caught up"

Log in to reply