Military Communications and Information Technology: A Trusted ...
Military Communications and Information Technology: A Trusted ... Military Communications and Information Technology: A Trusted ...
308 Military Communications and Information Technology... connection protocol will be used. Although TCP is the most common protocol used in an ROS, a UDP can also be used. The data exchange between nodes will create a peer-to-peer network. III. Systems in use A. C2LG GUI We use a graphical user interface, the C2LG GUI, to enter the orders for our robot system. C2LG GUI is used in other projects to test interoperability with simulation systems, e.g., with French and German systems [13]. The GUI supports the user generating the orders. It allows selecting objects from a list or to pick them from the integrated map. Geographical features like areas can be created on the map as well. These features then can be referenced. The GUI also visualizes the robots’ reports. In particular, the robots themselves are shown the map due to their periodic position reports. Figure 1. The GUI we used to create BML orders. First the action “move” was selected. Then the taskee “robot_group_1” was selcted and route “routeA” was created on the map and given as a paremter to the order 1 The initialization of the GUI was done using the Military Scenario Description Language (MSDL) [14]. We created an MSDL File which includes the units, the associated symbols, the order of battle, and also some geographical objects e.g., where the base is. 1 Map data (c) ῾OpenStreetMap’ (and) contributors (http://www.openstreetmap.org/), CC-BY-SA (http://creativecommons.org/licenses/by-sa/2.0/)
Chapter 3: Information Technology for Interoperability and Decision... 309 B. UGV RTS-HANNA Our multi-robot system consisted of a ground vehicle and two UAVs. This section provides information about the ground vehicle. The following section will cover the UAVs. The unmanned ground vehicle is called RTS-HANNA (see Fig. 2). It is based on an off-the-shelf Kawasaki Mule 3010 Diesel chassis which has been retrofitted with a drive-by-wire interface (by PARAVAN GmbH). That interface enables manual as well as full computer control of the vehicle. Due to the manual control, HANNA is fully street-licensed. Its maximum velocity is 40 km/h, and its maximum payload is 600 kg. HANNA can be equipped with a multitude of sensors. For environmental perception, two continuously rotating 3D laser rangefinders RTS-ScanDriveDuo with an update rate of 0.8 Hz each for close range, one Velodyne HDL-64E with an update rate of 15 Hz for long range, one Ibeo Lux for fast obstacle detection within the main driving direction, and a Microsoft Kinect are mounted. For the navigation, odometry, a gyroscope, and two GPS receivers are available. HANNA communicates either by WiFi, or a serial link in the unlicensed industrial, scientific and medical (ISM) radio band, or by GSM/UMTS. HANNA has five embedded PCs at her disposal, used for processing the sensor data, for navigation and to control her, in our case by BML orders, cf. [15] for more details. Software for those PCs is developed using the robotic framework RACK (Robotics Application Construction Kit). To make the PCs capable for executing ROS components, we, in general, cross-compiled ROS and made the ROS libraries and API available to our middleware RACK. In particular, a kind of gateway module has been implemented. That module is part of the RACK communication system, but is also able to publish and subscribe to ROS topics. It receives the BML tasks and organizes their execution by publishing corresponding tasks for the UAVs as ROS topics. It also publishes sensor data for the BML-GUI. In short, HANNA is running the ROSCore and the BMLConnector in the ROS context, the gateway module to connect both worlds, and the rest of the software components in RACK. HANNA navigates on a known road network available in OpenStreetMap (OSM) format. To navigate to a certain point of destination, a simple A* search for a shortest path in the OSM geodata is initiated, cf. [16] for details. To follow the planned path, a hybrid feedback controller, introduced in [17], is applied. This service uses reactive obstacle avoidance and local path re-planning.
- Page 257 and 258: Chapter 3: Information Technology f
- Page 259 and 260: Chapter 3: Information Technology f
- Page 261 and 262: Chapter 3: Information Technology f
- Page 263 and 264: Chapter 3: Information Technology f
- Page 265 and 266: Automatic Exploitation of Multiling
- Page 267 and 268: Chapter 3: Information Technology f
- Page 269 and 270: Chapter 3: Information Technology f
- Page 271 and 272: Chapter 3: Information Technology f
- Page 273 and 274: Chapter 3: Information Technology f
- Page 275 and 276: Chapter 3: Information Technology f
- Page 277 and 278: Chapter 3: Information Technology f
- Page 279 and 280: Chapter 3: Information Technology f
- Page 281 and 282: Information Fusion Under Network Co
- Page 283 and 284: Chapter 3: Information Technology f
- Page 285 and 286: Chapter 3: Information Technology f
- Page 287 and 288: Chapter 3: Information Technology f
- Page 289 and 290: Chapter 3: Information Technology f
- Page 291 and 292: Chapter 3: Information Technology f
- Page 293: Chapter 3: Information Technology f
- Page 296 and 297: 296 Military Communications and Inf
- Page 298 and 299: 298 Military Communications and Inf
- Page 300 and 301: 300 Military Communications and Inf
- Page 302 and 303: 302 Military Communications and Inf
- Page 305 and 306: Commanding Multi-Robot Systems with
- Page 307: Chapter 3: Information Technology f
- Page 311 and 312: Chapter 3: Information Technology f
- Page 313 and 314: Chapter 3: Information Technology f
- Page 315 and 316: Chapter 3: Information Technology f
- Page 317 and 318: Application of CID Server in Decisi
- Page 319 and 320: Chapter 3: Information Technology f
- Page 321 and 322: Chapter 3: Information Technology f
- Page 323 and 324: Chapter 3: Information Technology f
- Page 325 and 326: Chapter 3: Information Technology f
- Page 327 and 328: Chapter 3: Information Technology f
- Page 329 and 330: Chapter 3: Information Technology f
- Page 331 and 332: Managing Lessons Learnt from Daily
- Page 333 and 334: Chapter 3: Information Technology f
- Page 335 and 336: Chapter 3: Information Technology f
- Page 337 and 338: Chapter 3: Information Technology f
- Page 339 and 340: Chapter 3: Information Technology f
- Page 341 and 342: Chapter 3: Information Technology f
- Page 343: Chapter 3: Information Technology f
- Page 347 and 348: Federated Cyber Defence System - Ap
- Page 349 and 350: Chapter 4: Information Assurance &
- Page 351 and 352: Chapter 4: Information Assurance &
- Page 353 and 354: Chapter 4: Information Assurance &
- Page 355 and 356: Chapter 4: Information Assurance &
- Page 357: Chapter 4: Information Assurance &
Chapter 3: <strong>Information</strong> <strong>Technology</strong> for Interoperability <strong>and</strong> Decision...<br />
309<br />
B. UGV RTS-HANNA<br />
Our multi-robot system consisted of a ground vehicle <strong>and</strong> two UAVs. This<br />
section provides information about the ground vehicle. The following section will<br />
cover the UAVs.<br />
The unmanned ground vehicle is called RTS-HANNA (see Fig. 2). It is based<br />
on an off-the-shelf Kawasaki Mule 3010 Diesel chassis which has been retrofitted<br />
with a drive-by-wire interface (by PARAVAN GmbH). That interface enables<br />
manual as well as full computer control of the vehicle. Due to the manual control,<br />
HANNA is fully street-licensed. Its maximum velocity is 40 km/h, <strong>and</strong> its maximum<br />
payload is 600 kg.<br />
HANNA can be equipped with a multitude of sensors. For environmental<br />
perception, two continuously rotating 3D laser rangefinders RTS-ScanDriveDuo<br />
with an update rate of 0.8 Hz each for close range, one Velodyne HDL-64E with<br />
an update rate of 15 Hz for long range, one Ibeo Lux for fast obstacle detection<br />
within the main driving direction, <strong>and</strong> a Microsoft Kinect are mounted. For<br />
the navigation, odometry, a gyroscope, <strong>and</strong> two GPS receivers are available. HANNA<br />
communicates either by WiFi, or a serial link in the unlicensed industrial, scientific<br />
<strong>and</strong> medical (ISM) radio b<strong>and</strong>, or by GSM/UMTS.<br />
HANNA has five embedded PCs at her disposal, used for processing the sensor<br />
data, for navigation <strong>and</strong> to control her, in our case by BML orders, cf. [15] for more<br />
details. Software for those PCs is developed using the robotic framework RACK<br />
(Robotics Application Construction Kit). To make the PCs capable for executing<br />
ROS components, we, in general, cross-compiled ROS <strong>and</strong> made the ROS libraries<br />
<strong>and</strong> API available to our middleware RACK. In particular, a kind of gateway<br />
module has been implemented. That module is part of the RACK communication<br />
system, but is also able to publish <strong>and</strong> subscribe to ROS topics. It receives the BML<br />
tasks <strong>and</strong> organizes their execution by publishing corresponding tasks for the UAVs<br />
as ROS topics. It also publishes sensor data for the BML-GUI. In short, HANNA<br />
is running the ROSCore <strong>and</strong> the BMLConnector in the ROS context, the gateway<br />
module to connect both worlds, <strong>and</strong> the rest of the software components in RACK.<br />
HANNA navigates on a known road network available in OpenStreetMap<br />
(OSM) format. To navigate to a certain point of destination, a simple A* search<br />
for a shortest path in the OSM geodata is initiated, cf. [16] for details. To follow<br />
the planned path, a hybrid feedback controller, introduced in [17], is applied. This<br />
service uses reactive obstacle avoidance <strong>and</strong> local path re-planning.