I love breakdowns like these. Some feedback. You present it as a chart, yet it cannot be used as a chart. If you intended it to be a chart, then you have some major issues. It might better presented as 8 independent columns with a bit of space between each.
Inputs - this short list fails to capture some important distinctions. I’d break it down like this:
- Original ideas
- 2D files
- Parameterized 3D models
- Mesh 3D models
- Image files for reference
- Image files for tracing
- Image files for height maps (grayscale)
CAD Design - vCarve is only one of Vectric products. I sometimes leverage Photoshop to create 3D models from grayscale images.
CAM / Toolpaths - anything I can think of that can create toolpaths has some mechanism, either built-in or through a post processor, that generates g-code. So I don’t think the distinction between creating a tool path and generating g-code is meaningful.
Slice Model - I’ve never see a post where Prusa Slicer, Slic3r, or Cura is used to create g-code for a CNC. If this is being done, I’d love to see the posts. Beyond that, as mentioned, I don’t think this category is meaningful. I don’t know, but I don’t think OctoPrint is a slicer.
Machine Controller Software is perhaps the category I’m fuzziest on since I run headless, but typically I look at the this category of software as g-code senders that responsible for transport of g-code created by other software to the MPCNC. While RepetierHost is a slicer, it is one of the main ways MPCNC users send g-code generated elsewhere to the MPCNC. I think an important distinction in this category is wired vs. wireless. Running from the SD card might also belong in this category.
Machine Controller Hardware - The list is much longer. I’m not sure making the list of boards is meaningful other than to say that someone at some time has used that board to make an MPCNC.