Ask Your Question
1

Rosbridge: Could not process inbound connection

asked 2016-04-12 01:50:04 -0500

djsw gravatar image

updated 2019-10-12 01:22:09 -0500

130s gravatar image

I'm trying to implement a web server to initiate a trigger to ROS, but the way I've done it (consistent with the tutorials) seems to be causing a lot of info and warning messages. I have a button that reloads the page and sets ?button=true in the URL, and if the variable is set, the page publishes a message.

The problem is that every time it evaluates to true, the connection has to be made again, causing a delay of around 2 seconds. If I include the connection information outside of the statement evaluation, I get a series of warning messages and the messages will cease to publish when I expect them to. Am I going about this the right way?

The messages upon reloading the page are expected, since the page would be disconnecting and reconnecting to the rosbridge socket:

[INFO] [WallTime: 1460502279.235987] Client disconnected. 0 clients total.
[INFO] [WallTime: 1460502279.307687] Client connected.  1 clients total.

And the warning I receive when reloading the page but not publishing a messge:

[WARN] [WallTime: 1460502367.962932] Could not process inbound connection: [/rosbridge_websocket] is not a publisher of [/webtrig]. Topics are [['/rosout', 'rosgraph_msgs/Log']]{'message_definition': '\n', 'callerid': '/master', 'tcp_nodelay': '0', 'md5sum': 'd41d8cd98f00b204e9800998ecf8427e', 'topic': '/webtrig', 'type': 'std_msgs/Empty'}

This warning will be repeated about five times.

edit retag flag offensive close merge delete

Comments

It might be helpful to include the "warning messages" that you get.

gvdhoorn gravatar imagegvdhoorn ( 2016-04-12 02:46:50 -0500 )edit

I've edited the question to include them.

djsw gravatar imagedjsw ( 2016-04-12 18:07:32 -0500 )edit

1 Answer

Sort by » oldest newest most voted
0

answered 2019-10-12 01:21:06 -0500

130s gravatar image

updated 2019-10-12 01:21:41 -0500

Although the timestamp of this thread opened is older than my following suggestion, I still post this as this has not been answered for 3 years anyway.

rosbridge_suite#138 (omment) suggests that a quick hack that can be made within rosbridge_library code. My team recently hit an issue with the same error message and this hack solved (our fork fyi and PR).

The same ticket suggests that the "solution" can be made in rospy, which is already tracked ros_comm#111.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2016-04-12 01:50:04 -0500

Seen: 418 times

Last updated: Oct 12