-
Notifications
You must be signed in to change notification settings - Fork 4
Print3r: Remote Printing
Since Version 0.2.0 print3r
supports remote printing:
In order to make an USB connected 3D printer available on the local network:
print3r client
if you have multiple printers connected, use --device=/dev/ttyUSB1
etc to launch for each printer this client process. By default the process runs in the foreground, use &
to launch as background process.
print3r client &
print3r --device=/dev/ttyUSB1 --baudrate=230400 client &
print3r --device=/dev/ttyUSB2 client &
Further, the printer must be connected with common baudrate like 9600, 19200, 38400, 57600, 115200 (default), 230400, etc but not 250000 (default in Marlin).
IMPORTANT:
- by default there is no authentication required to connect and control your 3D printer(s) once
print3r client
is running - it is up to you to secure your local network, e.g. to put up firewall and secure the connnections
- by default port 3380 is used for
/dev/ttyUSB0
, and port 3381 for/dev/ttyUSB1
and so forth
You may attach an ESP8266 or ESP32 with ESP3D firmware, and connect it to the 3D printer controller board; once running configure through the web GUI the Data Port: 3380
.
In the printer profile, and/or if you set with --baudrate=...
when using print3r
, choose the same baudrate as defined in the ESP3D settings.
- ESP8266: Wemos D1 Mini (DHCP, baudrate=115200); Mainboard: RAMPS 1.4 + Atmega 2560; Wifi Hotspot: Belkin N600 2.4GHz 11g;
print3r
-host (Ubuntu 18.04 LTS) connected via Ethernet to Wifi Hotspot; 3D Printer: Ashtar K #2: success- 2.2hrs printjob finished correctly
To connect to the remote client, use --device=tcp:<remote-ip>
; if you have multiple printers connected to the client, add :<n>
like :0
(default) or :1
and so forth, this number corresponds with /dev/ttyUSB<n>
on the client-side.
print3r --device=tcp:192.168.0.16 --printer=prusa-i3 print 3DBenchy.stl
print3r --device=tcp:192.168.0.16:1 --printer=ender3 print 3DBenchy.stl