We look for a generic layout for information communication between components and middlewares, blender and middlewares..
(Thanks to notes from the irc #blendercoders and the robotics mailing list : email@example.com - Benoit Bolsee, Markus Mehrwald and others)
In the blender game engine it is possible to add a python controller that runs on every frame. This controller can be stopped or wait for an external signal thus blocking the actual game engine frame thread. Enabling the compute all frame options will make the game physics calculation consistent as if each next frame was played exactly 1/frame_rate seconds since the last frame.
- Need of a generic interface with middlewares
Middlewares and blender components
Separate the configuration files for middlewares from the blender files. Add a dynamic link to them
Handling sensor messages PUSH/PULL
For now morse sensors constantly send data PUSH but in some cases ( robots with plenty of sensors for examples) we'd rather use a request-based communication PULL.
Decoupling distribution aspect from architecture.
Clarify how to build a sensor
Sensor python class
To write yours you need to define the following functions:
Clarify how to build a robot