News

Microsoft Releases Robotics Developer Studio 2008 CTP

Microsoft today released the first community technology preview (CTP) of Robotics Developer Studio 2008 at the RoboBusiness conference in Pittsburgh. The product is the third version of the robotics programming platform, which previously had been called the Microsoft Robotics Studio.

Microsoft Robotics Developer Studio 2008 (RDS 08) significantly improves runtime performance, from 150 percent to 300 percent, according to Microsoft General Manager of the Robotics Group Tandy Trower. "It's not the monolithic, single-threaded model that people have normally used for robots. Instead this is a more asynchronous, distributed approach to programming," Trower said.

Trower said RDS 08 will enable developers to write code and routines that rely on asynchronous message passing, providing for a more distributed runtime environment and expanding the potential for future robots to process and act on large volumes of information. According to a Microsoft release, RDS 08 adds support for distributed language integrated queries (LINQ), intended to enable "advanced filtering and inline processing of sensor data at the source."

According to Trower, the distributed application architecture will make it easier for robotic applications to access processing from remote sources, enabling a simple machine to act on complex processing done on a corporate server or in the cloud.

"You can have cooperative robotic interaction, because the robots can easily share information among each other," Trower said.

The RDS 08 CTP also provides improved sensor interaction, enabling sensors to send granular state change information to the processor, rather than requiring code that constantly checks sensor status.

Microsoft Robotics Studio was launched in 2006 to give developers a way to write high-level robotics applications without having to dive down into the minutiae of hundreds of different sensor and motor interfaces.

Ultimately, Trower said, the tools and techniques developers in the Robotics group could very well end up in mainstream development products at Microsoft.

"You will see that this year the core pieces -- the CCR, which is our concurrency coordination runtime and our DSS services, which is its companion that provides the concurrency model across the distributed network -- these pieces we actually will separate out and offer independently as well as in the toolkit, so that people who are interested in using this for [other] applications will be able to do that," Trower said.

"You will also see them positioned as part of the development tools family outside of the robotics area by our marketing team in our developer tools marketing group."

About the Author

Michael Desmond is an editor and writer for 1105 Media's Enterprise Computing Group.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube