Sorry about the frustration, it probably would have been easier to just install ROS on a base Ubuntu VM…
I will see what I can do about updating the image.
You need to hit the space bar to select the first option, then TAB and enter to click the OK button. After that, you shouldn’t get the prompt to continue without installing grub.
@rohbotics , can you please upload a working virtual box image??
because is like I have a magni with out the softwares now…, I’m not an expert with ROS and also Iinux…I’m just novel and I’m using alot of time…trying to figure out how to run magni in simulation and even Inhave issues ssh to it…, I thought the software/image should be out of the box , ready to go!!! its frustrating that I have to start from scratch myself, spent the whole night starting from scratch and still going no where,
All I can do now is connect the app to the Robot, and the other issue I found is when I keep pressing forward and it goes but then it hits a wall or obstacle …it just hits it…, no warning or self stop, …, why is that? see below, it crashed into an obstacle …,
yea, thanks for message…, yea very rough time…, trying to get fruducial working at the moment but still no luck…, it thought it would be easy…but so hard…, so how does the robot auto stop then when it detects obstacles infront of it? thanks
I’m not sure how all the nodes are connected up, but the simple_navigation.launch demo seems to use the sonars to detect if there is an obstacle in front, and then while the robot is navigating it will stop.
You will need the sonars to be working, try running rostopic echo /sonars
If you have the simple_navigation.launch running you should see a stream of data there. But if nothing is running then you have a problem with your sonars.
not quite.
Check out the https://learn.ubiquityrobotics.com/fiducials, appropriately titled “Fiducials enable you to set waypoints and goals”
Basically, if you follow that setup, then you will be able to set waypoints for the robot, and it will then “autonomously” drive itself to the waypoint.
this means it will go in a straight line towards the location and stop if it detects any obstacles. It won’t navigate around obstacles however .
@inmoov I rekon you’ve got problems. My gut says you might have modified the fiducial_follow.launch file. https://github.com/UbiquityRobotics/magni_robot/blob/indigo-devel/magni_demos/launch/fiducial_follow.launch
See the bottom where the fiducial follow node is described, they only have it as type="follow.py" not type=fiducial_follow/follow.py, so you could make sure that your code looks like theirs. Although if that doesn’t fix it I don’t know whats going on then.
Regarding the ROS_IP, I imagine its the IP of the vm, but thats often also the IP of the laptop your running it off, so they could coincide.
@johnnyv , ok then how do you explain this then? I tried to set way points using the Robot Commander app (I can control it manually ) but when I voice command “set waypoint Alpha” for instance, I get this screen below, shouldnt this function work right out of the box? I’m not running from my vm or anything, just the rasperri PI it came and I have not modified anything inside…, I just plug and play but still I couldnt get it to work…, please explain thanks
@johnnyv also , I have git clone https://github.com/UbiquityRobotics/magni_robot.git to my catkin_ws/src workspace and still when I done a search on “follow.py” …I do not get any results, I assume this python file needs to be run right? but where is it…, but best if you could explain to me why Robot commander gave me that error when I tried to voice command set way point…, (I would be happy enough if I can get it working just in the app…)
hey man, you need to stop moving around from one problem to another. I rekon you should try to slow down and make sure you’ve resolved one problem before moving to the next.
So, the Robot Commander isn’t working because your fiducial slam doesn’t work. Since the fiducial slam isn’t working, robot commander doesn’t get a position when it asks for one, and so it says “The robots position could not be determined”
There seem to be alot of gotcha’s for new ppl in ros (I know, I’m starting too), but here’s a tip.
Make sure you have run source ~/catkin_ws/devel/setup.bash or better yet, put it into your .bashrc as everything hinges on having run that (and catkin_make ) and if you don’t have it setup right you’ll be in a world of pain.
2, Try to figure out which “fiducal_slam” you are using. If you setup is correct you should be able to go roscd fiducial_slam and it will take you to the directory containing fiducial slam. There should be a subfolder called launch and in there should be fiducial_slam.launch . that’s the file you want to check out, and make sure it looks like what the git repo looks like.
It seems like you are running a lot of these launch files in the VM, but most of them need to be run on the Pi via SSH.
So for fiducial_follow, you need to run roslaunch magni_demos fiducial_follow.launchafter SSH-ing into the Magni.
The only things you will really need to run in the VM itself are visualization tools like RViz or rqt. Some things are convenient to run on the VM, such as rostopic echo and teleop_twist_keyboard, but can easily be run on the Pi as well. Most of the launch files for running actual code need to be run on the magni and not the VM because they need access to the hardware, or the software they need is not installed in the VM, but is installed on the Pi.
Hope that helps you make some progress.
Good luck on your project, David told me about it, and it sounds awesome man!
Please keep us updated and share pictures of your progress.
ok, well I got robot commander app installed on my android, I have not modified anything in the Pi, I got the app connected to Magni and can control it via voice and also the arrow buttons (very impressive), but when I voice command “set waypoint A” for instance, I get this message coming back on the phone, can you please help? not sure what I done wrong here, I had followed instructions on your website and havent changed anything in the Pi (besides just sudo apt update and upgrade and also connetcted it to my home wifi network… and that’s it…)
I’m just thinking what i had done wrong? and also what prerequisites I have missed to make this function work ? I’m not sure if this is also related to roslaunch magni_demos fiducial_follow running on my the Pi , not working aswell, it sees the 49 marker I think and in the logs, 1 marker detected but it keeps spinning around and around…,
Yes, if I can get the base fiducial and waypoint working, definitely going to put my existing robot on top and will share it for sure,