Releases: robofit/arcor2
Releases · robofit/arcor2
arcor2_ur/1.5.0
Changed
- Checking for the robot's state disabled as it was not working reliably.
- Added Scene functions - the ability to manage collision objects. Please note that so far, only boxes are considered. Other types can be added but will be ignored.
arcor2_ur/1.4.1
Fixed
- Checking for robot's state - it should no longer be necessary to start the robot manually (before calling
PUT /state/start
). It should also work if the robot is already started.
arcor2_ur/1.4.0
Changed
- Ability to control OnRobot VGC10 suction through Modbus (requires RS485 URCap in the robot).
ROBOT_IP
env. variable changed toARCOR2_UR_ROBOT_IP
.PUT /state/start
often failed because the robot was not yet ready to start a program - added check for the robot's state - however, it does not work at the moment. Until it is resolved, it is recommended to start the robot manually.
arcor2_arserver/1.3.1
Fixed
- Handling of useless changes in
UpdateActionPointParent
.
arcor2_ur/1.3.0
- Docker image now checks for a robot calibration file at
/root/robot_calibration.yaml
. If not given, a default one is used. ROBOT_CONTAINER_IP
was changed toROBOT_IP
.
arcor2_ur/1.2.1
Fixed
- ROS logger was not set to debug when requested by argument/environment variable (however, it has no effect on moveitpy).
- Parameter
velocity
not shown in Swagger UI.
arcor2_ur/1.2.0
Changed
- Update of ROS 2 dependencies.
arcor2_ur/1.1.0
Changed
- Removed waiting after trajectory execution (probably useless).
- Ability to set movement velocity and payload (mass only).
arcor2_ur/1.0.0
Changed
- Initial release of the UR service.
arcor2_execution/1.6.0
Changed
- Dependency on
arcor2~=1.5.0
.