fascinating feed rate override error

Hello there,

I just encountered a fascinating bug or user error, can't say yet.
I used Gmoccapy 1.5.5.3 with LinuxCNC 2.7.4 and the error remains in Gmoccapy 2.3.0 with LinuxCNC 2.80-pre1-2992.
I have an automatic tool length setup.

In this gcode demo test40X40.ngc there are 4 tools.
With the first tool, third and forth in this demo, my cnc follows the feed rates in the program.
With the second tool(T6) my machine disregards the feed rates in te program using my rapids speed(3000).
I also switched the second tool T6 with T3, to make sure it's not the tool and the problem is consistent.

I don't know where to start in discovering the problem, any idea?

Wrong G Code,
Add in line N260 the missing G1 and it will work

Norbert

interesting ... looking at the program I would have thought you would be complaining about the program using feed rate after the tool change rather then rapid rate.
Th first G0 I see is at n440 everything before that should be at feed rate.
Is that what you intended - first rapid at n0440?

Chris M

it looks like (remapped?) M06 changes current motion mode to G0. is this ok or a bug?

Ya I wondered about whether you were using a remap.
In my opinion it's a bug - tool changes shouldn't change modes.

Chris M

i believe it's a vanilla gmocappy config, which has:

REMAP=M6 modalgroup=6 prolog=change_prolog ngc=change epilog=change_epilog

and change.ngc seems to be using G0:

github.com/LinuxCNC/linuxcnc/blob/af15a4...py/macros/change.ngc

It is not a bug!
If yo use code for remap, you should know what it is doing.
You can change the remap code to fit your needs.

IMHO it is bad style not to set speed, feed and G43 and cooling after a tool change.

Norbert

bad form or not .. changing feed modes after a tool change is unexpected behavior.
I wonder if it is easy to check the current g codes in the remap and then restore them?

Chris M

Hallo Cris,

you are right, but the user uses a remap part, within that one G0 is used, so the behavior is correct.

He should change the remap code to fit his needs.
It is definitely not a gmoccapy problem.

Norbert

Thank you guys.

As you noticed the problem is in the G code and the post-processor seems to be one problem.

Thank you for your support