Skip to main content
3D Printing

Return to Answer

Typo
Source Link
0scar ♦
0scar ♦
  • 37.1k
  • 12
  • 67
  • 155

Assuming the OctoPrint server is running on your Raspberry Pi, which is the usual "OctoPi" setup, then yes, once you have uploaded the G-Codecode to OctoPrint, you no longer need to leave the web interface open.

For example, one could upload code from their desktop running the slicing software to OctoPrint, walk to the printer to turn it on, then use a different device (a phone, for example) to connect OctoPrint to the printer and begin the print. At no point does the device accessing the web interface matter. The Raspberry Pi is in control of the printer, not the device that started the print.

Assuming the OctoPrint server is running on your Raspberry Pi, which is the usual "OctoPi" setup, then yes, once you have uploaded the G-Code to OctoPrint, you no longer need to leave the web interface open.

For example, one could upload code from their desktop running the slicing software to OctoPrint, walk to the printer to turn it on, then use a different device (a phone, for example) to connect OctoPrint to the printer and begin the print. At no point does the device accessing the web interface matter. The Raspberry Pi is in control of the printer, not the device that started the print.

Assuming the OctoPrint server is running on your Raspberry Pi, which is the usual "OctoPi" setup, then yes, once you have uploaded the G-code to OctoPrint, you no longer need to leave the web interface open.

For example, one could upload code from their desktop running the slicing software to OctoPrint, walk to the printer to turn it on, then use a different device (a phone, for example) to connect OctoPrint to the printer and begin the print. At no point does the device accessing the web interface matter. The Raspberry Pi is in control of the printer, not the device that started the print.

fixed capitalization
Source Link
edit approved Mar 17, 2021 at 18:06
agarza
edit approved Mar 17, 2021 at 18:06
agarza
  • 1.7k
  • 2
  • 16
  • 33

Assuming the octoprintOctoPrint server is running on your raspberry piRaspberry Pi, which is the usual "OctoPi" setup, then yes, once you have uploaded the gcodeG-Code to octoprintOctoPrint, you no longer need to leave the web interface open.

For example, one could upload code from their desktop running the slicing software to octoprintOctoPrint, walk to the printer to turn it on, then use a different device (a phone, for example) to connect octoprintOctoPrint to the printer and begin the print. AtAt no point does the device accessing the web interface matter. The raspberry piThe Raspberry Pi is in control of the printer, not the device that started the print.

Assuming the octoprint server is running on your raspberry pi, which is the usual "OctoPi" setup, then yes, once you have uploaded the gcode to octoprint, you no longer need to leave the web interface open.

For example, one could upload code from their desktop running the slicing software to octoprint, walk to the printer to turn it on, then use a different device (a phone, for example) to connect octoprint to the printer and begin the print. At no point does the device accessing the web interface matter. The raspberry pi is in control of the printer, not the device that started the print.

Assuming the OctoPrint server is running on your Raspberry Pi, which is the usual "OctoPi" setup, then yes, once you have uploaded the G-Code to OctoPrint, you no longer need to leave the web interface open.

For example, one could upload code from their desktop running the slicing software to OctoPrint, walk to the printer to turn it on, then use a different device (a phone, for example) to connect OctoPrint to the printer and begin the print. At no point does the device accessing the web interface matter. The Raspberry Pi is in control of the printer, not the device that started the print.

Source Link
Tal
Tal
  • 328
  • 2
  • 11

Assuming the octoprint server is running on your raspberry pi, which is the usual "OctoPi" setup, then yes, once you have uploaded the gcode to octoprint, you no longer need to leave the web interface open.

For example, one could upload code from their desktop running the slicing software to octoprint, walk to the printer to turn it on, then use a different device (a phone, for example) to connect octoprint to the printer and begin the print. At no point does the device accessing the web interface matter. The raspberry pi is in control of the printer, not the device that started the print.