tool frame i have only 3 points and 6 points
fanuc r 2000ib 210f offset 4 axis
-
mekeale -
April 11, 2022 at 8:54 AM -
Thread is Unresolved
-
-
How is your spindle mounted to the face plate?
A picture would be helpful.
-
a photo...
-
Is this seriously your measuring setup?
You want a precise result, so use at least half way precise measurement setup.
Attach your magnetic holder to something stiff, stable and magnetic.
Move it to a place at least 50 cm lower than now or more away from robot, so that the robot is not near singularity when measuring.
Try all again.
-
Is this seriously your measuring setup?
You want a precise result, so use at least half way precise measurement setup.
Attach your magnetic holder to something stiff, stable and magnetic.
Move it to a place at least 50 cm lower than now or more away from robot, so that the robot is not near singularity when measuring.
Try all again.
I agree. doesn't look very good. but everything is fine and does not move. I followed the instructions and set up the robot according to the instructions.
-
hermann is 100% correct here:
- Your wrist posture is in a ridiculous position for TCP teaching.
- Your spindle would also be better mounted at 45-90 from it's current position - forcing wrist posture.
- Your pointer/work is very central to the physical robot.
- Mr Robot prefers when ALL joints have freedom to move, your image suggests otherwise.
- Mr Robot will hate you for forcing him to teach/work TCP in these conditions, poor Mr Robot..
1. Can you post a videos of:
- Current setup actually milling showing the full tool and wrist posture during the cutting.
- RoboDK simulation showing the full tool and wrist posture during the cutting as control comparison.
** RoboDK is not a Fanuc application, so creating projects in RoboDK is no guarantee it's correct **
2. Have you tried removing the spindle.
- Move all joints to mechanical zero.
- Fitting a small pointer to central to the robot flange.
- Reset user frame to null.
- Reset tool frame and just have Z value representing the length of the pointer.
- Make sure your pointer is perpendicular to robot and bias more left or right and lower than current.
- Move to your pointer showing us the wrist posture.
- Using Tool and test Rx, Ry and Rz and show video of robot posture during Rx, Ry, Rz
- Post back video of you doing this, showing wrist posture.
- This may highlight any possible mastering issues as there is minimal external influence.
-
I agree. doesn't look very good. but everything is fine and does not move.
You are asking for help, and ignore nearly every tipp for enhancements.
My best wishes for solving your problem.
-
hermann is 100% correct here:
- Your wrist posture is in a ridiculous position for TCP teaching.
- Your spindle would also be better mounted at 45-90 from it's current position - forcing wrist posture.
- Your pointer/work is very central to the physical robot.
- Mr Robot prefers when ALL joints have freedom to move, your image suggests otherwise.
- Mr Robot will hate you for forcing him to teach/work TCP in these conditions, poor Mr Robot..
1. Can you post a videos of:
- Current setup actually milling showing the full tool and wrist posture during the cutting.
- RoboDK simulation showing the full tool and wrist posture during the cutting as control comparison.
** RoboDK is not a Fanuc application, so creating projects in RoboDK is no guarantee it's correct **
2. Have you tried removing the spindle.
- Move all joints to mechanical zero.
- Fitting a small pointer to central to the robot flange.
- Reset user frame to null.
- Reset tool frame and just have Z value representing the length of the pointer.
- Make sure your pointer is perpendicular to robot and bias more left or right and lower than current.
- Move to your pointer showing us the wrist posture.
- Using Tool and test Rx, Ry and Rz and show video of robot posture during Rx, Ry, Rz
- Post back video of you doing this, showing wrist posture.
- This may highlight any possible mastering issues as there is minimal external influence.
I did not say that I taught TCP in this position. In this position, the axes J5, J4, J3, J2 are being calibrated. I will do everything you wrote, I will inform you about the results. Thank you.
-
You are asking for help, and ignore nearly every tipp for enhancements.
My best wishes for solving your problem.
no, I do everything you say. Thank you.
-
Remember you have come to Robot Forum for assistance.
Many members are allocating their experience and free time to assist you.
How much time are they spending writing replies in comparison to contacting the OEM and paying for a service/application engineer to assist.......just have a think about that for a minute.
Some of your responses do suggest you are just casually brushing suggestions aside, not necessarily actioning them.
Remember, we are not seeing what you are seeing, and if you cannot convey that to us in text, provide video, pictures and evidence of results from the suggestions offered.
If it continues, there is a possibility these members may seek life elsewhere rather than assisting you.
So I suggest with your responses, to try and provide some sort of evidence/proof that you are indeed trying these things as opposed to comments like 'I assure you the code is correct', 'everything is fine' and 'no I do everything you say'
I could just offer a suggestion by saying 'Your robot is broke, buy a new one', do you see my point?
I am not suggesting to remaster or teach anything, read what I have suggested and post back videos, pictures and results and we can advise further.
You and us are sitting in an area with MANY unknowns at the moment:
1. Fanuc Robot, uncertainty of mastering being correct.
2. Fanuc Robot, TCP no evidence of XYZ motions to prove TCP XY vectors are orthogonal to milling bit.
3. Fanuc Robot, TCP appears inaccurate for rotational, suggests TCP XY vectors may not be orthogonal.
4. No evidence of TCP teaching, showing how you are doing it, wrist posture, fixed pointer position etc.
5. Fanuc Robot, recent image show wrist posture in singularity.
6. Recent image, suggests setup conditions is not ideal for TCP teaching.
7. RoboDK, is the code correct, Fanuc robot will execute what you tell it......shit in, shit out......
So my suggestion is to eliminate the majority of these unknowns and see if there is a fundamental issue with the robot, then at least that can be eliminated and shelved.
-
Remember you have come to Robot Forum for assistance.
Many members are allocating their experience and free time to assist you.
How much time are they spending writing replies in comparison to contacting the OEM and paying for a service/application engineer to assist.......just have a think about that for a minute.
Some of your responses do suggest you are just casually brushing suggestions aside, not necessarily actioning them.
Remember, we are not seeing what you are seeing, and if you cannot convey that to us in text, provide video, pictures and evidence of results from the suggestions offered.
If it continues, there is a possibility these members may seek life elsewhere rather than assisting you.
So I suggest with your responses, to try and provide some sort of evidence/proof that you are indeed trying these things as opposed to comments like 'I assure you the code is correct', 'everything is fine' and 'no I do everything you say'
I could just offer a suggestion by saying 'Your robot is broke, buy a new one', do you see my point?
I am not suggesting to remaster or teach anything, read what I have suggested and post back videos, pictures and results and we can advise further.
You and us are sitting in an area with MANY unknowns at the moment:
1. Fanuc Robot, uncertainty of mastering being correct.
2. Fanuc Robot, TCP no evidence of XYZ motions to prove TCP XY vectors are orthogonal to milling bit.
3. Fanuc Robot, TCP appears inaccurate for rotational, suggests TCP XY vectors may not be orthogonal.
4. No evidence of TCP teaching, showing how you are doing it, wrist posture, fixed pointer position etc.
5. Fanuc Robot, recent image show wrist posture in singularity.
6. Recent image, suggests setup conditions is not ideal for TCP teaching.
7. RoboDK, is the code correct, Fanuc robot will execute what you tell it......shit in, shit out......
So my suggestion is to eliminate the majority of these unknowns and see if there is a fundamental issue with the robot, then at least that can be eliminated and shelved.
Thanks again everyone for your answers and help, I appreciate everyone's time and thanks for the help. I will do everything that was written here and provide a photo, video and code if something does not work out again.
-