Ive gotten this error a few times. Just this time, I dont have a great workaround, other than send it, and then manually erase parts that engraved and send again.
I tried saving to a USB stick, but on the Nova 35, when I access it through the file menu, there is no way to run , only copy to the controller, which does not have enough space.
I tried doing a much larger sheet last week, just running, but it gives an error in lightburn, and runs until it stops engraving (like the x gantry is stuck).
BTW, running lightburn 0.919 (need to re-up our license, but we dont upgrade software that works unless there is a need)
I think this might qualify, “… dont upgrade software that works unless there is a need”.
Smaller, faster, better…
First, LightBurn has a new project file format - LBRN2 stores the same content, but in a more efficient way, making files about 4x smaller on disk, and about 6x faster to load. This will vary depending on the file content, but unless you have to share files with older versions of LightBurn we recommend using LBRN2.
We’ve also added a “sharing” system for vector and image data. In older versions of LightBurn, if your file contained 10 copies of the same thing, it would store those copies in memory as well as on disk. Now, the copies will just refer to the original until you edit them, saving additional memory and disk space.
@berainlb - Id rather not because it makes some often repeated jobs harder for some of our staff to run. I actually tried it the other day out of desperation, and funny enough, the jobs were back the next morning.
@Rick - Most of our files contain the same repeated image, but I dont use LB for creation or layout, I use CorelDraw, and export to AI. Will that still work? Sorry, I’m just used to in todays day and age losing features I liked and used to gain features that dont work 100%. And considering this machine is a major part of our operation, a bad change can set us back a lot of time and $$
Totally understand. I would try the new version in a noncritical, non-production environment as a test to see if this is the right decision for my business. Maybe on off hours, lunchtime…something like that, as to not disturb production. You should be able to load an existing LBRN file, then save as the new format, LBRN2, to compare file size and insure things produce as expected in short order. Testing and playing with the other new features may take you a bit longer as we have been busy.
The workflow used to create and run your LightBurn files remains unchanged. You keep doing the thing the way you are used to doing that thing. We changed the way this information is managed internally, no matter the source, to make it more compact and efficient.
I’ll try installing it on another machine after I buy tomorrow. Are we able to activate older copies if we need to go back?
I bet there are a lot of improvements, your software is heads and tails above what came with this machine. Ive just been burned by “upgrades” a bit too much in recent memory (my kingdom for an offline version of Fusion360… or just for my paid copy of acad 2012 to work )
@Rick Do the efficiency gains in the new LBRN2 format for storage size extend to files generated for DSP? I had assumed this was purely an internal storage format gain.
Always, and you can find all versions via this Older Version link.
Some of us are crazy and never follow our own suggestions… “Do your backups”, “Don’t intro un-tested goodies into a working production flow”, and the like. But, you want to avoid hearing how that sounds when we should have. (cringes & covers all the world’s children’s ears) Not pretty.
Thank you. We enjoy hearing the work is appreciated. Very kind.
Just an update. Tried the newest version, but still getting memory error messages when sending files to the machine. FOund that I also get a lot more failures if I just hit run instead of send to the machine.
Could it be the controller failing? Its about 6 years old now.
The size savings from LBRN2 are just for the files on your hard drive - they don’t affect what’s sent to the controller. How many files do you have on the controller itself, and how large are they? Ruida controllers typically have 128mb of working storage. If you’ve come close to filling that, you’ll have no choice but to delete some files.
You’ve said that it makes it harder to run repeat jobs if you don’t, but you can easily save the generated .RD output from LightBurn to your hard drive and just re-send them later when they’re needed.
Ive tried deleting whats on the laser, and they came back after re-booting.
Honestly until about a year ago when I had someone else come work for me running this, never used the stored files ability on the controller. Ive only ever just sent files from a PC.
Will give that another try. As for sending files, the lady who runs one of our largest repeat jobs is not exactly computer savvy, but we should be able to work something out there.
That could be indicative of a problem, or it might be that you didn’t wait long enough, especially if you were deleting from the start of a long list. Ruida controllers seem to ‘compact’ the files in memory when you delete one, moving the ones after it in memory to fill the hole. If you delete the last file in the list it’s basically instant. If you delete the first file, it can take a minute or two to complete.
If the files are coming back after deletion, that means the delete didn’t work for some reason, so I would check that. Controllers that are full, or close to full, can do really odd things.
)