Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hironx_ros_bridge_simulation.launch often fails on melodic #538

Closed
pazeshun opened this issue Apr 6, 2020 · 2 comments
Closed

hironx_ros_bridge_simulation.launch often fails on melodic #538

pazeshun opened this issue Apr 6, 2020 · 2 comments

Comments

@pazeshun
Copy link
Contributor

pazeshun commented Apr 6, 2020

I'm trying to use this repository on melodic.
As some dependencies are not released to melodic (see start-jsk/rtmros_common#1090), I created this rosinstall file, constructed a workspace, and ran catkin build.
This build succeeded, so I tried rtmlaunch hironx_ros_bridge hironx_ros_bridge_simulation.launch several times.
However, those trials often failed.
Some nodes such as hrpsys died and restarted, but couldn't reach to [HrpsysSeqStateROSBridge0] @onExecutece 0 is working at ~[Hz]
Log of a successful trial
Log of a failed trial
I couldn't understand why the following error message came up:

[rtmlaunch] Could not start rtmlaunch.py, Caught exception ([rtmlaunch] Could not start rtmlaunch.py, Caught exception ( CORBA.COMM_FAILURE(omniORB.COMM_FAILURE_WaitingForReply, CORBA.COMPLETED_MAYBE)  )
CORBA.COMM_FAILURE(omniORB.COMM_FAILURE_WaitingForReply, CORBA.COMPLETED_MAYBE) )
[rtmlaunch] .. Could not connect to NameServer at  localhost:15005 , Caught exception ( [rtmlaunch] .. Could not connect to NameServer at CORBA.COMM_FAILURE(omniORB.COMM_FAILURE_WaitingForReply, CORBA.COMPLETED_MAYBE) )
 localhost:15005 , Caught exception ( CORBA.COMM_FAILURE(omniORB.COMM_FAILURE_WaitingForReply, CORBA.COMPLETED_MAYBE) )
[rtmlaunch] .. Please make sure that you have NameServer running at localhost:15005/`
[rtmlaunch] .. You can check with `rtls localhost:15005/`
[rtmlaunch] .. Please make sure that you have NameServer running at localhost:15005/`
[rtmlaunch] .. You can check with `rtls localhost:15005/`
@pazeshun
Copy link
Contributor Author

pazeshun commented Apr 6, 2020

I made the following change to rtmros_common to increase rtc log:

pazeshun@46405e9dcc2a:~/ros/jsk_demo_ws/src/rtm-ros-robotics/rtmros_common$ git diff
diff --git a/hrpsys_tools/launch/hrpsys.launch b/hrpsys_tools/l
aunch/hrpsys.launch
index bda5a38c..17ff84c5 100644
--- a/hrpsys_tools/launch/hrpsys.launch
+++ b/hrpsys_tools/launch/hrpsys.launch
@@ -80,6 +80,7 @@
     '/>
   <arg name="hrpsys_opt_rtc_config_args" default=''/>
   <arg name="hrpsys_args" default='
+-o "logger.log_level:PARANOID"
 -o "exec_cxt.periodic.rate:$(arg hrpsys_periodic_rate)"
 -o "manager.shutdown_onrtcs:NO"
 -o "manager.modules.load_path:$(arg hrpsys_load_path)"
@@ -89,6 +90,7 @@
  $(arg hrpsys_rtc_config_args) $(arg hrpsys_opt_rtc_config_args)

 ' unless="$(arg USE_CHOREONOID)" />
   <arg name="hrpsys_args" default='
+-o "logger.log_level:PARANOID"
 -o "manager.shutdown_onrtcs:NO"
 -o "manager.modules.load_path:$(arg hrpsys_load_path)"
 -o "manager.modules.preload:$(arg hrpsys_preload_rtc)"

And got the following log:
https://gist.githubusercontent.com/pazeshun/2bea0aed2b0e0e6570b6f46314888bc0/raw/5f0d843586fdd014cef5d33ccb07b119c9bf62bd/rtc_logs_failure_hironx_ros_bridge_simulation

@pazeshun
Copy link
Contributor Author

This issue seems fixed because tork-a/openrtm_aist-release@ec065c9 is released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant