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. Simulation Systems
  4. RoboDK
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

Position not reachable

  • Ruts Ertfeld
  • August 19, 2021 at 8:19 PM
  • Thread is Unresolved
  • Ruts Ertfeld
    Reactions Received
    1
    Trophies
    2
    Posts
    11
    • August 19, 2021 at 8:19 PM
    • #1

    Hey,

    I will get straight to the issue. I created a simple and working program in RoboDK, that consisted of 3 targets. When I loaded the program on to the real robot, 2 positions worked but 1 threw an error, the error was "Position not reachable". So my question is, how to solve this?

    Now the physical robot is Fanuc ArcMate 100i (with RJ2 controller) and because that model is quite old and I could not find a 3D model anywhere so I had to create the model myself, so the problem may lie there.

    When jogging the joints in RoboDK everything looks correct, so I don't know where to look for the problem.

    Robot Paramaters:

    https://ibb.co/JmrWpTN

    Robot model in RoboDK:

    https://ibb.co/pz1pv4C

    Thank you in advance!

    Images

    • Oige.jpg
      • 51.1 kB
      • 512 × 424
      • 6
  • Lemster68 August 19, 2021 at 8:32 PM

    Approved the thread.
  • massula
    Reactions Received
    200
    Trophies
    8
    Posts
    1,421
    • August 20, 2021 at 2:55 PM
    • #2

    Your robot parameters image isn't showing the dimensions you inserted on your 3D model.

    I would make a double-check on that.

    What kind of movement you are using on your program, mainly at this point that doesn't work on real robot? J? L? Wrist configs on the generated program also worth a check.

  • Online
    SkyeFire
    Reactions Received
    1,042
    Trophies
    12
    Posts
    9,388
    • August 20, 2021 at 2:57 PM
    • #3
    Quote from Ruts Ertfeld

    I will get straight to the issue. I created a simple and working program in RoboDK, that consisted of 3 targets. When I loaded the program on to the real robot, 2 positions worked but 1 threw an error, the error was "Position not reachable". So my question is, how to solve this?

    To begin with:

    1. are these point Joint, or Cartesian?
    2. Are they the same values in the real robot, as compared to the RDK model?
    3. If you create a Cartesian point in RDK, then run the same point on the real robot, do both the real and virtual robots end up at the same joint pose?
      1. If not, then the first place I would look would be the active UFrame and UTool values.
    4. check the Configuration values for the "bad" point. Try creating a copy of it with different Config.
    5. Try just jogging the robot by hand to the coordinates of the "bad" point.
  • Ruts Ertfeld
    Reactions Received
    1
    Trophies
    2
    Posts
    11
    • August 23, 2021 at 12:52 PM
    • #4

    Hey massula thanks for the reply!

    Here are the dimensions:

    https://ibb.co/ZgbHw7c

    Its Linear movement that causes the error. I checked if I jog the robot near the point (that causes the problem) and continue the program the robot completes the linear move without a problem.

  • Ruts Ertfeld
    Reactions Received
    1
    Trophies
    2
    Posts
    11
    • August 23, 2021 at 12:58 PM
    • #5

    Hey SkyeFire, thanks for the reply!

    1. The point that causes is in Joint

    2. Yes they are the same value

    3. Yes, the first program I tested checked different Z (height) values and they matched.

    4. Will try to do that, thanks!

    5. As I replied to massula: I checked if I jog the robot near the point (that causes the problem) and continue the program the robot completes the linear move without a problem. So the point is reachable by the robot.

  • Ruts Ertfeld
    Reactions Received
    1
    Trophies
    2
    Posts
    11
    • August 23, 2021 at 1:18 PM
    • #6

    Hey guys your suggestions worked.

    The issue was with wrist configurations, I changed those and the program ran smoothly.

    Thank you!

  • Jeremy RoboDK
    Reactions Received
    17
    Trophies
    3
    Posts
    75
    • August 23, 2021 at 4:53 PM
    • #7

    I'm a bit late to the party.

    Thanks for all the answers.

    Quick note, as you use a Fanuc robot, it almost certainly uses coupling between axis 2 and axis 3.

    It is possible to define the robot workspace when it comes to the robot axis coupling. We don't do it by default because it is not something manufacturers properly state in their datasheet so it needs to be found experimentally using the real robot or the manufacturer's simulator software.

    If you have the 4 points that represent the workspace of the coupling between j2 and j3 (usually a trapezoid), you can enter it following these steps:

    1. Select Parameters
    2. Check Unlock advanced options
    3. Select Joint Senses
    4. Make sure the last index is not +1 if you want axis coupling
    5. Select OK
    6. Double click the joint limit labels for J2 or J3
    7. You'll see a window that represents the allowed interaction for the coupling. You can change the points that describe the allowed area.

    More information here:

    https://robodk.com/blog/robot-axis-coupling/

    Jeremy

    RoboDK - Simulation and Offline programming software for industrial and collaborative robots.

    Visit us at RoboDK.com
    Take a look at our tutorial videos on our YouTube channel.

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

Similar Threads

  • Position not reachable

    • Tran21
    • August 7, 2021 at 10:35 PM
    • Fanuc Robot Forum
  • Function to check if point is in robot range

    • dcrb
    • March 29, 2021 at 7:22 PM
    • Fanuc Robot Forum
  • ALARM CODE 4980

    • žiga
    • March 24, 2020 at 7:25 PM
    • Yaskawa Motoman Robot Forum
  • Brake

    • SimotionD410
    • June 18, 2018 at 7:23 AM
    • KUKA Robot Forum
  • iRVison removing roll (6th axis) in VRoffset

    • RJacobs
    • April 11, 2018 at 7:02 PM
    • Fanuc Robot Forum
  • Checking if position is reachable under conditions

    • CPh
    • November 22, 2017 at 4:23 PM
    • Fanuc Robot Forum
  • Position not reachable in automatic mode

    • inusO
    • August 28, 2017 at 11:55 AM
    • Fanuc Robot Forum

Tags

  • Fanuc
  • robodk
  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