Actions

Lulzbot Instructions: Difference between revisions

From HacDC Wiki

(Rough draft)
 
m (The adventure continues)
Line 1: Line 1:
Basic instructions for the HacDC Lulzbot 3D printers
Basic instructions for the HacDC '''Lulzbot 3D''' printers


Create your model with ImplicitCAD (http://www.implicitcad.org/) or
Create your model with [http://www.implicitcad.org/ ImplicitCAD] or [http://www.openscad.org/ OpenSCAD]Creating your model is beyond the scope of this document, but the two previous links include documentation. The model will be saved with the extension or '''.escad''' or '''.scad''' respectively.
OpenSCAD (http://www.openscad.org/).  The model will be saved with
the extension or ".escad" or ".scad" respectively.


This should then be exported as a "structure file" with the extension
This should then be exported as a ''structure file'' with the extension '''.stl'''. OpenSCAD can do this from the '''File -> Export''' menu.  ImplicitCAD appears to use a separate program:
".stl". OpenSCAD can do this from the File -> Export menu.  ImplicitCAD
appears to use a separate program:


     $ extopenscad model.escad model.stl
     $ extopenscad model.escad model.stl


While the .escad and .scad files are unique to the apps above, the
While the '''.escad''' and '''.scad''' files are unique to the apps above, the '''.stl''' file is a standard understood by many programs.  Some(?) printers understand STL files directly.  Our Lulzbot printers are not among them.  The STL file must be further converted into a series of instructions that tell the printer exactly how to calibrate, heat, move, extrude, and cool.
.stl file is a standard understood by many programs.  Some(?) printers
understand STL files directly.  Our Lulzbot printers are not among
them.  The STL file must be further converted into a series of
instructions that tell the printer exactly how to calibrate, heat,
move, extrude, and cool.


Again there is a widely used standard: G-code. G-Code files, logically
Again there is a widely used standard: ''G-code''. G-Code files, logically enough, typically have the extension '''.gcode'''[https://www.lulzbot.com/cura Cura], among other programs, reads STL files and produces G-Code files. [http://slic3r.org/ Slic3r] is another such program. (See the [http://manual.slic3r.org/ Slic3r manual] for more info.)
enough, typically have the extension ".gcode".  Cura, among other
programs, reads STL files and produces G-Code files. Slic3r
(http://slic3r.org/ and http://manual.slic3r.org/) is another such
program.


Use Lulzbot's Cura, not "standard" Cura!
== Use Lulzbot's Cura, not "standard" Cura! ==


See https://www.lulzbot.com/cura for download links. (I'm assuming you
Turn computer and 3D printer on
can follow directions for your OS.)


 
After boot, login as '''root'''. The password is printed on the monitor.
Turn computer and 3D printer on


After boot, login as "root" with a password "fai"
Insert USB stick or get your '''.gcode''' to the computer by other means


Insert USB stick (in this example we will print the file
{| class="wikitable"
"RoboRingV1.gcode" which is under the "fsgcode" directory)
|-
!|Command
!|Notes
|-
|$ '''lsblk'''
|List USB devices
|-
|$ '''mount /dev/sdb2 /mnt'''
|Mount USB
|-
|$ '''ls /mnt'''
|
|-
|$ '''cd /mnt'''
|
|-
|$ '''ls'''
|
|-
|$ '''pronsole'''
|
|-
|> '''connect'''
|
|-
|> '''settemp 190'''
|Remove any filament that may be stuck in extruder
|-
|> '''load ....'''
|Tab to complete name
|-
|> '''print'''
|
|-
|> '''monitor'''
|
|-
|> '''exit'''
|
|-
|}


Command                      (Purpose)
====================    ====================
$ lsblk                  (List USB devices)
$ mount /dev/sdb2 /mnt    (Mount USB)
$ ls /mnt
$ cd /mnt/fsgcode
$ ls
$ pronsole
> connect
> settemp 190            (Remove any filament that may be stuckin extruder)
> load ....              (Tab to complete name)
> print
> ...
> monitor
> exit


The Lulzbot Mini will eventually move the extruder head up
The Lulzbot Mini will eventually move the extruder head up


$ pronsole
{| class="wikitable"
> connect /dev/ttyACM0 (orconnect /dev/ttyACM1
|-
> home x               (watch the printers to see which responds)
!|Command
!|Purpose
|-
|$ '''pronsole'''
|
|-
|> '''connect /dev/ttyACM0'''
|or '''connect /dev/ttyACM1'''
|-
|> '''home x'''
|watch the printers to see which responds
|-
|}

Revision as of 02:28, 16 September 2016

Basic instructions for the HacDC Lulzbot 3D printers

Create your model with ImplicitCAD or OpenSCAD. Creating your model is beyond the scope of this document, but the two previous links include documentation. The model will be saved with the extension or .escad or .scad respectively.

This should then be exported as a structure file with the extension .stl. OpenSCAD can do this from the File -> Export menu. ImplicitCAD appears to use a separate program:

   $ extopenscad model.escad model.stl

While the .escad and .scad files are unique to the apps above, the .stl file is a standard understood by many programs. Some(?) printers understand STL files directly. Our Lulzbot printers are not among them. The STL file must be further converted into a series of instructions that tell the printer exactly how to calibrate, heat, move, extrude, and cool.

Again there is a widely used standard: G-code. G-Code files, logically enough, typically have the extension .gcode. Cura, among other programs, reads STL files and produces G-Code files. Slic3r is another such program. (See the Slic3r manual for more info.)

Use Lulzbot's Cura, not "standard" Cura!

Turn computer and 3D printer on

After boot, login as root. The password is printed on the monitor.

Insert USB stick or get your .gcode to the computer by other means

Command Notes
$ lsblk List USB devices
$ mount /dev/sdb2 /mnt Mount USB
$ ls /mnt
$ cd /mnt
$ ls
$ pronsole
> connect
> settemp 190 Remove any filament that may be stuck in extruder
> load .... Tab to complete name
> print
> monitor
> exit


The Lulzbot Mini will eventually move the extruder head up

Command Purpose
$ pronsole
> connect /dev/ttyACM0 or connect /dev/ttyACM1
> home x watch the printers to see which responds