Replies: 2 comments 3 replies
-
You are likely using a NAT-ed connection in your VM. The driver attempts to connect to several ports opened by the VC, but if they are not forwarded, it will not be able to do so. The fact the "ports are listening" does not change this. This is identical to how you cannot reach arbitrary ports behind a "nat router". Either configure the VM network to forward those ports, or change the VM to a bridged or host-only network. |
Beta Was this translation helpful? Give feedback.
-
Oh and off-topic perhaps, but please be aware that performance in a VM is going to be very sub-optimal. VBox is not known for its performance, and while the driver does not have any UI, scheduling inside your VM is going to influence the behaviour of the driver (and any controllers you load) significantly. If possible, reverse your setup (ie: native Linux, Windows-in-VM). |
Beta Was this translation helpful? Give feedback.
-
I can't seem to connect the virtual controller to ros launch rws....does anyone have any ideas?
The port for the virtual controller is listening and it is the same as the one set on the Ubuntu vm roslaunch but its still not working.
IP is set correctly as well as white listed
Beta Was this translation helpful? Give feedback.
All reactions