These are notes for myself on the crouton setup for my chromebook

1. Enter Developer Mode

Hold Power+ESC+Refresh, then let go of the power, when the OS verification warning screen appears enter Ctrl-D

2. Setup Crouton

Follow the instructions here to download the latest version of https://goo.gl/fd3zc.

Open a chrome terminal tab using CTRL+ALT+T and then open a shell

shell

Figure out what version of linux you want to run here https://github.com/dnschneid/crouton

Install the crouton extension in chromeos from here https://goo.gl/OVQOEt

3. Setup a chroot

I have been running Ubuntu Unity, Gnome 3 and enlightenment using an Ubuntu Trusty Tahr release.

sudo sh ~/Downloads/crouton -t keyboard,extension,unity -r trusty -n unitytrusty
sudo sh ~/Downloads/crouton -t keyboard,extension,gnome -r trusty -n gnometrusty
sudo sh ~/Downloads/crouton -t keyboard,xiwi,e17 -r trusty -n enlightenment

After the instalation is complete you will set up your unix username and password for the chroot in the terminal.

Once the chroot is done installing and you have set up your user you launch your chroot using:

sudo startunity
sudo startgnome

Crouton Command Cheat Sheet

4. Setup Lightweight Desktop

Click the dash icon in the top left corner and search for terminal, use xterm to install software using aptitude

sudo apt-get install terminator vlc git xarchiver

Install Google Chrome

sudo apt-get install libxss1 libappindicator1 libindicator7
wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
sudo dpkg -i google-chrome*.deb

Download Cura from http://software.ultimaker.com/

cd Downloads
sudo dpkg -i cura_15.02.1-debian_amd64.deb

Download and install Github Atom

cd Downloads
wget https://github.com/atom/atom/releases/download/v1.0.0/atom-amd64.deb
sudo dpkg -i atom-amd64.deb

##5. Update Keyboard to match ChromeOS

xmodmap -e "keycode 94 shift = backslash bar"
xmodmap -e "keycode 51 shift = numbersign asciitilde"
xmodmap -e  "keycode 11 shift = 2 quotedbl"
xmodmap -e "keycode 48 shift = apostrophe at"

xmodmap -e "keycode 22 shift = BackSpace Delete"
xmodmap -e "keycode 133 = Caps_Lock"

* Optional - Install Non Free Software that makes things easier and better looking

sudo apt-get install ttf-mscorefonts-installer

sudo apt-get install ubuntu-restricted-extras

Issues

  • The keyboard command used when installing the chroot don’t do anything
  • The chrome extension with chroot chrome window functionality is not working

Notes

You can copy and paste in the shell with Ctrl+Shift+C and Ctrl+Shift+V.

I got a printrbot simple metal kit on black friday so I have had it a little longer than those who got one for Christmas. It has printed at least 4 hours a day since and I think I have it up and running pretty nicely now, here are my tips for getting great prints quickly.

I really didn’t have any assembly issues other than accidentally using the 22mm M3 screws to connect the fan.

The printrbot documentation currently recommends Repetier Host which just went closed source and is hard to use and was buggy for me on both Ubuntu and Windows 8.1 While using Repetier Host I had to re-flash the firmware on my printrboard twice which was not a lot of fun.

I have been using Cura from Ultimaker and the free Windows 8 3D Builder app. I found that Cura is the best for both printing via USB and generating gcode for upload to OctoPi, I use 3D builder mostly to fix models.

I have been getting great results with cura after adding the bed auto leveling command to the default Cura Start gcode.

G28 Z0; move z to min endstops
G29; Auto level bed add this line
G1 z15.0 F{travel_speed}; move the platform down 15mm

Then make sure you have a spool holder of some kind, I made this one to go with my aluminum handle and have been happy with it. The spool holder made a huge difference in print quality for me.

The first thing I printed was the suggested fan shroud, and after I printed and installed it I started having more warping on my prints, when I put my hand behind the fan when the printer was running there was more back blow than air being pushed through the shroud opening.

After trying a couple of different models I found on thingiverse that didn’t work any better I tried this strange looking one that works great.

Once you are able to print some things you are happy with using Cura over USB, if you have some Linux / Raspberry PI experience I would highly recommend setting up OctoPi with the rasbperry pi camera to take timelapse videos of your prints easily, this really helps figure out what went wrong when unattended prints fail.

I even figured out how to upload all of my timelapses to youtube when they are complete using octoprint’s event hooks. You can find infomation on setting up youtube-upload here. I made a couple of adjustments to my config.yaml file

events:
  enabled: true
  subscriptions:
  - command: 'youtube-upload --email="my email" --password="my password"
      --title="3D Printing Timelapse: {movie_basename}" --description="Timelapse of
      {gcode}, printed and recorded via OctoPrint on a Printrbot Simple Metal" --category="Tech"
      --keywords="OctoPrint, Printrbot, 3D Printing" --unlisted --private {movie}'
    event: MovieDone
    type: system

I did have one issue once I received a macro lens for my camera mount and the status led on the camera was creating a red moon shaped reflection in the video. Good News is there is a raspberry pi setting in order to disable the camera status led, you will need to edit the boot config file:

sudo nano /boot/config.txt

And add the following line

disable_camera_led=1

After playing with the raspberry pi a bit longer it became clear that I needed some way to make backups of the SD card used for the OS. I quickly remembered that I could easily use Win32DiskImager to write an ISO image and was able to backup my PI easily.

Then I bought bigger SD cards and moving the OS around became more of an issue as once you expand the file system to use the whole SD card any copies you make of that card are now the same size as full SD card on disk.

While I had enough disk space to back up my two distinct PI images, it seemed kind of silly. Then I ran across this blog post with some automated raspberry PI backup scripts.

Since Matt is a unix systems adminstrator for his job, it seemed like a good place to start. I have not yet implemented any of the more complex scripting of new PI creation, but I do have a process that allows me to back up the os to a smaller SD card for image backup. I can store the backups at their actual size on my ubuntu system, or you can copy the whole card to a smaller card allowing you to more easily use different size cards