Has anyone run this combination yet?
After a previous LB Update left my machine dead for weeks until I could get it resolved I am considerably hesitant to try the next version.
I would love to try out the new features they offer but not at the expense of the machine going down again.
Any feedback would be much appreciated.
There shouldn’t be anything that Lightburn that can take your os down.
I think you can install multiple instances.
A lot of people, including me, have a Ruida, so if you have issues, sing out.
Yeah that is basically what everyone said when it happened, but yeah it took the laser out dead as a doornail until I found a workaround and was able to get a new firmware into the machine. With help from this forum but it took a long time to get to the bottom of it.
Can you explain what your machine’s firmware has to do with LightBurn? It could possibly help others but at least be interesting information.
You can read through the whole thread for yourself here mate.
…What an odyssey, oh man.
Bottom line is that you’ve had a firmware problem rather than a problem caused by LB. Of course, that doesn’t make it any easier for you. I wonder if it’s been one of those cases where only one (or a few) are plagued by a specific problem, those errors are just as irritating as periodic errors.
I had used the machine for 300+ hours with the same firmware and zero issues prior to installing LB 2.1 The second the pc with LB2.1 connected and I sent the very first cut file across the machine went haywire. Its all documented in there, including the fix if anyone else encounters the problem in the future.
And nothing I could do with any version of LB on any other pc via usb or eth could resolve the issue until I got in through RDWorks (which allowed the machine to operate flawlessly with the same firmware) And update the firmware to one that someone else had already confirmed works with 2.1 at the time.
Anyway all that aside, Im just wanting to know if anyone has already used 2.2 with the firmware version I linked above. I just dont want to have to go through the same kind of saga if its going to give me issues.
The only thing I’m saying/thinking is that it’s very difficult to troubleshoot the software when only one or two machines are affected by it, nothing else.
If it was v2.1 Lightburn that did it, then Lightburn would have done it again. But it appears you are up and running with v2.1 (you asked about v2.2), so “LB killed your laser” does not compute.
Yeah look i dont want to keep flogging a dead horse over and over about an old topic with different people asking the same question. All the info on what happened along with the solution is available to read in this thread linked down the bottom.
All im trying to find are people with the firmware I listed in my topic that have upgraded to LB2.2 and have not had any issues.
Do you have a C02 with a ruida controller and that firmware running LB2.2 currently?
Yes, I have such a configuration with CO2 Laser, Ruida (clone KT332N) but on MacOS - and none of the symptoms you describe.
However, there were a few settings that needed to be checked and corrected, for this I usually use an LB internal “Bundle”.
You probably already know this, but the possibility that LB can be installed next to each other, (i.e. different, functional versions) makes it easier to compare changes. I use this approach for all beta and RC versions.
PSA for those new to the discussion: this involves a specific 8445 controller, which is uncommon compared with the usual 644x series and apparently comes with a unique set of peculiarities mentioned in the previous discussion. The firmware version likely applies only to 8445 controllers.
This machine seems to be the only one having problems in the fleet of 8445 controllers available to LightBurn, which suggests even if no other machine has a problem with LightBurn V2.2, this one will.
I understood this to mean you had not upgraded to v2.2 yet, and wanted to know the result of others. If I read it wrong, I apologize for the error.
That is the difference between a Forum and an Email. I once asked a boss why I was invited to a meeting that had nothing to do with my job. He said, “You never know where a solution will come from.”