Ultimaker Operation Manual: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
m (10 revisions: Import 3D printer articles with history) |
mNo edit summary |
||
| Line 4: | Line 4: | ||
Currently, the working Ultimaker is hooked up to a RaspberryPi sitting on the small workbench behind the bar. | 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 | 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 G-Code to the RaspberryPi and run pronsole via SSH to serve it to the Ultimaker. | ||
== Checklist == | == Checklist == | ||
# Check there's no damage to the blue tape on the platform. If there is, unpower the | # 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. '''Do not cover the screws with tape on the platform'''. | ||
# RaspberryPi is powered | # RaspberryPi is powered | ||
# Ultimaker is powered | # Ultimaker is powered | ||