I was a bit confused where we get the hal for the buttons: https://forum.linuxcnc.org/forum/24-hal-components/26679-xhc-hb04-wireless-mpg-pendant-hal-module?start=200
> b) The sim configs use a halfile named xhc-hb04.tcl that loads > a helper component (pendant_util) and makes all hal connections. > For _simple_ configurations, no user added hal components or > connections are needed. So, it that saying xhc-hb04.tcl dynamically generates the hal connections for "probe-z" and "rewind" used in [XHC_HB04_BUTTONS]? Why isn't it just a static hal? Danny On 4/21/2016 1:44 AM, Gene Heskett wrote: > On Thursday 21 April 2016 01:12:13 dan...@austin.rr.com wrote: > >> Didn't realize I sent off-list. >> >> OK, I think I see a key problem, under Hal Meter, >> "xhb-hb04.require_pendant = false", although "connected" is true. >> >> Right in the main .ini: >> >> [XHC_HB04_CONFIG] >> require_pendant = yes >> >> I tried "true" instead of "yes", no change. >> > I believe hal treats them equally, but my hand isn't anywhere near a > bible. > >> [HALUI] for all the MDI_COMMAND stuff is in the main ini file now. It >> shows up under the HAL meter- but are always false. I pressed every >> button on the mpg. >> >> The jog.enable-x show true/false when selected. >> >> So, what I'm seeing is that any button listed inside my xhc-hb20.hal >> file works fine. But all the [HALUI] and [XHC_HB04_BUTTONS] stuff is >> inactive. >> >> >> Danny > The one file tha is part of my setup that didn't get posted, is > campins.hal which I believe shows how the HALUI stuff is connected to > the system. Yous obviously will be different, but this will show how > much of that stuff is done on my machine: > > ===================SOF================= > #CamView pins > > loadrt oneshot names=forOn,forOff > addf forOn servo-thread > addf forOff servo-thread > setp forOn.width .1 > setp forOff.width .1 > setp forOff.falling 1 > setp forOff.rising 0 > net forOnNet <= camview.hal_checkbutton1 => forOn.in forOff.in > net cam1 <= forOn.out => halui.mdi-command-00 > net cam2 <= forOff.out => halui.mdi-command-01 > net cam3 <= camview.hal_button1 => halui.mdi-command-02 > net cam4 <= camview.hal_button2 => halui.mdi-command-03 > net cam5 <= camview.hal_button3 => halui.mdi-command-04 > =================EOF================= > which shows how those 6 pyvcp buttons are "net"ed, hooking them up to mdi > functions. The <= and => symbols above are mostly ignored by hal, but > they help you keep track of where the signal comes from to get to the > net "name", and where its sent from that net name" > > To get any closer, the rest of the list, and there are far more > experienced people here than I, we'll have to see this mythical xhc-hb04 > file. How it uses the layout2 argument and all. > > [...] > > Cheers, Gene Heskett ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
