ROS1 vs ROS2 Comprehensive Comparison (2)

-

Introspection Commands Comparison

Task ROS1 Command ROS2 Command Notes
Node Introspection
List all nodes rosnode list ros2 node list The functionality is similar, but in ROS2 all command line tools use the ros2 prefix
Get node information rosnode info /node_name ros2 node info /node_name Shows publishers, subscribers, services, and actions associated with the node
Ping a node rosnode ping /node_name ros2 node ping /node_name Test connectivity to a specific node
Kill a node rosnode kill /node_name Not directly available In ROS2, you typically use Ctrl+C or task/process management
Run a node rosrun package_name node_name ros2 run package_name node_name The core functionality is the same
Topic Introspection
List all topics rostopic list ros2 topic list Lists all active topics
List topics with types rostopic list -v ros2 topic list -t In ROS2, the -t flag is used for showing types
Show topic information rostopic info /topic_name ros2 topic info /topic_name Shows publishers and subscribers of a topic
Echo (display) topic messages rostopic echo /topic_name ros2 topic echo /topic_name Displays message content in real-time
Show message type rostopic type /topic_name ros2 topic type /topic_name Shows the message type used by a topic
Publish to topic rostopic pub /topic_name msg_type "data" ros2 topic pub /topic_name msg_type "data" In ROS2, message types include the msg/ namespace (e.g., std_msgs/msg/String)
Show topic publishing rate rostopic hz /topic_name ros2 topic hz /topic_name Shows how frequently messages are published
Show topic bandwidth rostopic bw /topic_name ros2 topic bw /topic_name Shows bandwidth used by the topic
Find topics by type rostopic find msg_type ros2 topic find msg_type Find all topics of a specific message type
Service Introspection
List all services rosservice list ros2 service list Lists all available services
Show service type rosservice type /service_name ros2 service type /service_name Shows the service type
Call a service rosservice call /service_name [args] ros2 service call /service_name srv_type [args] In ROS2, you must specify the service type explicitly
Show service arguments rosservice args /service_name Use ros2 interface show srv_type In ROS2, you check the service interface definition instead
Find services by type rosservice find srv_type ros2 service find srv_type Find all services of a specific type
Monitor service calls Not directly available ros2 service echo /service_name ROS2 introduced service call monitoring
Interface Introspection
Show message definition rosmsg show msg_type ros2 interface show msg_type ROS2 unified msg, srv, and action introspection under "interface"
Show service definition rossrv show srv_type ros2 interface show srv_type Same command for all interface types in ROS2
List message types rosmsg list ros2 interface list Use with --only-msgs flag in ROS2 to filter
List service types rossrv list ros2 interface list Use with --only-srvs flag in ROS2 to filter
Parameter Introspection
List parameters rosparam list ros2 param list In ROS2, parameters are node-specific
Get parameter value rosparam get parameter_name ros2 param get /node_name parameter_name ROS2 requires specifying the node name
Set parameter value rosparam set parameter_name value ros2 param set /node_name parameter_name value Node name is required in ROS2
Load parameters from file rosparam load file.yaml ros2 param load /node_name file.yaml Node-specific in ROS2
Dump parameters to file rosparam dump file.yaml ros2 param dump /node_name file.yaml Node-specific in ROS2
Action Introspection (ROS2 Only)
List actions Not available (used actionlib) ros2 action list Actions are a first-class citizen in ROS2
Show action info Not available ros2 action info /action_name Shows action servers and clients
Send action goal Not available (required code) ros2 action send_goal /action_name action_type goal Command line interface for actions
Launch
Launch multiple nodes roslaunch package_name file.launch ros2 launch package_name file.launch.py ROS2 supports Python, XML, and YAML launch files

Key Differences in Introspection Commands

Feature ROS1 ROS2
Command Structure Individual tools (rostopic, rosnode, etc.) Unified ros2 prefix with subcommands
Message/Service Inspection Separate rosmsg and rossrv commands Unified ros2 interface command
Parameter Handling Global parameter server Node-specific parameters
Action Support Through actionlib package, no CLI tools First-class citizen with CLI tools
Service Call Monitoring Not available Available with ros2 service echo
Service Type in Call Not required Must specify service type
Command Arguments Simple More structured with --ros-args approach

留言

張貼留言

這個網誌中的熱門文章

Useful PX4 Parameters

-
1. For setting companion link SYS_COMPANION (Before ver. 1.9.0) MAV_0_CONFIG, MAV_0_MODE (After ver. 1.9.0) 2. EKF2 configuration EKF2_AID_MASK EKF2_HGT_MODE EKF2_EV_DELAY (Reduce this parameter if high rate external vision is available) EKF2_EV_POS_X, EKF2_EV_POS_Y, EKF2_EV_POS_Z 3. Offboard mode parameters ( The vehicle will exit the mode if target setpoints are not received at a rate of > 2Hz ) COM_OBL_RC_ACT (Default: position mode, I set land mode) COM_OBL_ACT COM_OF_LOSS_T 4. Position loss failsafe COM_POSCTL_NAVL 5. Land mode MPC_LAND_SPEED COM_DISARM_LAND: Time-out for auto disarm after landing. (Default: 0, I set 3.) 6. TBD Reference: [1]  https://dev.px4.io/en/advanced/parameter_reference.html [2]  https://dev.px4.io/en/ros/external_position_estimation.html#tuning-EKF2_EV_DELAY [3]  https://docs.px4.io/en/config/safety.html#qgc_safety_setup
閱讀完整內容

Tuing PID parameters in QGroundcontrol (2)

-
圖片
Based on tips for tuning PX4 PID parameters written in my previous post [1] or even using the default values directly, you will be able to fly your vehicle freely in manual or stabilized flight mode.   However, if you are using an unique vehicle (usually assembly by yourself and only equipped with sensors you desire) and struggling for finding the best PID parameters for your applications. I think following 8 tips will help you to get ideal PID parameters.  This is the vehicle I made based on LHI QAV250 fiber frame, with TX2, high-speed camera, etc.[2]  Tip1:  Tuning order: Rate controller -> attitude controller -> position controller The PX4 controllers are layered [3], which means a higher-level controller passes its results to a lower-level controller. Thus the PID tuning needs to be done from lowest-level controller to highest-level controller. Tip2:  Check if  PWM_MIN  is set correctly. Remove propellers Arm the vehic...
閱讀完整內容

Matlab Pixhawk Support Package installation (Windows)

-
圖片
1. Download the pixhawk support package [1] 2. Open MATLAB R2017b and navigate to the file location. 3. Click "PX4PSP_v3_0_4_351_R2017b" and install it 4. Create a folder for firmware download path (ex: D/PX4) 5. Setting bash environment for windows 10 [2]  (1) Active "Windows subsystem for linux" (2) Download and install Ubuntu (3) Using the terminal like in Ubuntu environment ex: 6. Install all necessary toolchain with " windows_bash_nuttx.sh " [3] or using Cygwin Toolchian [4] or [5] (python27 would show in following folder) 7. Key in command " PixhawkPSP(' D:\PX4 ') " in the Matlab 8. Make sure windows 10 bash and python path are correct => Validate paths 9. Download firmware to the folder we specify before and then validate firmware. 10. Selecting cmake configuration [6] 11. Build firmware *Error: make command not found   Solution: [7] T...
閱讀完整內容