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
In #2ee3299 the get_parameters from other node method was added.
In #4037e548d703d0c84e56d84c9f04eb46c18e4fca the motor start delay was added.
Now the HCM dies, because a runtime error occurs when starting the sim script.
Expected behavior
Normal simulator functionality with being able to walk etc.
Current behavior
HCM dies.
There is not /wolfgang_hardware_interface node, because if sim is used the sim parameter is true.
This results in the ros_control.launch not being started which leads to the node in bitbots_ros_control not being started (no wolfgang_hardware_interface node).
Steps to Reproduce
Build on current main.
Run ros2 launch bitbots_bringup simulator_teamplayer.launch game_controller:=false behavior:=false.
Wait 20 seconds.
Possible Solution
Use separate parameter for startup not in wolfgang.yaml.
Set parameter in launch file
Mock wolfgang_hardware_interface node for the parameters if sim:=true
The text was updated successfully, but these errors were encountered:
Summary
In #2ee3299 the get_parameters from other node method was added.
In #4037e548d703d0c84e56d84c9f04eb46c18e4fca the motor start delay was added.
Now the HCM dies, because a runtime error occurs when starting the sim script.
Expected behavior
Normal simulator functionality with being able to walk etc.
Current behavior
HCM dies.
There is not /wolfgang_hardware_interface node, because if sim is used the sim parameter is true.
This results in the ros_control.launch not being started which leads to the node in bitbots_ros_control not being started (no wolfgang_hardware_interface node).
Steps to Reproduce
Possible Solution
The text was updated successfully, but these errors were encountered: