2019
DOI: 10.1016/j.robot.2018.10.009
|View full text |Cite
|
Sign up to set email alerts
|

Pound: A multi-master ROS node for reducing delay and jitter in wireless multi-robot networks

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
24
0

Year Published

2019
2019
2024
2024

Publication Types

Select...
6
1

Relationship

1
6

Authors

Journals

citations
Cited by 39 publications
(24 citation statements)
references
References 41 publications
0
24
0
Order By: Relevance
“…Preliminary development steps, detailed in Section 4.2 and shown in Figure 6 , are the reason for the following changes compared to SITL. First, the image type is changed to a compressed representation due to networking effects [ 21 , 22 ], which causes an increase in CPU load. Second, the MAVROS node responsible for translating between ROS and Mavlink is required to run on the onboard computer, increasing its load.…”
Section: Resultsmentioning
confidence: 99%
See 1 more Smart Citation
“…Preliminary development steps, detailed in Section 4.2 and shown in Figure 6 , are the reason for the following changes compared to SITL. First, the image type is changed to a compressed representation due to networking effects [ 21 , 22 ], which causes an increase in CPU load. Second, the MAVROS node responsible for translating between ROS and Mavlink is required to run on the onboard computer, increasing its load.…”
Section: Resultsmentioning
confidence: 99%
“…Using the maximum computation available by offloading parts of the perception—planning—control loop over a network connection is the most common solution [ 6 , 16 , 17 , 18 , 19 , 20 ]. This method is highly effective, however it introduces networking effects and drop-outs, with potentially detrimental consequences when used in real-time cycles [ 21 , 22 ]. Furthermore, several remote-sensing applications cannot rely on network connections, making onboard computation the final goal.…”
Section: Introductionmentioning
confidence: 99%
“…The cause of this result is the difference between the communication middleware used in ROS 1.0 and ROS 2.0. ROS 1.0 is not suitable for networks with loss, such as wireless networks, because it uses the TCP protocol-based TCPROS as the middleware for its communications [23].…”
Section: B Latencymentioning
confidence: 99%
“…Instead, multihop communication, where intermediate robots act as relays to transmit the information from the source to the destination, is necessary. However, multihop communication has several drawbacks: (a) In the worst‐case, the available bandwidth is reduced to roughly 1(n1), where n is the number of robots involved in the communication (Ng & Liew, ); (b) the routing protocol must be able to manage fast topology changes due to the robots' displacements; and (c) every additional hop increases the delay and jitter associated with the information transmitted, making control inefficient and inaccurate (Tardioli, Parasuraman, & Ögren, ). While the first issue can be taken into account beforehand, planning the bandwidth demand to always be below the system capability, and the second can be solved using specific routing protocols, the third requires further consideration.…”
Section: Challengesmentioning
confidence: 99%
“…Unfortunately, multihop paths intrinsically introduce delay as the information must be relayed one or more times before reaching the destination. These relays also contribute to incrementing the jitter (Tardioli, Parasuraman, et al, ) given the nondeterministic scheme used by common wireless protocols (like 802.11) to access the medium. The intrinsic low reliability of the wireless medium (at least compared with its wired counterpart) worsens the situation.…”
Section: Setting Up An Intervention Teammentioning
confidence: 99%