You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which has issues around handling of M0/ M300/M117 and double entries of G Lines. I understand M commands are not easy to parse as they may be custom.
It seems to me that Fusion outputs one gcode per line which this parser does not really take advantage of cause I think it assumes many instructions may appear on the line.
The double entries are probably some user error on my side :/
Thanks :)
The text was updated successfully, but these errors were encountered:
Something tells me I'll need to rewrite the parser when I get some free time. Or at least revise the grammar so newlines have a semantic meaning and are handled correctly by the parser.
That should also give me a chance to handle your M0 Turn ON 5000RPM example in #5 (comment).
I can split by newlines and then parse each line which seems to fix the G ops appearing twice and also make them not get mangled by the M ones. (I'd like to plot them using wgpu+lyon much like the yew example and also display some statistics and possibly give the user some hooks for processing.)
FWIW this whole thing started for me cause a friend has trouble using another paid software with this gcode so I said well maybe I can help with that :D
Feel free to ping me if you'd like me to test something or need feedback :)
the following input
using
produces
Which has issues around handling of M0/ M300/M117 and double entries of G Lines. I understand M commands are not easy to parse as they may be custom.
It seems to me that Fusion outputs one gcode per line which this parser does not really take advantage of cause I think it assumes many instructions may appear on the line.
The double entries are probably some user error on my side :/
Thanks :)
The text was updated successfully, but these errors were encountered: