Message types

The Player message types. More...


Detailed Description

The Player message types.

#define PLAYER_MSGTYPE_DATA   1
 A data message.
#define PLAYER_MSGTYPE_CMD   2
 A command message.
#define PLAYER_MSGTYPE_REQ   3
 A request message.
#define PLAYER_MSGTYPE_RESP_ACK   4
 A positive response message.
#define PLAYER_MSGTYPE_SYNCH   5
 A synch message.
#define PLAYER_MSGTYPE_RESP_NACK   6
 A negative response message.

Define Documentation

#define PLAYER_MSGTYPE_REQ   3
#define PLAYER_MSGTYPE_RESP_ACK   4

A positive response message.

Such messages are published in response to a PLAYER_MSGTYPE_REQ. This message indicates that the underlying driver received, interpreted, and processed the request. Any requested data is in the body of this response message.

Referenced by mbasedriver::HandleConfig(), ToRanger::ProcessMessage(), SphereDriver::ProcessMessage(), SegwayRMP400::ProcessMessage(), RFLEX::ProcessMessage(), MapTransform::ProcessMessage(), LaserTransform::ProcessMessage(), Khepera::ProcessMessage(), FromRanger::ProcessMessage(), ER::ProcessMessage(), EpuckDriver::ProcessMessage(), ClodBuster::ProcessMessage(), and AdaptiveMCL::ProcessMessage().

#define PLAYER_MSGTYPE_RESP_NACK   6

A negative response message.

Such messages are published in response to a PLAYER_MSGTYPE_REQ. This messages indicates that the underlying driver did not process the message. Possible causes include: the driver's message queue was full, the driver failed to interpret the request, or the the driver does not support the request. This message will have no data in the body.

Referenced by ToRanger::ProcessMessage(), LaserTransform::ProcessMessage(), Khepera::ProcessMessage(), FromRanger::ProcessMessage(), and ER::ProcessMessage().

#define PLAYER_MSGTYPE_SYNCH   5

A synch message.

Only used in PLAYER_DATAMODE_PULL mode. Sent at the end of the set of messages that are sent in response to a PLAYER_PLAYER_REQ_DATA request.