Gmoccapy & carousel.comp problems after update

Unsure where to post this so feel free to move to a more relevant section.
for the past year this machone has been working perfectly using gmoccapy and carousel.comp on linuxcnc 2.9.2

Yesterday I updated to 2.9.3 and the latest gmoccapy and after a couple little bugs it's all working fine except my toolchanger , when commanding a toolchange though mdi it will home the tool changer like it should , then select the desired tool , but after that calling up a new tool only changes the offset and does not operate the tool changer.

Here is a short clip so you can see what I'm talking about.

Debian 12 , linuxcnc 2.9.3 , whatever the latest gmoccapy is. Updated yesterday.


 

Here is the hal and ini that has been running my machine for the past year.
 

Did you check HAL pins in Halshow?

Yes , I also forgot I have this in gmoccapy_postgui.hal.

 

looking in halshow everything related to carousel seems to be functioning fine using my tool change jog buttons, its as if ive lost communication between gmoccapy and carousel , but only after the forst tool selection.

Looking through some more pins , for that first tool change where it works through m code , iocontrol.0.tool-change triggers , it goes to the desired tool then iocontrol.0.tool-changed triggers and stays triggered , then I am no longer able to do any m6 tool changes

If I unlink this pin and manually clear it I am able to do another tool change , then manually set and clear I can do another and so on.

It seems to be that the iocontrol.0.tool-changed is no longer clearing itself.

Seems that 'carousel.comp' has not changed from 2.9.2 to 2.9.3:
github.com/LinuxCNC/linuxcnc/compare/v2.9.2...v2.9.3

I _think_ it's normal for 'iocontrol.0.tool-changed' to stay true.
Question: Does 'iocontrol.0.tool-change' go false?

I have read that there has been no changes to the carousel.comp , I'm thinking it has to be somewhere else.

When doing the 1 tool change it will do upon startup iocontrol.0.tool-change goes true then back to false and will not go true again.

Here is a video showing that.

youtube.com/shorts/ikY9XmgKaUE?si=r2Xf1ZPs4eCSNlDe

looking in halshow everything related to carousel seems to be functioning fine using my tool change jog buttons, its as if ive lost communication between gmoccapy and carousel , but only after the forst tool selection.

I presume you are not using the gmoccapy tool change dialog so I don't see why gmoccapy would need to play any role in this and indeed looking at the halfile you attached and comparing that to the screen shot of your postgui_halfile it seems that the signals in the postgui_halfile are actually not connected to anything (which I think is correct):
The question is why the MDI toolchange does not seem to work after the first change.
Maybe you could test if it works properly if you use a gcode file. If that also fails to work after the first change then it is not likely to be related to gmoccapy at all.

So my suggestions are:
- Test in a sim config on your machine
- Test with your machine config using a gcode file

I just went out to the shop and ran a program , it behaves exactly the same , the offsets and tool number chnage but the physical tool does not , then the program just continues on.

Im not sure what you mean by try in a sim.

I have noticed this since the update aswell , possibly related to something missing or out of place ? , the first time i open linux cnc it starts in some odd configuration,  notice the 5 decimal places and world mode at the bottom,  then I have to close and re open to continue.

 

 

 

Im not sure what you mean by try in a sim.

Try to run one of the Gmoccapy simulation configs for lathe located in 'configs/sim/gmoccapy/lathe_configs'.