Revision history [back]

Ok. Please tell me exactly how you setup your workspace, which versions of the packages you installed, what you installed, and what you are trying to run (launch files, etc). Please update your original question with that information.

The manipulator we are using is Fanuc Robot M-710iC/50.

I like the large image you included, but just the model name would've sufficed :). We could be needing all that space for question updates pretty soon.

Yes. I was only running rostate at that point. After reading your response I ran ros from TPE (which, correct me of I'm wrong, has RUN ROS_STATE, RUN ROS_MOVESM, CALL ROX_RELAY).

The ros TPE program does start the programs you mention. Can you add what kind of feedback you get on the TP once you've started the ros program? I'm looking for things like

12345 I RSTA Connected
12345 I RREL Connected

If you don't see that, something is wrong, and trajectory execution will not work no matter what you try.

RIVZ is still able to read the states from the robot but even now sending commands to the robot does not work.

I'm just going to include this for completeness, but do know that if your controller is not in AUTO mode, you'll have to keep pressing SHIFT + keep the deadman depressed for trajectory execution to work.

[..] I still get controller takes too long error:

With the way the current driver works, you'll always get that error (we cannot get 100% performance out of the controller), so I'd advise you to either allow way more time for execution (use the scaling factor) or disable the execution monitoring completely. See the fanuc_driver/Troubleshooting - Robot stops at seemingly random points during trajectory execution section for info on how to that (the linked ROS Answers post has an example that shows how to edit your launch files).

Ok. Please tell me exactly how you setup your workspace, which versions of the packages you installed, what you installed, and what you are trying to run (launch files, etc). Please update your original question with that information.

The manipulator we are using is Fanuc Robot M-710iC/50.

I like the large image you included, but just the model name would've sufficed :). We could be needing all that space for question updates pretty soon.

Yes. I was only running rostate at that point. After reading your response I ran ros from TPE (which, correct me of I'm wrong, has RUN ROS_STATE, RUN ROS_MOVESM, CALL ROX_RELAY).

The ros TPE program does start the programs you mention. Can you add what kind of feedback you get on the TP once you've started the ros program? I'm looking for things like

12345 I RSTA Connected
12345 I RREL Connected

If you don't see that, something is wrong, and trajectory execution will not work no matter what you try.

RIVZ is still able to read the states from the robot but even now sending commands to the robot does not work.

I'm just going to include this for completeness, but do know that if your controller is not in AUTO mode, you'll have to keep pressing SHIFT + keep the deadman depressed for trajectory execution to work.

[..] I still get controller takes too long error:

With the way the current driver works, you'll always get that error (we cannot get 100% performance out of the controller), so I'd advise you to either allow way more time for execution (use the scaling factor) or disable the execution monitoring completely. See the fanuc_driver/Troubleshooting - Robot stops at seemingly random points during trajectory execution section for info on how to that (the linked ROS Answers post has an example that shows how to edit your launch files).

Ok. Please tell me exactly how you setup your workspace, which versions of the packages you installed, what you installed, and what you are trying to run (launch files, etc). Please update your original question with that information.

The manipulator we are using is Fanuc Robot M-710iC/50.

I like the large image you included, but just the model name would've sufficed :). We could be needing all that space for question updates pretty soon.

Yes. I was only running rostate at that point. After reading your response I ran ros from TPE (which, correct me of I'm wrong, has RUN ROS_STATE, RUN ROS_MOVESM, CALL ROX_RELAY).

The ros TPE program does start the programs you mention. Can you add what kind of feedback you get on the TP once you've started the ros program? I'm looking for things like

12345 I RSTA Connected
12345 I RREL Connected

If you don't see that, something is wrong, and trajectory execution will not work no matter what you try.

RIVZ is still able to read the states from the robot but even now sending commands to the robot does not work.

I'm just going to include this for completeness, but do know that if your controller is not in AUTO mode, you'll have to keep pressing SHIFT + keep the deadman depressed for trajectory execution to work.

[..] I still get controller takes too long error:

With the way the current driver works, you'll always get that error (we cannot get 100% performance out of the controller), so I'd advise you to either allow way more time for execution (use the scaling factor) or disable the execution monitoring completely. See the fanuc_driver/Troubleshooting - Robot stops at seemingly random points during trajectory execution section for info on how to that (the linked ROS Answers post has an example that shows how to edit your launch files).

I just realized when setting things up, for the TPE Programs section, I just left everything at default. I am referring to this because I didn't know how to edit it using the teach pendant

You'll want to make sure that none of the used flags, integer or position registers is used by other programs on the controller. If the fanuc_driver Karel and TP programs are the only one running on the controller, the defaults are probably free to use.

(in particular, I didn't know how to get the colon in 1:ROS-I rdy). I'm not sure if this will cause any problems but thought I should let you know about it.

Forgive me asking, but how much experience do you have with these robots? Editing a TP program should not be too difficult.

Ok. Please tell me exactly how you setup your workspace, which versions of the packages you installed, what you installed, and what you are trying to run (launch files, etc). Please update your original question with that information.

The manipulator we are using is Fanuc Robot M-710iC/50.

I like the large image you included, but just the model name would've sufficed :). We could be needing all that space for question updates pretty soon.

Yes. I was only running rostate at that point. After reading your response I ran ros from TPE (which, correct me of I'm wrong, has RUN ROS_STATE, RUN ROS_MOVESM, CALL ROX_RELAY).

The ros TPE program does start the programs you mention. Can you add what kind of feedback you get on the TP once you've started the ros program? I'm looking for things like

12345 I RSTA Connected
12345 I RREL Connected

If you don't see that, something is wrong, and trajectory execution will not work no matter what you try.

RIVZ is still able to read the states from the robot but even now sending commands to the robot does not work.

I'm just going to include this for completeness, but do know that if your controller is not in AUTO mode, you'll have to keep pressing SHIFT + keep the deadman depressed for trajectory execution to work.

[..] I still get controller takes too long error:

With the way the current driver works, you'll always get that error (we cannot get 100% performance out of the controller), so I'd advise you to either allow way more time for execution (use the scaling factor) or disable the execution monitoring completely. See the fanuc_driver/Troubleshooting - Robot stops at seemingly random points during trajectory execution section for info on how to that (the linked ROS Answers post has an example that shows how to edit your launch files).

I just realized when setting things up, for the TPE Programs section, I just left everything at default. I am referring to this because I didn't know how to edit it using the teach pendant

You'll want to make sure that none of the used flags, integer or position registers is used by other programs on the controller. If the fanuc_driver Karel and TP programs are the only one running on the controller, the defaults are probably free to use.

(in particular, I didn't know how to get the colon in 1:ROS-I rdy). I'm not sure if this will cause any problems but thought I should let you know about it.

Forgive me asking, but how much experience do you have with these robots? Editing a TP program should not be too difficult.

edit:

I have all the directories relating to lrmate200ic and have removed the others (I assumed this would be the closed to the one I have).

The LR Mate 200 robots are some of the smallest Fanuc has, both in reach and in max payload. The M-710iC/50 is a moderately large robot with much lower (velocity) limits, so I would've gone for the files of the M-10iA for a first test.

I noticed that after quitting Moveit! I get an error (in red):

29448 E RSTA jnt_pkt_srlise err: -67208

That is normal, as closing RViz (not MoveIt actually) takes down all of the other nodes, including fanuc_driver, which then disconnects from the programs running on the controller. That is what that 'error' tells you.

If I launch Moveit! again, I see that only RSTA launches and says waiting:

29448 I RSTA Waiting for ROS state prox

and RREL does not launch.

That is not ok. Both RSTA and RREL should notice that you disconnected. Did you let go of either SHIFT or the deadman in the middle of a trajectory execution? If yes, it could be that RREL got hung up waiting for the last traj pt to be completed, which prevents it from detecting a closed socket.

Letting go of either SHIFT or the deadman causes the controller to pause both the ROS and ROS_MOVESM programs, so unless you continue or restart them, things will not work properly anymore.

Btw: neither of them 'launches': they are still running, just waiting for new connections.

I had to reboot the controller and launch roscore again to get everything right.

That is not necessary: just ABORT all programs on the controller by using Fctn→ABORT ALL on the TP. You might have to use that twice, depending on in which state the programs are.are. Then restart the ROS side if necessary.

I don't have any experience at all. I started working with these robots a week ago (part of my internship).

Then please do yourself a favour and spend some time getting familiar with the robot, controller and the TP (ideally by following a course, or learning from someone with experience) before attempting to use it with ROS. Without experience, judging what is 'normal' behaviour for the machine is hard, and you could end up damaging equipment, others or yourself. Using our tutorials is not a good way to learn how to handle these dangerous robots.

This may sound pedantic, but I've seen too many near-accidents with these things to ignore it.

• I don't know how to run the robot in AUTO mode. Could you please direct me on how to do it?

This is typically done using the selector switch on the control cabinet. Please do read the safety instructions before using it.

• Do you have the URDF for the M710ic/50 model? If you do, could you please share it.

I've just pushed a fanuc_m710ic_support package to the fanuc_experimental repository. Installation and use is identical to all other Fanuc support packages. No IKFast plugins nor MoveIt configurations are included at this time.

Note that this package is experimental: I've checked it as much as I can, but you are responsible for making sure that joint limits and the general configuration correspond to the specific variant you have there.

Ok. Please tell me exactly how you setup your workspace, which versions of the packages you installed, what you installed, and what you are trying to run (launch files, etc). Please update your original question with that information.

The manipulator we are using is Fanuc Robot M-710iC/50.

I like the large image you included, but just the model name would've sufficed :). We could be needing all that space for question updates pretty soon.

Yes. I was only running rostate at that point. After reading your response I ran ros from TPE (which, correct me of I'm wrong, has RUN ROS_STATE, RUN ROS_MOVESM, CALL ROX_RELAY).

The ros TPE program does start the programs you mention. Can you add what kind of feedback you get on the TP once you've started the ros program? I'm looking for things like

12345 I RSTA Connected
12345 I RREL Connected

If you don't see that, something is wrong, and trajectory execution will not work no matter what you try.

RIVZ is still able to read the states from the robot but even now sending commands to the robot does not work.

I'm just going to include this for completeness, but do know that if your controller is not in AUTO mode, you'll have to keep pressing SHIFT + keep the deadman depressed for trajectory execution to work.

[..] I still get controller takes too long error:

With the way the current driver works, you'll always get that error (we cannot get 100% performance out of the controller), so I'd advise you to either allow way more time for execution (use the scaling factor) or disable the execution monitoring completely. See the fanuc_driver/Troubleshooting - Robot stops at seemingly random points during trajectory execution section for info on how to that (the linked ROS Answers post has an example that shows how to edit your launch files).

I just realized when setting things up, for the TPE Programs section, I just left everything at default. I am referring to this because I didn't know how to edit it using the teach pendant

You'll want to make sure that none of the used flags, integer or position registers is used by other programs on the controller. If the fanuc_driver Karel and TP programs are the only one running on the controller, the defaults are probably free to use.

(in particular, I didn't know how to get the colon in 1:ROS-I rdy). I'm not sure if this will cause any problems but thought I should let you know about it.

Forgive me for asking, but how much experience do you have with these robots? Editing a TP program should not be too difficult.

edit:

I have all the directories relating to lrmate200ic and have removed the others (I assumed this would be the closed to the one I have).

The LR Mate 200 robots are some of the smallest Fanuc has, both in reach and in max payload. The M-710iC/50 is a moderately large robot with much lower (velocity) limits, so I would've gone for the files of the M-10iA for a first test.

I noticed that after quitting Moveit! I get an error (in red):

29448 E RSTA jnt_pkt_srlise err: -67208

That is normal, as closing RViz (not MoveIt actually) takes down all of the other nodes, including fanuc_driver, which then disconnects from the programs running on the controller. That is what that 'error' tells you.

If I launch Moveit! again, I see that only RSTA launches and says waiting:

29448 I RSTA Waiting for ROS state prox

and RREL does not launch.

That is not ok. Both RSTA and RREL should notice that you disconnected. Did you let go of either SHIFT or the deadman in the middle of a trajectory execution? If yes, it could be that RREL got hung up waiting for the last traj pt to be completed, which prevents it from detecting a closed socket.

Letting go of either SHIFT or the deadman causes the controller to pause both the ROS and ROS_MOVESM programs, so unless you continue or restart them, things will not work properly anymore.

Btw: neither of them 'launches': they are still running, just waiting for new connections.

I had to reboot the controller and launch roscore again to get everything right.

That is not necessary: just ABORT all programs on the controller by using Fctn→ABORT ALL on the TP. You might have to use that twice, depending on in which state the programs are. Then restart the ROS side if necessary.

I don't have any experience at all. I started working with these robots a week ago (part of my internship).

Then please do yourself a favour and spend some time getting familiar with the robot, controller and the TP (ideally by following a course, or learning from someone with experience) before attempting to use it with ROS. Without experience, judging what is 'normal' behaviour for the machine is hard, and you could end up damaging equipment, others or yourself. Using our tutorials is not a good way to learn how to handle these dangerous robots.

This may sound pedantic, but I've seen too many near-accidents with these things to ignore it.

• I don't know how to run the robot in AUTO mode. Could you please direct me on how to do it?

This is typically done using the selector switch on the control cabinet. Please do read the safety instructions before using it.

• Do you have the URDF for the M710ic/50 model? If you do, could you please share it.

I've just pushed a fanuc_m710ic_support package to the fanuc_experimental repository. Installation and use is identical to all other Fanuc support packages. No IKFast plugins nor MoveIt configurations are included at this time.

Note that this package is experimental: I've checked it as much as I can, but you are responsible for making sure that joint limits and the general configuration correspond to the specific variant you have there.

Ok. Please tell me exactly how you setup your workspace, which versions of the packages you installed, what you installed, and what you are trying to run (launch files, etc). Please update your original question with that information.

The manipulator we are using is Fanuc Robot M-710iC/50.

I like the large image you included, but just the model name would've sufficed :). We could be needing all that space for question updates pretty soon.

Yes. I was only running rostate at that point. After reading your response I ran ros from TPE (which, correct me of I'm wrong, has RUN ROS_STATE, RUN ROS_MOVESM, CALL ROX_RELAY).

The ros TPE program does start the programs you mention. Can you add what kind of feedback you get on the TP once you've started the ros program? I'm looking for things like

12345 I RSTA Connected
12345 I RREL Connected

If you don't see that, something is wrong, and trajectory execution will not work no matter what you try.

RIVZ is still able to read the states from the robot but even now sending commands to the robot does not work.

I'm just going to include this for completeness, but do know that if your controller is not in AUTO mode, you'll have to keep pressing SHIFT + keep the deadman depressed for trajectory execution to work.

[..] I still get controller takes too long error:

With the way the current driver works, you'll always get that error (we cannot get 100% performance out of the controller), so I'd advise you to either allow way more time for execution (use the scaling factor) or disable the execution monitoring completely. See the fanuc_driver/Troubleshooting - Robot stops at seemingly random points during trajectory execution section for info on how to that (the linked ROS Answers post has an example that shows how to edit your launch files).

I just realized when setting things up, for the TPE Programs section, I just left everything at default. I am referring to this because I didn't know how to edit it using the teach pendant

You'll want to make sure that none of the used flags, integer or position registers is used by other programs on the controller. If the fanuc_driver Karel and TP programs are the only one running on the controller, the defaults are probably free to use.

(in particular, I didn't know how to get the colon in 1:ROS-I rdy). I'm not sure if this will cause any problems but thought I should let you know about it.

Forgive me for asking, but how much experience do you have with these robots? Editing a TP program should not be too difficult.

edit:

I have all the directories relating to lrmate200ic and have removed the others (I assumed this would be the closed to the one I have).

The LR Mate 200 robots are some of the smallest Fanuc has, both in reach and in max payload. The M-710iC/50 is a moderately large robot with much lower (velocity) limits, so I would've gone for the files of the M-10iA for a first test.

I noticed that after quitting Moveit! I get an error (in red):

29448 E RSTA jnt_pkt_srlise err: -67208

That is normal, as closing RViz (not MoveIt actually) takes down all of the other nodes, including fanuc_driver, which then disconnects from the programs running on the controller. That is what that 'error' tells you.

If I launch Moveit! again, I see that only RSTA launches and says waiting:

29448 I RSTA Waiting for ROS state prox

and RREL does not launch.

That is not ok. Both RSTA and RREL should notice that you disconnected. Did you let go of either SHIFT or the deadman in the middle of a trajectory execution? If yes, it could be that RREL got hung up waiting for the last traj pt to be completed, which prevents it from detecting a closed socket.

Letting go of either SHIFT or the deadman causes the controller to pause both the ROS and ROS_MOVESM programs, so unless you continue or restart them, things will not work properly anymore.

Btw: neither of them 'launches': they are still running, just waiting for new connections.

I had to reboot the controller and launch roscore again to get everything right.

That is not necessary: just ABORT all programs on the controller by using Fctn→ABORT ALL on the TP. You might have to use that twice, depending on in which state the programs are. Then restart the ROS side if necessary.

I don't have any experience at all. I started working with these robots a week ago (part of my internship).

Then please do yourself a favour and spend some time getting familiar with the robot, controller and the TP (ideally by following a course, or learning from someone with experience) before attempting to use it with ROS. Without experience, judging what is 'normal' behaviour for the machine is hard, and you could end up damaging equipment, others or yourself. Using our tutorials is not a good way to learn how to handle these dangerous robots.

This may sound pedantic, but I've seen too many near-accidents with these things to ignore it.

• I don't know how to run the robot in AUTO mode. Could you please direct me on how to do it?

This is typically done using the selector switch on the control cabinet. Please do read the safety instructions before using it.

• Do you have the URDF for the M710ic/50 model? If you do, could you please share it.

I've just pushed a fanuc_m710ic_support package to the fanuc_experimental repository. Installation and use is identical to all other Fanuc support packages. No IKFast plugins nor MoveIt configurations are included at this time.time. See also wiki/fanuc_m710ic_support.

Note that this package is experimental: I've checked it as much as I can, but you are responsible for making sure that joint limits and the general configuration correspond to the specific variant you have there.

Ok. Please tell me exactly how you setup your workspace, which versions of the packages you installed, what you installed, and what you are trying to run (launch files, etc). Please update your original question with that information.

The manipulator we are using is Fanuc Robot M-710iC/50.

I like the large image you included, but just the model name would've sufficed :). We could be needing all that space for question updates pretty soon.

Yes. I was only running rostate at that point. After reading your response I ran ros from TPE (which, correct me of I'm wrong, has RUN ROS_STATE, RUN ROS_MOVESM, CALL ROX_RELAY).

The ros TPE program does start the programs you mention. Can you add what kind of feedback you get on the TP once you've started the ros program? I'm looking for things like

12345 I RSTA Connected
12345 I RREL Connected

If you don't see that, something is wrong, and trajectory execution will not work no matter what you try.

RIVZ is still able to read the states from the robot but even now sending commands to the robot does not work.

I'm just going to include this for completeness, but do know that if your controller is not in AUTO mode, you'll have to keep pressing SHIFT + keep the deadman depressed for trajectory execution to work.

[..] I still get controller takes too long error:

With the way the current driver works, you'll always get that error (we cannot get 100% performance out of the controller), so I'd advise you to either allow way more time for execution (use the scaling factor) or disable the execution monitoring completely. See the fanuc_driver/Troubleshooting - Robot stops at seemingly random points during trajectory execution section for info on how to that (the linked ROS Answers post has an example that shows how to edit your launch files).

I just realized when setting things up, for the TPE Programs section, I just left everything at default. I am referring to this because I didn't know how to edit it using the teach pendant

You'll want to make sure that none of the used flags, integer or position registers is used by other programs on the controller. If the fanuc_driver Karel and TP programs are the only one running on the controller, the defaults are probably free to use.

(in particular, I didn't know how to get the colon in 1:ROS-I rdy). I'm not sure if this will cause any problems but thought I should let you know about it.

Forgive me for asking, but how much experience do you have with these robots? Editing a TP program should not be too difficult.

edit:

I have all the directories relating to lrmate200ic and have removed the others (I assumed this would be the closed to the one I have).

The LR Mate 200 robots are some of the smallest Fanuc has, both in reach and in max payload. The M-710iC/50 is a moderately large robot with much lower (velocity) limits, so I would've gone for the files of the M-10iA for a first test.

I noticed that after quitting Moveit! I get an error (in red):

29448 E RSTA jnt_pkt_srlise err: -67208

That is normal, as closing RViz (not MoveIt actually) takes down all of the other nodes, including fanuc_driver, which then disconnects from the programs running on the controller. That is what that 'error' tells you.

If I launch Moveit! again, I see that only RSTA launches and says waiting:

29448 I RSTA Waiting for ROS state prox

and RREL does not launch.

That is not ok. Both RSTA and RREL should notice that you disconnected. Did you let go of either SHIFT or the deadman in the middle of a trajectory execution? If yes, it could be that RREL got hung up waiting for the last traj pt to be completed, which prevents it from detecting a closed socket.

Letting go of either SHIFT or the deadman causes the controller to pause both the ROS and ROS_MOVESM programs, so unless you continue or restart them, things will not work properly anymore.

Btw: neither of them 'launches': they are still running, just waiting for new connections.

I had to reboot the controller and launch roscore again to get everything right.

That is not necessary: just ABORT all programs on the controller by using Fctn→ABORT ALL on the TP. You might have to use that twice, depending on in which state the programs are. Then restart the ROS side if necessary.

I don't have any experience at all. I started working with these robots a week ago (part of my internship).

Then please do yourself a favour and spend some time getting familiar with the robot, controller and the TP (ideally by following a course, or learning from someone with experience) before attempting to use it with ROS. Without experience, judging what is 'normal' behaviour for the machine is hard, and you could end up damaging equipment, others or yourself. Using our tutorials is not a good way to learn how to handle these dangerous robots.

This may sound pedantic, but I've seen too many near-accidents with these things to ignore it.

• I don't know how to run the robot in AUTO mode. Could you please direct me on how to do it?

This is typically done using the selector switch on the control cabinet. Please do read the safety instructions before using it.

• Do you have the URDF for the M710ic/50 model? If you do, could you please share it.

I've just pushed a fanuc_m710ic_support package to the fanuc_experimental repository. Installation and use is identical to all other Fanuc support packages. No IKFast plugins nor MoveIt configurations are included at this time. See also wiki/fanuc_m710ic_support.

Note that this package is experimental: I've checked it as much as I can, but you are responsible for making sure that joint limits and the general configuration correspond to the specific variant you have there.