moving diagnostic updater for other robot

k-okada commented 9 years ago

I'd like to use diagnostic updater for pepper robot ,could you move/copy this to naoqi_bridge or pepper_robot repository? Or if you tell me the direction, I can create pull request.

https://github.com/ros-naoqi/nao_robot/blob/master/nao_apps/nodes/nao_diagnostic_updater.py

vrabaud commented 9 years ago

right now, we have one in the C++ bridge (that you can dl as the ros-indigo-naoqi-rosbridge package) and this Python one should simply be removed. I guess we will not move it: let's simply move the C++ bridge in naoqi_bridge and we'll have everything we need this way.

k-okada commented 9 years ago

Thanks, I tried but have segfaults, what's wrong with this?

+ /opt/ros/indigo/lib/naoqi_rosbridge/alrosbridge_bin --qi-url 133.11.216.224 133.11.216.64
going to add: /opt/ros/indigo
[W] 3513 qi.path.sdklayout: No Application was created, trying to deduce paths
[I] 3513 qimessaging.session: Session listener created on tcp://0.0.0.0:0
[I] 3513 qimessaging.transportserver: TransportServer will listen on: tcp://172.17.42.1:35074
[I] 3513 qimessaging.transportserver: TransportServer will listen on: tcp://127.0.0.1:35074
[I] 3513 qimessaging.transportserver: TransportServer will listen on: tcp://133.11.216.64:35074
[I] 3513 qimessaging.transportserver: TransportServer will listen on: tcp://192.168.206.1:35074
[I] 3513 qimessaging.transportserver: TransportServer will listen on: tcp://172.16.117.1:35074
[I] 3513 qimessaging.transportserver: TransportServer will listen on: tcp://133.11.216.158:35074
using ip address: 133.11.216.64
found a catkin prefix /opt/ros/indigo/share/naoqi_rosbridge/share/boot_config.json
load boot config from /opt/ros/indigo/share/naoqi_rosbridge/share/boot_config.json
found robot variable juliette
[W] 3516 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3515 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3514 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3516 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3516 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3517 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3517 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3514 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3517 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
no camera information found for camera_source 3 and res: 0
found robot variable juliette
[W] 3516 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3514 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
found a catkin URDF /opt/ros/indigo/share/naoqi_rosbridge/share/urdf/pepper_robot.urdf
[W] 3515 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3514 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3514 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
found robot variable juliette
[W] 3517 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3515 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3516 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3517 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3516 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3516 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3515 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
[W] 3517 qitype.signal: Exception caught from signal subscriber: Call argument number 0 conversion failure from LogMessage to LogMessage. Function signature: (LogMessage).
Audio Extractor: Start
registered subscriber:  teleop
registered subscriber:  moveto
nodehandle reset

Karsten1987 commented 9 years ago

You may pass a wrong formatted qi-url argument (tcp:// and port :9559 are missing) Sorry for the inconvenience, I've seen it's not correctly documented. Will fix that asap.

could you please re-run with this command: /opt/ros/indigo/lib/naoqi_rosbridge/alrosbridge_bin --qi-url=tcp://133.11.216.224:9559 133.11.216.64

k-okada commented 9 years ago

thanks, finally I can start alrosbridge_bin program and see following topics BTW, what is the goal of alrosbridge? replace all python ros drivers? if so should we rename alrosbridge prefix for backward compatibility of pepper_robot package and fix https://github.com/ros-naoqi/pepper_robot/blob/master/pepper_bringup/launch/pepper.launch t ouse alrosbridge?

$ rostopic  list
/alrosbridge/audio
/alrosbridge/camera/depth/camera_info
/alrosbridge/camera/depth/image_raw
/alrosbridge/camera/depth/image_raw/compressed
/alrosbridge/camera/depth/image_raw/compressed/parameter_descriptions
/alrosbridge/camera/depth/image_raw/compressed/parameter_updates
/alrosbridge/camera/front/camera_info
/alrosbridge/camera/front/image_raw
/alrosbridge/camera/front/image_raw/compressed
/alrosbridge/camera/front/image_raw/compressed/parameter_descriptions
/alrosbridge/camera/front/image_raw/compressed/parameter_updates
/alrosbridge/camera/ir/camera_info
/alrosbridge/camera/ir/image_raw
/alrosbridge/camera/ir/image_raw/compressed
/alrosbridge/camera/ir/image_raw/compressed/parameter_descriptions
/alrosbridge/camera/ir/image_raw/compressed/parameter_updates
/alrosbridge/imu_base
/alrosbridge/imu_torso
/alrosbridge/info
/alrosbridge/laser
/alrosbridge/sonar/back
/alrosbridge/sonar/front
/cmd_vel
/diagnostics_agg
/joint_states
/move_base_simple/goal
/rosout
/rosout_agg
/tf

vrabaud commented 8 years ago

I guess all that is obsolete now that the naoqi_driver is much more stable.

nlyubova commented 8 years ago

@k-okada did you fix the exception message ? I get the same message when launching naoqi_driver ...

warp1337 commented 7 years ago

Bump. The same with NaoQI 2.5.3 on the robot and ros-kinetic-naoqi-driver (0.5.9-0xenial-20170315-0 amd64)

ros-naoqi / nao_robot

moving diagnostic updater for other robot #21