-
Notifications
You must be signed in to change notification settings - Fork 987
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
applications package #135
Comments
Hello @francoiswindels :) Did you try download turtlebot3_msgs?? |
Hello,
yes i did
git clone https://github.com/ROBOTIS-GIT/turtlebot3.git
and then git clone https://github.com/ROBOTIS-GIT/turtlebot3_msgs.git
followed by cd ~/catkin_ws and catkin_make
cheers
F
…On Tue, Feb 20, 2018 at 3:05 PM, Taehun Lim ***@***.***> wrote:
Hello @francoiswindels <https://github.com/francoiswindels> :)
Did you try download turtlebot3_msgs??
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#135 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ab0a0un5EH7QAUfFzs3rqQAK2S9mMP1tks5tWlJ9gaJpZM4SLX2p>
.
|
Hello :) Delete |
Hi, thanks |
@francoiswindels That cpp file is written in a way, so that it works on both Burger and Waffle without duplicating code. When you run it, it looks for a variable robot_model and from then onwards, it knows whether you want to be working with Burger or Waffle. So all you need to do is initialize it. If you keep working with different models, you can initialize it in the terminal every time you decide to do some coding (and then when you close the terminal, your variable will disappear). Or (and that is what most people do, because who has money and time for both versions 😋), you just add an extra line to .bashrc file. It is actually described in the official manual here: http://emanual.robotis.com/docs/en/platform/turtlebot3/bringup/ Just go |
Hi,
thanks for taking time to look into this problem,
i do have the turtlebot 3 model specified in my bashrc,
i sourced bashrc before catkin_make but
the problem persist.
thanks for your patience
F
…On Mon, Feb 26, 2018 at 4:12 AM, PandaJules ***@***.***> wrote:
@francoiswindels <https://github.com/francoiswindels>
So your error log is actually quite explanatory - it tells you:
"error: ‘robot_model’ was not declared in this scope"
That cpp file is written in a way, so that it works on both Burger and
Waffle without duplicating code. When you run it, it looks for a variable
robot_model and from then onwards, it knows whether you want to be working
with Burger or Waffle. So all you need to do is initialize it. If you keep
working with different models, you can initialize it in the terminal every
time you decide to do some coding (and then when you close the terminal,
your variable will disappear). Or (and that is what most people do, because
who has money and time for both versions 😋), you just add an extra line
to .bashrc file. It is actually described in the official manual here:
http://emanual.robotis.com/docs/en/platform/turtlebot3/bringup/
Just go
gedit ~/.bashrc
add line export TURTLEBOT3_MODEL = ... (whatever you have)
source ~/.bashrc
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#135 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ab0a0nYy1CUqnNJCoXRM1TLzHSBw2FRzks5tYaKSgaJpZM4SLX2p>
.
|
Okay, but if you look at your log, all errors start at line 45
So just 2 lines above Then your log says "turning_radius_’, ‘rotate_angle_’ , ‘front_distance_limit_’ , ‘side_distance_limit_’ was not declared in this scope". What you are doing inside "if" is initializing, but those variable should have been declared in a header file (gazebo_ros_turtlebot3.h which is inside "include" folder) |
HI,
so you agree with me that the deluge of error message is triggered by the
build of the gazebo package for turtlebot3?
maybe i should start with
1/delete that package
2/re run catkin_make on my catkin_ws to make sure i get a clean build
3/re-install the gazebo turtlebot3 package (from
https://github.com/ROBOTIS-GIT/turtlebot3_simulations)
4/build that package only by using catkin_make -D
CATKIN_WHITELIST_PACKAGES="turtlebot3_simulations"
what do you think?
thanks for your time and patience
cheers
F
…On Tue, Feb 27, 2018 at 9:30 PM, PandaJules ***@***.***> wrote:
Okay, but if you look at your log, all errors start at line 45
If I am not mistaken, this is where it crashes:
`bool GazeboRosTurtleBot3::init()
{
// initialize ROS parameter
nh_.param("is_debug", is_debug_, is_debug_);
std::string robot_model = nh_.paramstd::string("tb3_model", "");
if (!robot_model.compare("burger"))
{
turning_radius_ = 0.08;
rotate_angle_ = 50.0 * DEG2RAD;
front_distance_limit_ = 0.7;
side_distance_limit_ = 0.4;
}`
So just 2 lines above robot_model.compare("burger") we have both
declaration and initialization of the variable robot_model. You could put a
print statement after it to see whether nh_.param<std::string>("tb3_model",
"") was actually able to find it out.
Then your log says "turning_radius_’, ‘rotate_angle_’ ,
‘front_distance_limit_’ , ‘side_distance_limit_’ was not declared in this
scope". What you are doing inside "if" is initializing, but those variable
should have been declared in a header file (gazebo_ros_turtlebot3.h which
is inside "include" folder)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#135 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ab0a0uqCcKsYch9ctTB7LeBU9msZYA0lks5tY-c8gaJpZM4SLX2p>
.
|
Hi, |
Hello,
i'm using a TB3 burger from an ubuntu 16.04 remote machine
i tried to install you applications package following the procedure you describe at the top of
http://emanual.robotis.com/docs/en/platform/turtlebot3/applications/#turtlebot-follower-demo
catkin_make runs to a point (~97%) and then sends out error messages until it ends with
Invoking "make -j4 -l4" failed
details of the error log attached
any thought on what went wrong?
thanks for your time and patience
François
TB3_applications.pdf
The text was updated successfully, but these errors were encountered: