Revision history [back]

Defective Comments only allow a few characters so I had to make my long-winded response to Benny Re and rtoris an answer. BennyRe gets 2 points for thinking outside the box. However, GC in JS probably doesn't change much and presumably the implementors of ROSlibjs got it working at least at some point. However, rtoris288 has a provocative clue. rostopic echo /cmd/result prints out nothing, it just hangs until I control to get the prompt back. More clues: rostopic list prints out: MacBook-Pro-2:ros_ws Fry$ rostopic list /cmd/cancel /cmd/feedback /cmd/goal /cmd/result /cmd/status /rosout /rosout_agg

The arguments to rostopic echo that give me no printout and just hang are: /cmd/cancel, /cmd/feedback, /cmd/goal, /cmd/result, /rosout_agg The ones that give me information are: /cmd/status Lots of iterations of : header: seq: 4853 stamp: secs: 1447793529 nsecs: 985096000 frame_id: '' status_list: - goal_id: stamp: secs: 1447792658 nsecs: 138962000 id: goal_0.9185599682386965_1447792657624 status: 3 text: ''

/rosout : header: seq: 1 stamp: secs: 1447792665 nsecs: 142908000 frame_id: '' level: 2 name: /cmd msg: cmd: Succeeded file: /Users/Fry/ros_ws/src/cpp_action_server_pkg/src/cmd_server.cpp function: executeCB line: 65

topics: ['/rosout', '/cmd/result', '/cmd/feedback', '/cmd/status']

header: seq: 2 stamp: secs: 1447792579 nsecs: 366230010 frame_id: '' level: 2 name: /rosapi msg: Rosapi started file: rosapi_node function: <module> line: 175

topics: ['/rosout']

header: seq: 7 stamp: secs: 1447793337 nsecs: 16545057 frame_id: '' level: 4 name: /rosbridge_websocket msg: Inbound TCP/IP connection failed: connection from sender terminated before handshake header received. 0 bytes were received. Please check sender for additional details. file: tcpros_base.py function: _tcp_server_callback line: 351 topics: ['/cmd/result', '/rosout', '/cmd/goal', '/cmd/status', '/cmd/feedback', '/cmd/cancel']

So it looks like there is at least one problem that doesn't have to do with the browser.

PS: ^CMacBook-Pro-2:ros_ws Fry$ printenv | grep ROS ROS_ROOT=/opt/ros/indigo/share/ros ROS_PACKAGE_PATH=/Users/Fry/ros_ws/src:/opt/ros/indigo/share:/opt/ros/indigo/stacks ROS_MASTER_URI=http://localhost:11311 ROSLISP_PACKAGE_DIRECTORIES=/Users/Fry/ros_ws/devel/share/common-lisp ROS_DISTRO=indigo ROS_ETC_DIR=/opt/ros/indigo/etc/ros

This is not an answer but more of a thickening of the plot :-(

Defective Comments only allow a few characters so I had to make my long-winded response to Benny Re and rtoris an answer. BennyRe gets 2 points for thinking outside the box. However, GC in JS probably doesn't change much and presumably the implementors of ROSlibjs got it working at least at some point. However, rtoris288 has a provocative clue. rostopic echo /cmd/result prints out nothing, it just hangs until I control to get the prompt back. More clues: rostopic list prints out: out:

MacBook-Pro-2:ros_ws Fry$ rostopic list
/cmd/cancel
/cmd/feedback
/cmd/goal
/cmd/result
/cmd/status
/rosout
/rosout_agg
/rosout_agg

The arguments to rostopic echo that give me no printout and just hang are: /cmd/cancel, /cmd/feedback, /cmd/goal, /cmd/result, /rosout_agg The ones that give me information are: /cmd/status are:

/cmd/status

Lots of iterations of : header: seq: 4853 stamp: secs: 1447793529 nsecs: 985096000 frame_id: '' status_list: - goal_id: stamp: secs: 1447792658 nsecs: 138962000 id: goal_0.9185599682386965_1447792657624 status: 3 text: ''