Todd Fleming

Ignore Three.js; it's not in LW4.

> offset [x,y]: will affect the gcode generation offset. I'm uncomfortable with this. I thought mark recognition was to aid setting zero.

I suspect G92 may cause confusion. @cprezzi ?

Hmmm. Do you plan on doing rotate? Unfortunately grbl can't do that using offsets. HAAS can, but that's a bit out of reach of our users...

Since you're going to do rotate, might as well handle it in cam. Maybe a transform2d argument passed into preflight.

1 marker might not be enough. e.g.: * Assume only a 1 degree error detecting rotation (I suspect it will be worse) * You're cutting a 100mm by 100mm rectangle...

@f0x52 please use https://plus.google.com/communities/115879488566665599508 for support questions.

Locking this thread so it doesn't attract more SVG support questions. @FabCreator hopefully you'll still be able to post here since you're a member.

Maybe the node server could run on the X9 and the PC could connect to it

Right now the cam's greedy optimizer doesn't pay attention to inner vs outer. If I add it then it will get horribly confused by things like this: