Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Crashing nodes

Hi, I'm new in the forum. I'm writing to explain to you about my problem. In my application (an atonomous indoor vehicle) we have ROS with a set of nodes for mapping and a set of nodes for navigation. I tested these nodes many times and all of the nodes work good.

Now I bought a new computer (intel NUC) and I installed all the tested repository on it and when I launch the Mapping nodes they crash (?). In this particular case, I run the gmapping node and it appears to run correctly (I can see the terminal where it is running and updates frames), but if I want to see the NODELIST (rosnode list) it is not in the list (also the other nodes ar not in the list, only /rosout).

So, I check in the running process list (command top in the linux terminal) and the "crashed" nodes are in the top process list, but I cannot comunicate with them.

ROSDISTRO: Melodic LINUXDISTRO: Ubuntu 18.04 LTS

PS I'd want to load some screenshot, but I'm a forum newbie :(

Crashing nodes

Hi, I'm new in the forum. I'm writing to explain to you about my problem. In my application (an atonomous indoor vehicle) we have ROS with a set of nodes for mapping and a set of nodes for navigation. I tested these nodes many times and all of the nodes work good.

Now I bought a new computer (intel NUC) and I installed all the tested repository on it and when I launch the Mapping nodes they crash (?). In this particular case, I run the gmapping node and it appears to run correctly (I can see the terminal where it is running and updates frames), but if I want to see the NODELIST (rosnode list) it is not in the list (also the other nodes ar not in the list, only /rosout).

So, I check in the running process list (command top in the linux terminal) and the "crashed" nodes are in the top process list, but I cannot comunicate with them.

ROSDISTRO: Melodic LINUXDISTRO: Ubuntu 18.04 LTS

PS I'd want to load some screenshot, but I'm a forum newbie :(

Crashing nodes'Invisible' nodes (invisible to rosnode, but seemingly working)

Hi, I'm new in the forum. I'm writing to explain to you about my problem. In my application (an atonomous indoor vehicle) we have ROS with a set of nodes for mapping and a set of nodes for navigation. I tested these nodes many times and all of the nodes work good.

Now I bought a new computer (intel NUC) and I installed all the tested repository on it and when I launch the Mapping nodes they crash (?). In this particular case, I run the gmapping node and it appears to run correctly (I can see the terminal where it is running and updates frames), but if I want to see the NODELIST (rosnode list) it is not in the list (also the other nodes ar not in the list, only /rosout).

So, I check in the running process list (command top in the linux terminal) and the "crashed" nodes are in the top process list, but I cannot comunicate with them.

ROSDISTRO: Melodic LINUXDISTRO: Ubuntu 18.04 LTS

PS I'd want to load some screenshot, but I'm a forum newbie :(


Edit: thank you for the answer.

have you copied any configuration files from your old PC?

No, I get the entire repository from my git with the standard procedure (git clone URL)

Do none of your nodes respond?

I'm sure that all the nodes launched for mapping are not present in the rosnode list (Slam_gmapping, Odometry_node, TCPserver_node, Static_tf_publisher ecc.), but only /rosout is present in the list.

are you running rosnode on the NUC, or from a remote one?

I use NUC trought teamviewer but all the ROS environment is running on the NUC

Do the nodes respond to rosservice call .. invocations?

I don't know, because I don't have the NUC until Monday

Is dynamic_reconfigure still working?

I don't know. I don't check for dynamic_reconfigure node comunication.

Did you rebuild everything in a fresh workspace, or did you copy your old workspace to the NUC?

I recreated a new catkin_ws from zero and I rebuilt all