Re: Towards printer-independent GCode January 06, 2018 05:07AM |
Registered: 8 years ago Posts: 3,525 |
Re: Towards printer-independent GCode January 06, 2018 05:29AM |
Registered: 8 years ago Posts: 622 |
Re: Towards printer-independent GCode January 06, 2018 06:39AM |
Registered: 9 years ago Posts: 383 |
Re: Towards printer-independent GCode January 06, 2018 07:39AM |
Registered: 10 years ago Posts: 14,672 |
Quote
DjDemonD
To address the issue of the way forward - having gcode that can print on any printer is IMO NOT the way forward. Having the slicer built into the 3d printer is.
Compare it to paper printers, you feed them something to print in standard format, the printer figures out the toolpaths required to print it.
The only reason we had separate slicers was to allow a PC to do the heavy lifting that 8 bit arduinos couldn't do. Now it's possible with 32bit controllers or raspberry pi's to just chuck an stl at your 3d printer. Since the slicing settings that work best for any given printer and material are specific to that machine they should be pre-programmed into the printer. Sure you can have some profiles, fine, normal, draft, etc..
Quote
DjDemonD
Surely the ideal is when we want to print a 3d object which we get in standard format stl, obj we chose a printer and pick a quality setting and press print and then a few hours later a green light comes on and we open the printer door and take the object out.
Quote
DjDemonD
Since the firmware we use now are for enthusiast machines, not truly consumer printer maybe the bridge is that using some built in calibration objects and a "unified calibration routine" the firmwares first job in a new machine is to walk the user through setting it up, determining the optimum slicing settings in the process,using objects to test the various variables, bed adhesion, dimensions, cooling etc.. After that you just hit print.
Re: Towards printer-independent GCode January 06, 2018 07:59AM |
Registered: 8 years ago Posts: 3,525 |
Re: Towards printer-independent GCode January 06, 2018 09:15AM |
Registered: 8 years ago Posts: 622 |
Quote
WesBrooks
STL isn't far of a raw mesh. It's a bit of a crappy format given today's computing power, even on raspberry pies. There's no information on shared vertexes. The only information is a huge sequence three coordinate sets. Most stl object handlers that I've worked with post process the files with assumptions to try and rebuild the connectivity information.
I get the impression this would be an easy task as at least Slic3r is driven by external programs such as Repitier.
I'd draft it in python and use the exisiting slic3r config files to set it up.
Edit: Not suggesting ditching STL at the same time, just discussing its a format born in a time of much reduced pricessing power. We could do netter now.
Re: Towards printer-independent GCode January 06, 2018 03:00PM |
Registered: 8 years ago Posts: 601 |
Quote
WesBrooks
STL isn't far of a raw mesh. It's a bit of a crappy format given today's computing power, even on raspberry pies. There's no information on shared vertexes. The only information is a huge sequence three coordinate sets. Most stl object handlers that I've worked with post process the files with assumptions to try and rebuild the connectivity information.
I get the impression this would be an easy task as at least Slic3r is driven by external programs such as Repitier.
I'd draft it in python and use the exisiting slic3r config files to set it up.
Edit: Not suggesting ditching STL at the same time, just discussing its a format born in a time of much reduced pricessing power. We could do netter now.
Re: Towards printer-independent GCode January 06, 2018 07:00PM |
Registered: 11 years ago Posts: 1,049 |
Quote
WesBrooks
Quote
cozmicray
the 3D printing world needs a type of language to move forward
I don't follow the argument you are making? Can you explain another way?
STL (Stereolithography) and gcode files (adapted from nc machine control) are exactly that?
I suspect the open source efforts for laser sintering and projector based systems use different files.
Move outside open source and each vendour will have its own (often binary) formats for build objects, slice data, and parameter sets.
Re: Towards printer-independent GCode January 07, 2018 04:58PM |
Registered: 7 years ago Posts: 18 |
Re: Towards printer-independent GCode April 20, 2018 02:12PM |
Registered: 10 years ago Posts: 401 |