Cerealbot

Creator:
ctag
Status:
Not serial
Born On:
23:32, 13 December 2014 (CST)
Last Updated:
11:32, 03 May 2017 (CDT)

Map

Cerealbot/Hardware - General tomfoolery and notes on random hardware design

Cerealbot/Plastics - Log of what plastic filaments work

Cerealbot/rpi - Setting up the Raspberry Pi server

Cerealbot/avr - Setting up the ATmega328 which middleman's between the RPi and sensors

Cerealbot/Financial - A list of links to every item I've purchased

Cerealbot/printrbot - Doesn't exist yet?

Cerealbot/Queue - To be deleted

Cerealbot/Archive - Cruft that still may be helpful

Project code on github

Livestream of the prototype - If this link doesn't open, copy the URL it into the network stream address in VLC.

Video of part ejection

Overview

Cerealbot Development
Unmodified Printer
Unmodified Printer
Concept Design
Prototype Frame
Workspace
Climate Container
Glass Build Plate

Regardless of an assortment of companies or model types, low cost FDM 3D printers operate on roughly the same level. Whereas I can incrementally fire off several dozen pages across multiple document types to our shop's laser printer from the comfort of my own home half an hour away, I can pretty much only 3D print while I'm present in the room to scrape each part off the build plate. This project, CerealBot, is my attempt at fixing a few of the issues that keep FDM printers out of practicality for a range of use-cases by making a low cost 3D printer serialized.

It is my hope that this project will bring about an affordable printer that can be placed in a school and maintained in a low-overhead, ad-hoc manner. The serialization will also allow for maximal student use from each printer, meaning that more investigative minds have access to this technology.

Method

The current Cerealbot will cycle its hotbed up to ~60C a few times, and the process of heating up and cooling down the part tends to remove its grasp on the build plate. Then the print head can push the part out of the way. BUT: if the part is printed underneath the print head's home location, then the print head will wind up drilling down into the part before trying to sweep it off the plate! To allow for use of the entire print surface, I've added a servo to the hot end which will swing down an arm to push parts off, this alleviates the issue of needing to lower the entire print head and risk crunching the printed part.

Cron script checks Octoprint for files that have not yet been attempted
1. Script automatically starts the first new file it sees
Printer prints part normally
1. On completion, a script is called by octoprint
The hotbed is "cycled" a few times
1. Each cycle entails heating the glass plate and then cooling with the fan on
2. This process shocks the printed object free of the glass
The servo and print head scan the build plate and push the part away

Build a Cerealbot

If you want to make your own serialized printer, start here.

Prerequisites

Borosilicate glass hotbed
1. I really recommend getting an inductive Z sensor (8mm) as well, they're cheap and somewhat automate the task of bedleveling!
Servo mounted on the extruder carriage
1. Mount an arm to the servo that can swing under the hotend
12/24V fan aimed at hotbed
1. Fan is wired to a 5V relay which is controlled by the arduino
Arduino to control fan and servo
Octoprint server (w/ arduino attached)
1. Optional webcam
2. Cerealbot program/scripts run from this computer

ATmega Firmware

If you haven't yet, clone the git project. In the project, go to cerealbox/avr/src. Build the .ino source and flash it to the board.

Super simple, right?

Set up scripts

The the root of the project are a ton of scripts, they must be tweaked before use. I'll be making them more flexible to a variety of printers soon, hang tight.

From the git project, make the file ../.cerealbox/apis.sh

# To be sourced into config
# Export Octoprint api key
OCTO_API_KEY="abcde"
# Placeholder RedQueen api key
RQ_API_KEY="12345"

These api keys are private, and not stored on github. RQ is our hackerspace hivemind, you can leave the api key blank and disable it in the config file.

Edit the config file to work with your printer:

pop_part: Script that cycles the hotbed to dislodge the part.
push_part: Script that uses the servo and print head to sweep the part off the bed.

I strongly recommend disabling push_part and tuning the pop_part cycles and temp for a few prints first.

Set Octoprint Hooks

This is the dangerous part. I HAVE NOT COMPLETED this guide, and you have to check that you're ready for these scripts to run rampant whenever a print starts and finishes.

Edit ~/.octoprint/config.yaml to have:

events:
  enabled: true
  subscriptions:
  - command: /home/pi/cerealbox/print_start.sh "{__filename}"
    event: PrintStarted
    type: system
  - command: /home/pi/cerealbox/print_done.sh "{__filename}" "{__currentZ}" > /tmp/lastprint.log
    event: PrintDone
    type: system

That's it, the scripts should run upon next print.

Tasklist

Measure resty vs curl
- Change all api calls to one or the other
[done] Migrate scripts into folders
Validate shell scripts
- Right now I'm scaffolding with .sh files to test the algorithm which clears the print bed, I want a few continuous days of test prints.
Fix this wiki
- Clear instructions, separate random notes from instructions.
Migrate shell scripts to python
Make project compatible with variety of printers

Script Architecture

Hook Scripts
1. on_print_begin.sh "name"
2. on_print_done.sh "name" "z"
3. on_print_fail.sh "name"

Util Scripts
1. do_write_msg.sh "type" "msg"
2. get_printer_status.sh
3. send_cmd.sh
4. get_file_status.sh
5. print_file.sh
6. util.sh
7. config

Processes Scripts
1. do_pop_part.sh
2. do_push_part.sh
3. do_proc_q.sh

External Resources

Cerealbot

Contents

Map

Overview

Method

Build a Cerealbot

Prerequisites

ATmega Firmware

Set up scripts

Set Octoprint Hooks

Tasklist

Script Architecture

External Resources

Parts

MISC

Other serial printers

Navigation menu

Views

Personal tools

wiki pages

Search

Categories

User pages

external links

Tools