- #1
fog37
- 1,568
- 108
- TL;DR Summary
- Sharing G-code files instead of stl.files
Hello,
I am aware that the workflow of 3D printing involves the following steps:
1) Design the part using CAD and saving it as a .stl file.
2) Import the stl file into a slicing software to be converted to a G-code file
3) Load and run the G-code file on the 3D printer
It is simple and safe to email and exchange stl files. But what about email g-code files directly? For example, my friends and I share one 3D printer. Would it be ok for us to email each other the G-code files after slicing our models so those G-code files can be directly imported in the 3D printer? Are there any risks? I know G-code contains information about the 3D printers, layer information, support information, and all the instructions the printer must follow to print the part.
I am assuming we are using the same slicing software selecting exactly the same 3D printer model...
Thanks!
I am aware that the workflow of 3D printing involves the following steps:
1) Design the part using CAD and saving it as a .stl file.
2) Import the stl file into a slicing software to be converted to a G-code file
3) Load and run the G-code file on the 3D printer
It is simple and safe to email and exchange stl files. But what about email g-code files directly? For example, my friends and I share one 3D printer. Would it be ok for us to email each other the G-code files after slicing our models so those G-code files can be directly imported in the 3D printer? Are there any risks? I know G-code contains information about the 3D printers, layer information, support information, and all the instructions the printer must follow to print the part.
I am assuming we are using the same slicing software selecting exactly the same 3D printer model...
Thanks!