Handling large files

If there are no subroutines or O calls in the gcode, you should be always able to resume or run from line. I have several clients using Linuxcnc machines for production daily and they use run from line several times a day, every day without a single issue, ever. Those machines have all the logic and routines for probing in Hal so resuming is never an issue.
Almost forgot, it will not resume with the G64 Pn active, that has to be entered manually for run from here or set in the INI file.

OK, this sounds good.

> Almost forgot, it will not resume with the G64 Pn active, that has to be entered manually for run from here or set in the INI file

Are you referring to the ARC_BLEND parameters in the [TRAJ] section of the INI file ? I have copied the default values as shown below :
# (shown to explicit default values)
ARC_BLEND_ENABLE = 1
ARC_BLEND_FALLBACK_ENABLE = 0
ARC_BLEND_OPTIMIZATION_DEPTH = 50
ARC_BLEND_GAP_CYCLES = 4
ARC_BLEND_RAMP_FREQ = 100

There must be something else, as I don't see where the <Q- > value of the "G64 P- <Q- >" is set ?

I haven't had any of the error that @Grotius reported, could it be an inch to mm bug ?
Could be. I did not have your g-code intro... :whistle:

Nice to see, the Gremlin is in full mode, while scanning the Mars surface.

If you need a restart at line, you need a line number. Save way is : keep your tool high.

Would there be a way to output the line number just processed
You could do this on several way's. One option is to output a text log file trough a hal component. This log file can contain every parameter or line you want. In fact you could do a real time texture rendering of what your machine has done already, updated every gcode line in a simple glut window. This to give you just an idea of the linux power !

@Grotius said : One option is to output a text log file trough a hal component.

Yes, I was thinking about this type of solution. Pushing the idea a bit, one could create a script that would load the required state commands, such as G64, read the last line number that was output and stored in a file, and launch the "restart from line" command.

Now I need to learn how to create a HAL component... :huh:

To log data, you don't need to write a component, you just need to get your head arounnd streamer and its mate halstreamer .

Its very useful for data analysis I found.

EDIT: Sorry sampler and halsampler

Hello @rodw,
Thank you for the pointer, but I think you might be talking about Sampler and HalSampler ?
I've looked at Streamer and HalStreamer, they seem to be concerned with streaming data into HAL rather than from HAL.

I'm looking at the MAN pages at the moment, did not realize before that this is such a goldmine of info