Part of the RobotBrain project.

This is a page for discussing how [http://playerstage.sourceforge.net/ Player/Stage] can be used by the RobotBrain.

The most important part of Player is the client (device) side. And the protocol used to communicate with them.  We may (probably do) want to replace the server part with our own DAI scheme.  We would not be the first. The [http://orca-robotics.sourceforge.net/ ORCA] project discusses their motivation here [http://orca-robotics.sourceforge.net/faq.php#AEN28 FAQ].  Another interesting user of Player/Stage is the [http://marie.sourceforge.net/en/HomePage.html MARIE] which "uses the mediator design pattern for distributed system in order to cope with different applications not sharing the same communication protocol."

The [http://playerstage.sourceforge.net/doc/Player-manual-1.5-html/node69.html CMvision] player device documentation node leads to [http://www.exploits.org/v4l/ Video4Linux].
This and other video/vision can be discussed on BrainVision.

There is a wifi device driver in Player, it and other wifi can be discussed on BrainWiFi.

BrainMotion is for discussing making the platform move.  It may be possible to use a player position driver as-is.  Or we may need to adapt one.
Some of the more promising ones are part of a 'whole robot' package