From BlenderWiki

[edit] Blender and middlewares

[edit] The interfacing route

-> Python ?

-> C ?

-> at which level? custom sensors/actuators? only accessible through Python API?

[edit] The simple Python route

An "always" sensor call a Python controller that write or read data to/from the middleware. Some initialization/finalization can be done through "runOnce"/"quit" sensors.

See a Robotics:Middleware/YARP

[edit] The "sensors/actuators" route

Implement custom sensors/actuators that read/write from the middleware.

Some background on the Robotics:Sensors, Controllers, Actuators architecture in the GameEngine by Benoit Bolsee.

For the sensors, it would requires a event loop to trigger the sensor.

[edit] Non-exhaustive list of potential targets

• YARP (MIT/IIT Yet Another Robotic Platform)
• ROS (Willow Garage's Robotic Operating System)
• VRPN (Virtual Reality Peripherical Network)
• OSC (Open Sound Control, that came out of the music world but seems to have grown far beyond that -> Nick Porcaro successfully interfaced it with Blender)
• OpenRobots (LAAS middleware -> interfacing will occur most probably through other middlewares)
• Verse (see below)

[edit] Verse

• Pros:
  • + already closely integrated with blender
• Cons:
  • - No good armature support
  • - No support in Game Mode
  • - Not been edited in a long time (like 2006)

-> Overal not a good idea.