Interface specifications
[libplayercore]


Detailed Description

All Player communication occurs through interfaces, which specify the syntax and semantics for a set of messages.

See the tutorial Interfaces, drivers, and devices for a discussion of what an interface is.

Below are the details. For each interface, the following is given:

It can be the case that a given message can be sent as data or in response to a request. A common example is geometry. For many devices geometry is fixed and so need only be requested once. For others geometry may change dynamically and so the device will publish it periodically.

Todo:
  • Normalize subtype names (PLAYER_PTZ_REQ_GEOM vs PLAYER_POSITION2D_REQ_GET_GEOM)
  • Normalize subtype numbers (PLAYER_POSITION2D_SET_ODOM = 6 and PLAYER_POSITION2D_RESET_ODOM = 5, while position3d has PLAYER_POSITION3D_REQ_SET_ODOM = 5 and PLAYER_POSITION_3D_REQ_RESET_ODOM = 6)


Modules

 actarray
 aio
 audio
 audiodsp
 audiomixer
 blinkenlight
 blobfinder
 bumper
 camera
 dio
 energy
 fiducial
 gps
 graphics2d
 graphics3d
 gripper
 ir
 joystick
 laser
 limb
 localize
 log
 map
 mcom
 opaque
 planner
 player
 position1d
 position2d
 position3d
 power
 ptz
 simulation
 sonar
 sound
 speech
 speech_recognition
 truth (deprecated)
 waveform
 wifi
 rfid
 wsn

Last updated 12 September 2005 21:38:45