Cheers Hendrik, I will have a closer look at this too. I admit I've not been testing so hard on the regular _a1 code because I've been preoccupied with the _mega branch, so it's possible I've just done something very stupid.

I am assuming that your r243 test routine was the same as your r190 test routine, that is, update firmware, upload machine spec to machine, set home, then draw vectors. So the first actual drawing command will have been the same for both versions.

One test you could do is to make a note of the values in the first command (or the command that sends the machine off on a wild goose chase), and try and move the gondola to those coordinates by using "move pen". Press "i" to show the debugging overlay that will display the mouse position in steps and mm. And I'll get a chance to look at the _a1 code later this week.

The difference between the two versions is that the later version uses Longs instead of Ints for positioning, which is important if your machine cords get longer than 32,768 steps. If they don't, then you will be fine with the old code for the time being, but I will figure it out too.

Cheers!
Sandy Noble

OK, great I finally found it! It only occurs when the is no area selected.
I did not care about selecting an area when drawing vectors. In the interface you also can't select an area when there is not bitmap image loaded. It also seems that having a frame selected is not sufficient. The difference between frame and area is not so clear to me.
The workaround that works for me is to load an image first, select an area, clear the image and load a vector file.

.. nice to start the week with a solution!
And glad I found out this way about the debugging overlay.

Sandy thanks for your time to investigate on this.