You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm just following the steps linked here, which for micro_ros_agent come up to:
# Source the ROS 2 installationsource /opt/ros/$ROS_DISTRO/setup.bash
# Create a workspace and download the micro-ROS tools
mkdir microros_ws
cd microros_ws
git clone -b $ROS_DISTRO https://github.com/micro-ROS/micro_ros_setup.git src/micro_ros_setup
# Update dependencies using rosdep
sudo apt update && rosdep update
rosdep install --from-paths src --ignore-src -y
# Install pip
sudo apt-get install python3-pip
# Build micro-ROS tools and source them
colcon build
source install/local_setup.bash
# Download micro-ROS-Agent packages
ros2 run micro_ros_setup create_agent_ws.sh
# Build step
ros2 run micro_ros_setup build_agent.sh
source install/local_setup.bash
# Run agent with UDP method
ros2 run micro_ros_agent micro_ros_agent udp4 -p 2019 -r dds_xrce_profile.xml
# OR# Run agent with Serial method (actual /dev/pts/x comes from `socat -d -d pty,raw,echo=0 pty,raw,echo=0`
ros2 run micro_ros_agent micro_ros_agent serial -b 115200 -r dds_xrce_profile.xml -D /dev/pts/2
Expected behavior
I should be able to see nodes with ros2 node list, and then inspect and interact with them.
Actual behavior
I get a deserialization error, constantly. No nodes are listed at all when using ros2 node list.
If useful, output from socat:
slim71@slim71-Ubuntu:~/Documents/git/ardupilot/libraries/AP_DDS$ socat -d -d pty,raw,echo=0 pty,raw,echo=0
2023/06/02 11:08:01 socat[12853] N PTY is /dev/pts/3
2023/06/02 11:08:01 socat[12853] N PTY is /dev/pts/4
2023/06/02 11:08:01 socat[12853] N starting data transfer loop with FDs [5,5] and [7,7]
I'm using micro_ros_agent together with Ardupilot in order to run some simulations. The ultimate goal is to be able to interact with nodes and topics in ROS2, since I'll have to build my project from that (with Ignition Gazebo).
The text was updated successfully, but these errors were encountered:
I haven't changed anything code-wise, I was just using the simple snippets mentioned right after installing everything
it did happen with both UDP and Serial modes
I've actually managed to understand the core issue some hours ago. It was due to the ROS_DOMAIN_ID, which I had set before (through .bashrc). What helped me figure it out was this issue, which I hadn't seen before.
I wish I did, since it was so simple... 😓
Issue template
Steps to reproduce the issue
I'm just following the steps linked here, which for micro_ros_agent come up to:
Expected behavior
I should be able to see nodes with
ros2 node list
, and then inspect and interact with them.Actual behavior
I get a deserialization error, constantly. No nodes are listed at all when using
ros2 node list
.If useful, output from socat:
slim71@slim71-Ubuntu:~/Documents/git/ardupilot/libraries/AP_DDS$ socat -d -d pty,raw,echo=0 pty,raw,echo=0 2023/06/02 11:08:01 socat[12853] N PTY is /dev/pts/3 2023/06/02 11:08:01 socat[12853] N PTY is /dev/pts/4 2023/06/02 11:08:01 socat[12853] N starting data transfer loop with FDs [5,5] and [7,7]
Output from the micro_ros_agent:
Additional information
I'm using micro_ros_agent together with Ardupilot in order to run some simulations. The ultimate goal is to be able to interact with nodes and topics in ROS2, since I'll have to build my project from that (with Ignition Gazebo).
The text was updated successfully, but these errors were encountered: