Ruida 6332M unresponsive and crashing

[Russell Collins]

Hi Everyone!

I have a new rig which landed a couple of weeks back, which is a FigTek branded 300w YongLing Laser with RDC 6332M controller and Auto Live Focus.

have been working through the settings over the last couple of weeks and managed to get good results with non-metal and slowly getting better results with sheet metal.

I noticed over the previous few days the machine was taking longer to boot up after turning on and now it takes about 30-50 mins from turn on to be able to move the head around (from the control pad on the machine and / or the computer).

Any files that I send to the machine just crashes the system completely and I have to do a hard reset. This happens regardless of files from the computer or trying to run a file already sent to the machine.

Seems to be a software glitch and have tried to clear the memory with "Format Memory Speedily" as well as "del all mem file" to no effect.

Any inputs on this would be wonderful!

[Gene Uselman]

I am not familiar with this controller but have a lot of experience with Ruida controllers- first check that you have the latest firmware on your controller- I recently bought a 6445 and wrestled with it for a couple months before upgrading the firmware, which cured the problem. Ruida has a website with this kind of info and files... which I cannot find right now- a member will please help us out?
It sometimes helps to delete and reload the software program as well.
We have translated the RDworks manual to English which might help at times, too. Gene

[Russell Collins]

Hi Gene, yes I was wondering if a firmware upgrade would do the trick. The supplier is suggesting its a software issue rather than hardware, and I have checked everything else I can think of. Have been searching for firmware for the 6332M without luck so far. If anyone does have a link to this, would be muchly appreciated!

[Jeffrey Aley]

Just a random thought: is it possible that you've [almost] filled up the memory on the controller? Do you upload your projects to the controller before cutting them? If so, have you ever deleted any of them?

Good luck!

[Dave Vigness]

OH GOD !!!!!

Don't remind me of that. I spent a week trying to figure out why I couldn't download a project that had to go out. Unless it's a really complicated job, the only thing that downloads and stays on the controller are the test and calibration files. START button only for me.

[Russell Collins]

Just a random thought: is it possible that you've [almost] filled up the memory on the controller? Do you upload your projects to the controller before cutting them? If so, have you ever deleted any of them?

Good luck!

Yes that was one of the first things I tried... cleared the memory and formatted, the issue persisted.

Issue now resolved as mentioned below...

[Russell Collins]

Ok... so I have now resolved the issue for the moment, although I suspect there is a persistent glitch as explained below.

I had been having issues since 20 May 2021 (as described above) and thought it was hardware or firmware, but just now finally worked out that if I uninstall LightBurn and reinstall, it works. If I load up an older file into Lightburn, it stops working again (in the manner as above).

I am still exploring all the implications, but my initial pondering is that perhaps an update to Lightburn has glitched the relationship between older Lightburn files and the Ruida controller. At this stage I am just relieved to have access to the laser again, but it seems that I might have to redraw any older files (perhaps).

I am using a MacMini M1 16/256 and everything else seems to be working fine. (This is pertinent to a post on the Lightburn forum where another user is also have issues with their MacMini M1, although slightly different to this.)

[Pete Cyr]

The LIGHTBURN programer is very responsive and I am sure would be interested in your issue - I would contact him and expalin your sequence of problems and the resolution. He may have some insights and or mod LIGHTBURN.
At least now you know it is not a hardware/controller issue.

[Russell Collins]

The LIGHTBURN programer is very responsive and I am sure would be interested in your issue - I would contact him and expalin your sequence of problems and the resolution. He may have some insights and or mod LIGHTBURN.
At least now you know it is not a hardware/controller issue.

Yes I now have a partially usable machine some of the time... I have yet to definitively articulate all the permutations of the glitch, and some days I have a machine that works, and today... I'm back to looking on forums rather than cutting stuff out. I will try to narrow down the parameters and send a note to the Lightburn team. I've given up trying to get support from the company that delivered the machine.

Meanwhile, Update on the controller... it still takes some time before the directional arrow keys become functional most mornings (20-30 mins) and then when they boot up, I check to see if I have read/write access from the computer to the machine... sometimes yes, and sometimes no. Today's variation is that the machine booted "quickly" (maybe 5-10 mins) and I had motion access to the head from both the control panel and the computer, but whenever I send a file to the machine, it just starts the air and the clock starts ticking on the control panel, but the head doesn't move at all and the laser doesn't fire (luckily or I'd have a decent hole in one spot), and I can't stop or reset the machine so I have to hit the Big Red Button and go through the start up sequence again. Curiouser and curiouser!

[Gene Uselman]

I would be looking at a new controller- just for peace of mind. They are more expensive than ours but I have to guess you already have a bit of coin invested and have a need for this to work? Just the way my mind works- when you are 75yo you have more money than time