Microsoft Gadgeteer

I just came across the Microsoft Gadgeteer website while doing some research for La Machine.

Gadgeteer allows you to quickly create prototypes without necessarily knowing electronics, just plug in, write a few lines (in NETMF of course) and you’re done. You can see a full demonstration on the Channel 9 website (Included below).

<object data="data:application/x-silverlight-2," type="application/x-silverlight-2" width="512" height="288"> <param name="source" value="http://channel9.msdn.com/scripts/VideoPlayer.xap?v=3.2"> <param name="initParams" value="deferredLoad=true,duration=0,m=http://ecn.channel9.msdn.com/o9/ch9/6d32/4015d252-f215-4945-9d48-9e0901306d32/dotNetGadgeteer_ch9.wmv,autostart=false,autohide=true,showembed=true, thumbnail=http://ecn.channel9.msdn.com/o9/ch9/6d32/4015d252-f215-4945-9d48-9e0901306d32/dotNetGadgeteer_512_ch9.jpg, postid=0"> <param name="background" value="#00FFFFFF"> <a href="http://go.microsoft.com/fwlink/?LinkID=124807" style="text-decoration: none;"> <img src="http://go.microsoft.com/fwlink/?LinkId=108181" alt="Get Microsoft Silverlight" style="border-style: none"> </a> </object>

For now, this product is still within Microsoft Research, but we could hope to see it commercialized by spring or summer 2011.

[Read More]

The Machine

In a previous post, I mentioned that I had acquired a FEZ Domino. I then started the project of building a robotic platform from it and improving it over time. So here is the beginning of The Machine.

Components

I bought a few components from RobotShop to start the construction of The Machine:

I also used a Logitech Dual Action USB game controller to control the robot. The Fez Domino supports joysticks, keyboards, and mice, so no driver needed.

[Read More]

I received my Fez Domino

After a few weeks of waiting, I received my Fez Domino ordered via RobotShop!

snapshot-3

This microcontroller running on the .Net Micro Framework (NETMF) is designed in the same format as the Arduino, allowing the use of its “shields”.

While waiting to play with it and give you my feedback, you can check out the following sites:

C# 5.0: Asynchronous Programming

For those who are not aware, you can download the Visual Studio Async CTP to get a preview of what is coming in the asynchronous world! This is just the CTP version, so there may be changes between this version and the official release.

Also, visit Eric Lippert’s blog to learn more about the topic.

Pyxis 2–An OS for the .Net Micro Framework

Pyxis 2 is an OS running on the .Net Micro Framework (NETMF). It can theoretically run on any NETMF platform, but it is currently configured only for GHI Electronics (Tinyclr.com) products.

To learn more, read the NETMF team blog or visit the official site. The code is available as open source at pyxis2.codeplex.com. Here is a video to whet your appetite:

Pyxis 2 Beta Released!

Reference Documentation

In the November edition of MSDN Magazine, Peter Gruenbaum explains how to write good reference documentation for APIs in his article titled “A Coder’s Guide to Writing API Documentation”.

My attention was particularly drawn to Figures 2 and 3, which explain how to comment while maintaining consistency throughout the API. I have reproduced them here:

Figure 2: Reference Documentation Style

Type Guideline Examples
Class Start with a word like “Represents” “Represents a user’s photo album.”
Methods and functions Start with a verb “Returns the number of contacts for the specified area.”

“Pauses the video.”
Properties Use a noun or start with verbs such as “Gets” or “Gets and sets” “The user’s tasks.”

“Gets and sets a collection of the user’s tasks.”
Events Start with a phrase such as “Raised when” or “Occurs when” “Raised when the response from server is received.”
XML elements Use a noun-based phrase “The city’s postal code.”
Boolean values For Boolean properties, start with “Indicates whether”; for Boolean return values on methods and functions, start with “Returns whether” “Indicates whether the control is visible.”

“Returns whether two regions intersect.”

Figure 3: Reference Documentation Example

[Read More]