We are discussing this internally with the aim of providing a more thorough answer to what we think the issue is.
1 Like
I just noticed that your profile says âMacBook Pro running Big Surâ. Since you mentioned that you tried the file through RDWorks and there was no issue, it never occurred to me to check.
There is a known issue with the USB driver that ships with newer versions of MacOS that causes communication issues with Ruida controllers (or any FTDI device that relies on hardware flow control).
If you ran the files in RDWorks under Windows, but ran the files from LightBurn on a Mac, itâs very likely that the issue is the flawed MacOS driver, not LightBurn itself. FTDI, the company who makes the USB chip used in the Ruida controller, has released a driver update that you can download and install from here: VCP Drivers - FTDI
1 Like
This selection for the USB method is this in Windows only ? As that appears to be a Windows OS window. If so where is this in Mac or does it not exist in Mac OS ?
I did SEND file from Lightburn
My Macbook Pro is 16" 2019 model with i9 intel processor. i ran Windows 7 in Parallels to run RDWorks so it used the same hardware.
Are you running LightBurn from parallels as well? If not, theyâre using the same hardware but different device driver software, and that will likely be the problem.
I am running Lightburn natively on the Mac. I would assume virtualization of USB would be more problematic than native hardware / drivers
Well, you said RDWorks was fine, so I would assume it was ok, but that is an assumption.
In the other hand, I know for certain that the drivers shipped with more recent versions of MacOS are flawed, so Iâd suggest trying the newer drivers I linked to.
Even just running the trial of LightBurn through Parallels would let you verify that the behavior of LightBurn is the same as RDWorks under Windows.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.