3D Printers

From Hacklab.TO Public Wiki
Revision as of 21:18, 1 March 2016 by Saskeah (Talk | contribs)

Jump to: navigation, search


Please do not leave 3d printers unattended for long periods! These printers are prone to failure, and leaving them unattended could result in cooked filiment / extruders, damaged mechanical components, or fires.

Machine Status and Important Notices

Ultimaker 1.jpg
Ultimaker 1
Ultimaker 2.jpg
Ultimaker 2
Type A.jpg
Type A
Makerbot Cupcake.jpg
Status Operational Operational Operational Operational
Material 3mm ABS only 3mm PLA only 1.75mm PLA only 3mm ABS only
Hardware state Good. Minor backlash observed. Good. Power connector is loose. Good. Cooling fan cowling may need some work Good.
Software state Working well with OctoPrint Working well with OctoPrint Usable, prints pause momentarily/frequently due to Raspi slowness, some issues with long print jobs randomly failing. Good (Grab latest Cura profile from github [1])
Pending tasks None None None PID tuning, bed wobble, wavvy ABP.

Printer-specific pages

Print specific pages include details about the machines, maintenance logs, and workflows.

Ultimaker 1 Camera (720p)

Open this URL exactly with VLC: rtsp://admin:@

3D Printer Workflow at the Hacklab

The hacklab 3d printers are set up using the Construct Protocol which allows 3d printers to be used over the local network. The users personal computers are not required to be physically connected to the printers during the duration of the print, and allows for users to continue working on other projects without fear of print interruptions, etc. Construct only acts as the gcode sending layer, which means the user still has to generate the gcode based on an STL file.


  • The printers are all equipped with OctoPrint web interface software. See the quick start instructions for server addresses.
  • Ultimaker CURA is the software used to generate Gcode for the Ultimakers. You can get it here: CURA download link. Here's our guide on preparing models for printing at HackLab.
  • Cupcake Also works with cura, but you'll have to download the profile on hacklab's github page, and edit Cura's machine dimentions to match.
  • Type A Gcode is generated via KISSlicer using a profile maintained by Will

Quick Start Instructions

  1. Generate Gcode from an STL using printer-specific software. Here are instructions on using Cura for the Ultimaker machines.
  2. For the Type A, make sure to use the Cura for Type A!
  3. Visit the OctoPrint web interface for the printer you're using (note: you must be on the members' wifi network!):
  4. Upload Gcode to the printer using the web interface.
  5. Click print and wait.
  6. When finished, make sure you do the following steps:
    • Clean up bed and machine for the next user.
    • Delete the file on OctoPrint if you are done with it.
    • Turn the machine off.


Physical Problems

  • Print not sticking to bed
    • Check bed levelness
    • Check print bed distance to print head
    • Reapply fresh blue tape (Interpolymer Group brand for PLA printers only)
  • Extruder no longer extruding filament
    • Check filament feeder for ground plastic preventing extrusion
    • Check gcode generator settings to ensure proper filament properties selected (diameter, density)
    • Inspect hot-end for plugs by manual extrusion at temperature
  • Extrusion is discontinuous
    • Check filament feeder for ground plastic preventing full continuous extrusion
  • Print has random blobs due to pausing of printer mid extrusion
    • Known bug in prontserve due to bottleneck in Raspberry pi I/O. Print simpler file or directly control printer via USB/pronterface

Software Problems

  • tegh
    • Temperature stops updating after estop command issued
      • Known bug, ssh to host machine, screen -r, ctrl-C, python2 prontserve.py to restart prontserve.
    • Printer auto-discovery did not work.
      • Restart prontserve: ssh to host machine, screen -r, ctrl-C, python2 prontserve.py to restart prontserve.
    • tegh discovers no printers on network
      • Check firewall settings
      • Verify on internal networks: 192.168.111.x or 192.168.113.x