how to start an .ngc file somewhere in the middle?

sorry to keep you waiting,
attached you find one example. The same happens on my LuxTurn in the same way so I thought, this must me a bug in Axis or LinuxCNC. But maybe, you spot where this misbehaviour comes from

regards

that is a very good point. It has to know the history of cource
When I write the code by hand I always use G0 and G1 but the cam system wants to be clever an skips them where not necessary. I'll check that out tomorrow right away

ok, so I tried that today and it works. Maybe I can ask my posprocessor to add the complete information in each line ie. G1.XYZ..., F...
Then I should be fine.
Thanks for looking into the file.

Another curious thing occured to me today. I ran a program with the G59.1 coordinate system set. After finishing the program LinuxCNC went back to G54. Sadly I noticed too late and after issuing a G0 Zxx command the end mitt went straight into the workpiece because in G54 the Z Height was set differently than in G59.1.
Would I had to expect this?

ok, you're right. I guess I should start reading through the complete documentation (and remember it all)

Rainer

I am struggling with this issue in these days. Here is my considerations.

First of all, i figured out that the machine is trying to measure all of available tools if m6 tool probe is enabled when you started from the middle of file. You are setting line number in linuxcnc via the gui. When you start it, according to logs, the interpreter is looking for T<n> commands in whole ngc file. Then it tries to measure all tools one by one.
While measuring the first tool, it jumps some g-code commands. The flow is like this, when software sees M654 T<n> command, it jumps to tool-probe.ngc subroutine identified by the path variables in configuration files. I am using this tool-probe.ngc file given in the link: forum.linuxcnc.org/10-advanced-configura...off?limit=6&start=38

While measuring the first tool, the machine makes some weird moves. Everything is ok until it reaches to the second command of G38.2.
> G38.2 Z[#<_ProbeRetract>*-1.25] F[#<_ProbeFeed2>] ( trip switch very slowly )


When it comes to execute this command, the program(this is my thought) is crashing or doing whatever, even it says retract Z from some point, it does not execute that commands after second G38.2 command, so it crashes the tool. Bu it works ok when it comes to second tool.

I didn't find a solution, but i am trying to find it. I am wondering, is there anyone faced with this issue like me? You guys are asking and trying to explain that 'how to start from middle of the file?' . I thought my problem may be a roadmap to your issues. I think this problem is Gcode related, i think tool-probe.ngc file is not working well but it may be wrong of course. I debugged the linuxcnc messages by giving DEBUG flag 0x7FFFFF in the .ini file. The result is nothing. According to logs, it is executing that commands also, but i am the one who is seeing the machine, i say it is not!

Thank you for your answers aldready, take care.
I opened a topic related to this issue, if you want tho check follow the link specified below.

forum.linuxcnc.org/38-general-linuxcnc-q...-measurement-problem