Skip to content Skip to main navigation Skip to footer

Multi-Robot Collaboration and Dispatching

Multi-Robot Collaboration

Multi-robot collaboration includes multi-robot dispatching and multi-robot avoidance, which are basic capabilities of robot collaboration. The communication module involved here is also part of these basic multi-robot collaboration capabilities and is a system feature.

        Multi-robot collaboration requires no manual operation; all behavior is dispatched by the robot system. The prerequisite is that the robots work on the same map. When several robots meet, they use robot-to-robot communication to rank their current work priorities and decide whether to give way or keep working. This prevents robots from meeting at the same spot and getting stuck. Therefore, as long as the robots’ performance and hardware are working normally, multi-robot collaboration works normally.

Multi-Robot Collaboration Information

On robots with an ESP32 multi-robot communication module installed, you can use the following method to get multi-robot information, for example to build a multi-robot dispatching system. Currently, LuckiBot always has an ESP32 multi-robot communication module; other robots do not include this module by default.

RobotApi.getInstance().registerStatusListener(Definition.STATUS_MULTIPLE_ROBOT_WORKING, mStatusListener);
private StatusListener mStatusListener = new StatusListener() {
    @Override
    public void onStatusUpdate(String type, String data) {
        try {
            Type dataType = new TypeToken<List<MultiRobotStatus>>(){}.getType();
            List<MultiRobotStatus> curRobotStatus = mGson.fromJson(data, dataType);
        }catch(Exception ex){
        }
    }
}

MultiRobotStatus is defined as follows:

public class MultiRobotStatus {
    private BasePoseBean pose;
    private BasePoseBean goal;
    private int id;
    private int priority;
    private boolean mapMatch;
    private long time;
    private int status;
    private boolean curRobot = false;
    private int errorStatus = 0;
 }