I have recently received my first magni silver, and am having issues with magni_viz, I am getting an error on my workstaion computer as I run:
roslaunch magni_viz view_nav.launch
or
roslaunch magni_viz view_robot.launch
it says its a network error on varrious ports and says it is probably not able to ping itself.
I have followed the tutorials up to visualize with RViz.
I get the same error using the magni hotspot or running over the company wifi, and set up with host names or ip addresses. rostopic list show the expected pile of nodes (same on robot through ssh as on workstation).
Have you looked at the page on our learn site yet: https://learn.ubiquityrobotics.com/workstation_setup
Pay attention to the discussion of the ROS variables of ROS_MASTER_URI and ROS_HOSTNAME.
When you make changes to those environment variables they must be properly exported so I suggest if you change them in your .bashrc you re ‘source’ the file or better yet do a reboot.
The error you report is often due to setup of these environment variables.
ROS1 must be setup on our Magni (which of course it would be) and also be setup on the workstation or laptop. Both computers must be on the same network and able to ping each other as well.
Be sure that the network names you use for those variables are able to be used with success in a linux ping command as well.
A word on versions of Ubiquity Linux and ROS. We ship using Ubuntu 16.04 on our current images and we do our makes for production code on ROS Kinetic (matches to Ubuntu 16.04).
A couple of us here are using Ubuntu Linix 18.04 (Melodic) on our laptops with great success for running Rviz and other ssh python scrips so I will not go so far as to say it is supported but it ‘seems ok’ and I use that combination with daily success.
The use of ROS2 has been ‘played with’ but that is a fast moving area in a lot of ‘flux’ and I cannot recommend that path at this time due to the flux in ROS2 and the ROS1 to ROS2 bridge but I don’t think you are asking that level of support.
Let us know if your issue is still not resolved after looking at that page of ours.
Mark
Yes I was following the learn.ubiquity tutorials.
I have exported ROS_MASTER_URI and ROS_HOSTNAME. and I know that works because rostopic list works. I am running ubuntu 16.04 and ros kinetic on the workstation.
Can you please post the output of env | grep ROS and ifconfig and hostname? Also the output of roswtf.
Thanks,
Rohan
on workstation:
env | grep ROS
ROS_ROOT=/opt/ros/kinetic/share/ros
ROS_PACKAGE_PATH=/home/lorne/catkin_ws/src:/opt/ros/kinetic/share
ROS_MASTER_URI=http://ubiquityrobot.local:11311
ROS_PYTHON_VERSION=2
ROS_VERSION=1
ROS_HOSTNAME=.local
ROSLISP_PACKAGE_DIRECTORIES=/home/lorne/catkin_ws/devel/share/common-lisp
ROS_DISTRO=kinetic
ROS_ETC_DIR=/opt/ros/kinetic/etc/ros
on robot:
ROS_ROOT=/opt/ros/kinetic/share/ros
ROS_PACKAGE_PATH=/home/ubuntu/catkin_ws/src:/opt/ros/kinetic/share
ROS_MASTER_URI=http://ubiquityrobot.local:11311
ROS_VERSION=1
ROS_PARALLEL_JOBS=-j2
ROS_HOSTNAME=ubiquityrobot.local
ROSLISP_PACKAGE_DIRECTORIES=/home/ubuntu/catkin_ws/devel/share/common-lisp
ROS_DISTRO=kinetic
ROS_ETC_DIR=/opt/ros/kinetic/etc/ros
workstation ifconfig
enp2s0 Link encap:Ethernet HWaddr b8:ae:ed:99:7c:2a
inet addr:10.105.11.123 Bcast:10.105.11.255 Mask:255.255.255.0
inet6 addr: fe80::9bbc:ab81:a1e8:1da6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2110010 errors:0 dropped:0 overruns:0 frame:0
TX packets:35155 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:207204806 (207.2 MB) TX bytes:2907020 (2.9 MB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:7558 errors:0 dropped:0 overruns:0 frame:0
TX packets:7558 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:655938 (655.9 KB) TX bytes:655938 (655.9 KB)
wlp3s0 Link encap:Ethernet HWaddr c4:8e:8f:7a:7b:39
inet addr:10.42.0.86 Bcast:10.42.0.255 Mask:255.255.255.0
inet6 addr: fe80::d315:70e2:7b7b:d2bb/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:73021 errors:0 dropped:0 overruns:0 frame:0
TX packets:73131 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:17475112 (17.4 MB) TX bytes:6435947 (6.4 MB)
the top connection is a hardline to company network, I’ve tried with it unplugged as well.
lorne@rosmaster:/$ hostname
rosmaster
lorne@rosmaster:/$ roswtf
Loaded plugin tf.tfwtf
No package or stack in context
================================================================================
Static checks summary:
Found 1 warning(s).
Warnings are things that may be just fine, but are sometimes at fault
WARNING ROS_HOSTNAME may be incorrect: ROS_HOSTNAME [.local] cannot be resolved to an IP address
================================================================================
Beginning tests of your ROS graph. These may take awhile…
analyzing graph…
… done analyzing graph
running graph rules…
… done running graph rules
running tf checks, this will take a second…
… tf checks complete
Online checks summary:
Found 1 warning(s).
Warnings are things that may be just fine, but are sometimes at fault
WARNING The following node subscriptions are unconnected:
- /tf2_web_republisher:
- /tf2_web_republisher/cancel
- /tf2_web_republisher/goal
OK thanks. I had a $ by the hostname (host was $rosmaster) fixed that and its working. thanks