Trying to get started and having some issues with Lightburn. Trying to make a simple gradient burn to test parameters for best results.
I’m exporting to g-code files.
One behavior I noticed is the laser not turning off, even when navigating. Another was the opposite. The first test didn’t turn it on. I rewound, started again and turned on the laser with the soft button.
The results seems to be nothing but 100% laser burn.
At first Lightburn suggested checking the $32 setting, but when asking for more help they changed the answer to “We don’t support the MASSO controller”.
Is there a way to inspect and change settings via the controller? Would I have to physically wire up to the MASSO via USB to get access to settings and functionality that I can’t do via g-code?
Yes. Just installed it the other day. I did follow that, and got the mentioned results. I can’t tell if LB truly believes they don’t work with MASSO of if they just don’t want to deal with it. Pretty sure someone with experience in this would know how to get this working, but I’m still floundering my through the learning curve. I went back to Aspire to experiment with basic concepts and getting to know the laser.
I image its because lightburn can’t take control of the controller.
If you exported the gcode and loaded it on your controller and the masso header is in there its not a lightburn problem and we have to look at Masso and figure out what’s not right
I’m pretty sure no. And if you can, id love to know how.
It’s a standalone controller. Since it’s intertwined with the motors and stuff it couldn’t control it.
The buildbotics controller is a Linux based system and the interface was an internet browser. If you were able to escape the browser you could theoretically control it (assuming you can run lightburn on a raspberri pi)… but i hated that system so much i refused to get it so i can’t confirm if it was possible