Ultimaker Operation Manual: Difference between revisions
m (→Checklist: Clarified stop instructions) |
(No difference)
|
Revision as of 03:54, 26 October 2012
This page holds instructions for transfering G-Code and doing the print jobs on the Ultimaker. For generating the G-Code see Ultimaker Slicing Page.
Overview
Currently, the working Ultimaker is hooked up to a RaspberryPi sitting on the small workbench behind the bar.
Until Rob fixes his cloudslicer project (which is already totally sweet but only runs Slic3r for the moment), the procedure is to generate G-Code on your computer or the hacklab public computer with Cura and then upload the gcode to the RaspberryPi and run pronsole via SSH to serve it to the ultimaker.
Checklist
- Check there's no damage to the blue tape on the platform. If there is, unpower the ultimaker and replace it as it will cause you grief later.
- RaspberryPi is powered
- Ultimaker is powered
- USB cable to Ultimaker is plugged into RaspberryPi (Blue light comes on)
- Generate G-Code Ultimaker Slicing Page
- Transfer G-Code to RaspberryPi (SCP)
- SSH into RaspberryPi
- Run "pronsole"
- Enter "connect" at prompt
- Watch for printer to initialize
- Load g-code file "load <file>"
- Heat up extruder with "settemp 220"
- Watch heat using "gettemp"
- Wait about 10-30 seconds at temperature
- Extrude 1mm at a time until ooze seems connected to your command "extrude 1"
- Be careful. If after 5mm the plastic doesn't seem to be flowing, stop and cool it down. The Bowden cable may have come loose again or something else might be happening.
- Run print "print"
- Finish by using "exit"
If at any time the printer needs to cease printing, run "pause" and then "reset" from pronsole. Move the bed out of the way by running "move z 20" so you can remove the half-printed model. In emergencies, disconnect the power and data to the Ultimaker (note this will require resetting the rasberry pi)
SSH
The RaspberryPi running the ultimaker is accessed at ultimaker.hacklab.to or 192.168.111.23
User is: hacklab
Password is: hacklab
SCP
Upload G-Code using SCP or WinSCP if you need to.
scp <your file>.gcode hacklab@ultimaker.hacklab.to:
Let's try to keep the main folder uncluttered so if you're using the Ultimaker a lot, please make your own folder /home/hacklab/<username> and stick stuff in there. The RaspberryPi does have limited space so clean up after yourselves. We might use LDAP or simple SSH mounts to your shell.hacklab.to user accounts soon.
pronsole
The in-terminal help function is very useful. More details to come if people need it.
Troubleshooting
- No plastic is being extruded
- The bed may be too close to the extruder. This is very very bad as it can cause the bowden cable to build up pressure and eventually tear itself loose.
- Relevel the bed using the adjustment screws
- Check the endstop for the Z axis to make sure it's still homing to where the nozzle is just barely hitting the bed in the center.
- The bed may be too close to the extruder. This is very very bad as it can cause the bowden cable to build up pressure and eventually tear itself loose.
- Printer never connects or only spits out crazy symbols
- "exit" then restart pronsole. Now run "connect 115200" or "connect 230400"
- If that doesn't work, depower everything and restart
- Nothing is sticking to the platform
- Some unsticking is alright but if more than about 5% of the starting layer isn't sticking there may be a problem
- Replace the tape on the bed
- Relevel the bed
- If the bed seems like you can push up one end and the whole bed flexes instead of moving as a whole, there may need to be some screw retightening.
- Some unsticking is alright but if more than about 5% of the starting layer isn't sticking there may be a problem
- Print doesn't look good
- Platform may need leveling
- Z axis may need greasing
- Contribute to some tuning of the G-code profiles at Ultimaker Slicing Page