jihoonl's profile - activity

jihoonl@MacBook-Pro:~/work/ros2/mine/src/hello_ros2/my_cpp_pkg$ cmake --version cmake version 3.12.3 Could this be the

@Karsten It still gives me the same error.

Failed to compile ros2/examples in OS X Hello there, I am failing to compile ros2/examples after fresh install in os X

Recently, siemens announced to rossharp to use ROS together with unity. I suggest to try this. https://github.com/sieme

you might want to check if your smart phone supports websocket. rosbridge does not work without websocket.

Or can you try

http://wiki.ros.org/rospy_message_con...

It looks like rosgraph_msgs is not detect in your ros package path. Make sure that correct ros environment is set in the PC. It cannot find message packages without proper ROS_PACKAGE_PATH setup.

Just as question.

Is there any tutorial that guides how to develop local planner for navi stack?

There is remapping rule in laserscan_nodelet_manager.

<remap from="scan" to="/scan"/>

You may want to remove this.

It might have racing condition in https://github.com/robotics-in-concer... .

However, it waits 60 seconds for the topics to be ready. which should be enough time for turtlebot to be started in most of recent laptops. So I would suggest to try with other laptops. Or increase the timeout in source level.

If you have hydro apps in your android device, you may need to completely remove them.

This problem is related to this issue https://github.com/corot/world_canvas... which has been resolved yesterday. So please update your debs and source, then retry. It should work as of now.

What was the output when you did 'rosdep install --from-paths src -i -y'?

you may want to check out rqt_reconfigure. move_base, cmd_vel_mux, navigation_smoother these packages support dynamic reconfiguration.

http://wiki.ros.org/rqt_reconfigure

This link will help you.

http://wiki.ros.org/turtlebot/Tutoria...

bondpy.py warning is created by http://wiki.ros.org/bondpy . I have confirmed that it does not cause any problem.

I would suggest to follow kobuki tutorials to start kobuki and ros tutorial how to write your own node in cpp.

Do you use kobuki or create?

This is weird. 3dsensor.launch does not associate with any kobuki udev rules...

This kobuki script might be helpful to implement backward move.

https://github.com/yujinrobot/kobuki/...

It seems like docker does not support avahi-daemon properly. And it causes a problem in zero configuration.

I have proposed a patch to use rocon without zero configuration in https://github.com/robotics-in-concer...

With this patch, you should be able to run chatter concert without zeroconf failure.

Could you explain how did you start the robot? For example, how you set the environment variables.

rosinstall file used in the installation page has been updated. turtlebot_create_desktop should get installed with instruction from now.

https://github.com/yujinrobot/yujin_t...

There are no released package in hydro. But you should be able to checkout turtlebot_simulator hydro-devel branch which includes turtlebot_stage. https://github.com/turtlebot/turtlebo...

Yeah I was curious about this. It would be really nice feature to test sensors and robot logics in simulation.

turtlebot's spec would be helpful

Could you mark it as resolved if it is no longer problem?

What do you get from lsusb? and how did you start kinect? what's your pc spec?

Check https://github.com/rosjava

have you souce setup.bash in devel directorY?

kobuki_desktop includes kobuki_gazebo_plugin which generates libgazebo_ros_kobuki.so. Or did you follow turtlebot src installation guide? if you follow http://wiki.ros.org/turtlebot/Tutoria... , you shouldn't have any problem..

Does it happen every time you try? Sometimes, github causes a connection problem.

Did you install kobuki_desktop?

Either way should work.

You can flip the position_share publisher from robot A to system X, or you can flip position_share subscriber from system X to robot A.

In this case, a position_share subscriber node in the system X will receive position of robot A.