Brad Kratochvil wrote:
> I've been considering developing this type of interface for a while.
> It would be a "robot health" interface. A general interface could be
> written using a package such as libstatgrab
> (http://www.i-scream.org/libstatgrab/), so that everyone could use
> it. From the examples you gave, you could easily make all of those
> system wide parameters. There are quite a few you could provide based
> on that library, but the most commonly used 5-10 would really be
> usefull. You could also include a mechanism similar to what Reed
> mentioned to allow users to supply additional health metrics through
> the same interface. Let me know if you're interested. If not, I have a
the robot device i'm using have all this info available for me to read,
i'm only looking for the interface to pass all of it through.
a SensorArray interface may be the right thing, as for robot health , it
will suffer from commands that are device specific (like some existing
interfaces such as position).
maybe there should be some method for the driver to dynamically let the
client know which commands are available for use, a config request can
be used for this.