Connecting to UR3 with WSL causes compile error: "null" not defined #689
Description
Affected ROS Driver version(s)
latest from github
Used ROS distribution.
Noetic
Which combination of platform is the ROS driver running on.
Windows using WSL2
How is the UR ROS Driver installed.
Build both the ROS driver and UR Client Library from source
Which robot platform is the driver connected to.
UR CB3 robot
Robot SW / URSim version(s)
3.15
How is the ROS driver used.
Through the robot teach pendant using External Control URCap
Issue details
Summary
i am trying to control the UR3 robot using WSL however i keep getting issues when running the external control program getting connection to remote PC at 192.168.1.102:50002 could not be established. Reason connection timed out. i followed the solution #486 adding portforwarding and turning the firewall off. however i get a new issue Compile error name "null" is not defined. this error seems to appear when i add my windows IP as the reverse_ip:=192.168.1.102 when loading the driver.
Issue details
i have done portforwarding:
netsh interface portproxy add v4tov4 listenport=50002 connectport=50002 connectaddress=172.17.96.1
netsh interface portproxy add v4tov4 listenport=50001 connectport=50001 connectaddress=172.17.96.1
netsh interface portproxy add v4tov4 listenport=50003 connectport=50003 connectaddress=172.17.96.1
set my external control ip and port to 192.168.1.102 50002
i run the driver: roslaunch ur_robot_driver ur3_bringup.launch robot_ip:=192.168.1.101 reverse_ip:=192.168.1.102
i can see the robot in rvis and track how it moves. however when i try to run the extrenal control program (external control urcap in the program tree) i get the error mentioned.
when i dont pass the reverse_ip argument into the driver i get the error connection to the remote pc at ip:port could not be established. reason: connection timed out.
what do i need to do in order to control my robot through WSL?
could headless mode work better if i keep getting errors with the external control URCap?
Relevant log output
No response
Accept Public visibility
- I agree to make this context public