Having issues Configuring ROS on VOXL CAM
-
I am having issues configuring ROS on VOXL. A little bit confused with this.
-
I'm connected to the VOXL CAM via adb, however to view the Stereo tracking data I need to configure ROS on the VOXL CAM. when i run this command line vi ~/my_ros_env-sh, do I have to change anything on there?
-
When I try to rviz, this what pops up
-
Localhost refers to the running machine's ip, if you're trying to connect to the voxl's ros instance you need to configure your computer's ros to look for your drones ip.
-
@Alex-Gardner What command lines are my using to for this configuration
-
@Alex-Gardner When setting up the ROS on voxl I am supposed to make any change to the ROS_MASTER_URI / ROS_IP / ROS_USERNAME.
-
@Alex-Gardner Please is it possible to have a meeting with you. I have had the VOXL CAM for a while now and I am still encountering issues setting it up. Please it will be well appreciated if someone from your team can start a remote session with me for guidance.
-
You need to set your Ubuntu development environment with ROS to point to the ROS Master process on the VOXL.
Check out: https://answers.ros.org/question/35603/ros_master_uri-change-it-and-save-it/
So for example if the IP address of the VOXL is
192.168.1.118then you need to executeexport ROS_MASTER_URI=http://192.168.1.118:11311on the Ubuntu system and then runrvizfrom the same terminal.You then also need to run the MAVROS or MPA ROS Bridge on the VOXL along with the ROS master node.
Start ros master:
roscoremavros: https://docs.modalai.com/mavros/
On the voxl you need to edit the ROS_IP to match your voxl's IP address so that other hosts can connect to it.
If this doesn't work, consider examining your firewall on your ubuntu system to make sure it isn't block ROS traffic. If it's a vanilla ROS/Ubuntu install you should be fine.
-
@Steve-Turner I updated the ROS_MASTER_URI but its still saying the same thing and saying it cannot contact ROS master
-
Saying the same thing
-
Assuming you are trying to run ROS master on your VOXL, first find out what is your VOXL's IP? Let's call that <VOXL IP>
Then, can you ping that IP from the computer you are trying to run Rviz?
$ ping <VOXL IP>If so, on VOXL edit your ROS environment
export ROS_IP="<VOXL IP>"Then start ROS on the VOXL. Monitor the output of the ROS master when it launches, you should see the "roscore" IP the same as what you just configured.
If so, configure the ROS environment on your PC
What is the IP of your PC on the same network as the VOXL? We'll call that <PC IP>
Configure the PC's ROS environment as such:
export ROS_MASTER_URI="http://<VOXL IP>:11311" export ROS_IP="<PC IP>"Then launch RViz
Note: The instructions above are configuring the master to be the VOXL by pointing both VOXL and the PC to the VOXL's IP address as master. Checkout slides 7,8,9 in the presentation here
-
@Chad-Sweet thanks Chad, so I got Rviz working now !
-
Is the IP address of my VOXL CAM 192.168.8.1
-
@Chad-Sweet I’m connected to the VOXL using Adb not wifi
-
ROS uses wifi to communicate, not ADB. You'll need to connect the drone and you computer to the same network in order to use ros. This can either be done by connecting the drone to your home/work network or by setting the drone to serve as an AP. Instructions for either can be found here
-
@Chad-Sweet I am also having the same issue. I am not sure what im doing wrong.
This is my PC (my_ros_env.sh)
This is my VOXL (my_ros_env.sh)
This is what I get when I try to show my voxl-env
Setting up environment variables for ROS is a little confusing for me.
I am using wifi to communicate with VOXL.
My VOXL IP is the usual 192.168.8.1
My PC IP is 192.168.8.78I am stuck here.
Could someone please point me in the right direction?
-
Just wondering why my voxl environments are all blank everytime I try to view them. Should I " export " the values manually?
-
My Voxl System Image-
-
My current voxl services-
-
Hi,
It looks like you're on a pretty old release of our software stack (3.3.0-0.5), you should download the latest release (3.8.0-0.7) from our downloads page and we'll be better able to support issues that you're having since there's a good chance we've fixed them in the 10 months since the 0.5 release.
