Quote from Paul on June 12, 2024, 8:09 pm

Hi, Thanks for sending the YT video. Apologies for the late reply but we have been debating about the issues.

Are you able to share the G code from LB? There is an option to store the G code in LB so we can see if there is a dwell gcode (pause) in there. At this moment I am a bit stumped so let's look into this first.

Thanks heaps Paul

Quote from Rommel1787 on June 13, 2024, 6:17 am

Hi Paul

Thank you.

I have determined with help from LB that the issue is to do with a M4 command being present before the job start. LB have told me this is standard gcode for lasers. Additonally i tested with laserweb and i dont have this issue.

Removing the M4 command as instructed by LB appears to fix the issue but obviously i cant keep running my jobs directly from gcode.

I have three of your controllers. The V1 and two V2s. Both my V2 controllers have this issue with firing before job start which has ruined a number of my tumblers on my rotary jobs (issue present on flat jobs also).

My work has always been starying from absolute coordinates so it may have always done this but i never noticed untill i need to run from user or current position for tumblers.

I dont have another other controllers to test against yours but considering buying the MKS DLC32 as a backup and to compare.

See attached info - gcode file ext renamed to pdf to allow upload

Quote from Rommel1787 on June 17, 2024, 7:43 pm

Quote from Paul on June 12, 2024, 8:09 pm

Hi, Thanks for sending the YT video. Apologies for the late reply but we have been debating about the issues.

Are you able to share the G code from LB? There is an option to store the G code in LB so we can see if there is a dwell gcode (pause) in there. At this moment I am a bit stumped so let's look into this first.

Thanks heaps Paul

Any thoughts Paul? 🙂

Quote from Rommel1787 on July 3, 2024, 8:27 am

Is this forum dead? Suprised how long it takes to get support/response 🙁