Closed k-okada closed 10 years ago
From kei.ok...@gmail.com on December 29, 2013 19:05:04
From following log message, it seems rtcd is not started correctly, check rtls command or/and output of rtcd program
[hrpsys.py] Could not find RobotHardware0 [hrpsys.py] Candidates are .... []
From gm130s on December 29, 2013 19:10:44
This is using OpenHRP3 3.1.5, hrpsys 315.1.5, both built from source.
And just now, this error stops occurring after I revert back OpenHRP3 to 3.1.4 and hrpsys 315.0.0 on the robot's QNX. I might have missed something while building either/both of them.
From kei.ok...@gmail.com on December 29, 2013 19:31:11
hrpsys 315.0.0 Is this correct?
From gm130s on December 29, 2013 20:20:18
LocalUbuntu:~$ rtls nxc100:15005
rtls: Cannot list ports.
QNX:$ more /opt/jsk/var/log/rtcd-20131230114509.log
Logger::Logger: streambuf address = 0x805fc70
hrpExecutionContext is registered
unknown symbol: read_digital_output
unknown symbol: read_digital_output
Load failed.
Load failed.
Load failed.
Load failed.
Load failed.
Load failed.
Load failed.
Load failed.
Load failed.
Load failed.
Load failed.
Load failed.
Load failed.
Load failed.
Load failed.
Load failed.
Load failed.
Load failed.
hrpExecutionContext is registered
Load failed.
sh: rtcprof_python: cannot execute - No such file or directory
Abort (core dumped)
As in the error above, read_digital_output
was not found in the robot's hardware library that wasn't updated. Updating it resolved this issue.
Status: Invalid
From gm130s on December 29, 2013 19:32:43
Occasionally RTM client can't establish connection between RTC manager.
Today this error was seen on 2 different machines that use ros-hydro-nextage-ros-bridge 0.2.5-0raring-20131228-1621-+0000.
Original issue: http://code.google.com/p/rtm-ros-robotics/issues/detail?id=296