Make GCode parser more robust

[jscheumann-iapt]

Let the Gcode parser detect comments, headers etc.

Currently, Gcode created with FullControl can't be directly handled with Volco as, e.g., FullControl gets interpreted as F ullControl (a speed change with non convertable string).

[fullcontrol-xyz]

Hi, in the short term, there isn't a need for a gcode parser. It will be simplest if VOLCO uses FullControl data directly, since it can include much more detail than gcode (e.g. extrusion width and height as opposed to E which has different units for different printers, e.g. colour, etc.

If VOLCO, simply reads the visualisation data from FC, that will be in line with other things, like the current stl output. It will also mean it can simulation robot paths and stuff that might be designed in FullControl.

This data is exemplified in the plot tutorial of fullcontrol

[jscheumann-iapt]

Hi,
yes, this is meant more as a note to myself (or for later development).
I came across this, because I'm currently on connecting FullControl and Volco, also using FC data directly as you described.

[fullcontrol-xyz]

Ah gotcha, I would put the parser in FullControl though. It's more valuable there since then someone could then take gcode from one printer and make it work on another printer, or edit it in interested ways before going back to gcode, or make it work on a robot, use it for VOLCO or other visualisation/modelling options in FC. It already something that will happen in FC for sure