Gcode Modularity

From Open Source Ecology
Revision as of 10:27, 15 February 2016 by Tobben (talk | contribs) (Created page with "Gcode is commands that most RepRap firmware understands. To make a RepRap do a certain action, you need to tell it the corresponding gcode or sequence of gcodes. A slicer prog...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Gcode is commands that most RepRap firmware understands. To make a RepRap do a certain action, you need to tell it the corresponding gcode or sequence of gcodes. A slicer program is a program that translates a 3D model, such as an STL file, into a sequence of gcodes. See RepRap Wiki on Gcode for more.

Modularity

Slicer programmers have been eager to improve print quality, and have therefore implemented many features that compensate for the mechanical specifics of RepRap FFF 3D printers. So gcode output of slicers depend not only on input files (STL files), but also on the mechanical specifics that the user configures the slicer program to compensate for. This makes gcode non-portable, and gcode files are in general not distributed within the RepRap community.'

Examples of non portable slier functionality are:

  • Filament retraction
  • Wipe of nozzle
  • Extruder enumeration


The RepRap community has adapted the gcode standard from CNC controlling firmwares. RepRap designers can often choose whether FFF printer specific functionality should be provided by the The interface between slicer and firmware is not very clean.

Retrieved from "https://wiki.opensourceecology.org/index.php?title=Gcode_Modularity&oldid=135764"