Skip to content
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

Micro-ros-Agent and esp32 ( WSL2 setup ) #194

Open
JoelsonCRJ opened this issue Jun 6, 2023 · 1 comment
Open

Micro-ros-Agent and esp32 ( WSL2 setup ) #194

JoelsonCRJ opened this issue Jun 6, 2023 · 1 comment

Comments

@JoelsonCRJ
Copy link

Issue template

  • Hardware description: Dell Inspiron 15 (Ubuntu 20.04 wsl2)
  • RTOS: ESP32 Node MCU
  • Installation type: micro_ros_setup
  • Version or commit hash: foxy

Steps to reproduce the issue

  • Set the micro-ros credentials through the command "idf.py menuconfig";
  • Compile and flash the INT32_SUB_PUB example on esp32;

In the Ubuntu 20.04 wsl2 Host machine:

  • Windows 11 side:
  • Open the windows power shell as admin user and type: "netsh interface portproxy add v4tov4 listenport=8888 listenaddress=0.0.0.0 connectport=8888 connectaddress=<wsl2_ip_address>"
  • Go to the firewall and create a new inbound rule for port 8888 ;
  • Ubuntu 20.04 wsl2 side:

Expected behavior

I was expecting the same behavior when use a native linux machine: the esp32 finding the ros agent and publishing messages over ros2.

Actual behavior

Esp32 tries to connect to the ros agent but it is not finding it and eventually i get this message on the esp32 monitor: "Failed status on line 57: 1. Aborting".

Additional information

@Sebski123
Copy link

Currently netsh portproxy doesn't support UDP which is used for microROS agent communication.
This is an active issue in the WSL repo: microsoft/WSL#4150

My current workaround is to have the agent running in a separate Linux VM (VirtualBox) using a bridged network adapter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants