blue_core
blue_core copied to clipboard
berkeleyopenarms
ROS metapackage containing the core software needed for running a Blue robot arm
- this adds python bindings to the bldc controller client for easier usage of blue_hardware_drivers.
I got error saying that "REQUIRED process [right_arm/blue_controller_manager-2] has died!" I thought this is happening because I am using the wrong config file, so I tried the following two but...
Instruction says "Proceed to setup the arm with power supply and USB adapter ("Electrical Setup" in Quick Start Guide)" but I couldn't find the Quick Start Guide.
It is saying "**Robot model parameter not found! Did you remap 'robot_description'?**" I try replaced the "robot_description" in blue.rviz into "blue_description" but did not help. It seems like ros cannot...
Do I have to edit "blue_bringup>config>robot_parameters_right.yaml" ? or do I have to make a new config file using "blue_configs" repo and place it under blue_bringup?
https://github.com/berkeleyopenarms/blue_core/pull/82 introduces a mutex on the driver. This should be moved lower level into the BLDCDriver class.
The read and write function should properly match the functions defined in the parent RobotHW class. See https://github.com/ros-controls/ros_control/blob/melodic-devel/hardware_interface/include/hardware_interface/robot_hw.h
...rather than relying on the softstop limits in the robot parameter yaml #79
Should we be forcing blue to be fixed at the origin in Gazebo with the world joint? That stops the model from being moved around which might be inconvenient if...
I found that the joint limits specified in the V1 URDF are a lot more conservative than the arm allows, which causes issues with planning. This PR fixes that.
Metadata
Owner
Metadata
ROS metapackage containing the core software needed for running a Blue robot arm