However, the maximum camera resolution in LightBurn seems quite low compared to the ~4000x3000 pixels of the M1 camera, so the resulting pictures look quite blurry in LB. Yes I’ve got it working, somewhat (see below). Meanwhile my demo license of LB is set to run out in 6 days or so and I have not yet been able to actually use it to try it out. The whole thing seems crazy, because if the machine can run of GCode then it should be fairly straightfoward to interface it with other software, no? I’m coming from the 3D printing world and use all sorts of mainboards, firmware, slicers, etc all unified by the use of GCode, so it’s a world I’m somewhat familiar with. This is after 6 emails back and forth they tell me this, and still have not told me how to start xLB in developer mode, nor can I find the docs explaining how that works. Apparently xLB needs to be run in developer mode to be able to import GCode from LB. If you are a M1 owner, I’d reach out to xTool - the more of us that complain, the more likely they will patch the firmware, like they did with the D1 to make it work.Īs a work around, they told me that gcode from LB will work imported through their LaserBurn software - the software they are sunsetting in favour of XCS (which cannot import GCode).
I don’t hold out much hope and I’m pretty disappointed by it - I never would have bought the machine if I knew I’d be stuck with their crappy house software. Which I said was silly because they both have the same laser. They also tried to tell me the D1 was a “more professional” machine, hence it working with LB. I said to them just make it work with the laser and save the cutting tool for XCS, that’s fine.
I did not, but xTool/Makeblock confirmed that the firmware of M1 is not compatible with LB at this time - they tried to say it was complicated because of the cutting tool.
0 kommentar(er)
