Chapter 6 Pioneer 2 Operating System; Communication Packet Protocol - Pioneer 2 / PeopleBot Operation Manual

Pioneer 2 Operating System
Chapter 6
All ActivMedia robots use a client-server
mobile robot-control
developed by Dr. Kurt Konolige and others
at SRI International.
robot's controller servers—the Pioneer 2
Operating System
manage all the low-level details of the
mobile robot's systems.
operating the motors, firing the sonar,
collecting sonar and wheel encoder data,
and so onall on command from and
reporting to a separate client application,
such as ARIA or Saphira.
With this client/server architecture, robotics
applications developers do not need to
know many details about a particular robot
server, because the client insulates them
from this lowest level of control. Some of
you, however, may want to write your own
robotics control and reactive planning
programs, or just would like to have a
closer programming relationship with your
robot. This chapter explains how to
communicate with
ActivMedia robot via the P2OS client-server
interface. The same P2OS functions and
commands are supported in the various
client-programming
accompany your robot or are available for
separate license.
Experienced Pioneer users can be assured that P2OS is upwardly compatible with PSOS,
implementing all the same commands and information packets.
extends the servers to add new functionality, improve performance, and provide
additional information about the robot's state and sensing.
programs may not operate on original Pioneers.

Communication Packet Protocol

Table 2. Main elements of PSOS/P2OS communication packet protocol
Component
Header
Byte Count
Data
Checksum
P2OS communicates with a client application using a special packet protocol for both
command packets from client to server and server information packets (SIPs) from the
architecture
In the model, the
(P2OS)—work to
These include
and control your
environments that
Bytes Value
2 0xFA, 0xFB
1 N + 2
N command
or SIP
2 computed
Figure 19. ActivMedia Robotics client-
server control architecture
Description
Packet header; same for client and server
Number of subsequent data bytes, including
the Checksum word, but not the Byte Count.
Maximum 200 bytes.
Client command or server information
packet (SIP)
Packet integrity checksum
ActivMedia Robotics
P2OS, of course,
Hence, P2OS-specific
29