Incompatibility Ruida 6445G dsp controller with Lightburn?

Hi, Since 3 months I have a new CO2 laser with a 6445G dsp controller. The machine has a add-on pc (windows 10 platform) unit to operate the lasermachine directly. Now the Dutch retailer were I bought the machine from has RD Works installed has the standard laser burning software. I am however a big fan of Lightburn so I installed Lightburn, imported the machine specs into Lightburn and start working. Now in the three months of using the machine I encounterd a few operation problems. One of the major problems is that during the lasering of a project the machine suddenly stops moving on the Y-axis. Therefore lasering/engraving everything only on the x-axis and therefore ruining my project. Also the importing of some dxf files (specific with multiple layers) does go flawless. Ofcourse I talked to the retailer about these issues. The importing issue seems to be a known shortcoming of RD Works. The more reason to keep using Lightburn. However the other issue is a serious one. And this weekend the machine completely shutted down. The machine is not operable any more with the X and X buttons on the machine panel. When the down Z-axis button is pressed, the machine goes up and pressing on Z-axis up results in the up movement of the laserbed. Also resetting the machine doesn’t solve the problem. Normally when resettting the machine the laserhead moves to the HOME position (in my case left-top), now the laserhead sits in the right-bottom corner. My retailer says that Lightburnig causes this problem. His argument is that Lightburn overwrites the controller settings and therefore messing up the controls.

What I want to validate are 3 things:

  1. Should Ruida 6445G DSP controllers be fully compatible with Lightburn?
  2. Could there be a conflict of some kind when using RD Works and Lightburn on the samen machine?
  3. Could the retailers argument be true that when using the machine normally (no settings or whatsoever are changed, only svg files are executed)?

LightBurn does not change anything in the machine configuration or the settings in your (or someone else’s) Ruida by itself. Unfortunately, it is probably too late for the deal, but you should have made it a condition that your Ruida controlled laser, like all others, can run under/with LightBurn. If it can’t, it is not worth buying - in my world.

Thanks for describing your homing issue.

In your device settings, is the origin set to the corner it usually homes to?

If you have RDworks and LightBurn open at the same time, they may ‘fight’ for the USB port.

Did you change any of your firmware settings in the machine settings of LightBurn?

Because that does not involve LightBurn, it will be easy to diagnose. Unplug the USB or Ethernet cable from the machine so nothing else can affect it.

When you turn the machine on, it should home correctly. If it does not, then something has gone wrong with the home switches or the controller.

Plug the USB or Ethernet cable in again, turn the laser on (it will once again not home correctly), and start LightBurn.

In LightBurn:

  • Go to Edit → Machine Settings
  • Scroll down a bit to the Vendor Settings section
  • Click on small triangle to open that section
  • Agree you want to continue

The X and Y Axis sections should look like this, perhaps with slightly different wording:

Verify that Enable Homing is True for both axes.

If the other values resemble what you see above, then

  • Unplug the USB / Ethernet cable
  • Turn the machine off and on again
  • It should attempt to home

If the head starts moving away from the home switch on either axis, invert the Direction Polarity switch for that axis.

If the head moves very slowly on either axis, invert the Limiter Polarity switch for that axis.

If the laser head sits there without moving at all when it’s turned on or reset, then the controller is defective.

If you know the appropriate “Vendor Password” for RDWorks, then you can (presumably) verify & adjust those settings without using LightBurn. OMTech was unable to produce a working password for my KT332N controller, so I cannot show an example.

Try those tests and report what happens, as the results may suggest other tests.

All these issues seem more like a hardware failure to me.

  1. it has been working
  2. it fails in the middle of a job
  3. machine console is also not working correctly
  4. doesn’t home when booting
  5. Z axes is also not homing

IMHO, I can’t see this as being a software/controller configuration issue, unless they purchased the gremlin option.

I’d suggest, upon failure

  1. look in the electronics cabinet for any red error condition led’s on any of the motor drivers.
  2. check the Ruida for an error indicator on the device itself
  3. check all low voltage supplies

If you visit the machine settings, make sure you save an original copy for safe keeping, just in case.

:smiley_cat:

1 Like
  1. Yes I run this controller with Lightburn 2. One program may not be releasing the USB port, try unplugging cable and plugging back in to new port number, then try connecting on that port. 3. No, I use both vector and graphics files with no problems. you could try reloading your preferences file from prior to these problems, Edit>Preferences>load Preferences Backup. Default Controller password is RD8888.
1 Like

Tnx for the explanation. I will look into it right away and come back with the results

Hi Jess,

I never have RD Works and Lightburn opened simultaneously. And I didn’t touch the machine setting either.

You are problably right Bernd. I am now in discussion with the seller. I asked him specifically (before I bought the machine) if the machine could work with Lightburn. The answer was not strict yes or no but something in the line of …“the machine comes standard with RD Works so I don’t know if its compatible with Lightburn”. This should have rang alarm bells on my side :frowning:

If it uses RDWorks, it’s likely Lightburn compatible. Normally I use a Linux machine, so I can’t use RDWorks. Makes for rater a moot point.

I found the USB connection very unstable, so I swapped it all over to the Ethernet on my lan.

Good luck

:smiley_cat:

1 Like

I would have a look on the files stored on your controller, and delete some/all, will work best one by one if its overloaded. When its memory is full it behaves strange at least my 6442 does