Revision history [back]

ROS programs with GUIs involved (ie: RViz, Gazebo, etc) never really work very well for me in virtual machines. It can probably be done, but it's always more work than it's worth to me.

But in this case, I think the following is your problem:

katie@katie-VirtualBox:~$ rosrun nerian_sp1 nerian_sp1_node
[ WARN] [1498674946.954273774]: No camera calibration file configured. Cannot publish detailed camera information!

Illegal instruction (core dumped)

Ignoring the warning, the next line shows that the node has most likely crashed. This means that even if everything else works as it should, nerian_sp1_node is not there any more, hence no images received.

See warning when I try to run node nerian_sp1, but still shows up when I run rosnode list

The fact that the node still shows in the output of rosnode list is probably because of the sudden crash of the node. Try running rosnode cleanup after the node has crashed and then do a rosnode list again.

ROS programs with GUIs involved (ie: RViz, Gazebo, etc) never really work very well for me in virtual machines. It can probably be done, but it's always more work than it's worth to me.

But in this case, I think the following is your problem:

katie@katie-VirtualBox:~$ rosrun nerian_sp1 nerian_sp1_node
[ WARN] [1498674946.954273774]: No camera calibration file configured. Cannot publish detailed camera information!

Illegal instruction (core dumped)

Ignoring the warning, the next line ("illegal instruction") shows that the node has most likely crashed. This means that even if everything else works as it should, nerian_sp1_node is not there any more, hence no images received.

See warning when I try to run node nerian_sp1, but still shows up when I run rosnode list

The fact that the node still shows in the output of rosnode list is probably because of the sudden crash of the node. Try running rosnode cleanup after the node has crashed and then do a rosnode list again.