Daughterboard inputs not recognized in HALMETER

Yeeeeees.... sorry Im a bit confused. So the erratic motion I'm seeing in my Z axis is a result of wiring then, not that pin 10 was being used already? I ask because I disabled the pin in the Z axis settings of my .hal, so you're saying theyre not related?

Thanks Andy. Just having trouble with the limit switches not stopping the homing movement in X and Y now. Z works and homes the cycle just fine, X and Y home in the correct direction but do not stop when the switch is triggered :/. Ill keep messing around I guess, unless you have some insight.

With the limit settings below I get a funtional Z home, XY do not stop when switch triggered. The setting is the same for Z as it is for the others so it doesnt make sense to me. I redacted lines from both below to make it easier to view.

The home switches all should trip when the table reaches -Xlimit/home, -Ylimit/home, and +Zlimit/home


########################################################################
HAL BELOW

# home switches
# must noise debounce inputs - otherwise coolant on/off can cause estops

net home-limit-x-raw <= hm2_5i25.0.7i76.0.0.input-01-not => debounce.0.1.in
net home-limit-y-raw <= hm2_5i25.0.7i76.0.0.input-02-not => debounce.0.2.in
net home-limit-z-raw <= hm2_5i25.0.7i76.0.0.input-03-not => debounce.0.3.in






########################################################################
INI BELOW


[AXIS_0]
MIN_LIMIT = -0.000001
MAX_LIMIT = 16.65
HOME_OFFSET = -0.010
HOME_SEARCH_VEL = -0.750
HOME_LATCH_VEL = 0.050
HOME_IGNORE_LIMITS = YES
HOME_SEQUENCE = 1


[AXIS_1]
MIN_LIMIT = -0.000001
MAX_LIMIT = 8.65
HOME_OFFSET = -0.010
HOME_SEARCH_VEL = -0.750
HOME_LATCH_VEL = 0.050
HOME_IGNORE_LIMITS = YES
HOME_SEQUENCE = 1


[AXIS_2]
MIN_LIMIT = -13
MAX_LIMIT = 0.000001
HOME_OFFSET = 0.010
HOME_SEARCH_VEL = 0.750
HOME_LATCH_VEL = -0.050
HOME_IGNORE_LIMITS = YES
HOME_SEQUENCE = 0

The full HAL is a few posts back on this thread.

The debounce goes from:

net home-limit-x-raw <= hm2_5i25.0.7i76.0.0.input-01-not => debounce.0.1.in
net home-limit-y-raw <= hm2_5i25.0.7i76.0.0.input-02-not => debounce.0.2.in
net home-limit-z-raw <= hm2_5i25.0.7i76.0.0.input-03-not => debounce.0.3.in

#onwards to

net and-home-x debounce.0.1.out enable-limit-x.in1 door-limit-x-lut.in-0 door-limit-in.in1
net and-home-y debounce.0.2.out enable-limit-y.in1 door-limit-x-lut.in-1 door-limit-y-lut.in-0
net and-home-z debounce.0.3.out enable-limit-z.in1

Could the logic above that links the X and Y to the (nonexistant) door switches be causing issue?


The truth table:


# door/
# limit-sw-enable x-homing door-sw-configured - Y in - X in -- out axis.0.*-lim-sw-in -- lut5 weight

# 0 X X X X | 0

# 1 0 0 0 0 | 0
# 1 0 0 0 1 | 1 0x00020000
# 1 0 0 1 0 | 0
# 1 0 0 1 1 | 1 0x00080000
# 1 1 0 0 0 | 0
# 1 1 0 0 1 | 1 0x02000000
# 1 1 0 1 0 | 0
# 1 1 0 1 1 | 1 0x08000000

# 1 1 1 0 0 | 0
# 1 1 1 0 1 | 0
# 1 1 1 1 0 | 1 0x40000000
# 1 1 1 1 1 | 1 0x80000000
# ----
# 0xCA0A0000
setp door-limit-x-lut.function 0xCA0A0000

# connect X and Y to axis.0.*-lim-sw-in via lut5-based mux configured as above
net x-lim-out door-limit-x-lut.out axis.0.home-sw-in axis.0.neg-lim-sw-in axis.0.pos-lim-sw-in

#
# limit-sw-enable x-homing door-sw-configured - Y in -- out axis.1.*-lim-sw-in -- lut5 weight

# 0 X X X | 0

# 1 0 0 0 | 0
# 1 0 0 1 | 1 0x00000200
# 1 0 1 0 | 0
# 1 0 1 1 | 1 0x00000800
#
# 1 1 0 0 | 0
# 1 1 0 1 | 1 0x00002000
# 1 1 1 0 | 0
# 1 1 1 1 | 0
# ----
# 0x00002A00
setp door-limit-y-lut.function 0x00002A00

net y-lim-out door-limit-y-lut.out axis.1.home-sw-in axis.1.neg-lim-sw-in axis.1.pos-lim-sw-in

net x-is-homing axis.0.homing door-limit-x-lut.in-3 door-limit-y-lut.in-2

# door switch to spindle comp is former x-axis limit input ANDed with NOT door-sw-configured from UI
# if door-sw-configured is TRUE then the spindle comp input follows the X limit input
# if door-sw-configured is FALSE the the spindle comp input is always FALSE

# inverter NOT gate
net enc-door-switch-configured door-limit-x-lut.in-2 door-limit-y-lut.in-1 door-limit-in.in0 tormachspindle.enc-door-switch-configured

# connect X limit inputs to axis.2.*-sw-*
net z-lim-out enable-limit-z.out axis.2.home-sw-in axis.2.neg-lim-sw-in axis.2.pos-lim-sw-in

# UI can display this
net enc-door-switch-status door-limit-in.out tormachspindle.enc-door-switch-status

So I've been playing with removal of the door logic, and I managed to make the Z axis which was working for homing not work. I'm comparing the files now to see what it could have been that broke it, hoping that its what is wrong with the X and Y axis. Not having much luck so far.