-
This QA applies to the following cases:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
There are two typical causes:
Consider the following example: On a robot, the control pc (e.g. pc104) has one internal board (ip: 10.0.1.104) and one external board (ip: 192.168.100.10). The board with 10.0.1.104 is intended to communicate with the robot internal boards. The yarp server, instead, has to be configured to run on the external board with ip address 192.168.100.10. This is accomplished using the command: Moreover: If you start yarp server and it fails to launch, displaying a message similar to:
you are warned that you are not using the usual configuration and there exists the possibility that you are doing something wrong (e.g. requesting to run yarp server on the wrong ethernet board 10.0.1.104). Yarp server will seem to run correctly both if you execute it with --write and --read option so read carefully the ip addresses of the two interfaces displayed in the message and choose the right one, otherwise other machines of cluster will be not able to receive data through yarp ports. In this specific example use command |
Beta Was this translation helpful? Give feedback.
There are two typical causes:
Consider the following example:
On a robot, the control pc (e.g. pc104) has one internal board (ip: 10.0.1.104) and one external board (ip: 192.168.100.10). The board with 10.0.1.104 is intended to communicate with the robot internal boards. The yarp server, instead, has to be configured to run on the external board with ip a…