Gcode generation timeout

[eagledawg]

Hi All,

I'm trying to generate gcode for a large SVG file (laser fill path) and it fails after 1 hour consistently. I assume this is due to a timeout setting in the code. If so, would it be possible to provide a user-defined gcode generation timeout value under Settings > Gcode to allow long-running gcode generation processes to complete successfully? Any other alternative suggestions are appreciated.

Thanks,

Scott

[cprezzi]

As far as I know, there is no timeout in the code, but it could be a timeout of the browser. Which OS and Browser are you using?

The duration for generating the gcode strongly depends on the used client computer (CPU/RAM) and some settings in LW. For example, you can configure the amount of worker threads, that LW is using (see settungs/gcode). Increase this value to the maximum of threads of your CPU.

Right the next field in the settings is gcode curve linearisation facor. This defines how long the generated G1 lines will be for curves. A value of 0.4mm is a good balance between resolution and gcode-size (=speed).

Also the beam diameter (in settings/machine or the cam operation) is relevant for the amount of gcode (=speed).

[eagledawg]

Thanks, Claudio for the background info and the suggestions - much appreciated.

My comment regarding a code-based timeout was based on seeing a timeout value below while viewing cam-gcode.js source in the Chrome debugger :

export function getGcode(settings, documents, operations, documentCacheHolder, showAlert, done, progress) { "use strict";

let starttime=new Date().getTime()

const QE = new queue();
QE.timeout = 3600 * 1000;                                       <======== 1 hour in milliseconds
QE.concurrency = settings.gcodeConcurrency || 1;

My apologies if this finding is off-base.

Also, here are the current settings for the parameters mentioned:

OS/Browser - Win 10 + Chrome v76 64 bit Processor: Core i7-8650U w/ 16 GB Ram Worker Threads - 5 Linearization Factor - .5 Beam Diameter - .1 Do I need to increase this? I have a 5500mw Chinese laser cutter

Also, for the Laser Fill Path operations, the Line Distance parameter is .15. Does this affect overall gcode generation time as well (lower value generates more commands)? And, does this value have any correlation to the beam diameter (do they need to be the same)? I have a total of two Laser Fill Path operations defined at 45 and -45 degrees to produce a good fill on my material.

The SVG file has 1 path with 63471 nodes. I've attached a PNG-version of the file for reference (looks like GIT doesnt like SVG attachments). I've tried to simplify the SVG in Inkscape as much as possible based on my knowledge of the tool. Could the file just be too complex to reasonably assume the gcode is generated within an hour?

Thanks again for your help.

Scott