/HackerBot

HackerBot 3D printer

HackerBot

Hackerbot 3D printer is based on Ultimaker XY core design

It was build using CNC aluminium parts, quality chromed shafts and bushings, a reliable extruder and E3D hotends for ultimate performance. Enclosure is made in 5mm Polycarbonate and PMMA

Hackerbot has been build to last a lifetime.

We also added a Raspberry Pi for WiFi and Ethernet connection (Octoprint) and as optional big stepper motor drivers for smooth, quiet and reliable motion.

We designed it observing, when it was possible, the standards used in RepRap community so you will find easy to change some parts with others (ex. hotends, extruders, etc.)

Current version of the HackerBot is 2.2 (26-Jan-2016)

''The HackerBot is an open source 3D Printer under CC-SA-BY license.''

Main Features

  • Print area: 300x200x200mm (with Heatbed)

  • Modular Head. Dual extruder with second extruder interchangeable.

  • High quality aluminium frame and CNC parts. Last a lifetime.

  • Easy of use: Wifi (Octoprint) and/or big LCD display & SD Card

  • know printable materials: ABS, PLA, HIPS, Nylon, Polycarbonate

  • width: 510mm

  • height: 650mm

  • depth: 510mm

  • weight: about 26kg

Changelog

  • v 2.2 (26-Jan-2016) New aluminum extruder (AluExtruder)
  • v 2.1 (20-Dec-2015) Removed a lot of 3D printed parts and replaced with CNC aluminum parts
  • v 2.0 Hackerbot V2 released. (spring 2015)
  • v 1.5 (pre 2.0) Major rework: new profiles, head, Z axis motor mount, extruder and cover panels.
  • v 1.3a (17-Jun-2014) New bed support, aluminium base plate
  • v 1.3 (02-Jan-2014) Major update. Hackerbot is now bigger.
  • v 1.1 (24-Oct-2013) dimensional fix and minor updates
  • v 1.0 (1-Oct-2013) first release

Support forum: http://forum.oshw.it/ Buy it from: http://opensourcehardware.it

Reporting bugs

HackerBot's issue tracker can be found on Github. Or Hackerbot issue/feature/bug tracker is on http://oshw.it

Sending pull requests

Please create all pull requests against the edge branch of HackerBot, as that one is used for developing new features and then merged against master when those features are deemed mature enough for general consumption. In case of bug fixes we'll take care to cherry pick them against master if the bugs they are fixing are critical.