I am beginning to think the 10W was rushed so they could move on to the 20/40W. I think any attempt at getting it right had been put to the bottom of the priority list.
As mentioned many times, the 10W camera resolution is awful, much worse than the 1.6W. It’s just the same camera, used higher up, and digitally zoomed.
And as also mentioned elsewhere, what is the point of the undocumented image quality setting??
But, I realise now also that the 10W (maybe Luban) has an error in that the positioning X,Y used by Luban to create the Gcode is based on Machine X,Y (i.e… the bottom left corner of the bed) but the machine attempts to process the Gcode with reference to the Work Origin, which is by default, in laser mode, the centre of the bed.
So, within Luban, you obtain a reasonable background photo of the bed with your piece of material. You position a simple shape from Luban’s tool-bar onto the image of the material, process a tool-path, and view it in the preview. You can see from there its position relative to the grid display that your design is in the upper right quarter, say X200,Y200 from the machine’s origin. this is confirmed when you go to ‘Workspace’. You then send the file to the machine.
On the machine you see that the work origin is 0,0 at roughly the centre of the bed. When you run the file or just the boundary you will see the machine tries to add another 200,200 and so goes to 400,400.
There are many work-rounds of course. One is to run the machine to bed 0,0 and then hit Set Work Origin, which means you’re basically back to manual positioning and the advantage of the camera is lost. It also will run directly from there to the work-piece hitting any clamps you have.
It’s no good glossing over these work-arounds though, it shouldn’t be necessary.
How difficult is it to fix!