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 doing some research on navigation solutions for pepper robot and because of the current situation I'm not able to work on a real robot so I'm using gazebo simulator. I was trying to use exploration and mapping script that uses python-sdk but to run that script an ip address of a robot is required. I tried using ip address of my laptop and 127.0.0.1 but I get an error that it cannot connect to that address. I also tried to change the port from 9559 to gazebo master port but it didn't help. So my question is there any way to connect to virtual robot via ip address and if yes how can I find that ip address?
Thanks
The text was updated successfully, but these errors were encountered:
I am in a similar position. I think that the python-api for Pepper will not work with the Gazebo simulation because it would, I think, require the naoqi-os to run somewhere in the backend and I doubt that this is the case for the simulated model in gazebo. Please correct me if this is wrong...
It's really unfortunate, we couldn't use our Pepper's for almost a year now, because there is no simulation that goes beyond the most simple commands, like gestures or voice messages...
Hi,
I'm doing some research on navigation solutions for pepper robot and because of the current situation I'm not able to work on a real robot so I'm using gazebo simulator. I was trying to use exploration and mapping script that uses python-sdk but to run that script an ip address of a robot is required. I tried using ip address of my laptop and 127.0.0.1 but I get an error that it cannot connect to that address. I also tried to change the port from 9559 to gazebo master port but it didn't help. So my question is there any way to connect to virtual robot via ip address and if yes how can I find that ip address?
Thanks
The text was updated successfully, but these errors were encountered: