I knew unionising polargraph machines was a bad idea.

My first guess is that if you press ctrl-c in the controller, you'll see lots of vector commands being sent, but lots of error responses from the machine - saying something like "this line wasn't on the page, skipping it". There's two reasons this might happen. First is that the point you've tried to draw to is not on the machine. This happens if your controller thinks the surface is a different size than the machine thinks it is.

The second reason is when the target point _is_ on the surface, but the start point is off. This is almost always the case in the period prior to your "set home" because when you first turn your machine on, the default position of the pen is an impossible, and definitely not on the board.

In the first case, the solution is to synchronise your machine and controller specs, either upload your spec from the controller (if it is correct), or download the spec from the machine to the controller (if that is correct).

In the second case, the solution is to do "set home" to make sure the machine thinks the pen is actually on the surface.

The last thing I can think of sounds a bit daft but.. are the motors turned on? Unless you energise them with a "set home" or by tapping the "motor on" panel on the touchscreen, moves will be processed properly (ie no errors), but result in no move.

sn