2016-07-06 12:20:24 -0500 | received badge | ● Famous Question
(source)
|
2016-04-25 00:19:51 -0500 | received badge | ● Notable Question
(source)
|
2016-02-13 01:49:12 -0500 | received badge | ● Popular Question
(source)
|
2016-02-12 08:22:39 -0500 | received badge | ● Editor
(source)
|
2016-02-12 04:22:56 -0500 | asked a question | Dynamixel A12 tutorial: controller dies Hey there, I've started going through dynamixel tutorials ( http://wiki.ros.org/dynamixel_control... ).
Now I'm in this one (roslaunch my_dynamixel_tutorial start_tilt_controller.launch) The tilt controller is dying and not giving info about why.
This are the steps: 1) I've launched the manager properly: ` $ roslaunch dynamixel_tutorials
SUMMARY
========
PARAMETERS *
/dynamixel_manager/namespace:
dxl_manager *
/dynamixel_manager/serial_ports/pan_tilt_port/baud_rate:
1000000 *
/dynamixel_manager/serial_ports/pan_tilt_port/max_motor_id:
25 *
/dynamixel_manager/serial_ports/pan_tilt_port/min_motor_id:
1 *
/dynamixel_manager/serial_ports/pan_tilt_port/port_name:
/dev/ttyAMA0 *
/dynamixel_manager/serial_ports/pan_tilt_port/update_rate:
20 * /rosdistro: indigo *
/rosversion: 1.11.15
NODES /
dynamixel_manager (dynamixel_controllers/controller_manager.py)
ROS_MASTER_URI=http://localhost:11311
core service [/rosout] found
process[dynamixel_manager-1]: started
[INFO] [WallTime: 1455271947.687416]
pan_tilt_port: Pinging motor IDs 1
through 25... [INFO] [WallTime:
1455271949.918483] pan_tilt_port: Found 1 motors - 1 AX-12 [1],
initialization complete. `
2) launch dynamixel tutorial tilt controller $ roslaunch dynamixel_tutorials start_tilt_controller.launch SUMMARY
========
PARAMETERS
* /rosdistro: indigo
* /rosversion: 1.11.15
* /tilt_controller/controller/module: joint_position_co...
* /tilt_controller/controller/package: dynamixel_control...
* /tilt_controller/controller/type: JointPositionCont...
* /tilt_controller/joint_name: tilt_joint
* /tilt_controller/joint_speed: 1.17
* /tilt_controller/motor/id: 1
* /tilt_controller/motor/init: 512
* /tilt_controller/motor/max: 1023
* /tilt_controller/motor/min: 0
NODES
/
tilt_controller_spawner (dynamixel_controllers/controller_spawner.py)
ROS_MASTER_URI=http://localhost:11311
core service [/rosout] found
process[tilt_controller_spawner-1]: started with pid [5975]
[INFO] [WallTime: 1455271966.834666] pan_tilt_port controller_spawner: waiting for controller_manager dxl_manager to startup in global namespace...
[INFO] [WallTime: 1455271966.877447] pan_tilt_port controller_spawner: All services are up, spawning controllers...
[INFO] [WallTime: 1455271967.194521] Controller tilt_controller successfully started.
[tilt_controller_spawner-1] process has finished cleanly
log file: /home/iñigo/.ros/log/e8ebc1f4-d0da-11e5-809d-b827eb5a7d39/tilt_controller_spawner-1*.log
all processes on machine have died, roslaunch will exit
shutting down processing monitor...
... shutting down processing monitor complete
done
The log error is not really valuable: [rosout][INFO] 2016-02-12 10:20:59,094: pan_tilt_port controller_spawner: All services are up, spawning controllers...
[rosout][ERROR] 2016-02-12 10:20:59,130: Controller [tilt_controller] already started. If you want to restart it, call restart.
[rospy.core][INFO] 2016-02-12 10:20:59,172: signal_shutdown [atexit]
[rospy.impl.masterslave][INFO] 2016-02-12 10:20:59,191: atexit
Is this normal??? Iñigo EDIT An exception is happening: SUMMARY
========
PARAMETERS
* /rosdistro: indigo
* /rosversion: 1.11.15
* /tilt_controller/controller/module: joint_position_co...
* /tilt_controller/controller/package: dynamixel_control...
* /tilt_controller/controller/type: JointPositionCont...
* /tilt_controller/joint_name: tilt_joint
* /tilt_controller/joint_speed: 1.17
* /tilt_controller/motor/id: 1
* /tilt_controller/motor/init: 512
* /tilt_controller/motor/max: 1023
* /tilt_controller/motor/min: 0
NODES
/
tilt_controller_spawner (dynamixel_controllers/controller_spawner.py)
ROS_MASTER_URI=http://localhost:11311
core service [/rosout] found
process[tilt_controller_spawner-1]: started with pid [3769]
[INFO] [WallTime: 1455286719.002746] pan_tilt_port controller_spawner: waiting for controller_manager dxl_manager to startup in global namespace...
[INFO] [WallTime: 1455286719.037128] pan_tilt_port controller_spawner: All services are up, spawning controllers...
[INFO] [WallTime: 1455286719.359311] Controller tilt_controller successfully started.
[tilt_controller_spawner-1] process has finished cleanly
log file: /home/erle/.ros/log/eeb18aa0-d18a-11e5-a4fa-b827eb5a7d39/tilt_controller_spawner-1*.log
all processes on machine have died, roslaunch will exit
shutting down processing monitor...
... shutting down processing monitor complete
done
Unhandled exception in thread started by
sys.excepthook is missing
lost sys.stderr
|
2016-02-10 16:18:53 -0500 | received badge | ● Famous Question
(source)
|
2015-10-29 10:48:22 -0500 | received badge | ● Famous Question
(source)
|
2015-05-26 21:54:14 -0500 | received badge | ● Notable Question
(source)
|
2015-05-09 11:02:58 -0500 | received badge | ● Popular Question
(source)
|
2015-05-07 02:51:47 -0500 | received badge | ● Enthusiast
|
2015-05-05 11:34:55 -0500 | asked a question | roslaunch failed, enviroment variable problem Hi all, I have downloaded and compiled some Ros nodes from here (just to have more info). I am trying to launch the five ROS nodes with parameters using a launch file that is taken from that repo. After executing source catkin_ws/devel_isolated/setup.bash and executing roslaunch crab.launch (the launch file from the link above) the next error appears: root@beaglebone:~# roslaunch crab.launch
... logging to /root/.ros/log/4f6332fe-dbe2-11e3-86a8-7ec70b079d59/roslaunch-beaglebone-2067.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://beaglebone:58881/
SUMMARY
========
PARAMETERS
* /clearance
* /duration_ripple
* /duration_tripod
* /joint_lower_limit
* /joint_upper_limit
* /port_name
* /robot_description
* /rosdistro
* /rosversion
* /trapezoid_h
* /trapezoid_high_radius
* /trapezoid_low_radius
NODES
/
crab_body_kinematics (crab_body_kinematics/body_kinematics)
crab_gait (crab_gait/gait_kinematics)
crab_imu (crab_imu/imu_control)
crab_leg_kinematics (crab_leg_kinematics/leg_ik_service)
crab_maestro_controller (crab_maestro_controller/controller_sub)
ROS_MASTER_URI=http://localhost:11311
core service [/rosout] found
ERROR: cannot launch node of type [crab_leg_kinematics/leg_ik_service]: can't locate node [leg_ik_service] in package [crab_leg_kinematics]
ERROR: cannot launch node of type [crab_maestro_controller/controller_sub]: can't locate node [controller_sub] in package [crab_maestro_controller]
ERROR: cannot launch node of type [crab_body_kinematics/body_kinematics]: can't locate node [body_kinematics] in package [crab_body_kinematics]
ERROR: cannot launch node of type [crab_gait/gait_kinematics]: can't locate node [gait_kinematics] in package [crab_gait]
ERROR: cannot launch node of type [crab_imu/imu_control]: can't locate node [imu_control] in package [crab_imu]
I have reinstalled the packages as suggested in some other threats about similar problems. I also have noticed that 1º- if I move all the executables of the nodes to the folder src/<package>/ , I'm able to execute roslaunch crab.launch . But I don´t want to leave it like that, not proper way to work ;) Additional info: 2º- If I execute, for example, source devel_isolated/<package>/setup.bash and then roslaunch crab.launch , the package which I have just source -d works and executes... (while the other still don't) 3º- So I have source -d all the source devel_isolated/<package>/setup.bash and try again: no one worked this time. This leads to think that the problems are due to ROS variable enviroment: if I make an export | grep ROS after 2º, I can see that the package path appears in $ROS_PATH -s and the others are not there: root@beaglebone:~# export | grep ROS
declare -x ROS_DISTRO="hydro"
declare -x ROS_ETC_DIR="/opt/ros/hydro/etc/ros"
declare -x ROS_MASTER_URI="http://localhost:11311"
declare -x ROS_PACKAGE_PATH="/root/catkin_ws/src/crab_msgs:/root/catkin_ws/src/joy:/root/catkin_ws
/src/ps3joy:/root/catkin_ws/src/xacro:/root/catkin_ws/src/roslint:/root/catkin_ws/src/kdl_parser:/root/catkin_ws
/src/urdf:/root/catkin_ws/src/urdf_parser_plugin:/root/catkin_ws/src:/opt/ros/hydro/share:/opt/ros/hydro
/stacks:/root/ros_catkin_ws/install_isolated/share:/root/ros_catkin_ws/install_isolated/stacks"
declare -x ROS_ROOT="/opt/ros/hydro/share/ros"
declare -x ROS_TEST_RESULTS_DIR="/root/catkin_ws/build_isolated/crab_msgs/test_results"
root@beaglebone:~# source catkin_ws/devel_isolated/crab_imu/setup.bash
declare -x ROS_PACKAGE_PATH="/root/catkin_ws/src/crab_imu:/root/catkin_ws/src/crab_msgs:/root/catkin_ws
/src/joy:/root/catkin_ws/src/ps3joy:/root/catkin_ws/src/xacro:/root/catkin_ws/src ... (more) |
2015-02-02 15:46:01 -0500 | received badge | ● Notable Question
(source)
|
2015-02-02 08:45:27 -0500 | commented answer | catkin is compiling c++ with python Yes, the main.elf is there! Thanks, but why is not appearing when I type rosrun ros_ubled and press tab key?? |
2015-02-02 08:44:36 -0500 | received badge | ● Supporter
(source)
|
2015-02-02 08:44:32 -0500 | received badge | ● Scholar
(source)
|
2015-02-02 05:33:36 -0500 | received badge | ● Popular Question
(source)
|
2015-02-02 04:55:24 -0500 | commented question | catkin is compiling c++ with python |
2015-02-02 03:50:52 -0500 | asked a question | catkin is compiling c++ with python Hi everyone, I'm a newbie in ROS, and after making the tutorials I'm trying to rosificate a C++ project that already is running in my BeagleBone Black. My problem is that, when I compile the code using catkin_make_isolated , my main.cpp is not being properly built up:in the compilation process, python is being used, instead of gcc compiler. This means that I cannot execute the node using rosrun <package> main even if I have done source devel/setup.bash witihin catkin_ws . This is the print out of the command line in the compilation process: -- Using PYTHON_EXECUTABLE: /usr/bin/python
-- Python version: 2.7
-- Using Debian Python package layout
-- Using CATKIN_ENABLE_TESTING: ON
-- Call enable_testing()
And this is how the CMakeLists.txt looks like: cmake_minimum_required(VERSION 2.8.3)
project(ros_erle_ubled)
find_package(catkin REQUIRED COMPONENTS
roscpp
)
catkin_package(
INCLUDE_DIRS include
LIBRARIES ros_erle_ubled
CATKIN_DEPENDS roscpp
)
include_directories(include)
include_directories(
${catkin_INCLUDE_DIRS}
)
add_executable(main src/GPIO_BBB.cpp src/DycoLEDDriver.cpp src/DycoLED_Linux.cpp src/main.cpp)
target_link_libraries(main ${catkin_LIBRARIES})
add_dependencies(main ros_erle_ubled_main_cpp)
I have also tried to force to use gcc compiler executing the next command (with little success): catkin_make_isolated -DCMAKE_CXX_COMPILER=/usr/bin/gcc --pkg ros_ubled Any idea how can I proceed?? Thanks in advance! Edit: console output of running catkin_make_isolated : root@beaglebone:~/ros_catkin_ws# catkin_make_isolated -DCMAKE_BUILD_TYPE=Debug -DCMAKE_CXX_COMPILER=/usr/bin/gcc-4.7 --pkg ros_ubled
Base path: /root/ros_catkin_ws
Source space: /root/ros_catkin_ws/src
Build space: /root/ros_catkin_ws/build_isolated
Devel space: /root/ros_catkin_ws/devel_isolated
Install space: /root/ros_catkin_ws/install_isolated
Additional CMake Arguments: -DCMAKE_BUILD_TYPE=Debug -DCMAKE_CXX_COMPILER=/usr/bin/gcc-4.7
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~ traversing 48 packages in topological order:
~~ - catkin
~~ - genmsg
~~ - gencpp
~~ - genlisp
~~ - genpy
~~ - console_bridge (plain cmake)
~~ - cpp_common
~~ - message_generation
~~ - message_runtime
~~ - mk
~~ - ros
~~ - ros_comm
~~ - rosbash
~~ - rosboost_cfg
~~ - rosbuild
~~ - rosclean
~~ - roscpp_traits
~~ - roscreate
~~ - rosgraph
~~ - roslang
~~ - rosmake
~~ - rosmaster
~~ - rosmsg
~~ - rospack
~~ - roslib
~~ - rosparam
~~ - rospy
~~ - rosservice
~~ - rostime
~~ - roscpp_serialization
~~ - rosbag_storage
~~ - roslaunch
~~ - rosunit
~~ - rosconsole
~~ - rostest
~~ - std_msgs
~~ - rosgraph_msgs
~~ - std_srvs
~~ - xmlrpcpp
~~ - roscpp
~~ - ros_ubled
~~ - rosout
~~ - message_filters
~~ - rosnode
~~ - rostopic
~~ - roswtf
~~ - topic_tools
~~ - rosbag
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Skipping package: 'catkin'
Skipping package: 'genmsg'
Skipping package: 'gencpp'
Skipping package: 'genlisp'
Skipping package: 'genpy'
Skipping package: 'console_bridge'
Skipping package: 'cpp_common'
Skipping package: 'message_generation'
Skipping package: 'message_runtime'
Skipping package: 'mk'
Skipping package: 'ros'
Skipping package: 'ros_comm'
Skipping package: 'rosbash'
Skipping package: 'rosboost_cfg'
Skipping package: 'rosbuild'
Skipping package: 'rosclean'
Skipping package: 'roscpp_traits'
Skipping package: 'roscreate'
Skipping package: 'rosgraph'
Skipping package: 'roslang'
Skipping package: 'rosmake'
Skipping package: 'rosmaster'
Skipping package: 'rosmsg'
Skipping package: 'rospack'
Skipping package: 'roslib'
Skipping package: 'rosparam'
Skipping package: 'rospy'
Skipping package: 'rosservice'
Skipping package: 'rostime'
Skipping package: 'roscpp_serialization'
Skipping package: 'rosbag_storage'
Skipping package: 'roslaunch'
Skipping package: 'rosunit'
Skipping package: 'rosconsole'
Skipping package: 'rostest'
Skipping package: 'std_msgs'
Skipping package: 'rosgraph_msgs'
Skipping package: 'std_srvs'
Skipping package: 'xmlrpcpp'
Skipping package: 'roscpp'
==> Processing catkin package: 'ros_ubled'
==> Building with env: '/root/ros_catkin_ws/devel_isolated/roscpp/env.sh'
Makefile exists, skipping explicit cmake invocation...
==> make cmake_check_build_system in '/root/ros_catkin_ws/build_isolated/ros_ubled'
-- Using CATKIN_DEVEL_PREFIX: /root/ros_catkin_ws/build_isolated/ros_ubled/devel
-- Using CMAKE_PREFIX_PATH: /root/ros_catkin_ws/devel_isolated/roscpp;/root/ros_catkin_ws/devel_isolated/xmlrpcpp;/root/ros_catkin_ws/devel_isolated/std_srvs;/root/ros_catkin_ws/devel_isolated/rosgraph_msgs;/root/ros_catkin_ws/devel_isolated/std_msgs;/root/ros_catkin_ws/devel_isolated/rostest;/root/ros_catkin_ws/devel_isolated/rosconsole;/root/ros_catkin_ws/devel_isolated/rosunit;/root/ros_catkin_ws/devel_isolated ... (more) |