The xhc-hb04.tcl script is provided to make connections for pendant jogging
with the assumption that the hal pins required are not previously connected.
For normal and vnormal jogging, the xhc-hb04.tcl script connects to:
axis.N.jog-scale, axis.N.jog-enable, axis.N.jog-counts, axis.N.jog-vel-mode,
halui.max-velocity.value.
Similarly, a number of pins are required for spindle-override, feed-override
plus-minus jogging, and other functions handled by xhc-hb04.tcl.
The error you posted will occur if another [HAL]HALFILE has made connections
before calling xhc-hb04.tcl.
To see the pins used by xhc-hb04.tcl, start one of the working xhc-hb04 pendant
simulation configs and in a separate shell:
Code:
$ halcmd show sig pendant: >xhc_hb04_connections.txt
(example attatched)
From the signal name
already linked to signal 'selected-jog-incr' while executing
it looks like you are using a config created by stepconf or pncconf. If
you want to use the xhc-hb04 pendant alone (no other jogging mpg), there may be
a way to prevent stepconf (or pncconf) from connecting those pins or you can remove or
comment out [HAL]HALFILE= lines that connect those pins prior to xhc-hb04.tcl
If you want separate halfiles to share jog control pins in order to support
(perhaps multiplex) multiple mpg sources, you will not be able to use the
xhc-hb04.tcl script directly but can still use the xhc-hb04 component and wire
it up with whatever multiplexing arrangements you require with custom halfiles
that you create yourself.
There is a man page for the xhc-hb04 in 2.7 (and most items are the same for
2.6):
www.linuxcnc.org/docs/2.7/html/man/man1/xhc-hb04.1.html
If you would make a zip file of your entire configuration directory and post
it you will assist folks in making suggestions.
