2016
DOI: 10.1007/978-3-319-26054-9_24
|View full text |Cite
|
Sign up to set email alerts
|

The ROS Multimaster Extension for Simplified Deployment of Multi-Robot Systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
23
0
1

Year Published

2017
2017
2023
2023

Publication Types

Select...
4
3
2

Relationship

0
9

Authors

Journals

citations
Cited by 38 publications
(25 citation statements)
references
References 0 publications
0
23
0
1
Order By: Relevance
“…Polling solutions are not feasible for low-level remote control (as teleoperation) [16] Based on the use of SpaceBrew It is not clear if visibility among agents is requested or managed by SpaceBrew. Some limitations are presented in the paper but not discussed [18] Communication based on a proxy virtual machine Listed results are limited to one robot [19] Based on three subsystems in the cloud environment: middleware subsystem, background tasks subsystem, and control subsystem Built upon the ROS Multimaster FKIE [20], which requires bi-directional visibility among all the agents in the system [21] Based on WebSocket protocol to guarantee the bi-directionality of the flow of data Visibility requirements between the agents not detailed. Still limited in an early developer program [10] New protocol, similar to rosbridge protocol Tests limited to few simulated robots…”
Section: Features Of the System Used Limitation Of The Presented Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Polling solutions are not feasible for low-level remote control (as teleoperation) [16] Based on the use of SpaceBrew It is not clear if visibility among agents is requested or managed by SpaceBrew. Some limitations are presented in the paper but not discussed [18] Communication based on a proxy virtual machine Listed results are limited to one robot [19] Based on three subsystems in the cloud environment: middleware subsystem, background tasks subsystem, and control subsystem Built upon the ROS Multimaster FKIE [20], which requires bi-directional visibility among all the agents in the system [21] Based on WebSocket protocol to guarantee the bi-directionality of the flow of data Visibility requirements between the agents not detailed. Still limited in an early developer program [10] New protocol, similar to rosbridge protocol Tests limited to few simulated robots…”
Section: Features Of the System Used Limitation Of The Presented Workmentioning
confidence: 99%
“…Bi-directional communications are presented in the paper, but it is not detailed how these are achieved. Furthermore, the proposed architecture is built upon the ROS Multimaster FKIE [20], which requires bi-directional visibility among all the agents in the system.…”
mentioning
confidence: 99%
“…Al igual que el resto de plataformas robóticas asegura el soporte y gestión de elementos hardware heterogéneos (R1), pero no integra las características sociales dentro de la arquitectura. En el caso concreto de ROS, existen paquetes externos (ROS multimaster [11]) que permiten comunicar diferentes elementos robóticos que empleen este marco, dotando al sistema de ciertas capacidades sociales y autónomas (R2, R3).…”
Section: Marcos Robóticosunclassified
“…The depth integration takes about 100 ms per frame and the patch alignment and fusion takes between 1 and 15 s, but this process is not time critical and is processed in another thread. To facilitate information exchange between the robots, the multi-master node manager system [24] was used. This software shares ROS topics between different computers, with clock synchronization from a common NTP reference.…”
Section: A Platforms Dataset and Map Configurationmentioning
confidence: 99%