K40 stops just a few seconds after I press start

[donhart1966 (Donald Hartsaw)]

Using Windows 10, Cohesion3d laserboard on a K40 with the most current version of lightburn. Once I press start, it starts just fine but runs for about 5 seconds then stops completely and it’s showing in lightburn that it has finished.
What could be causing this?

[jkwilborn (Jack Wilborn)]

Might want to post what you are working with. The .lbrn file would probably ok, as that would give us your settings for the layers.

It sounds like the machine thinks it’s finished the job.

[donhart1966 (Donald Hartsaw)]

It’s just a basic 2 layer file. It also does the same thing on other files not just this one.

Ram Reunion-1.lbrn (299.5 KB)

[DavidF (David Fenton)]

Hi Donald, the file you uploaded is slightly different than your screen shot and has 3 layers. But given that the file looks good and the Gcode looks correct. Preview time is 7:mins 45 secs. Could it be a electrical noise problem, or long USB cable perhaps? that is causing the controller to stop?

Cheers

David

[donhart1966 (Donald Hartsaw)]

I’ve used the same USB cable for years without a problem. But I did switch it out for a brand new cable. But it’s still doing the same thing. Not sure what you mean by electrical noise though. I’ve checked all connections and everything seems to be ok. It’s frustrating. I have an order to fill but will have to refund them at this point.

[Squid]

Hi, here’s my two cents.
I have a k40 with Smoothieware based controller and when the transfer mode was set to Bufferd I experienced the same: scan stopped after two lines or so.

Since I switched to Synchronous mode - all’s good.

I am not saying this is the solution for you cause many uses the Buffered mode which should be faster, but this mode does not work for me. so you can give it a try and see if you get different results.

[DavidF (David Fenton)]

By electrical noise I am talking about something switching that is generating a spike on the supply line to the controller. Possibly something in the laser itself or external. Others have found that loose ground connections can cause this type of fault.

[donhart1966 (Donald Hartsaw)]

You are a game saver Squid. I have no idea how that setting got changed. Thank you so much for your help.

[Squid]

@donhart1966

You are a game saver Squid. I have no idea how that setting got changed. Thank you so much for your help.

You’re walcome.

Gcode Controller - Transfer Mode

“Buffered” means that we send data whenever there is room for it in the receive buffer of the controller, regardless of whether the controller has sent back ‘ok’ responses or not. “Synchronous” means that we send a single line of GCode and wait for the ‘ok’ for it before sending the next one. All controllers will push code into a block queue for motion planning, so there is an internal buffer that holds some number of moves in advance of what’s actually being executed. The serial receive buff…

Gcode Controller - Transfer Mode

That’s the same firmware I run, but mine is on the LPC1769 board, running at 120 MHZ. It’s not impossible that’s the problem - it was written and tested on the faster chip.

@LightBurn
It seems this is not LPC1769 nor LPC1768 related. Just FYI as Donald is using a Cohesion3D LPC1769 based and I am using SKR LPC 1768 based controller.