Thanks Todd! Your suggestion solved it. My original syntax was correct. (Which, ozzy, explains the absence of a "no pin" error.) But I needed to set a jog speed. I have a GladeVCP panel in my gui with a jog speed slider. So I connected this to halui.axis.jog-speed (in a post-gui hal file, don't know if that's necessary) as follows:
#post-gui.hal
Code:
net jog-speed gladevcp.jog_speed halui.axis.jog-speed
And in my main hal file I connected my hardware input to halui as follows:
Code:
net jog-x-plus <= hm2_7i76e.0.gpio.017.in_not => halui.axis.x.plus
In my case, there were drop-outs and spontaneous machine movement! until I buffered the signals with a debounce object. Final code for all three axis:
Code:
loadrt debounce cfg=10 # for 4 limit switches and 6 jog buttons
addf debounce.0 servo-thread
setp debounce.0.delay 15
# --- Jog Buttons ---
net jog-x-plus-raw debounce.0.4.in <= hm2_7i76e.0.gpio.017.in_not
net jog-x-plus debounce.0.4.out => halui.axis.x.plus
net jog-x-minus-raw debounce.0.5.in <= hm2_7i76e.0.gpio.019.in_not
net jog-x-minus debounce.0.5.out => halui.axis.x.minus
net jog-y-plus-raw debounce.0.6.in <= hm2_7i76e.0.gpio.021.in_not
net jog-y-plus debounce.0.6.out => halui.axis.y.plus
net jog-y-minus-raw debounce.0.7.in <= hm2_7i76e.0.gpio.023.in_not
net jog-y-minus debounce.0.7.out => halui.axis.y.minus
net jog-z-plus-raw debounce.0.8.in <= hm2_7i76e.0.gpio.025.in_not
net jog-z-plus debounce.0.8.out => halui.axis.z.plus
net jog-z-minus-raw debounce.0.9.in <= hm2_7i76e.0.gpio.026.in_not
net jog-z-minus debounce.0.9.out => halui.axis.z.minus
Thanks all! (Now it's on to some stepping logic...)
Dave L
