You are confused.
The format of the file save has absolutely nothing to do with the communication between LB and your controller.
You are taking a scattergun, rather than a scientific approach to your problem.
@Chara6 and @SJDR both have Ethernet-capable DSP controllers but are using the much-inferior USB connection.
Why?
These boards are full of people reporting problems with USB on Ruida, many of those problems exactly mirror yours, but you are persisting with a known problematic system when a cheap, reliable and easy solution is right at hand.
Why?
1 Like
Why use USB?
Because Lightburn never picked up my laser when I installed it and tried using the ethernet cable supplied with my laser.
It does recognise it with USB so I continued using it.
If USB is not recommended, maybe that should be communicated to the customer during the installation process.
Here’s some facts:
As I’ve repeatedly pointed out - it has worked flawlessly hundreds of times using lbrn format and usb cable.
The only thing that changed when it messed up was saving as lbrn2 format
I changed back to not saving a lbrn2 and it worked perfectly again using the exact same design.
How much more scientific do you want to get?
Yes, the failure sample was 1, so it absolutely could be a coincidence.
Yes, I could spend hours and hours testing an intermittent problem and using my materials in the process but I’m not a beta tester or a LB developer - I’m using a fully paid version of the software.
Part of my job is software testing/UAT so I’m happy to work with Lightburn on this issue if they have any suggestions or require any assistance, but it doesn’t look like it’s high on their list of priorities.
I’ll stick to using the old format for now and maybe if enough people report this issue, the developers will get to the bottom of it (regardless of whether or not it’s related to file type or usb cable, 9.24 or something entirely different) and we can all move on with life.
Hi Bo,
I’ve actually talked to a couple of people on a different forum that are having this problem and they aren’t using a usb cord so I figured the cord wasn’t the issue. I’m not sure that is the solution but I’ll give it a try.
You didn’t read the instructions, did you?
Auto detect doesn’t work over Ethernet.
Blaming the tool you didn’t read how to use is not uncommon
I have had similar problems and have read the responses regarding USB cables and wifi. My work prints clean when I “send” the file to the laser from LB or load it from a USB fob. bypass the cables and my issues went away. (for now)
CAH
Quite the contrary, I’m desperate to figure out what’s causing this, but haven’t been able to reproduce it even once in house.
For 0.9.21 I changed how the connection to the laser is managed - It used to be that LightBurn would connect to the laser on startup, and release the connection when you quit. That meant if you ran a 2nd copy of LightBurn you couldn’t send to the machine with that copy, because the 1st one was holding the connection to the machine, and only one can talk to it at a time.
People complained about this constantly, so it was changed to open the connection when you do something that interacts with the machine, then closes the connection when it’s not needed any more. For some reason, for a small handful of users, this is causing intermittent issues like you’re seeing. I haven’t been able to figure out why.
Thanks Oz,
Apologies, - I wasn’t having a dig when I said it wasn’t a priority. I should have worded that better.
I actually did have the issue of not being able to connect the 2nd instance of LB to the machine (hence why I got into the habit of saving one of the files, then closing LB and opening the saved file to run it).
If it’s any use, I can send the lbrn2 file that had the issues if it helps you replicate it. It was an imported svg, not created from scratch in LB.
As I mentioned, it’s the first time I used this format and had the issue so I’ve reverted to the old format so I’ve only encountered it once.
Send it to support@lightburnsoftware.com and include a link to this thread - I’ll try running it here. What controller model are you using? (not just “Ruida”, but the actual model number?)
Hi Oz, I sent the files along with my info to the listed address about a week ago and included this thread but haven’t heard anything. I’ll resend right now.
Hey Oz, I sent the info and files twice. I hope you saw it
I did - we’re just still getting set up in the new space so there are a lot of other demands on my time at the moment. Might take me a bit to dig through this.
Ok, totally understandable. I’m still having issues and still trying to figure them out. I’ll keep trying to troubleshoot.
I will confirm this issue as well. Very intermittent for me almost rare. However it has ruined expensive jobs. It is not a usb cable issue at all. I will say it shows up more for me on jobs that took a while to send the entire data packet. I sometimes use the ramp option on complex artwork as I pour epoxy in to engraved wood and having the edges ramped helps to not have air bubbles along the edge. However I get this issue very often when ramp is used. Generally never see it otherwise. To me it seems to be related to large files and having lb run before the entire packet is transmitted. Actually over four years anytime I have seen weird failures in engraving it was with large files that took up to 30 seconds to transmit along with having lb start the run immediately verses waiting for the entire file to transmit. That’s what I have seen so it is a bug…I get the same random lines.
I had issues with the Ruidas handling of the usb port, and different computers and sneakernet. Finally I went with Ethernet and I’ve had no more worries or issues. I’d suggest you try that. My Linux box is in my computer room and China Blue is in the garage, opposite ends of the house. If it’s happening with large files, Ethernet will assure that it’s not a communications issue.
I originally plugged the laptop directly into the Ethernet of the machine and ran it that way. No Ethernet out there so bought a bridge for 25 bucks and it runs wirelessly through the local network. So far it’s been very reliable.
You can also right click on the ‘device’ button and it will try and re-establish communications on either port.
Good luck, take care… (8o)
I have had the same issue with the 50w, not sure what causes it but here is what I do to fix the issue…
- Deleted all files from the controller
- Downgraded LB to V 9.19 (last version I used successfully)
- Opened and resaved files that had issues
- Shutdown and restarted the laser
- Upload and run files FROM THE CONTROLLER only.
This seems to work for me though not certain which step is the fix.
Ok, I’ll try these tips. Thanks
Did this get addressed with the new 1 0 update by any chance?
I’m hoping so, yes - I’ve never been able to reproduce this issue myself, which makes it incredibly hard to troubleshoot, but a lot of under the hood things have changed for 1.0.
Cheers - I’ll test it as soon as I get chance and let you know how it goes.