Multi-agent Control System Manual
Table Of Contents
- Roboworks
- Roboworks
- Summary
- Roboworks
- Table of contents
- 1. Introduction to Multi-agent Algorithms
- 2. Multi-agent Communications Setup
- 3. Multi-agent Synchronisation Setup
- 4. Multi-agent ROS Package
- Roboworks
- Introduction to multi-agent algorithms
- 1.1 Multi-agent formation algorithms
- 1.2 Obstacle avoidance algorithms
- Roboworks
- multi-agent communication setup
- Multi-agent communication is one of the key steps to complete a multi-robot formation. When the relative positions of multiple robots are unknown, the robots need to share each other's information through communication to facilitate the establishment of connections. ROS distributed architecture and network communications are very powerful. It is not only convenient for inter-process communication, but also for communication between different devices. Through network communication, all nodes can run on any computer. The main tasks such as data processing are completed on the host side. The slave machines are responsible for receiving environmental data collected by various sensors. The host here is the manager that runs the Master node in ROS. The current multi-agent communication framework is through a node manager and a parameter manager to handle communications among multiple robots.
- Roboworks
- 2.1 The steps to set up multi-agent communications
- Roboworks
- Roboworks
- 2.2 Automatic Wifi connection in ROS
- Roboworks
- Roboworks
- Roboworks
- Roboworks
- Roboworks
- Roboworks
- multi-agent synchronisation setup
- 3.1 Successful master/slave network connection
- 3.2 Troubleshooting network dis-connections
- Roboworks
- multi-agent ros package
- 4.1 ROS Package Introduction
- Roboworks
- Roboworks
- Roboworks
- Roboworks
- Roboworks
- Roboworks
- 4.2 Operation Procedure
- Roboworks
www.roboworks.com.au/support
sudo date -s “2022-01-30 15:15:00” # Manual time setup
MULTI-AGENT ROS PACKAGE
4.1 ROS Package Introduction
4.1.1 Set up slave name
In the wheeltec_multi function package, it is necessary to set a unique name for each slave robot in order to
avoid errors. For example, No. 1 for slave1 and No. 2 for slave2 etc..
ROBOWORKS
Fig 3-2-1 Steps to enter Broadcast Command