Hi,
I’m looking to buy a new motherboard to use in the 3D printer. The motherboard I’m currently using uses Marlin and I have no problem using Lightburn. This new motherboard that I’m looking to buy already has a Raspberry Pi on it. This board uses Klipper as the firmware. In Lightburn in the configuration of the Devices there is no Klipper.
I’m putting the link of said motherboard: I’m looking to buy a new motherboard to use in the 3D printer. The motherboard I’m currently using uses Marlin and I have no problem using Lightburn. This new motherboard that I’m looking to buy already has a Raspberry Pi on it. This board uses Klipper as the firmware. In Lightburn in the configuration of the Devices there is no Klipper.
I would like to continue using 3d printer and laser at the same time as I am using Marlin today.
How could I setup Lightburn?
I would like to continue using a 3D printer and laser at the same time as I am using Marlin today.
How could I set up Lightburn?
LightBurn does not support Klipper and from what I’ve read Klipper itself right now is not a great platform for supporting lasers based on the way it handles queuing.
Having sait that you could try to validate if Klipper supports g-code to control laser function. Then manually adjust g-code and send to Klipper front-end to start printing.
However, I’d think you’d be much better off going with a firmware that’s known to work well with laser engraving if that’s an important use case for you.
Smoothieware is probably the most balanced for laser + 3d printing. Then Marlin.
Thanks for the answer.
I’m sorry for asking so many questions, but I would like to clear up a few more doubts!
I don’t know if I understood correctly, in case I use the Lightburn bridge, who communicates with Lightburn and processes the information that was generated by it: The Raspberry Pi or Ruida?
Why am I asking this: Because in the case of this motherboard in question it has a Raspberry Pi.
It’s possible you’re not familiar with the Klipper architecture fundamentally. I’ll start there and then go back to your question.
Klipper is split between a very light firmware component that lives on the controller and a processing component that typically runs on a Raspberry Pi. At a high level the firmware is much lighter than things like Marlin and is only responsible for managing simple movements. It has no processing duty. That duty is handled by the component running on the Raspberry Pi with it’s relatively higher performance.
You asked about LightBurn Bridge. It sounds like you’re asking in the context of this conversation. However, you need to be aware that LightBurn Bridge is only relevant for Ruida controllers. It is an intermediary communication/relay device that bridges communication from LightBurn to Ruida over WiFi.
As far as I know Bridge is focused on data transmission. It’s not “processing the data” and driving the Ruida. At the end of the day, the information that gets to the Ruida is the same as if plugged in through USB or connected through Ethernet.
Bottom line, none of this really applies to your original question about running LightBurn on Klipper.