Gmoccapy - G43 is disabled after selecting tool with zero z compensation

[zz912]

RIP 2.9 Branche
Debian Bookworm
Oracle VM VirtualBox
Test sim Gmoccapy.

If any tool other than 0 is selected at the start, the z offset is displayed correctly.
If I choose tool 0, the z offset is displayed incorrectly.

[rmu75]

Before selecting tool 0, G43 is active, after you select tool 0, G49 is active, i.e. tool compensation is off.

[zz912]

So the question is why is G43 automatically disabled when tool 0 is selected?

[zz912]

If a tool with Z=0 compensation is selected, G43 is deactivated.

Is this a bug or a feature? This behavior is not described here:
http://linuxcnc.org/docs/2.9/html/gcode/g-code.html#gcode:g43

[zz912]

Axis dont kill G43 never.

[zz912]

I did some research on this issue and found out that it is again a problem with the G43 auto-starting after a tool change.

linuxcnc/src/emc/usr_intf/gmoccapy/gmoccapy.py

Lines 3540 to 3544 in c2b5595

	if "G43" in self.active_gcodes and self.stat.task_mode != linuxcnc.MODE_AUTO:
	self.command.mode(linuxcnc.MODE_MDI)
	self.command.wait_complete()
	self.command.mdi("G43")
	self.command.wait_complete()

Norbert knows about this problem and plans to solve it. However, I will leave this Issue open so that we don't forget to check if his solution removes this consequence as well.

My solution is:

1. Remove lines auto-starting g43
2. Add the lines here:
   

   linuxcnc/src/emc/usr_intf/gmoccapy/gmoccapy.py

   Lines 4980 to 4982 in c2b5595

   	self.command.mode(linuxcnc.MODE_MDI)
   	self.command.wait_complete()

            self.command.wait_complete()
            self.command.mdi("G43")
            self.command.wait_complete()

[rmu75]

I don't see how "tool offset == 0" can influence the code you cited.

[zz912]

The cited code makes random problems. It makes race conditions. I have been dealing with this for a long time.

lookt at:
#2489

lookt at:
#2552

lookt at:
https://forum.linuxcnc.org/38-general-linuxcnc-questions/49445-python-command-wait-complete-does-not-wait-for-c-halui-commands

lookt at:
#2453 (comment)

I would like ask you. Could you try reproduce this bug? I wouldn't be surprised if I was the only one with the problem.

[rmu75]

This issue may be related but I don't think this is caused by a race condition.

[zz912]

Feel free to find source of problem. I am mechanical designer. Programing is only my hobby.

This is video with my code modifications:

It is interesting that G43 and G49 switch when selecting tool offset == 0. Axis does not do this.

For now, I will not look into this issue further until the previous issues are resolved.

[gmoccapy]

In Axis you are changing the tools by MDI commands like T1 M6 and T2M6, but in gmoccapy you use M61 Q1 and M61 Q2.

So that is one difference. I checked gmoccapy code and did not find any place, where M49 is commanded. So the problem may be deeper.

Norbert

[zz912]

In Axis you are changing the tools by MDI commands like T1 M6 and T2M6, but in gmoccapy you use M61 Q1 and M61 Q2.

Thank you for notice. Here is AXIS with the M61 QX:

G49 does not appear