Closed christophfroehlich closed 1 month ago
@saikishor it seems that we have a bug or a race condition in the spawner:
There is no rrbot_1.spawner_joint_state_broadcaster
launched, but two for rrbot_2 with the obvious error
2: [spawner-10] [WARN] [1727282065.051104080] [rrbot_2.spawner_joint_state_broadcaster]: [93mController already loaded, skipping load_controller[0m
When I uncomment the rrbot_2_launch here, then the JSB for rrbot_1 is spawned as expected. Any ideas?
@saikishor it seems that we have a bug or a race condition in the spawner: There is no
rrbot_1.spawner_joint_state_broadcaster
launched, but two for rrbot_2 with the obvious error2: [spawner-10] [WARN] [1727282065.051104080] [rrbot_2.spawner_joint_state_broadcaster]: �[93mController already loaded, skipping load_controller�[0m
When I uncomment the rrbot_2_launch here, then the JSB for rrbot_1 is spawned as expected. Any ideas?
Ahh I believe I might know. Both the robots use the same controller manager here?
No, /rrbot_1/controller_manager
vs /rrbot_2/controller_manager
The problem seemed to be the RegisterEventHandler
. We don't need it here for the spawners (or in the demos at all?). Binary build fails until next release of ros2_control.
Follow-up to #540
Re-evalute after #502 is merged.