search

OpenPTrack / open_ptrack_v2

OPT v2 "Gnocchi" - adding object tracking and pose recognition
BSD 3-Clause "New" or "Revised" License
220 stars 65 forks source link

RLException: Unable to contact my own server #139

Open plbergeron opened 3 years ago

plbergeron commented 3 years ago

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:

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

jburkeucla commented 3 years ago

Can you run export to see whether the ros_network_env is properly updating the ROS_MASTER_URI ? You might need to set it manually if there is an issue with the environment variable?

From: plbergeron notifications@github.com Reply-To: OpenPTrack/open_ptrack_v2 reply@reply.github.com Date: Thursday, November 19, 2020 at 11:05 AM To: OpenPTrack/open_ptrack_v2 open_ptrack_v2@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: [OpenPTrack/open_ptrack_v2] RLException: Unable to contact my own server (#139)

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:

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

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/OpenPTrack/open_ptrack_v2/issues/139, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AADFGR2AYI65G6GBNORTY5LSQVT5TANCNFSM4T3ZUM6A.