One of the subproblems I found with the whiteboard plotter was that it didn't like a lot of small movements and that my SVG to Path process would often generate a lot of tiny steps which could be consolidated into single steps without a lot of 'visible' changes. Firstly, let's

I recently uploaded a longer video about this, but here is the code (and maths) that relates: The main bit of maths is working out the (x,y) coordinate for a location for a point on the circle, based upon an angle. From our high school maths, that's done by

The next phase of the build was to write the control code for the module. That can be seen in this video here, and this document is the first half of that (the arch and programming): For those not wanting to scroll through the same thing a second time, here

This was an interesting sub-problem that I discovered in the Project Scribbles: when deciding what route to take, the pathing is important. There are a few factors to take into account. If you're cutting, then cutting internal holes before external ones are important, if you're drawing, less so, but your

Many many years ago (we're talking circa 2000) I read an article in a book about a V plotter used to make mammoth pictures - sheets of cloth hung on the side of a building, spray can dangled between two wires. It used Autocad to generate the path, and then