Hi I seem to have an issue with lightburn.
I am running an engrave project that hangs 5min into the run on a Co2 Omtech 747.
I have previously run this image with out an issue.
I have changed formats from stucki to dither and to greyscale all with the same result.
It starts firstly doing erratic movements then just stops and i have to shut lightburn down to get any access.
Have anyone else had this issue ?
Have you checked if there is enough space in your controller? Nb. are you “starting” or “sending” your jobs to the KT32N?
I use start in lightburn for all my projects very really use the send function
It was just a question, I do it the same way as you.
But have you checked if there is enough space in the controller, they don’t like to be almost full.
The file you are trying to send is 89 Megabytes, so rather large. What is your DPI set to for your Image in LightBurn? That’s likely the issue, and lowering the DPI will reduce the file size you’re trying to transmit. Just a thought.
And is, probably, larger than the maximum 96.3 MB available in a KT332N controller with any other files / data:
Many thanks for the suggestion will lower it and give it a go. Was at 254 DPI.
Can you upgrade the memory of the KT332N controller ?
As far as I know, the memory is soldered in and isn’t user up gradable. Doubt it’s up gradable at all.
Most co2 machines have about a 0.20mm spot size with a 50.8mm lens (2"), so you might want to try an interval of around 0.20mm (127dpi) as a start for scanning operations.
I have the same controller and it is not upgradeable, just like @jkwilborn writes.
On the statement about the spot size in the same post I can say for my machine that it has, with the mentioned configuration, a smaller spot size.
In the picture you can see a line spacing of 0.2 and 0.1, in fact you can still see a clear demarcation between the lines even in the example with 0.1 LS.
So when I engrave images I am not above 0.1mm LS if I want the best result.
Hi Jk,
Thanks for the info greatly received.
I have reduced the size of the image and reduced the DPI to 210.
The transfer / sending window is now down to
But still have the same issue when using greyscale.
This is what appears after i press start i don’t use send.
At what point is using or with this sending of a file to my CO2 too much in Kb’s, how small does the file size have too be?
I have never had this issue before, if my CO2 is running out of flash memory is there a way to remedy.
Has lightburn now taken up more of this flash memory with this latest version 1.7.08??
Is it possible the firmware is the issue with my controller?
I assume you are usb connected?
Have you tried to use send instead of start? You have to run it from the machines console.
Does the machine start to run at all?
Reading the Ruida file list with Lightburn shows what?
I’ve only had issues when there are a number of files on the machine. In order to know, you’d have to look up your controller and how much room it has on it. Many times that’s shared with the devices firmware.
No.
Hi and many thanks for the replies
.
To answer the questions :
Yes, USB connected.
I have sent the file to the controller (instead of using start) which the controller accepts and then runs if i press start on the controller.
No files listed in the file list and have formatted the memory so empty.
I have just ran a smaller version of the image of 25Kb which transferred to the controller in just over a minute without an issue ( the transfer went to 100% and the engrave ran ok.
I then doubled the image size (changed no other setting) and tried again, now 50Kb, this started ok, Laser started the engrave until it got to the 70% sent point then the laser head started to over run its position on both sides (so lost its position) of the image and then hung (head stopped), at this point the l could do nothing from my laptop.
I had to press stop on the controller to get it to home, as soon as i did this it then continued to send the file to the controller.
Light-burn wont allow you to do anything until this transfer is complete.
I have also noticed that the transfer progress starts getting slower almost as if it is struggling to find space in the memory and this causes the issue.
I think this controller has a memory problem do you think i should be looking at this as the fault??
Has anyone else had issues with controller memory that may create a fault similar to what i describe?
I have just carried out another test by pressing start on my laptop with out the machine in the ready state.
Here you can see the transfer progress and size of file. it got to this point, and lightburn stopped.
The controller had the error message (open cover protection work paused), which was not the case as all covers were closed.
So it seem even with the machine in a non ready state, yellow light to green start state there appears to be an issue.
Was this with the larger file or the small one?
Was this using start or send?
Hi Tim,
Your 1st question
This was the larger file.
Your 2nd question
I used the start option
That tells me you should use the send function for larger files. I use send for all but the simplest jobs on mine. Have not had any problems. I have heard of others having issue with using start, which is why send is the recommended choice.
From what I understand, start streams the data. When the controller has enough info to start processing, it does while the rest of the file continues streaming until the controller has it all. There can be a lot of EMI caused by the laser running that can cause communication issues like you’re seeing.
Just my 2 cents.
Edit: I also connect via Ethernet through my LAN rather than USB. Historically Ethernet seems to have fewer communication issues than USB.
Ditto…
If your machine can talk to the Internet, it can talk to the Ruida as there is no drivers that need be installed, they are present. It’s a defined system with less amount of variables that in the serial communication of usb.
I had both computers connect to the Ruida, and I can send data from either.. the Ruida too dumb to send error messages or seem to care who talks to it. I blame a lot of this on the udp/ip is uses instead of the normal tcp/ip protocol.
Maybe the new Ruida will have this fixed, along with a dynamic IP or at least one that you can change via software…
I agree with @thelmuth that you should use send rather than start.
My thanks for the info and will give your recommendations a go and see what happens.
I think as lightburn evolves the controller will struggle, hopefully a new version will help.
I guess they heard your wish, a new controller upgrade from the 6445 model.
