Hi all,
running a ruida and an LMC4. When i go to extensions tab on the device settings to change API port for the lasers, it isn’t retained by galvo. Pendant and dragondrop is likewise not retained.
Is this a bug?
Cheers
Hi all,
running a ruida and an LMC4. When i go to extensions tab on the device settings to change API port for the lasers, it isn’t retained by galvo. Pendant and dragondrop is likewise not retained.
Is this a bug?
Cheers
Hello ,
Small clarification: are you referring to the IP port?
A screenshot would be very useful.
Thanks Brian,
We have reached out to the responsible dev for feedback and will reach back shortly. ![]()
Thanks for the report. It looks like a bug for the galvo device settings page.
We’ll have a fix ready shortly.
@sn0 can I ask what you intend to use the device-specific port for? I’m genuinely curious.
Thanks Jon, appreciate you guys looking into it!
I’ve got two lasers running off the same PC, a galvo and a Ruida 644XS gantry. I’m hoping to hook both into Home Assistant so I can monitor them and automate some of the workshop equipment.
Mainly things like switching the extractor on when the galvo starts framing, turning the compressor off when it’s not needed, and keeping track of when either laser is busy for some nerdy graphs!. The dedicated ports would let me monitor both independently without worrying about which LightBurn window is active.
I’ve been playing around with the API already. Interestingly, the galvo reports running with 100% progress when marking, but around 99.x% when red-light framing. Not sure if that’s intentional, but it seems to be a way of distinguishing the two.
One other thing I noticed is that the Ruida reports idle even when it’s actually cutting a job started using the Start button in LightBurn. Not sure if that’s expected behaviour?
Really excited about the API though, opens up loads of possibilities!
If you need me to test any fixes just let me know
Thanks, that’s a really cool use-case, I look forward to seeing reports of it in action.
Ruida is one of the few things where I need to share some clarification on the REST API. The status report is really only talking about how far along we are when sending a job stream. Ruida we literally write a file to the controller memory and either tell it to run it or let you push the start button on it. So to get the progress report on Ruida you’d need to have caught it right as it was sending data to it.
When framing on a galvo, 99.9% would be that it is not done because it’s still executing, even if the data is on the device, we didn’t send it the “stop” command. Something you don’t see when actually engraving since we naturally stop the job at the end of it ![]()
The bug you found in the galvo settings is fixed and will be available in the first patch release shortly.