Microsoft Robotics Developer Studio Example

We've added some more support for Microsoft Robotics Developer Studio (MSRDS). The newest release adds Video and Direct Connect support to the API, expanding the large set of supported features. With the ease of Visual Programming Language (VPL) and inclusion of the precompiled Qwerk libraries, you can hit the ground running with your Qwerk. Sample VPL applications are bundled with the software, including a differential drive client with streaming video that lets you drive around a Qwerkbot using a GUI joystick. Make sure you have Microsoft Robotics Developer Studio 2008 CTP installed. Users with older installations will need upgrade to this newest release.

To download all TeRK source code, which includes the Microsoft Robotics Developer Studio libraries and examples, click on the "Download Source Code" link below.

Download Source Code »

Installation

Download the TeRK source code using the above link and follow the included installation instructions. Then follow the instructions in the TeRKClient/code/c#/MicrosoftRoboticsStudio/TeRK/README.txt file.

As described in the README, you can use the precompiled libraries with MSRDS right away with minimal effort. Just follow the instructions in the README and copy the required files, and the QwerkService should be available for immediate use in VPL and/or directly with your services.

Advanced users who wish to modify and compile the QwerkService themselves should also consult the README file for detailed instructions.

Usage

Once the QwerkService is installed, you can load up the sample VPL applications in TeRKClient/code/c#/MicrosoftRoboticsStudio/TeRK/QwerkService/SampleApplications to drive your Qwerk right away. Just modify the links going to the QwerkService with the DirectLogin and/or RelayLogin messages with your personal info (username, password, etc..) so the software can connect with your individual Qwerk.

Notes

There is an existing bug in the version of Ice we use that can cause Direct Connect to take upto thirty seconds for the initial connect. After connected, however, command and response times should be as immediate as you expect. We are working on a workaround and upgrading Ice in the meantime to try and solve this problem.