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

Attachment: layout2.inc
Description: Binary data

_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to