I already wired in another small 12v PSU, it powers something on the heidenhain impulseformer so I'm not sure if that would introduce noise into the encoder input but I do have buck converters as well now that you mention it.
Another note on this, I don't have home limits, just the index it looks for. This could be the stem of my issue but the reference machine I am "copying" is the same setup with no limits just search for the index
I would verify that the index works by manually setting the index enable signal
for the tested joint (via the halcmd sets command) and then manually moving
the axis past the index mark to see if the index enable signal gets cleared
at the index mark.
So on the z axis I did manually set the z enable and jogged to where the index was and it did turn off. I then tried changing the final velocity to invert it from the starting velocity of homing to make it come back instead of continuing into the E stop limit and that did not change its behavior it still goes past and it's homing sequence to the E stop
Is index-enable connected to both motion and the driver?
If the encoder index (something like hm2_cardname.0.encoder.00.index-enable)
has been set but is not ever cleared when the index location has been passed,
that suggests a hardware issue with the index signal itself.
in testing the "Z" axis right now I have it passing the index point, it turns off the enable signal, seems to hesitate for a split second before continuing to the estop hard limit
watching the "DRO" the z axis zeros then moves, hits the index, zeros, and then hits the estop. I have the offset set to 0 so it should just stop correct?
