Chris Hammond is
a father, husband, developer, geek, car guy. The Director of Training for DotNetNuke Corporation. To learn more about Chris check out the about me page.
LIVESTRONG Challenge Davis

I use Strava to track my bicycle rides. Below you can see my recent activity.

 

Follow Me Facebook Me Plus Me

Latest Photos

weblogs.asp.net
Wednesday, May 16, 2012 4:20 PM
If you are in the San Francisco Bay Area, or even feel like making a quick weekend tripI highly recommend checking out the Maker Faire this weekend in San Mateo, CA ( www.makerfaire.com ). I’ve posted a write up of some of my suggestions on what to bring...(read more)
Views: 110 Comments: 0
Chris Hammond
Wednesday, May 16, 2012 1:13 AM

The 2012 Bay Area Maker Faire is coming up this weekend in San Mateo, California. It will be about a mile from the offices of DotNetNuke Corporation so we will be heading over on Saturday as a family, and then I will likely go again on Sunday.

All the info about the faire can be found at http://www.makerfaire.com

After having attended last year, I have a couple of tips if this is your first time going. Here’s a list of what to bring, along with an explanation for each item.

  1. Bike – Ride a bicycle to the Maker Faire, you can save $5 on your ticket, and get access to the bike valet, plus you’ll be doing something good for the environment, get to avoid some of the traffic, and the parking last year was kind of nuts. I think I parked about 1/2 a mile away in a building’s parking garage.
  2. Cash – You will find so many things you want to buy, it will be better to have cash on hand Open-mouthed smile Bring lots of cash if you want to buy something like a 3D printer. I really wanted to last year, and will want to again this year, but the budget just won’t allow it yet. Maybe later this year. You should definitely check out the MakerShed, I did end up spending way more money than I planned last year after making a long stop there. There are also plenty of food options on site as well.
  3. Backpack – There will be plenty of swag to pick up, things to see, things to buy, have a backpack or something else to haul all your scores back.
  4. Camera – Screw it, you won’t need a camera, you need 3 cameras! I think I had 3 last year, seriously. I had my GoPro mounted on my head (video down below), my Motorola Xoom and my Motorola Droid. This year I plan on taking the GoPro, along with multiple batteries and SD cards, my Galaxy Nexus, and perhaps my Canon 5D Mark II. What kind of things might you take pictures of? Cupcake Go-karts, R2-D2, need I say more?
  5. Hat – It will be sunny and most likely sunny, and while a lot of Maker Faire is inside, even more of it is outside. Though if you don’t want to bring a hat there was a pretty cool custom leather hat stand (steam punk style) last year, perhaps I’ll break down and buy one this year.
  6. Family – I went to Maker Faire 2011 expecting it to be a male dominated tech event. Boy was I wrong. As soon as I walked in I regretted not bringing the wife and baby along. This year I won’t make that mistake, and the baby being 19 months now should definitely get a kick out of it. If you’re a single male, don’t let that scare you, it will be well worth attending for you as well.
  7. Time – There is so much at the Maker Faire, be sure to give yourself all day. I got there last year right as they opened up, and spend a good 4 or 5 hours there before I was baked and ready to go home. I’m in much better shape this year, hoping to last all day both days!
  8. Water – it may be warm, bring something to drink, preferably in a refillable container

What to expect at Maker Faire?

I seriously can’t even begin to describe what all you will see at the Maker Faire. Big mechanical dragons spitting flames, little Android robots, R2-D2 robots, steam punk hipsters, the Rally Fighter open source car, Wooden Bicycles, Rocks as big as a car that you can move,

Here are two videos from last year’s Maker Faire

and a time lapse of my day (at least most of it)

Views: 314 Comments: 0
weblogs.asp.net
Wednesday, May 02, 2012 12:03 PM
We’re in full swing for planning and preparations for DNN World 2012 this October in Orlando Florida. Our call for speakers is open for a couple of more days (5/5 I believe). The conference is 10/11-12 with pre-conference training on 10/10. More details...(read more)
Views: 138 Comments: 0
DotNetNuke.com
Monday, April 16, 2012 3:21 PM

Tomorrow morning I’ll be delivering one of our free DotNetNuke Explained web seminars, the 4th in our series of 6. This seminar is for Basic Module Development, in which I will show you how to quickly get up and running with custom module development for DotNetNuke.

If you haven’t signed up yet, you still can, go to the registration link. After the web seminar is delivered and posted online that same registration link will allow you to watch the recording.

In order to get up and running with module development it is best to have your module development environment configured. Due to the seminar only being an hour I will be jumping in after my development environment is already setup, but this blog post will point you to the resources necessary to get your own environment setup and running.

Rather than regurgitate information that is already posted, this post will simply point you to the appropriate resources.

We’ve got a thorough page in the DotNetNuke Wiki about Setting Up Your Development Environment. If you would like to try to follow along with the live web seminar, or the recording after the seminar, please first follow the steps outlined in that Wiki entry.

I will have completed all of the above steps on that Wiki page prior to the web seminar tomorrow morning.

Useful Links from Web Seminar

From there, I will do a few things in the webinar, I will refer to these links live, but finding them in the blog post will be helpful to many of you.

I will begin by downloading and installing the MSI for the MSBuild Community Tasks project.

Then I will be downloading and installing the custom C# project template from http://christoctemplate.codeplex.com, you can also find a VB.net version of the template as well.

If you would like to customize the templates prior to use you can find instructions for installing and customizing the project templates on this wiki page. I will not be customizing the template in the seminar.

After template installation I will walk you through the process of creating a project based on the template, the location as to where this project will live, and how it will work within DotNetNuke. We will make a few changes to the project to get it configured for our environment, then step through the process of packaging and installing the module within DotNetNuke.

From there we will actually add some functionality to the module utilizing Module Settings and code in our View and Edit controls.

For another approach to module development be sure to check out the Task Manager series of module development videos on the DotNetNuke Video Library.


More ...
Category: Extension Forge
Category: Reference
Category: Community
Category: Development
Views: 270 Comments: 0
Chris Hammond
Thursday, April 12, 2012 12:48 PM

In case you missed the announcement on 4/4, the guys and Secret Labs, along with other members of the Netduino Community have come out with a new platform called Netduino Go. Head on over www.netduino.com for the introduction forum post.

This post is how to quickly get up and running with your Netduino Go, based on Chris Walker’s getting started forum post, with some enhancements that I think will make it easier to get up and running, as Chris’ post unfortunately leaves a few things out.

Hardware

I ordered a variety of hardware when I ordered my Netduino Go here’s a list, though in this tutorial I’ll only be using a small portion of this.

  1. (1) Netduino Go
  2. (1) Shield Base Module
  3. (2) RGB LED Module
  4. (4) Button Module
  5. (1) Potentiometer Module

One thing to keep in mind with the hardware is that each module needs a cable to be able to connect to the Go, but the Go only comes with two cables. I did order a 5 pack of cables as well, and up until about 2 minutes ago thought I left them at the office, only to realize I do have them at home, which is going to change the rest of this tutorial.

Software

  1. Visual Studio 2010
  2. .NET MicroFramework V4.2

First and foremost, you need to install the .NET MicroFramework 4.2 and Visual Studio 2010 (not sure if express will work). Chris’ post assumes that you already have .Net MicroFramework V4.2 installed. You can download this from Codeplex though to be honest I don’t know if you need the PK or the SDK, I installed both.

What will the project do?

Before we get into actually creating the project, what will it be? Well this is just something simple, nothing useful, but hopefully gives you an idea how to work with the Netduino Go.

We’re going to use the Netduino Go, one Button Module, one Potentiometer Module, and 3 RGB LED Modules. The button will be used to turn the system on and off. The RGB LEDs will blink in succession, one Red, one Green and one Blue (I realized during the development that I only had 2 RGB LED Modules, so I removed Blue from the code with comments, I ordered two more they should be here Friday. The potentiometer will be used to control the timing of the light succession.

Project Creation

For the first part of this you can follow Chris Walker’s instructions posted in the thread, copied here for ease of reading.

To manually create a project for your Netduino Go:

  • Download and unzip the attached assemblies.
  • Create a new .NET Micro Framework "Console Application"
  • Add the references "GoBus.dll" and "SecretLabs.NETMF.Hardware.NetduinoGo.dll" to your project. You'll need to use the "Browse..." tab for the moment.
  • Add the references to the go!modules you'd like to use (NetduinoGo.Button.dll, Nwazet.Relay.dll, etc.)
  • At the top of your project, add the line:
using SecretLabs.NETMF.Hardware.NetduinoGo;

From here I’ll switch out of Chris’ examples and provide my own code.

Plug your NetduinoGo into the MicroUsb cable attached to your computer. It might take your PC a few moments to find the drivers.

Right click on the Project properties and be sure to change your target framework to 4.2. You’ll also want to change the Deployment options on the .NET Micro Framework tab in the project properties, Transport = USB and Device = NetduinoGo_NetduinoGo.

The first thing we’re going to do is initialize the objects we’re going to use.

static NetduinoGo.Button button = new NetduinoGo.Button(GoSockets.Socket1); 
// this button will start/stop the flashing
static NetduinoGo.RgbLed redLed = new NetduinoGo.RgbLed(GoSockets.Socket2);
// this is the socket for the first LED

static
NetduinoGo.RgbLed greenLed = new NetduinoGo.RgbLed(GoSockets.Socket3);
// this is the socket for the second LED

//static NetduinoGo.RgbLed blueLed = new NetduinoGo.RgbLed(GoSockets.Socket4);
// this is the socket for the third LED
public static bool currentState = false; // keep track of if the button was pressed to turn it on, or off static NetduinoGo.Potentiometer pt = new Potentiometer(GoSockets.Socket5);
// the potentiometer to control the speed of the LEDs

We’re going to have a single method that turns off all the LEDs, likely not the most efficient approach, but it will do what I want. We also provide the button handler event.

//method to turn off all the LEDs
static void AllOff()
{
    redLed.SetColor((byte)0, (byte)0, (byte)0);
    greenLed.SetColor((byte)0, (byte)0, (byte)0);
    //blueLed.SetColor((byte)0, (byte)0, (byte)0);
}

//button handler
static void Button_ButtonReleased(object sender, bool buttonState)
{
    currentState = !currentState; //set the state to the opposite of whatever we were before
}

The Main() for the project is a bit longer, but nothing too complex. Basically we wire up the button handler, make sure to start in the off state, and then setup our While loop. Because we’re running on a device, this loop While(true) will just loop forever.

Inside of the loop we’re going to check if we should be on or off, if on, we go through and pass through each RGB LED Module to turn it on, then sleep for a moment, how long is based on the potentiometer, and then turn off the LEDs, move on to the next color.

public static void Main()
{

    button.ButtonReleased += new NetduinoGo.Button.ButtonEventHandler(Button_ButtonReleased); 
// setup the button handler currentState = false; //make sure we start with it off while (true) //we're using a device, it will never end { if (currentState) // see if we should be displaying the LEDs or not { redLed.SetColor((byte)255, (byte)0, (byte)0); // turn on the red LED System.Threading.Thread.Sleep((int)(100 * pt.GetValue()));
// pause for a moment based on the potentiometer state
AllOff(); // turn off all LEDs greenLed.SetColor((byte)0, (byte)255, (byte)0); // turn on the green LED System.Threading.Thread.Sleep((int)(100 * pt.GetValue()));
// pause for a moment based on the potentiometer state
AllOff(); // turn off all LEDs //blueLed.SetColor((byte)0, (byte)0, (byte)255); // turn on the blue LED //System.Threading.Thread.Sleep((int)(100 * pt.GetValue()));

// pause for a moment based on the potentiometer state

//AllOff(); // turn off all LEDs } } }

Once you have all this together you need to be able to deploy the code to your Netduino. Deploying the code is easy, simply hit F5 in Visual Studio and that should send it off to your device. From there you can see how well it works.

Here’s a video of the code in action on my Netduino Go, I’ll see if I can’t get another video done when I get the third LED module in place (only 2 for now).

For another overview and tutorial check out Pete’s blog post over on 10rem.net

UPDATE

I've updated the code to work with 3 RGB LED modules, you can find the updated code on Github at https://gist.github.com/2418912 

Here's an updated video, filmed using a GoPro, let me know what you think of the video quality.

Views: 790 Comments: 0
RSS URL