1. Home
    1. Dashboard
    2. Search
  2. Forum
    1. Unresolved Threads
    2. Members
      1. Recent Activities
      2. Users Online
      3. Team Members
      4. Search Members
      5. Trophys
  3. Articles
  4. Blog
  5. Videos
  6. Jobs
  7. Shop
    1. Orders
  • Login or register
  • Search
This Thread
  • Everywhere
  • This Thread
  • This Forum
  • Articles
  • Pages
  • Forum
  • Blog Articles
  • Products
  • More Options
  1. Robotforum - Support and discussion community for industrial robots and cobots
  2. Forum
  3. Industrial Robot Support and Discussion Center
  4. KUKA Robot Forum
Your browser does not support videos RoboDK Software for simulation and programming
Visit our Mainsponsor
IRBCAM
Robotics Channel
Robotics Training
Advertise in robotics
Sponsored Ads

Kuka robot position distortion

  • Recep
  • October 5, 2022 at 9:03 AM
  • Thread is Unresolved
  • Recep
    Trophies
    2
    Posts
    13
    • October 5, 2022 at 9:03 AM
    • #1

    Hello ,

    I have a project with a lot of programs.

    In this project, sometimes the robot is hit and the positions run away. I fix all the points by re-teaching. I need an easier and simpler method. I ask for your help.

  • Online
    Fubini
    Reactions Received
    271
    Trophies
    9
    Posts
    1,871
    • October 5, 2022 at 9:28 AM
    • #2

    Do not hit the robot! Thats cruel. :face_with_tongue:

    Are those hits unidentienal or by purpose because you want to achieve something. If latter waht are you trying to do?

    Ever heard of CollissionDetection? Might be a direction for some cases.

    Fubini

  • Recep
    Trophies
    2
    Posts
    13
    • October 5, 2022 at 10:30 AM
    • #3

    I want to correct my deteriorated positions without teaching.

    Quote from Fubini

    Do not hit the robot! Thats cruel. :face_with_tongue:

    Are those hits unidentienal or by purpose because you want to achieve something. If latter waht are you trying to do?

    Ever heard of CollissionDetection? Might be a direction for some cases.

    Fubini

    I want to correct my deteriorated positions without teaching.

  • Online
    Leon
    Reactions Received
    32
    Trophies
    5
    Posts
    463
    • October 5, 2022 at 11:06 AM
    • #4

    Well, i would advise to fix the problem that keeps your points from deteriorating. This should be simpler then reteaching all your points.

    Else make a new base to refer your points to, and if something happens you only have to reteach the new base. (but i strongly advise that you fix your problem)

    Every problem has a solution, that isn't the problem. The problem is the solution.

  • Online
    Fubini
    Reactions Received
    271
    Trophies
    9
    Posts
    1,871
    • October 5, 2022 at 12:39 PM
    • #5

    Totally agree deteriorated positions as you call it is something a process should never generate. Reteaching the positions is a solution if something like this happens but not the problem. The problem should be solved. So again: What is the problem? Otherwise if all points refer to a common base of course the "error" can be compensated by shifting the base as Leon said.

    Fubini

  • Mentat
    Reactions Received
    61
    Trophies
    5
    Posts
    243
    • October 5, 2022 at 12:53 PM
    • #6

    Depending on how hard and where the robot was hit, maybe consider remastering the robot's axes too.

  • Recep
    Trophies
    2
    Posts
    13
    • October 5, 2022 at 3:41 PM
    • #7
    Code


    Files

    pasted-from-clipboard.png 312 Byte – 66 Downloads
  • Recep
    Trophies
    2
    Posts
    13
    • October 5, 2022 at 3:43 PM
    • #8
    Quote from Mentat

    Depending on how hard and where the robot was hit, maybe consider remastering the robot's axes to

    Code
    I tried something like this. I introduced one base. I then simulated the points distorted by changing the angle of the flange. I bought a base again as it is. but when I play the program, the corrupted points are not fixed. what do you think is the reason? where am i doing wrong?
  • Recep
    Trophies
    2
    Posts
    13
    • October 5, 2022 at 3:44 PM
    • #9
    Quote from Fubini

    Totally agree deteriorated positions as you call it is something a process should never generate. Reteaching the positions is a solution if something like this happens but not the problem. The problem should be solved. So again: What is the problem? Otherwise if all points refer to a common base of course the "error" can be compensated by shifting the base as Leon said.

    Fubini

    Code
    I tried something like this. I introduced one base. I then simulated the points distorted by changing the angle of the flange. I bought a base again as it is. but when I play the program, the corrupted points are not fixed. what do you think is the reason? where am i doing wrong?
  • panic mode
    Reactions Received
    1,263
    Trophies
    11
    Posts
    13,030
    • October 5, 2022 at 5:01 PM
    • #10

    as everyone already suggested - make sure that robot does not collide with things. this causes severe stress on the robot arm and controller. both of them could be damaged by this even if it is not showing up as obvious damage. Often one collision is enough to create a problem, such as stretch the belts or strip the teeth...

    this is no different than driving a car. do not hit anything (other cars, stationary objects, pedestrians...).

    number of collisions is inversely proportional to skill and competence level of of the driver (or in this case programmer).

    but if that happens you also need to find WHY points do not match any more... what exactly has moved?

    maybe it is the robot axes. This requires arm inspection and mastering of the robot.

    maybe it is the tooling. This requires repairing or remeasuring tooling

    maybe it is the fixture that robot is reaching into. That requires remeasuring base associated with the fixture.

    maybe the robot foot is not in the same place any more (support moved or robot slipped relative to support). Properly mounted robots are anchored securely to sturdy support and have locating pins to prevent slipping.

    ...etc. and maybe it is more than one thing...

    when collisions cannot be avoided, they need to managed. this means using suitable strategy such has moving slowly, sensing situation, use collision detection, limit torque etc.

    1) read pinned topic: READ FIRST...

    2) if you have an issue with robot, post question in the correct forum section... do NOT contact me directly

    3) read 1 and 2

  • Recep
    Trophies
    2
    Posts
    13
    • October 6, 2022 at 9:08 AM
    • #11
    Code

    pasted-from-clipboard.png

  • Recep
    Trophies
    2
    Posts
    13
    • October 6, 2022 at 9:10 AM
    • #12
    Quote from panic mode

    as everyone already suggested - make sure that robot does not collide with things. this causes severe stress on the robot arm and controller. both of them could be damaged by this even if it is not showing up as obvious damage. Often one collision is enough to create a problem, such as stretch the belts or strip the teeth...

    this is no different than driving a car. do not hit anything (other cars, stationary objects, pedestrians...).

    number of collisions is inversely proportional to skill and competence level of of the driver (or in this case programmer).

    but if that happens you also need to find WHY points do not match any more... what exactly has moved?

    maybe it is the robot axes. This requires arm inspection and mastering of the robot.

    maybe it is the tooling. This requires repairing or remeasuring tooling

    maybe it is the fixture that robot is reaching into. That requires remeasuring base associated with the fixture.

    maybe the robot foot is not in the same place any more (support moved or robot slipped relative to support). Properly mounted robots are anchored securely to sturdy support and have locating pins to prevent slipping.

    ...etc. and maybe it is more than one thing...

    when collisions cannot be avoided, they need to managed. this means using suitable strategy such has moving slowly, sensing situation, use collision detection, limit torque etc.

    Display More
    Code
    Please do not think of this as a collision. eg flange angle changed for some reason. How can I most easily arrange the previously taught points relative to the new flange.
    Code

    pasted-from-clipboard.png

  • Online
    Leon
    Reactions Received
    32
    Trophies
    5
    Posts
    463
    • October 6, 2022 at 1:13 PM
    • #13
    Quote from Recep

    Please do not think of this as a collision.

    How Then should we think about this? The problem that are describing i would label as a serious problem with either your programming or your robot. The worst thing is you only seem to be interested in solving the symptoms and not the problem itself.

    This way of thinking will get you nowhere and personally i don't really like to help in this way.

    Every problem has a solution, that isn't the problem. The problem is the solution.

  • panic mode
    Reactions Received
    1,263
    Trophies
    11
    Posts
    13,030
    • October 7, 2022 at 6:56 PM
    • #14

    "it's not a collision"... meanwhile things inside robot are like this

    1) read pinned topic: READ FIRST...

    2) if you have an issue with robot, post question in the correct forum section... do NOT contact me directly

    3) read 1 and 2

Advertising from our partners

IRBCAM
Robotics Channel
Robotics Training
Advertise in robotics
Advertise in Robotics
Advertise in Robotics

Job Postings

  • Anyware Robotics is hiring!

    yzhou377 February 23, 2025 at 4:54 AM
  • How to see your Job Posting (search or recruit) here in Robot-Forum.com

    Werner Hampel November 18, 2021 at 3:44 PM
Your browser does not support videos RoboDK Software for simulation and programming

Tag Cloud

  • abb
  • Backup
  • calibration
  • Communication
  • CRX
  • DCS
  • dx100
  • dx200
  • error
  • Ethernet
  • Ethernet IP
  • external axis
  • Fanuc
  • help
  • hmi
  • I/O
  • irc5
  • IRVIsion
  • karel
  • kawasaki
  • KRC2
  • KRC4
  • KRC 4
  • KRL
  • KUKA
  • motoman
  • Offset
  • PLC
  • PROFINET
  • Program
  • Programming
  • RAPID
  • robodk
  • roboguide
  • robot
  • robotstudio
  • RSI
  • safety
  • Siemens
  • simulation
  • SPEED
  • staubli
  • tcp
  • TCP/IP
  • teach pendant
  • vision
  • Welding
  • workvisual
  • yaskawa
  • YRC1000

Thread Tag Cloud

  • abb
  • Backup
  • calibration
  • Communication
  • CRX
  • DCS
  • dx100
  • dx200
  • error
  • Ethernet
  • Ethernet IP
  • external axis
  • Fanuc
  • help
  • hmi
  • I/O
  • irc5
  • IRVIsion
  • karel
  • kawasaki
  • KRC2
  • KRC4
  • KRC 4
  • KRL
  • KUKA
  • motoman
  • Offset
  • PLC
  • PROFINET
  • Program
  • Programming
  • RAPID
  • robodk
  • roboguide
  • robot
  • robotstudio
  • RSI
  • safety
  • Siemens
  • simulation
  • SPEED
  • staubli
  • tcp
  • TCP/IP
  • teach pendant
  • vision
  • Welding
  • workvisual
  • yaskawa
  • YRC1000

Tags

  • KUKA
  • position modfying
  • TouchUp
  • Position configuration
  1. Privacy Policy
  2. Legal Notice
Powered by WoltLab Suite™
As a registered Member:
* You will see no Google advertising
* You can translate posts into your local language
* You can ask questions or help the community with your knowledge
* You can thank the authors for their help
* You can receive notifications of replies or new topics on request
* We do not sell your data - we promise

JOIN OUR GREAT ROBOTICS COMMUNITY.
Don’t have an account yet? Register yourself now and be a part of our community!
Register Yourself Lost Password
Robotforum - Support and discussion community for industrial robots and cobots in the WSC-Connect App on Google Play
Robotforum - Support and discussion community for industrial robots and cobots in the WSC-Connect App on the App Store
Download