You can run a player server on both the client robot and the server
robot on the same port. What needs to be different is specifying the
address of the robot to connect to when you run your client programs and
playerv. So, for example, if I run a server on one robot, I would then
connect to it from the other robot using the first robot's address.
Otherwise, it will attempt to connect to the default address, which is
127.0.0.1, in other words, the robot the client is running on.
R C wrote:
> Can someone please help with the problem working with
> actual hardware communitcation. I have two robots. One
> being a server and the other being a client. I must
> use diffrent ports while they are communicating. As I
> run the executable file for the server robot (which is
> a simple collision avoidance) it performs its task.
> This server robot runs on default port 6665. On a
> completely separate computer and robot is the client
> executable (which is to follow the server robot in a
> formation). This client robot is assigned to port
> 6666. As I try to establish communication with the
> server robot from the client robot the following error
> pops up ON SERVER ROBOT:
> accepted client 1 on port 6665, fd 8
> warning : other error on client 1
> closing connection to client 1 on port 6665
> Client 1 should be accepted on port 6666. Vise versa
> with the CLIENT ROBOT, it displays a similar error
> message at the same instant:
> accepted client 1 on port 6666, fd 8
> closing connection to client 1 on port 6666
> On this machine, the server robot should be accepted
> on port 6665.
> Should there be any changes to the configuration files
> to achieve this task? The configuration file for both
> are shown below. They are the same. The server robot
> runs off the default ports(6665) so I don't need to
> specify ports used. The executable commands for SERVER
> ROBOT are:
> player pioneer3_2.cfg
> playerv --position2d:0 --sonar:0 --power:0
> The CLIENT ROBOT the executables are assigned ports:
> player -p 6666 pioneer3_2.cfg
> playerv -p 6666 --position2d:0 --sonar:0 --power:0
> ./minion 6666
> Configuration file for both robots:
> name "p2os"
> provides ["odometry:::position2d:0"
> port "/dev/ttyUSB0"
> Looking at the executable commands and configuration
> file, what changes should be made for the robots to
> accept each other on different ports. Thank You.
> Never miss an email again!
> Yahoo! Toolbar alerts you the instant new Mail arrives.
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> Playerstage-users mailing list
Robotics research group, University of Auckland