Releases: robofit/arcor2
Releases · robofit/arcor2
arcor2_runtime/1.4.1
Fixed
- Avoided high CPU load when running under Docker Compose without stdin attached.
Theselectcall returned immediately due to detached stdin, causing a busy loop.
Now, the stdin command thread is only started when stdin is a TTY.
arcor2_build/1.7.1
Fixed
High CPU load (fixed in arcor2_runtime).
arcor2_arserver/1.3.2
Fixed
High CPU load (fixed in arcor2_runtime).
arcor2_fit_demo/1.5.1
Changed
- Some actions were renamed, etc.
arcor2_dobot/1.3.1
Fixed
- Conveyor belt direction.
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_IPenv. variable changed toARCOR2_UR_ROBOT_IP.PUT /state/startoften 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_IPwas changed toROBOT_IP.