- Posts: 19311
- Thank you received: 4655
Current turning capabilities status
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
I got a bit confused by index-homing on my milling machine.
The behaviour 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 mush sense)
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)
I have latch and search in the same direction on my Hardinge with no ill effects. Home offset is 0 and home use index is yes.
JT
Please Log in or Create an account to join the conversation.
the tool change component is almost done, but I have a problem. sometimes when I start linuxcnc the a-pos-feedback starts with the value of -89.9 and the turret goes 1/4 turn. what can cause this problem? this value is an input on the toolchange component so I suppose that is nothing on the programming side. this is the code how it is connected:
other problem that I have is that I cant reduce the speed of the A axis. I tried change parameters on the ini file but has no effect on the speed.
velocity and acceleration are 0, but it don't change the speed.
tnks,
João
Please Log in or Create an account to join the conversation.
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.
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
It happens when launch linuxcnc. I did what you told it looks fine now. initial value is 0 like it should to be.
now only have the velocity problem on the A axis. I don't have any idea how to resolve this.
tnks
João
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.
The axis velocity settings are used by the motion planner for G-code moves etc. What you are calling an A-axis isn't really an Axis at all, it is a separate motor controlled by your toolchanger component.
The A-position commands come direct from the tc component. You either need to add some rate-limiting inside the component or pass the output of the component through the limit3 HAL component:
www.linuxcnc.org/docs/html/man/man9/limit3.9.html
Please Log in or Create an account to join the conversation.