RE: Wish List

Dear Herman,

Thanks for your reply.  I don't consider myself enough of a robotics expert to do a great job of creating a detailed wish list.  But I will try to share with you a few ideas that may help.

A "snippet" of RIMCP might look like this:

Grasp("Wine glass 7",  0.3,  0.1)

where "Wine glass 7" is already defined as a "detailed 3D drawing", 0.3 is the maximum pressure in ounces that can safely be applied to the glass, and 0.1 is a measure of the rate of change in speed and inertia to prevent spilling the liquid in the glass.


Before I can write a wish list very well, I need more experience in understanding the work that has already been done in robotics.

In order for the master CPU to understand the "design of a new arm", during the learning process, a table of Range of motion values would have to be transferred from the arm's CPU to the master CPU.  Each Range of motion record would also need to have a torque rating, speed rating, and a way to "calculate" the available torque accurately at any given speed.  Each Range of motion record also needs to specify some details that enable the Master CPU to understand the full range of "combined" motions possible to acheive, based on an overview of all the range of motion records in the table.  Exactly how to do this is still a bit "fuzzy" in my head....:)

Once we have these "heavy duty theoretical pictures" in place, I think it will be easier to encourage mfgs to adopt our standards...mostly because they realize that it makes their job so much easier.

Sincerely,

Arthur Baldwin