-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
youbot_driver base_arm_gripper_test problem #16
Comments
Dear CheffOtter,
I.e. if you execute
from any subdirectory of the youbot_driver package, then at least the test start to run, but I get the same errors as you described in the second case. I will look into this now. |
Dear CheffOtter, Please let us know if it worked for you. Best regards, |
Hi Frederik,
I am getting following error
if I execute
from any subdirectory of the youbot_driver package,it doesn't test start to run, but if I execute from
and so on. do you know where are the coming from? is there any fix for it? and also i added a video, which is included behaviour from youbot self. |
Hi ChefOtter, The workaround, as described in the previous comment, worked for me (call rosrun from any subdirectory of the youbot_driver package). Unfortunately, I can not reconstruct your problem, that you can do this only from the build directory. The errors in the txt file you provided, look like communication errors. Does your youBot work properly otherwise, e.g. by launching the driver? It might be also that your youBot has an older firmware (1.48) than ours (2.00). I don't know if this makes a difference. But I guess not, since the test cases were written in the times where v2.00 was not available yet. And unfortunately, I do not have a youBot with firmware v1.4.8 available. The remaining error with "could not create folder" I fixed. You can find the fix in the updated pull request #17 . If it helps, I can upload the information outputted on the terminal when running the test cases on our youBot. Best regards, |
Hi ChefOtter, Best, |
Hi Frederik, Although I added all changes in my code, what you changed in here, i can call this program anywhere but i am getting this errors, it can't find config folder, actually which is in folder. ##Failure Location unknown## : Error
##Failure Location unknown## : Error
##Failure Location unknown## : Error
##Failure Location unknown## : Error
##Failure Location unknown## : Error
##Failure Location unknown## : Error
##Failure Location unknown## : Error
##Failure Location unknown## : Error
##Failure Location unknown## : Error
##Failure Location unknown## : Error
Failures !!! Should I add also this config folder into my bashrc? Any idea? |
Did you recompile the repository? Maybe you try to delete the devel and build folder before as well. |
I deleted files under these folders
I recompile all
and same errors like before, previous post. |
Somehow, you are doing things twice. So, either you compile the youbot_driver package without catkin and just using plane cmake (like the first three commands) or you just compile it using catkin_make. I suggest to do the following:
|
Hi again Frederick, |
Dear Frederik, |
Perfect. Nice to hear. Thanks. |
@frederikhegger
Hi mate,
I have some problem with youbot_driver
I am using ROS Indigo in Ubuntu 14.04 and try to experiment with youbot which i downloaded youbot_driver from github repo.
I cloned youbot_driver in my
catkin_ws/src
in
catkin_ws
executed catkin_make
source devel/setup.bash
i did also
sudo setcap cap_net_raw+ep catkin_ws/devel/lib/youbot_driver/base_arm_gripper_test
after then i execute
rosrun youbot_driver base_arm_gripper_test
I am getting following error
but if i do like this, according to readme text in youbot_driver folder
I am getting this error which is in following text file
youbot_driver_error.txt
youbot arm moves little bit and then stops and also arm beeps. after all no reaction any more.
Did you have also any error like this on your youbot? Is there any fix or solution for it?
I am very happy about any help or advice
thank you in advance
The text was updated successfully, but these errors were encountered: