Dwell Time

[marcvs]

I'm using git master of svgtogcode and j-tech with a laser driven by grbl.

I've activated Dwell Time.

This adds G4 P statements into my gcode

These statements are however added AFTER the laser did it's cut. When cutting things like cardboard, it be very useful if the dwell time is here:

1. laser powered off (m5)
2. laser is moved to next position (g1)
3. laser is turned on (m3)
4. dwell time (G4 P)
5. laser is moving for a cut (g1)

right now step 4 is done before step 1.

I'm not sure, if my use-case is different, or if this is a bug.

[PadLex]

To be honest I'm not sure how the dwell time helps. I added it based on someone's request because it easy to implement. Could you help me understand the purpose of dwelling before a cut?

I'd propose having a two integer argument like dwell_before_cut and dwell_after_cut. What do you think?

[marcvs]

I experienced this issue on my blue diode laser, when cutting white paper / cardboard / stickers too quickly. Basically, the paper will absorb better, once it got black. When cutting too quickly, this may not happen at the point where the cut is supposed to start, but along the line where a small disturbance increases the absorption. This is where that dwell_before_cut would really help.

I understand that the actual reason to introduce dwell_time comes from milling machines, where the actual milling process requires some time to settle in.

Making this configurable as you say sounds like a perfect solution!

[marcvs]

Hi There,

I came back to the very same issue. The fix seems simple. Please see the PR #29