Wiki
Clone wikiariac / 2018 / competition_interface_documentation
ARIAC Interface
GEAR provides a ROS interface to the teams participating in ARIAC. This interface can be used by teams to control all available actuators, read sensor information and send/receive notifications.
During the competition, it is against the rules to control the ARIAC simulation using anything other than the interface specified below.
Teams are not permitted to use any of the topics or services in the /gazebo/
namespace prefix to control the Gazebo simulation or get information about the simulation state. These interfaces will be blocked during the Finals.
For a hands-on tutorial on interfacing with GEAR through command line tools, see the GEAR Interface tutorial. For a tutorial on interfacing with GEAR through a ROS node, see the Hello World tutorial.
Sensors
Topic name | Message/Service | Description | Message definition |
---|---|---|---|
/ariac/{name} | Message | Break beam's output | osrf_gear/Proximity.msg |
/ariac/{name}_change | Message | Break beam's output (output changes only) | osrf_gear/Proximity.msg |
/ariac/{name} | Message | Proximity sensor's output | sensor_msgs/Range.msg |
/ariac/{name} | Message | Laser profiler's output | sensor_msgs/LaserScan.msg |
/ariac/{name} | Message | Depth camera's output | sensor_msgs/PointCloud.msg |
/ariac/{name} | Message | Logical camera's output | osrf_gear/LogicalCameraImage.msg |
Note: The string {name}
is replaced with the name you give the sensor in the config file. See: https://bitbucket.org/osrf/ariac/wiki/2018/configuration_spec Since the sensor names are unique, it ensures that all sensors publish data to unique topics.
TF frames
TF frames for static key points of the workcell are published by the ARIAC simulation. Dynamic TF frames for the arm and faulty products are also published by the simulation. Other dynamic TF frames can be accessed through logical cameras.
Description | TF frame | Type |
---|---|---|
Origin of the workcell | world | static |
Each sensor | {sensor_name}_frame , e.g. logical_camera_1_frame |
static |
Bin storage units | bin{N}_frame , where N=1..8 |
static |
Arm links | {link_name} , e.g. wrist1_link |
dynamic |
Products detected by logical cameras | {logical_camera_name}_{product_name}_frame , e.g. logical_camera_1_piston_rod_part_1_frame |
dynamic |
Products detected by quality control sensors | quality_control_sensor_{N}_{anonymize_mode_name}_frame , where N=1..2, e.g. quality_control_sensor_1_model_1_frame |
dynamic |
Shipping boxes detected by logical cameras | {logical_camera_name}_shipping_box_{N}_frame , where N>=0, e.g. logical_camera_1_shipping_box_0_frame |
dynamic |
Actuators
Topic name | Message/Service | Description | Message definition |
---|---|---|---|
/ariac/arm/command | Message | Update the arm | trajectory_msgs/JointTrajectory.msg |
/ariac/joint_states | Message | Arm joint states | sensor_msgs/JointState |
/ariac/arm/state | Message | Arm Controller's state | control_msgs/JointTrajectoryControllerState.msg |
/ariac/conveyor/control | Service | Modify power of the conveyor belt | osrf_gear/ConveyorBeltControl.srv |
/ariac/conveyor/state | Topic | Conveyor belt's state | osrf_gear/ConveyorBeltState.msg |
/ariac/gripper/control | Service | Enable/disable gripper's suction | osrf_gear/VacuumGripperControl.srv |
/ariac/gripper/state | Message | Gripper's state | osrf_gear/VacuumGripperState.msg |
Process management
Topic name | Message/Service | Description | Message definition |
---|---|---|---|
/clock | Message | Simulation time | rosgraph_msgs/Clock.msg |
/ariac/start_competition | Service | Start the competition | std_srvs/Trigger.srv |
/ariac/end_competition | Service | End the competition early | std_srvs/Trigger.srv |
/ariac/competition_state | Message | State of the competition (init , ready , go , end_game , done ) |
std_msgs/String.msg |
/ariac/orders | Message | New order to be completed | osrf_gear/Order.msg |
/ariac/drone | Service | Notify a drone that a shipment is ready. The name of the shipment being submitted should match what was requested in the order, e.g. order_0_shipment_0 . Any unknown shipment name will cause the drone to remove the box without scoring it. |
osrf_gear/DroneControl.srv |
/ariac/drone/state | Message | State of the drone (ready_to_collect , collecting , collected , returning ) |
std_msgs/String.msg |
/ariac/quality_control_sensor_{N} | Message | Output of quality control sensor {N} (N=1,2), model names anonymized | osrf_gear/LogicalCameraImage.msg |
Cheats
These are only provided for debugging/development purposes and their use is not permitted during the competition trials. See the developer tips page for how to enable cheats.
Topic name | Message/Service | Description | Message definition |
---|---|---|---|
/ariac/shipping_boxes | Message | State of the shipment being built in each shipping box | osrf_gear/BoxContents.msg |
/ariac/submit_box | Service | Submit a shipping box for evaluation without drone collection | osrf_gear/SubmitBox.srv |
/ariac/shipping_box_{N}/clear_box | Service | Clear the contents of shipping box | std_srvs/Trigger.srv |
/ariac/current_score | Topic | Current completion score | std_msgs/Float32.msg |
/ariac/material_locations | Service | Query storage locations for a material (e.g. disk_part, pulley_part) | osrf_gear/GetMaterialLocations.srv |
Updated