-
Notifications
You must be signed in to change notification settings - Fork 39
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
"wait for HrpsysSeqStateROSBridge0 : None" continues #333
Comments
Btw, with a commit in the pull request #305 I can reproduce the issue on the simulator on my computer.
|
I was wrong; on the simulation on this user's Ubuntu computer, this issue is NOT occurring. |
please confirm that impedance controller is running on simulator with hironx robot with https://github.com/start-jsk/rtmros_hironx/pull/338/files#diff-197cb5094a9e431bf96e62d767605f2fR783, before you try to run them on nextage robot, they are slightly different. |
```
[hrpsys.py] wait for HiroNX(Robot)0 : <hrpsys.rtm.RTcomponent instance at
0x7f7130a59fc8> ( timeout 0 < 10)
[hrpsys.py] findComps -> RobotHardware : <hrpsys.rtm.RTcomponent instance
at 0x7f7130a59fc8> isActive? = True
```
on real robot, it should connect to RobotHardware, not HiroNX(Robot)0.
please check code around [this line](https://github.com/tork-a/rtmros_nextage/blob/1194537861361bb7308d1cc0618c6343c05a6d28/nextage_ros_bridge/script/nextage.py#L69).
|
On simulator on my computer,
Yes Impedance Controller works for Hironx sim. On the real robot,
Good point, I failed to include the full log in my post from the real robot #333 (comment). But anyway it used the latest deb at that time Still, I understand that it's a bit confusing to discuss an issue on the real and simulator in a single ticket even for the same error. On this ticket let us only talk about the real robot issue. |
#333 (comment) logs seems rtcd is dieing , we need rtcd.log and full log of roslaunch output, also you'd better to start with |
Turned out that |
On a user's Ubuntu host,
HrpsysSeqStateROSBridge0
can't be connected, both with their real robot and on simulation.Downgrading `*_ros_bridge (source build) didn't help.
Having seeing
duplicated sensor Id
, updating the sensor id inmain.wrl
to use non-duplicate number then restarted QNX, which seems not working.The same error message is seen on sim.
Reinstalling some DEB files didn't help.
The text was updated successfully, but these errors were encountered: