gophergala / matching-snuggies

A remote slicer for 3D printers

Matching Snuggies

Matching Snuggies is a slicing software that exposes a backend slicing program (currently slic3r) through an HTTP API. A command line slicing tool is provided for ease of use and to support eventual integration with host software like Repetier-Host and OctoPrint.

Matching Snuggies is well suited for integration with host-software that may run in a resource constrained environment, such as a Raspberry Pi.

Documentation

Install

First install slic3r, the backend slicing software Matching Snuggies has chosen to support initially.

NOTE: OS X users should symlink the executable at Slicer.app/MacOS/slicer into their environment's PATH.

./build.sh

Slicing API

A REST API is exposed to schedule slicing jobs, retrieve resulting gcode, and get periodic status updates while slicing is in progress.

./bin/snuggied -slic3r.configs=testdata

See the snuggied documentation on godoc.org. See the API doc for information about each endpoint.

Command line tool

After starting, the daemon can be sent files to slice using the command line tool.

./bin/snuggier -preset=hq -o FirstCube.gcode testdata/FirstCube.amf

When snuggied is running on another host specify the server when calling snuggier.

./bin/snuggier -server=10.0.10.123:8888 -preset=hq -o FirstCube.gcode testdata/FirstCube.amf

See the snuggier command documentation on godoc.org godoc.org.

Long term goals

• API authorization
• integration with other backend slicers (Cura)
• a slicing queue that may be consumed by a pool of workers (shared configuration; dropbox?)
• cluster health/monitoring dashboard

matching-snuggies's Issues

client polls way too often

the client should poll less often the longer the job takes.

each time it polls it should double the delay before the next poll.

the delay between polls should max out at something like 5 seconds.

List available presets

It would be nice if the client program could display a list of available presets

$ snuggier -L
slic3r
hq

This can be facilitated by adding an API to snuggied to list the presets for slic3r

GET /slicer/presets/slic3r
{
  "slicer": "slic3r",
  "presets": ["slic3r", "hq"]
}

open source license

MIT, BSD or something else

POST /slicer/jobs/ -- include the list of available presets in appropriate error messages

Instead of responding with "invalid preset" and "unknown preset", we should respond with messages like "invalid preset: must be one of [hq slic3r]" and "unknown preset: must be one of [hq slic3r]".

CreateJob should respond with HTTP 202 Accepted status code on success

currently 200 OK is used. 202 Accepted is more appropriate.

use the WriteHeader method of the ResponseWriter to set the status code appropriately.

change the client code to expect 202 instead of 200