I've set up a gocupi machine, and whilst the drawing is really accurate, the code documentation is poor and really hard to find. I like the implementation on the command line, but it feels all sorts of clunky when sat next to an UNO based polargraph, let alone an SD.
It's really picky about gcode, (The author said it only recognizes a subset of gcode, but never says which commands) and the error messages are really unhelpful, so getting it to plot gcode output from Death to Sharpe, or the amazing Pen Plotter program seems to be an exercise in frustration for me. (I'm probably missing something simple).
It falls over a lot with random error messages, and I've just got it to draw it's first svg file after trying about 15 different svgs. The only difference seems to be that all of the svg info is in a single line, unlike normal svgs with a new line for a new instruction.
Just saying, I've had more trouble than joy with it so far, the documentation and community around the Polargraph seems far better and far less frustrating.
Re:Visualbyte
I tried the polargraph controller in processing on a RPI 3, and it was slow, and could load a queue and drive the setup, but the lightweight controller was by far the best way to go. In which case, you might as well use something like an A or an A+ with a wi-fi dongle for minimum fuss.
|