that’s about the size of it. I’m working in inches, and I’d like to export the file to run remotely on my machine. If I switch to metric, the issue resolves. It appears that the export runs the same conversion on time that it runs on length.
version 1.7.08
thanks
If you multiply you entered Pause time by 25.4, do you get P2.54 in the GCode output?
The current release is v2.0.05, so I wonder if this still exists. Can’t check right now…
Yes. That’s how I got to the results above. When i switch to metric, the p value matches the start pause value (with the gcode in seconds and the input in ms, of course).
I entered 2540 ms in the Start Pause Time box. It is fixed, so you may need to upgrade. 
; LightBurn Pro 2.0.05
; GRBL device profile, absolute coords
; Bounds: X111.08 Y243.18 to X252.19 Y295.22
G00 G17 G40 G21 G54
G90
M4
; Cut @ 6000 mm/min, 20% power
M8
G0 X111.084Y243.185
G0 Z0
G4 P2.54
; Layer C00
G1 Y295.224S200F6000
G1 X252.192
G1 Y243.185
G1 X111.084
M9
G1 S0
M5
G90
; return to user-defined finish pos
G0 X380Y380
M2
It looks like you’re outputting in millimeters, which works for me, too. Would you mind trying to switch your machine setup to inches and then output?
Thanks.
Device Settings= Inches/min.
Start Pause Time = 2540 ms.
; LightBurn Pro 2.0.05
; GRBL device profile, absolute coords
; Bounds: X103.08 Y268.2 to X158.12 Y306.23
G00 G17 G40 G20 G54
G90
M4
; Cut @ 196.85 in/min, 50% power
M8
G0 X4.0582Y10.5592
M3
G0 Z0
G4 P2.54
; Layer C00
G1 Y12.0564S500F196.85
G1 X6.2252
G1 Y10.5592
G1 X4.0582
G1 S0
M9
G1 S0
M5
G90
; return to user-defined finish pos
G0 X14.961Y14.961
M2
1 Like
Ah yeah, that looks good. Guess there’s nothing for me to do except decide whether to upgrade or write a script to fix it post export. Thanks for the help!
There is always the Upgrade option if you are running Win10 too.
Consider this… How many times might you forget the script in the next year and scrap a project?
The plot thickens. Apparently I only have this issue if I’m using the custom Gcode controller (admittedly marked “experimental”). I tried each of the GRBL variants, and the output is as expected. The only thing I don’t like about those is that the pierce delay shuts off the fire signal before moving on to the first layer cut…I’d like pierce and cut to be continuous, hence the custom gcode controller. As long as I don’t need more than 0.4 seconds delay, maybe I’ll be fine to just multiply my desired delay by 2540 in the library.
I do not use this feature, so I am no help with this one. 
that’s alright, my man. I appreciate you helping me out in the first place. I’d have been even more upset to buy the upgrade and then realize it was just my stupid self not paying enough attention to the options available.
At any rate, I can’t really complain about a feature that doesn’t work the way I expect when it’s marked “experimental” and I’m already pushing the envelope by using this to run a plasma cutter offline. It is what it is.
Thanks again, and have a great week ahead.
Plasma cutter? Experimental setup with experimental features. You do realize you are a pioneer in this field, right? 
very generous of you! But I do understand I’m putting a few round pegs into a few square holes…
I can say that custom GCode has gotten a LOT of work since 1.7.08, but I’ll check to see if that conversion issue is still there in the current version.
1 Like