-
Notifications
You must be signed in to change notification settings - Fork 67
Description
Hi!
We did some test with openptrack on a test rig of 2 imagers and a master and everything was working fine.
Then, we installed everything on the real pcs we are gonna use on our project and now when i try to start the calibration on our master i get this:
RLException: Unable to contact my own server at [http://192.168.100.101:46687/].
This usually means that the network is not configured properly.
A common cause is that the machine cannot ping itself. Please check
for errors by running:
ping 192.168.100.101
but the master's ip is 192.168.100.100:
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.100.100 netmask 255.255.255.0 broadcast 192.168.100.255
here's the content of my ros_network.env:
ROS_MASTER_URI=http://192.168.100.100:11311/
ROS_IP=192.168.100.100
ROS_PC_NAME=master
ROS_KINECT_NAME=kinect01
and my camera_network.yaml:
enable_people_tracking: true
enable_pose: true
enable_object: true
Camera network parameters
network:
- pc: "node1"
sensors:- type: zed
id: "node1"
people_detector: yolo
- type: zed
- pc: "node2"
sensors:- type: zed
id: "node2"
people_detector: yolo
- type: zed
- pc: "node3"
sensors:- type: zed
id: "node3"
people_detector: yolo
- type: zed
- pc: "node4"
sensors:- type: zed
id: "node4"
people_detector: yolo
- type: zed
- pc: "node5"
sensors:- type: zed
id: "node5"
people_detector: yolo
- type: zed
- pc: "node6"
sensors:- type: zed
id: "node6"
people_detector: yolo
- type: zed
Checkerboard parameters
checkerboard:
rows: 9
cols: 7
cell_width: 0.025
cell_height: 0.025
Maybe i'm missing a file i need to change for ros to see the right address.
Thanks