- Posts: 4819
- Thank you received: 0
Boxford 125 lathe Tool Changer Comp FERROR (SOLVED)
position_req -= ((moves / divisor) + fudge_factor);
Which is the same as
position_req = position_req - ((moves / divisor) + fudge_factor);
So as the divisor used to be 2 we got the 1.5 degrees for a single move:
(1/2+1)=1.5
and since I now changed the divisor to 1 it is now 1/1+1=2 degrees.
So I guess each forward move is a bit too long to get past the locking mechanism and then the toolchanger is moved backwards by the number of moves (moves) times the extra plus the "fudge factor".
The position is not reset but if the motor looses steps it does not matter since the next move just starts from where it is sitting against the lock. As there is no position feedback.
Just thought of that now.
Please Log in to join the conversation.
Aciera wrote: As I see it, there is only one place where the backwards locking move comes in:
position_req -= ((moves / divisor) + fudge_factor);
Which is the same as
position_req = position_req - ((moves / divisor) + fudge_factor);
So as the divisor used to be 2 we got the 1.5 degrees for a single move:
(1/2+1)=1.5
and since I now changed the divisor to 1 it is now 1/1+1=2 degrees.
So I guess each forward move is a bit too long to get past the locking mechanism and then the toolchanger is moved backwards by the number of moves (moves) times the extra plus the "fudge factor".
The position is not reset but if the motor looses steps it does not matter since the next move just starts from where it is sitting against the lock. As there is no position feedback.
Just thought of that now.
Thank you that all makes sense. So this means it can be moved past the locking mechanism with a bit of leeway and then reverse far enough to always stall the motor .
I will now put the turret back together and hopefully it is a job well done.
I will mark it as solved
Please Log in to join the conversation.
[edit]
Make sure you check the "stepgen.2.position-scale" and connect "toolchanger.ishomed" and "stepgen.2.enable" the way you want.
Please Log in to join the conversation.
Please Log in to join the conversation.
The two different angles are entered in the "param" section as "odd_move" and "even_move".
The component adds "odd" or "even" moves to derive the required position depending on whether the current toolnumber is even or not. It then calculates the required number of moves and starts with an odd_move if the currenttoolnumber is even.
[edit]
Note that I doubled the original angles (22.2° and 24°) as the trick with using half-angles was only there to avoid unwanted backward moves.
The angles sum up to (44.4°+48°)x4=368.8° so actually more than a full turn because of the need to get past the locking mechanism.
[/edit]
Please Log in to join the conversation.
You have given me more homework to test out. I will save my config and see how it goes without the A axis.
I will report back.
You have gone more that above with your help in this. Thanks
Please Log in to join the conversation.
Ok just when I thought I was getting to the end
Ha Ha, it will NEVER end! :evil:
Please Log in to join the conversation.
Aciera wrote:
Ok just when I thought I was getting to the end
Ha Ha, it will NEVER end! :evil:
Ha very good You should not take the piss out of a 74 year OAP.
Now I am trying to find out how to auto home the toolchanger.ishomed When I don't have an axis in the ini file ?
Please Log in to join the conversation.
I connected it to the machine enable so its "homed" as soon as you start the machine. Since it is not an axis it does not have a real "homing" routine. Does it not work that way?
[edit]
I think the homing might have been a leftover from the original use to drive a tool changer with a sensor so it could actually home itself before use. Since yours does not have a sensor there is no point in homing as the system has no feedback. Your original INI only had immediate homing so might as well just enable it when you start the machine. At least I think it should work.
Please Log in to join the conversation.
Aciera wrote:
Code:net estop-ext => iocontrol.0.emc-enable-in => toolchanger.ishomed => stepgen.2.enable
I connected it to the machine enable so its "homed" as soon as you start the machine. Since it is not an axis it does not have a real "homing" routine. Does it not work that way?
[edit]
I think the homing might have been a leftover from the original use to drive a tool changer with a sensor so it could actually home itself before use. Since yours does not have a sensor there is no point in homing as the system has no feedback. Your original INI only had immediate homing so might as well just enable it when you start the machine. At least I think it should work.
Its telling me "can't issue MDI command when not homed"
I think I have always had to home the machine by clicking on each radio button but now I only have X and Z so can't issue the command to the toolchanger.
These are the current hal and ini files
Attachment not found
Attachment not found
Edit: Could it be homed in the comp.
Please Log in to join the conversation.
