andypugh wrote:maxvdh wrote:net estop-out hm2_5i25.0.7i77.0.0.output-00
net xenable hm2_5i25.0.7i77.0.0.output-03
Well, these are half of it, defining signals and where they need to go to. What I don't see in the lines you have pasted is where the signals come from.
I would rather expect to see, for example
net estop-out halui.estop.is-activated
because estop-out is just a signal name, and it has no meaning to LinuxCNC. halui.estop.is-activated, however, is an output pin driven by LinuxCNC.
The same is true for xenable, I would expect it to be netted to axis.0.amp-enable-out
(Yes, i do know most of these pin names off by heart, but they are all listed in the docs for example:
www.linuxcnc.org/docview/html/gui/halui.html
www.linuxcnc.org/docview/html/man/man9/motion.9.html
Knowing where to look for each one is a bit more difficult)
Thanks a lot for the references. I wasn't aware that xenable wasn't a LinuxCNC function. That said, xenable is netted to axis.0.amp-enable-out later in the HAL file. Maybe I should take a look at that signal to see what it's doing.
andypugh wrote:net jog-incr-a => jogincr.sel0
net jog-incr-b => jogincr.sel1
net jog-incr-c => jogincr.sel2
net jog-incr-d => jogincr.sel3
Here we have the reverse problem, I don't see where jog-incr-a etc are driven from. I would expect them to be wired to gpio and from there to the jog-speed selector switch.
I have no jog speed selector switch or buttons so that's probably the problem. I'd just like to be able to set a fixed jog speed for the joysticks I have and use the MPG in velocity mode.