English
Login

Sending G-codes to printer via network

(PrusaConnect, PrusaLink, Octoprint)

Relevant for

MK4 family
XL family
MINI family
MK3 family
MK3.5 family
+
•17 comments
Article is also available in following languages
English
Čeština
Polski
Deutsch
Français
Español
Italiano
日本語

PrusaSlicer separates the printer connection settings from the Printer profile into a Physical printer profile.

You can create a new Physical profile by clicking Add printer in the printer profile select box or by clicking the cog icon and picking Add physical printer.

In the Physical printer dialog, you can name the printer and assign it one or more printer profiles. If you're using, for example, the MMU2S upgrade, you only have to set one physical printer, but you can have both Single mode and MMU profiles linked to it.

If you have a Physical printer with network info filled out selected as your current printer, you can send generated G-codes directly to your device.

PrusaConnect

If you'd like to send files to your printer via PrusaConnect, add a Physical printer or Edit an existing one.

Select PrusaConnect from the select box as the Host type. The hostname/IP will be automatically filled, you don't have to change it.

To find your API key, go to PrusaConnect, select the printer you want to send the files to, go to the Settings tab and scroll down to he API keys section. Copy PrusaConnect API key to the Physical printer window and confirm with OK.

 

11 comments

Log in  to post a comment
Trent Robertson
•
This looks like "set up a printer to send gcode files to printer using Prusa Connect," not "sending gcode files..." Please add additional information for actually sending the commands.
Reply
Pitel
•
PrusaConnect is not available as Host Type in PrusaSlice 2.6.1.
Reply
Bpendragon
•
I honestly think you guys went the wrong way about this. I shouldn't have to create seperate physical printers for my MMU and MMU Single profiles, let alone a pair of those for each time I want to change the nozzle. If anything a "Physical Printer" should be the barest possible information needed to identify a printer: 1. The Notes section and anything like that that WON'T change between setups 2. The connection info (which is technically part of step one, but I'm stating it explicitly). Each Physical printer can then have any number of presets inside of it. So a multicolor and an MMU Single. Presets for different nozzles, etc.  They then point back to their root Physical Printer for exporting Gcode and the like. I should not have to make  multiple "physical printers" when I only have one.
Reply
Netfool
•
If the rationale for separating the physical printers is to keep the connection information for a physical printer apart from the profile information, why must I create a new physical printer to add connection information for each of the Prusa nozzle size System Presets? ...and if I want to have a profile for a non-Prusa nozzle size (e.g. 0.20), where do I find what to change in the base physical printer presets?  A diff  for the different System Presets would at least let me base all of my presets on one physical printer definition, instead of four.
Reply
Giuliano - Official Prusa CS
•
Hello. The option of creating custom printer profiles hasn't been implemented in details as for our own Prusa printers, as it's not our main focus. You can still write manually the nozzle diameter under Print Diameters, however it's necessary to creat different printer profiles for each nozzle diameter.
Reply
cbabbman
•
Version 2.3.3... This cannot be this difficult. I set up 2 physical printers for my 2 MK3Ss. All of my filaments are Prusament types. As soon as I make a preset, I lose all access to filaments and print settings with just 'default' as a choice. These aren't custom printers or filaments... they are all Prusa things... there must either be a bug in the dependancy perl conditions listed or else this is so overly complicated that it is absolutely useless. Some clarification is sorely needed. In the end, the only way for me to get access to anything is to break the dependancies on everything. At that point, why is it there at all??
Reply
Mikolas Zuza
•

I don't understand, creating physical printers should have no effect on the rest of the profiles. It just assigns network information to a named printer and links a printer profile to it. If you're making a new printer preset and it is for the MK3S, it's best to start by copying an existing MK3S profile. That way you don't have to worry about any of the dependencies.

Reply