I know this is a bit of an ask, but just got the 10Watt Laser, tried the sample ruler / protractor project, and used the camera for a background image to align the job with, great, sent to controller as file. Upon running a check of the boundary before running job it went way off top right, because the controller always defaults the work origin to centre. Is there a way to stick the desired work origin in the gcode, with an official command, or even just as a header comment?
<TLDR> Will luban ever change the way work origin / job setup happens to reflect real usage, rather than having to repeat setup on the controller, or manually change the work origin from bottom-left to center-center? I know using the camera messes it up, but it feels like a UX issue…
We have noticed this problem. The G-code captured by the camera cannot be separated from “Start on Luban”. We’re going to add a field to the G-code. Considering but now working well with “Start on Luban” so this job is not in a hurry
Thanks for the update. It would be wonderful if the depth measurement could be triggered by gcode, and also the camera capture and retrieval (return base64 encoded image with content type like http request uses).
The current camera capture workflow is very good over wifi, and very painful via the touchscreen controller, but if you touch the controller even once the your workspace origin is reset to centre and the machine must be power-cycled to restore origin to be compatible with camera.
Just to say I’m very pleased with the API so I can run image capture and thickness calculations from my web browser, and then use them in other software (lightburn)