- Posts: 19311
- Thank you received: 4655
BigJohnT wrote:
www.linuxcnc.org/docs/html/config/ini_co...d_sub_axis_section_aHOME_USE_INDEX = NO - If the encoder used for this axis has an index pulse, and the motion card has provision for this signal you may set it to yes. When it is yes, it will affect the kind of home pattern used.
www.linuxcnc.org/docs/html/config/ini_homing.htmlT
Please Log in or Create an account to join the conversation.
andypugh wrote: I got a bit confused by index-homing on my milling machine.
The behavior was that after the initial search move the Z was moving up to index, then a rapid back down onto the limit switch, and tripping an error.
I set the home offset to 0 and that worked a lot better. I suspect that you always want the HOME_OFFSET to be zero if you are index homing and the latch is in the opposite direction to search. (and having search and latch in the same direction when homing to index doesn't really seem to make much sense)
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
PCW wrote: Does the -89.9 degree initial offset happen with initial linuxcnc launch or when switching machine-off/machine-on?
There do seem to be cases where the initial encoder count is not cleared prior to homing the axis
I would try removing this (unused) line:
net a-pos-rawcounts <= hm2_5i20.0.encoder.00.rawcounts
to see if the problems is resolved
Please Log in or Create an account to join the conversation.
jtc wrote: now only have the velocity problem on the A axis. I don't have any idea how to resolve this.
Please Log in or Create an account to join the conversation.