Adding a GO/RUN physical button to run the MDI command typed in the command line

More
8 months 1 week ago #343449 by HansU
What I found in a Heidenhain manual is that MDI is there meant as small programs which you can run. And for those you need the start button:

 
[ content.heidenhain.de/doku/tnc_guide/pdf...01/en/533_188-20.pdf ]

Maybe there are other options which I don't know. I never used a Haidenhain control.

Please Log in or Create an account to join the conversation.

More
8 months 5 days ago - 8 months 5 days ago #343585 by Aciera
It is relatively easy to have a halpin execute the current mdi command in gmoccapy.py:

create the pin:
Code:
pin = self.halcomp.newpin("mdi_execute", hal.HAL_BIT, hal.HAL_IN) hal_glib.GPin(pin).connect("value_changed", self._mdi_execute)


Create the handler:
Code:
def _mdi_execute(self, pin): if pin.get() and self.widgets.ntb_button.get_current_page() == _BB_MDI: mdi_entry = self.widgets.hal_mdihistory.submit()

As mentioned above, you would want to remove all other events in 'hal_mdihistory.py' that currently execute the 'submit()' function (eg. double clicking on an entry):
github.com/LinuxCNC/linuxcnc/blob/master...l_mdihistory.py#L151

GUI development in LinuxCNC has, generally speaking, not been driven by industry standards but by what is convenient and the easiest way forward, which is also what most lower end users want.
Personally I would welcome a GUI that could at least be configured to only allow initiation of physical machine movement through hal pins. This would also remove the possibility to start a tool change by mouse click from the GUI.
Last edit: 8 months 5 days ago by Aciera.
The following user(s) said Thank You: maxi177

Please Log in or Create an account to join the conversation.

Moderators: newbynobi, HansU
Time to create page: 0.288 seconds
Powered by Kunena Forum