31-03-2011, 04:06 PM
Presented by:
Sahithya B
[attachment=11438]
Microsoft Robotics Studio
Microsoft Student Partner
• PESIT
• Next Generation Robotics…!
• Requirements for
developing a ROBOT
• Sensors
• Controller
• Motors
• Wheels
• Power System
• Base
Shared Challenges…
Input from industry, hobbyists, academia, research, …
• Configuring sensors and actuators in running system
• Coordinating sensors and actuators asynchronously
• Monitoring/Interacting/Debugging running system
• Development when access to robot is limited
• Re-use of components across hardware platforms and devices
Microsoft Robotics Studio
Addressing the Challenges
• End-to-end robotics development platform. – authoring tools(VPL), Simulation…..
• Lightweight services-oriented runtime - (CCR-Concurrency and Coordination RuntimeDSS-Decentralized System Services)
• Scalable, extensible platform. - (Visual C#,Visual Basic, Jscript, IronPython….)
Microsoft Robotics Studio
Key runtime features
• Concurrency and coordination runtime
– Makes writing and managing asynchronous processes easy
– Avoids need to understand manual threading, etc.
• Decentralized system services
– Makes state observable, easily accessible
– Provides for reusability and failure tolerance
– Supports remote/distributed execution
– Makes the programming model scalable
Architecture of Robotic System
• Perceive – Sensors (Touch, Light, Ultrasonic, etc)
• Make Decisions – Logic (Computation)
• Take Action – Actuators
• Interact – User Interface and Communication
• Power Unit
• Communication
• Microsoft Robotics Studio package
• DEMO
One more thing…
Laws of Robotics
• Law 1: A robot may not injure a human being or through inaction, allow a human being to come to harm
• Law 2: A robot must obey orders given to it by human beings, except where such orders would conflict with a higher order law
• Law 3: A robot must protect its own existence as long as such protection does not conflict with a higher order law
» Issac Asimov, 1941