Re: [Emc-users] Issues with custom pendant.
Further to this. I unplugged the USB pendant. Commented out HALFILE = LIB:xhc-hb04.tcl I had actually set up two buttons. Once for G0 Z0 and one for G0 X0 Y0 in order to prevent running into something on the table while moving XYZ simultaneously. [HALUI] # add halui MDI commands here (max 64) MDI_COMMAND = G0 Z0 MDI_COMMAND = G0 X0 Y0 And in the postgui_call_list.hal net remote-rapid-to-Z-home halui.mdi-command-00 <= pyvcp.rapid-to-Z-home net remote-rapid-to-XY-home halui.mdi-command-01 <= pyvcp.rapid-to-XY-home And without the pendant they work exactly as expected. If I change the halui.mdi-command-nn to 16,17 instead of 00,01, which puts them after the Pendant MDI_COMMANDs like this: net remote-rapid-to-Z-home halui.mdi-command-16 <= pyvcp.rapid-to-Z-home net remote-rapid-to-XY-home halui.mdi-command-17 <= pyvcp.rapid-to-XY-home I get a totally different error. Now when booting and running the xhc-hb04.tcl the system complains that it's trying to create an already defined spindle-vel-cmd-rpm-abs Which in a way makes sense because in the pyvcp_options.hal file we have # Setup of spindle speed display using pyvcp -START net spindle-vel-cmd-rpm-abs=>pyvcp.spindle-speed net spindle-at-speed-led=>pyvcp.spindle-at-speed-led # Setup of spindle speed display using pyvcp -END The real question is why without the new buttons on the axis screen this error doesn't occur. Still very confused. John > -Original Message- > From: John Dammeyer [mailto:jo...@autoartisans.com] > Sent: March-02-21 7:13 PM > To: 'Enhanced Machine Controller (EMC)' > Subject: Re: [Emc-users] Issues with custom pendant. > > Alright thanks. I'll look into that. I don't think it's a spelling mistake. >I suspect that it's two outputs connected to one input since the > pendant I have has a button that sends all three axis to home. > > Based on > http://www.linuxcnc.org/docs/2.5/html/hal/basic_hal.html > > The net signal name "remote-rapid-to-home" > Is connected to the input pin "halui.mdi-command-00" > defined in the section > [HALUI] > MDI_COMMAND = G0 X0 Y0 Z0 > > The value of pyvcp.rapid-to-home comes from the screen button I created in > the xml file. (it's on the screen and shows motion > when I click on it). > > Now I forgot to mention that there's a included file layout2.inc which I've > attached. I just noticed that it also has a [HALUI] section > and has the same MDI command. > > And under [XHC_HB04_BUTTONS] > goto-zero = halui.mdi-command-00 > > So it looks like there are two outputs both connected to the input > halui.mdi-command-00 > Does that make sense? > Is that why there's an error? > > I'm assuming it must be possible to have a screen button and something else > cause motion because the Up arrow key on the > keyboard, the MPG on the Pendant and the Axis Screen button all move the Y > axis. > > So I'm a tad confused. > Thanks > John > > > > > -Original Message----- > > From: Jon Elson [mailto:el...@pico-systems.com] > > Sent: March-02-21 6:24 PM > > To: Enhanced Machine Controller (EMC) > > Subject: Re: [Emc-users] Issues with custom pendant. > > > > On 03/02/2021 08:11 PM, John Dammeyer wrote: > > > I've followed the directions in this link. > > > http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Adding_Custom_MDI_Buttons > > > > > > LinuxCNC fails on start up if I include this line in the postgui.hal file. > > > net remote-rapid-to-home halui.mdi-command-00 <= pyvcp.rapid-to-home > > > > > > > > If you run LinuxCNC from the command line, you should get a > > specific message about what on that line was wrong. But, > > you could also use hal configure or even halmeter to look > > for the two > > hal pins at the end of that command line. I'd give about > > 90% chance that one of these hal pin names is either > > mistyped or doesn't exist due to something not having been > > loaded with the > > loadrt or loaduser command. Once you know which of the pins > > is missing, you can search for why it did not get exported. > > The other possibility is you are trying to connect two > > output or input pins together. Every net should have one > > output pin and as many input pins as needed. The only > > exception is where two inout pins are connected. > > > > Jon > > > > > > ___ > > Emc-users mailing list > > Emc-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/emc-users ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Issues with custom pendant.
Alright thanks. I'll look into that. I don't think it's a spelling mistake. I suspect that it's two outputs connected to one input since the pendant I have has a button that sends all three axis to home. Based on http://www.linuxcnc.org/docs/2.5/html/hal/basic_hal.html The net signal name "remote-rapid-to-home" Is connected to the input pin "halui.mdi-command-00" defined in the section [HALUI] MDI_COMMAND = G0 X0 Y0 Z0 The value of pyvcp.rapid-to-home comes from the screen button I created in the xml file. (it's on the screen and shows motion when I click on it). Now I forgot to mention that there's a included file layout2.inc which I've attached. I just noticed that it also has a [HALUI] section and has the same MDI command. And under [XHC_HB04_BUTTONS] goto-zero = halui.mdi-command-00 So it looks like there are two outputs both connected to the input halui.mdi-command-00 Does that make sense? Is that why there's an error? I'm assuming it must be possible to have a screen button and something else cause motion because the Up arrow key on the keyboard, the MPG on the Pendant and the Axis Screen button all move the Y axis. So I'm a tad confused. Thanks John > -Original Message- > From: Jon Elson [mailto:el...@pico-systems.com] > Sent: March-02-21 6:24 PM > To: Enhanced Machine Controller (EMC) > Subject: Re: [Emc-users] Issues with custom pendant. > > On 03/02/2021 08:11 PM, John Dammeyer wrote: > > I've followed the directions in this link. > > http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Adding_Custom_MDI_Buttons > > > > LinuxCNC fails on start up if I include this line in the postgui.hal file. > > net remote-rapid-to-home halui.mdi-command-00 <= pyvcp.rapid-to-home > > > > > If you run LinuxCNC from the command line, you should get a > specific message about what on that line was wrong. But, > you could also use hal configure or even halmeter to look > for the two > hal pins at the end of that command line. I'd give about > 90% chance that one of these hal pin names is either > mistyped or doesn't exist due to something not having been > loaded with the > loadrt or loaduser command. Once you know which of the pins > is missing, you can search for why it did not get exported. > The other possibility is you are trying to connect two > output or input pins together. Every net should have one > output pin and as many input pins as needed. The only > exception is where two inout pins are connected. > > Jon > > > ___ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users layout2.inc Description: Binary data ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Issues with custom pendant.
On 03/02/2021 08:11 PM, John Dammeyer wrote: I've followed the directions in this link. http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Adding_Custom_MDI_Buttons LinuxCNC fails on start up if I include this line in the postgui.hal file. net remote-rapid-to-home halui.mdi-command-00 <= pyvcp.rapid-to-home If you run LinuxCNC from the command line, you should get a specific message about what on that line was wrong. But, you could also use hal configure or even halmeter to look for the two hal pins at the end of that command line. I'd give about 90% chance that one of these hal pin names is either mistyped or doesn't exist due to something not having been loaded with the loadrt or loaduser command. Once you know which of the pins is missing, you can search for why it did not get exported. The other possibility is you are trying to connect two output or input pins together. Every net should have one output pin and as many input pins as needed. The only exception is where two inout pins are connected. Jon ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
[Emc-users] Issues with custom pendant.
I've followed the directions in this link. http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Adding_Custom_MDI_Buttons LinuxCNC fails on start up if I include this line in the postgui.hal file. net remote-rapid-to-home halui.mdi-command-00 <= pyvcp.rapid-to-home I am also running the XHC_HB04 Pendant and in the HAL file there is this [HAL] HALFILE = LIB:xhc-hb04.tcl [XHC_HB04_CONFIG] layout = 2 There's also the xhc-hb04-layout2.cfg [XHC-HB04] BUTTON=01:button-goto-zero BUTTON=02:button-start-pause BUTTON=03:button-rewind BUTTON=04:button-probe-z BUTTON=05:button-macro-3 BUTTON=06:button-half BUTTON=07:button-zero BUTTON=08:button-safe-z BUTTON=09:button-home BUTTON=0A:button-macro-1 BUTTON=0B:button-macro-2 BUTTON=0C:button-spindle BUTTON=0D:button-step BUTTON=0E:button-mode BUTTON=0F:button-macro-6 BUTTON=10:button-macro-7 BUTTON=16:button-stop BUTTON=17:button-reset I can't find how the button-goto-zero is linked to MDI_COMMAND = G0 X0 Y0 Z0 Any suggestions? Thanks John "ELS! Nothing else works as well for your Lathe" Automation Artisans Inc. www dot autoartisans dot com ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
