You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
setting /run_id to d5633268-ee5c-11e9-923c-b8aeed7a6236
process[rosout-1]: started with pid [2691]
started core service [/rosout]
process[twist_mux-2]: started with pid [2694] terminate called after throwing an instance of 'XmlRpc::XmlRpcException'
[twist_mux-2] process has died
The solution is to change 5 to 5.0. It's not an important issue but I spent some time trying to find out what happen. I also think that the problem does not come at all from the node, instead of the .yaml parser or something related to the .yaml reading, but not sure.
The text was updated successfully, but these errors were encountered:
I found that when launching the twist_mux node with timeout parameter as follow(config.yaml):
topics:
name : navigation
topic : nav_vel
timeout : 5
priority: 10
The node throw:
setting /run_id to d5633268-ee5c-11e9-923c-b8aeed7a6236
process[rosout-1]: started with pid [2691]
started core service [/rosout]
process[twist_mux-2]: started with pid [2694]
terminate called after throwing an instance of 'XmlRpc::XmlRpcException'
[twist_mux-2] process has died
The solution is to change 5 to 5.0. It's not an important issue but I spent some time trying to find out what happen. I also think that the problem does not come at all from the node, instead of the .yaml parser or something related to the .yaml reading, but not sure.
The text was updated successfully, but these errors were encountered: