I’m using MKS DLC 32 V2.1 board with TMC2209 drivers on XY belt drive DIY laser diode machine. I’m working on engraving large 318 DPI image on 40x40cm tile. The generated G-code from Lightburn came out in size of 82MB.
The job was always stops at around 14 hours running time from estimated 18 hours finish job.
I tried Lasergbrl, Lightburn, and then running offline from MKS board SD card. 3 trials stopped on about the same place, not at the same line. Lasergbrl reported connection failed to controller, LB didn’t notice anything, offline SD card just hanging.
Is the board not capable to run big file? I did success before, running 254 DPI on the same size tile with the old MKS 8 bit board. Or my DLC 32 has something wrong.
Any experience and advice will be helpful…
As a workaround you can do this to resume your job from where it stopped.
82MB of GCode sounds a bit large for this kind of task.
Please upload your .LBRN2 project file for investigation.
Are you referring to the source Image’s resolution, or the Line Interval / DPI shown in the LightBurn Cut Settings?
I’m familiar with the DLC32, but never ran such a long engraving.
Is your power supply reliable, and does the board appear to get hot?
There should be a message on the console when this happens, but letting it run for another 14 hours just to check is not an option.
Perhaps scrub through the Preview to a bit before the failure, then Start from here to reach the failure on the same day?
I’d vote for burning cardboard, though. 
My guess: Windows goes through an irregularly scheduled internal convulsion interrupting the regularly scheduled USB connection.
You’re quoting me a little out of context here 
It fails when run from the SD card as well though.
Good catch!
Scrubbing through the preview will let it run up to the failing point; you could save the shortened job to an SD card, too.
If it still fails, then the G-Code has a baked-in problem.
If it doesn’t, then the controller has issues with very-long-running jobs.
Hi all. Thanks for the replies. I think there is issues with my DLC 32 board. Today I check my Lasergbrl file which was successful running 17 hours image engraving. It was one week before I changed from DLC 8 bit to DLC 32. It used the old MKS DLC V2.1 8 bit.
The old engraving image file (G-code) has 80 MB too. So I will try now back to DLC 8 bit board and dry run the new 82 MB file to see if it will pass the 18 hours.
I set the image in GIMP to 318 DPI, dithering and set the same DPI in LB.
My assumption: it’s Ok with my laptop and its USB. There were already 3 jobs with the same file size (+/-80MB). All ran good, used the 8 bit board through USB.
I will report here how it will come
After changed to the old MKS DLC 8 bit, it ran the big job (82MB G-code) until finish (18 hours+30min). The MKS DLC 32 has something wrong
Did you use the same stepper drivers on both boards? I can imagine that you might get a heat issue. You could try to put some active cooling to the board, I had some reports of users that benefited from active cooling a lot.
I use the same motor for X & Y, small NEMA 17, single Y motor. I didn’t experience motor heat issues, I check their temp with my hand. It doesn’t feel warmer than my hand (<37°C). I use TMC 2209 step stick driver, silent and cool. My average working feedrate is 2000 mm/min. And my average job time>18 hours (per run)
Ok, the motors can take much heat, they also work fine at 100°C, I was talking about the drivers. People seem to have problems with them heating up too much.