Gmocappy fires relay twice

The userspace pin halui.machine.is-on is following
realtime motion pin motion.motion-enabled.
Some investigation shows this behavior with gmoccapy
has existed for a while -- it has probably just
never been reported.

The problematic code is likely in this function or
its triggers (2.8 branch):
github.com/LinuxCNC/linuxcnc/blob/fbd3f7...py/gmoccapy.py#L2296


Using configs/sim/gmoccapy/gmoccapy.ini, Pressing the Machine-On button:


Suggestion: file a bug report (issue) on github and/or notify Norbert

PCW wrote: Does your axis config use halui the same way?
What pokes halui.machine.on and halui.machine.off ?

Yes it does. This basically a generic pncconf. I am just starting towork on the configs and I wanted the customer to use gmocappy.
I am really comfortable with Axis, so I am testing in axis and thenmodifying gmocappy config. I have two machine configs.

dgarrett wrote: The userspace pin halui.machine.is-on is following
realtime motion pin motion.motion-enabled.
Some investigation shows this behavior with gmoccapy
has existed for a while -- it has probably just
never been reported.

The problematic code is likely in this function or
its triggers (2.8 branch):
github.com/LinuxCNC/linuxcnc/blob/fbd3f7...py/gmoccapy.py#L2296


Using configs/sim/gmoccapy/gmoccapy.ini, Pressing the Machine-On button:

What is triggering motion.motion-enable?

/EDIT nevermind I think I understand how it works. The function (on_tbtn_on_toggled) looks like it works. Must be in the triggers in the widgets.

Where can I create a bug report?

github.com/LinuxCNC/linuxcnc/issues

Chris

Hallo @ALL,

i am able to reproduce the behavior. so now is just to find the reason and bug fix that one.
I apologize for the inconvenience.

Norbert

Any headway on this issue?