D2.1 Requirements and Specification - CORBYS
D2.1 Requirements and Specification - CORBYS
D2.1 Requirements and Specification - CORBYS
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>D2.1</strong> <strong>Requirements</strong> <strong>and</strong> <strong>Specification</strong><br />
System (software) architecture:<br />
The iCub architecture is based on YARP (Yet Another Robot Platform) (Metta, 2006)], open-source<br />
framework that supports distributed computing. Figure 32 shows the layers of the iCub architecture. The<br />
lowest level API-0 of system architecture is used for accessing hardware components, by formatting <strong>and</strong><br />
unformatting IP packages into appropriate classes <strong>and</strong> data structures. IP packets are sent to the robot by GBit<br />
Ethernet connection. High-level cognitive processes are implemented as YARP processes.<br />
Real time control:<br />
In order to achieve real-time control of the robotic system, control of joint actuators is carried out by digital<br />
signal processing (DSP) units that are mounted on robotic platform. The iCub software runs in parallel on a<br />
distributed system of computers that are connected via Gbit Ethernet with the Hub unit (PC/104) that is also<br />
located on the robotic platform.<br />
Planning:<br />
In the brain, the basal ganglia are responsible for action selection <strong>and</strong> therefore in modulation circuit is present<br />
action selection circuit that corresponds to ganglia.<br />
Communication:<br />
Multiple CAN bus structure is used to communicate with control/driver <strong>and</strong> AD cards on the robotic system,<br />
while Gbit Ethernet is used to communicate data between the robotic system <strong>and</strong> distributed system of<br />
computers. YARP architecture supports building robot control system as a collection of programs<br />
communicating in peer-to-peer way, with broad range of connection types (tcp, udp, multicast, XML/RPC,<br />
tcpros <strong>and</strong> etc.)<br />
13.2.4 CareObot<br />
System architecture:<br />
The Care-O-bot System is controlled by a heterogeneous hybrid layered software architecture, which<br />
combines reactive <strong>and</strong> deliberative control. It consists of several basic modules, as displayed in the following<br />
figure.<br />
Figure 34: Architecture of Care-O-bot (Hans et. al. 2001)<br />
141