Coolbot. Overview

CoolBOT.
Overview
Antonio Carlos Domínguez Brito
Inst. Univ. SIANI/Dpto. Informática y Sistemas
[1] Universidad de Las Palmas de Gran Canaria
[www.coolbotproject.org] Spain

CoolBOT
Overview

CoolBOT is a
distributed
CBSE
(Component
Based Software
Engineering) C++
[2] programming
[www.coolbotproject.org] framework

CoolBOT
Overview

CoolBOT's design principles:
1. Component based → easy
software integration.
2. Take advantage of
multithreading/multicores OSs.
3. System control & monitoring.
4. Transparent distributed
[3]
computing.
[www.coolbotproject.org]

CoolBOT
Overview

A system is
composed by
integrations and
software
components
[4]

CoolBOT
Overview

There are three
kinds of software
components:
components,
views and
probes
[5]

CoolBOT
Overview

Integrations are
processes in the
underlying OS.
They contain
components

[6]

CoolBOT
Overview

Integrations also may
contain views, and a
machine can host
several integrations

[7]

CoolBOT
Overview

probes are software
components to interface
non CoolBOT software
with CoolBOT systems,
and viceversa

[8]

CoolBOT
Overview

[9]

CoolBOT
Overview

CoolBOT users
program at system
level

[10]

CoolBOT CoolBOT runtime
infrastructure
Overview
supports system level
abstractions and
execution

[11]

CoolBOT
Overview

CoolBOT runtime
infrastructure is
supported by the OS
API and the ACE
library for network
communications

[12]

CoolBOT
CoolBOT Components

[13]

CoolBOT
CoolBOT Components
CoolBOT components are port automata
(input port data packets receptions trigger
automaton transitions)

[14]

CoolBOT
CoolBOT Components
Meta state running
implements component's
functionality. It is user
defined

[15]

CoolBOT
CoolBOT Components

Components' input and output
ports constitute its external
[16]
interface. Through them they
receive and send port packets
(data packets)

CoolBOT
CoolBOT Port Connections

Port connections are
unidirectional (from input port
to output port), and follow a
publish/subscribe
communication pattern

one publisher,
multiple subscribers

[17]

CoolBOT
Port connections are
unidirectional (from input port
to output port), and follow a
publish/subscribe
communication pattern

multiple publishers,
one subscriber

[18]

CoolBOT

Components interact
using only port
connections. Thus, a
system can be seem
as a network of
components
interchanging port
packets and running as
data driven machines

[19]

CoolBOT

There are different
typologies for input and
output ports for establishing
port connections with
different communication
patterns: fifo on input port,
“blackboard” on output
port and multipacket.

[20]

CoolBOT

Port Connections Typologies
Active Publisher/Passive Subscriber (AP/PS)
Output Port Input Port Port Connection Type
tick
There are different tick tick connections
typologies for input and last last connections
output ports for establishing
generic fifo fifo connections
ufifo unbounded fifo connections
different communication
multipacket
patterns: fifo on input port, multipacket multipacket connections
“blackboard” on output
lazymultipacket
port and multipacket.Active Publisher/Passive Subscriber (PP/AS)
poster poster poster connections
[21]

CoolBOT

A port connection can be
established when the
typologies of the ports
involved are compatible,
and the type of port
packets they transport are
the same

[22]

CoolBOT

Integrations are CoolBOT
processes hosting
component instances at
runtime

Port connections
established between
components (local
components) in the same
integration are supported
transparently by the
underlying OS thread API

[23]

CoolBOT

Integrations are CoolBOT
processes hosting
component instances at
runtime

Port connections between
components in different
integrations are
multiplexed over TCP/IP
connections

[24]

CoolBOT
CoolBOT Views

The second type of
software component
available in CoolBOT
are views

CoolBOT views expand
component interfaces to
decouple and separate
system computation
and control from
graphical interfaces
for monitoring and
control

[25]

CoolBOT
CoolBOT Views

Likewise components,
views have also an
external interface of
input and output ports

[26]

CoolBOT
CoolBOT Views

CoolBOT integrations
may contain indistinctly
components and views

As software components
views may establish
any other component or
view (local or remote) in
a system

[27]

CoolBOT
CoolBOT Views

CoolBOT integrations
may contain indistinctly
components and views

As software components
views may establish
any other component or
view (local or remote) in
a system

[28]

CoolBOT
CoolBOT Probes

The third type of software
component available in CoolBOT
are probes

Expanding even more the
concept of component interface
probes implement interfaces of
input and output ports in order
to allow non CoolBoT software to
intercommunicate with CoolBoT
components

[29]

CoolBOT
CoolBOT Probes

The third type of software
component available in CoolBOT
are probes

CoolBOT probes implement
interfaces of input and output
ports in order to allow non
CoolBoT software to
intercommunicate with CoolBoT
components

[30]

CoolBOT CoolBOT provides two tools for
developing CoolBOT software:
Development Tools coolbot-bundle and coolbot-c

[31]


coolbot-bundle creates
[32] workspaces for developing
[www.coolbotproject.org] components, views, port
packets and integrations


coolbot-c is the CoolBOT
compiler. We can generate C++
skeletons for components,
probes, views, port packets
[33] and integrations


and integrations

[34]


and integrations
[35]


[36] and integrations

CoolBOT
An Example: A Secure
Navigation System

This is an
integration
implementing a
Secure
Navigation
System (SNS)
for a mobile
robot,
concretely a
[37] Pioneer 3 DX

CoolBOT
Navigation System

It uses
Player/Stage
for abstracting
the robot
hardware, a
Global ND+
algorithm
implementation,
in combination
with the MbICP
algorithm for
[38] scan matching

CoolBOT

[39]
Navigation System


CoolBOT
Navigation System

Component
PlayerRobot
abstracts the
[40] robot hardware
using
Player/Stage

CoolBOT
Navigation System

Component
MbICPCorrector
implement the
MbICP scan
matching
algorithm to
reduce odometry
errors

[41]

CoolBOT
Navigation System

Component
GridMap
registers range
laser sensor data
in a grid while the
robot navigates

[42]

CoolBOT
Navigation System

Component ND
makes the robot
navigates while
avoiding
obstacles using
ND+ algorithm

[43]

CoolBOT
Navigation System

Component
Planner plans
which way to get to
arrive to a specific
point using the grid
built by component
GridMap. It
provides
component ND
with subobjetives
while navigating
[44]

CoolBOT

[45]
Navigation System


CoolBOT

[46]
Navigation System


CoolBOT

[47]
Navigation System


CoolBOT

[48]
Navigation System


CoolBOT

[49]
Navigation System


CoolBOT

[50]
Navigation System


CoolBOT
Conclusions and Future Work

∙ In CoolBOT, decoupling interfaces makes
software components deployable and integrable
wherever we want, no matter its functionality, or
which grade of granularity they have.

▸ Components (implement generic algorithms)
▸ Views (implement graphical interfaces)
▸ Probes (implement generic interfaces)

∙ CoolBOT is an open source project available at:
[51]
[www.coolbotproject.org] www.coolbotproject.org

CoolBOT
Conclusions and Future Work

●
Ongoing/Future work:

1. Documentation.
2. Integration with ROS.
3. Runtime interpret for integrations.
3.1. Component Name Service.
3.2. Remote instantiation Service.
[52]

THAT'S ALL!
THAT'S ALL!
More info in
www.coolbotproject.org
[53]

Coolbot. Overview

More Related Content

Similar to Coolbot. Overview

Recently uploaded

Coolbot. Overview