Hello, I’m running a Rudia Rd6563 controller, and when running a small cut like a 1in square every thing is fine, but I tried a bigger cut, and 30 seconds into it, the controller says incompatible file and stops. Running Lightburn 1.4.03
I tried sending it to the controller and then starting
Uploaded to a flash drive
Deletes all files off the controller
restarted the controller, and the light burned.
all the same error
A casual search provides this information (emphasis mine):
Ruida RDC6563F is an offline fiber-cutting controller that can be used to control a fiber laser cutting machine. It provides an interface for the user to input cutting parameters and send them to the cutting machine for processing. The offline nature of the controller means that it does not need to be connected to a computer or network during cutting operations.
Without knowing anything more about it, the controller seems intended for a very different kind of laser machine than LightBurn handles. That may account for the “incompatible file” message: LightBurn generates Ruida instructions for a different family of Ruida controllers.
@LightBurn may have more to say on the subject.
Whats weird is it fails in the middle of the cut not the start of it.
It uses rd cutist as the normal software for it I just dont like it. For lightburn i just need line cuts and a set power level
From what you’ve described, the job fails when the controller reaches an unsupported instruction. Having that instruction in the middle of a job, rather than the start, doesn’t seem surprising.
RDCutist is apparently different from the RDWorks used with Light-burn-compatible machines, which implies the machine is not compatible with LightBurn (or RDWorks, for that matter).
Is there a way to edit the file and see what command it fails on and possibly remove it?
Unlike G-Code, the Ruida protocol is both binary and undocumented.
Some reverse-engineered doc:
That repository also includes some utilities that may be of some help:
If I’m right about the incompatible command set, then that decoder will choke on unknown commands.
Darn Its still weird that its only on larger cuts small cuts it doesn’t run into this
I ran a few tests and its when I do a bunch of little separate cuts in one run for example starts on the United states flag
Could light burn be trying to use the z axis maybe I don’t have it setup
I also update lightburn to newest version to try that
NOT if you have Enable Z axis unchecked in the Device Settings window.
Darn wouldnt happen to know any alternatives to rdcutist?
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.