Ruida RDC8445S ( EC ) no connection to RDworks at all

[Eski1985]

Hello , im trying solve that problem for god knows how many hours already.

I got RdWorks V8.01.65
Ruida rdc8445S (EC)

already i was trying USB connection , no matter what i do , how many drivers im gonna install to the windows 10 is no connection.

Ethernet cable same thing ( using same IP on the ruida and my PC no connection )

Ethernet cable PC to Ruida , same thing.

There is no comunication at all.

I found one preson on this forum he recomendec install Visual C++ but this also didn’t help at all.

For some reason my RdWorks don’t show my model of the Ruida Controller maybe this is the issue ?
Im really have no id what the hell is going on. I would appreciate any help

[jkwilborn (Jack Wilborn)]

Multiple post here is frowned upon on this site. It take time for everyone to read through and some don’t realize they may have answered it before.

It just makes it more difficult for you and everybody else to get help.

I’d suggest you stay with the original thread.

RuiDa RDC8445S(EC) WiFi, and bust. Total Communication Lockout across USB, LAN, and some success in Wi-Fi

Can you use RDWorks to generate a file of a simple rectangle (Output to UFile), and then do the same thing with LB (Save RD File), and email the results to support with a link to this thread? I can look at what’s different between the two. We did make some changes to 2.1 to improve support for these controllers, so it’ might work with the update, but if not, there may be more things that I need to tweak.

[Eski1985]

Trust me , already check this post , and still i cannot fix this.

[jkwilborn (Jack Wilborn)]

You totally missed the point, if you don’t get a result from the original post go elsewhere or add another comment doesn’t help you at all. Just keep posting until you get satisfaction?

Don’t just keep posting.

Maybe @JohnJohn can explain it better.

[ednisley]

@Eski1985

using same IP on the ruida and my PC no connection

The Ruida controller and the PC must have different IP addresses. Then you must set the controller’s IP address in LightBurn.

The doc covers the details:

Connect to a Ruida or Trocen Laser via Ethernet - LightBurn User Guide

If that doesn’t get it started, these discussions cover the details we’ll need to go further:

Ruida 8445 over LAN not connecting - subnet issue?

Hey all, I can’t seem to connect Lightburn to my Ruida 8445 via LAN. They’re both on the same network and both connected. I can ping the controller from the PC, but Lightburn just doesn’t see it. A bit of googling suggests that is may be a subnet issue, suggesting Ruida controllers only support 255.255.255.0 subnets, whereas I have a 255.255.254.0 subnet. Before I go to the trouble of creating a VLAN just for the laser and PC, can anyone confirm this, or suggest other things to try? Thanks. …

Monport and Lightburn no longer connect through ethernet

Lightburn no longer will connect to my machine ( Monport co2 80w) I have tried resetting both machine & software. I checked, ethernet ips are the same. I don’t know what to do, I need desperate help & now I have orders to do with the rotary & it’s not working.

[Sparrow082 (Adam s)]

Hey all — I’ve been working through this for a few days and here’s what finally got it working:

You need to do all of these:

Update Microsoft Visual C++ Redistributable (just Google it, grab the latest from Microsoft)

Install RDWorks 8.01.68 or newer — even if you never use it, the libraries matter

Update LightBurn to 2.1 or newer

And the one that’s not obvious at all:

When you send a file to the controller, the filename can only be plain lowercase letters. Nothing else. No spaces, no numbers, no underscores, no capitals. Just letters.

testsquare works. test square, TestSquare, test_1 — all lock up the controller.

Hope this saves someone a few days of frustration.

[soniclab (Jeremy Hutchinson)]

@Sparrow082

When you send a file to the controller, the filename can only be plain lowercase letters. Nothing else. No spaces, no numbers, no underscores, no capitals. Just letters.

That’s an interesting one I haven’t heard yet. We will definitely keep an eye out for that.

[Sparrow082 (Adam s)]

Oz wanted me to do a test and email it to the team. I haven’t gotten around to it, I haven’t actually touched my laser in several days.I’ve been working on another project.