Work with probe

verser
Topic Author
Offline
Senior Member

7 years 11 months ago #121570 by verser

Replied by verser on topic Work with probe

FernV wrote: I noticed that with gmoccapy, when pressing a jog button and the screen change that it will jog until <esc> is pressed.

Connecting V2 version to gmoccapy has a nuance.
In the .ini file everything is as usual:

Code:

EMBED_TAB_NAME=Probe Screen 
EMBED_TAB_LOCATION = ntb_user_tabs
EMBED_TAB_COMMAND = gladevcp  -x {XID} -u python/probe_screen.py probe_icons/probe_screen.glade

And then I fixed gmoccapy.py so that it doesn’t wipe Probe Screen when switching MDI-MANUAL modes.
For this I comment out the line (requires root)
self.widgets.ntb_main.set_current_page (0)

here

and here

Code:

def on_hal_status_mode_mdi(self, widget):
        print ("MDI Mode", self.tool_change)
        # self.tool_change is set only if the tool change was commanded
        # from tooledit widget/page, so we do not want to switch the
        # screen layout to MDI, but set the manual widgets
        if self.tool_change:
            self.widgets.ntb_main.set_current_page(0)
            self.widgets.ntb_button.set_current_page(_BB_MANUAL)
            self.widgets.ntb_info.set_current_page(0)
            self.widgets.ntb_jog.set_current_page(0)
            return
        # if MDI button is not sensitive, we are not ready for MDI commands
        # so we have to abort external commands and get back to manual mode
        # This will happen mostly, if we are in settings mode, as we do disable the mode button
        if not self.widgets.rbt_mdi.get_sensitive():
            self.command.abort()
            self.command.mode(linuxcnc.MODE_MANUAL)
            self.command.wait_complete()
            self._show_error((13, _("It is not possible to change to MDI Mode at the moment")))
            return
        else:
            # if we are in user tabs, we must reset the button
            if self.widgets.tbtn_user_tabs.get_active():
                self.widgets.tbtn_user_tabs.set_active(False)
            if self.widgets.chk_use_kb_on_mdi.get_active():
                self.widgets.ntb_info.set_current_page(1)
            else:
                self.widgets.ntb_info.set_current_page(0)
#            self.widgets.ntb_main.set_current_page(0)
            self.widgets.ntb_button.set_current_page(_BB_MDI)
            self.widgets.ntb_jog.set_current_page(1)
            self.widgets.hal_mdihistory.entry.grab_focus()
            self.widgets.rbt_mdi.set_active(True)
            
            # if the status changed, we reset the key event, otherwise the key press
            # event will not change, if the user did the last change with keyboard shortcut
            # This is caused, because we record the last key event to avoid multiple key
            # press events by holding down the key. I.e. One press should only advance one increment
            # on incremental jogging.
            self.last_key_event = None, 0

gmoccapy placed in /usr/bin

The following user(s) said Thank You: FernV

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

newbynobi
Offline
Platinum Member

7 years 11 months ago #121599 by newbynobi

Replied by newbynobi on topic Work with probe

Hallo verser,

your changes in gmoccapy could lead to a gui not beeing syncronised with LinuxCNC mode state!

Imho that is not a good idea. It would be better to check if probe screen is active and only in that case avoid a gui mode switch. That way is much more complicated, but secure.

I needed to do a similar check for the tool reloading on start up!

Norbert

The following user(s) said Thank You: verser

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

Roguish
Offline
Elite Member

7 years 11 months ago #121616 by Roguish

Replied by Roguish on topic Work with probe

verser, fernV, and newbynobi,
do you all know what Cmorley is working on with QtVCP and QT5?
it might be good to work together....
at least check it out.
just a thought.
thanks for the work.

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

Vitkus
Offline
New Member

7 years 10 months ago #122470 by Vitkus

Replied by Vitkus on topic Work with probe

Hello,
I installed Probe Screen V2 and it seem all functions work fine, but when I try upload Gcode (from fusion 360) code not work. In preview screen it doesen't show tool pases, when I try hit cycle start machine go to Z0 and then nothing happens. I noticed G code without tool in descripcion work fine(example linux engrave program "Linux CNC" ). So I what to ask if anyone have similar problem and solve it, or I simply wrongly intalled program and asked stupid question? :dry:

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

Karri
Offline
New Member

7 years 10 months ago #123150 by Karri

Replied by Karri on topic Work with probe

Damn, i should have look this thread 3 hours ago, fighting with the same problem x)

Should there come some sort tool replacing window where you could click "tool replaced"? atleast it doesn't come for me

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

verser
Topic Author
Offline
Senior Member

7 years 10 months ago #123155 by verser

Replied by verser on topic Work with probe

Tool replacing window can fall to a level below due to manipulations with the mouse on the Axis screen during the procedure. You can pull out it by folding Axis in the tray.

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

Time to create page: 0.156 seconds

Forum Menu

Work with probe