Tagged Posts

Ever since I upgraded to Windows 10 (and then a couple of weeks later, paved the machine straight to Windows 10) I’ve been unable to install Quicktime, from Apple.

Here are a couple of time lapse videos from the winter (spring) snow storm here in St. Louis over the past weekend.

The first video got a couple of media inquiries via YouTube this morning, and was featured on Fox 2 here in St. Louis on their 5 o’clock news broadcast. It is an hour’s worth of shoveling on Sunday morning compressed into 27 seconds.

The second one is of our trip to see the Moolah Shrine Circus at the St. Charles Family Arena.

Both videos were shot with a GoPro Hero3 Black.

The @Netduino tank is finally ready for @makerfaire

It was About 8 or 9 months ago that I posted my first video using my Netduino powering a Tamiya Tracked Vehicle Chassis Kit. After that I actually did a little more work on the project, but I never posted any video or updates for the project itself.

Last week I was asked if I still had the project, and would be able to bring it to the Maker Faire. I thought, sure thing! So I got to work making it actually do something a bit more than going in a very long slowly arcing circle.

V1.5 (if you consider the video linked above v1) actually had a piece of plexiglass as a base, sitting on some standoffs up off the wooden base of the Tamiya kit. But it was my first time working with PG and I ran into a couple of issues, I drilled holes and they weren’t right, so I drilled some more, and they still weren’t right, the "rectangle” was off center on the vehicle itself, and I never even got around to taking the protective coating off the plexiglass. I did mount a GoPro camera on it, using zip ties, and drove it around the office scaring the pets, but never published that video, or even took pictures of the setup.

Thursday evening I decided I would try to take the motorshield I was using and make it work with the Netduino Go. Unfortunately due to a bug with PWM in .NET MF 4.2 qfe1 (or whatever is currently release) I was unable to get the Go working, so I wasted a full evening of time.

Friday evening I got to work getting the original Netduino going again, along with the motorshield, and a new piece of plexiglass. The end result was the photo seen above, a cell phone picture taken at something like 2 in the morning Saturday before Maker Faire, so I apologize for that :D

I ended up doing a little bit of coding, on the project (all sample code is hosted on Codeplex, at the time of this blog it is using Changeset 67198 (motor test project). I didn’t add a bunch of logic to the code, it basically has 4 programs, one that spins, goes, and repeats. Another that just spins. Another that goes forward then backward, and finally one that doesn’t do anything (stop). You can trigger through the programs using a button that was wired into the breadboard. Not the ideal setup, as the button was hard to get to while it was moving, but it was 2am and I just wanted to finish.

I made the programs fairly short because I figured that the area where it would be displayed wouldn’t be very big, unfortunately even with the short programs there wasn’t any way to safely have it running during the Maker Faire, so it for the most part remained unplugged the entire weekend. But it looked cool!

Speaking of looks, I took another piece of black plexiglass and cut it, shaped it on the belt sander, and then took the drill press to it to create holes for the standoff mounts, and somewhere to mount the Netduino/Shield to.

I also stuck an old (think original AAA battery powered, pre HD/960) GoPro camera to the front, this was all for show at this point, there was no chance I was going to get it wired up, and I really just needed the weight up there to keep the nose down. The back end was rather heavy due to the two battery packs, one for the Netduino one for the Motorshield, and it wanted to ride a wheelie without the camera up front.

Update (before I even posted the original blog) I stuck the GoPro 3D Case and two cameras up front to shoot some video and photos, you can see them below. This setup weighed the front end down heavily, and also, on a rough surface (bricks outside) started to cause problems for the tracks, I haven’t tried to figure out why yet, but they were coming off pretty regularly.

Here’s some video of the Netduino Tank in action, though I promise you it isn’t all that fancy yet Open-mouthed smile

and then of course 3D Video of what it sees (you’ll want to wear red/blue glasses for this one, or turn off 3D on youtube)

s

Photo Gallery

Parts List (quantity)

  1. Tamiya Tracked Vehicle Chassis Kit $20 (1)
  2. 9V Battery Case (1)
  3. AA Battery Case 4-AA (1)
  4. Plexiglass platform
  5. Long screws (4)
  6. Nuts, for above. (4)
  7. Aluminum spacers, mounted between base and platform (4)
  8. Small breadboard (1)
  9. Heat shrink
  10. Solid core wire
  11. Plexiglass sheet

What’s Next?

1) I would like to add some sensors to it so that it can move around on its own a bit, and know when it should turn around.

2) I’d like to get the Wi-Fi-bac for the GoPro Hero 2 setup, whenever it comes out (this summer) and mount a Hero2 up front so I can stream video using the camera. This wouldn’t actually wire into the Netduino in any way, but I can imagine putting the GoPro on a servo system so that the Netduino could at least “point” the camera, at what, I don’t know yet.

3) It needs either a remote control (DotNetNuke module) and Wifi access or some other wireless access to the tank and send commands.

The @Netduino tank is finally ready for @makerfaire

It was About 8 or 9 months ago that I posted my first video using my Netduino powering a Tamiya Tracked Vehicle Chassis Kit. After that I actually did a little more work on the project, but I never posted any video or updates for the project itself.

Last week I was asked if I still had the project, and would be able to bring it to the Maker Faire. I thought, sure thing! So I got to work making it actually do something a bit more than going in a very long slowly arcing circle.

V1.5 (if you consider the video linked above v1) actually had a piece of plexiglass as a base, sitting on some standoffs up off the wooden base of the Tamiya kit. But it was my first time working with PG and I ran into a couple of issues, I drilled holes and they weren’t right, so I drilled some more, and they still weren’t right, the "rectangle” was off center on the vehicle itself, and I never even got around to taking the protective coating off the plexiglass. I did mount a GoPro camera on it, using zip ties, and drove it around the office scaring the pets, but never published that video, or even took pictures of the setup.

Thursday evening I decided I would try to take the motorshield I was using and make it work with the Netduino Go. Unfortunately due to a bug with PWM in .NET MF 4.2 qfe1 (or whatever is currently release) I was unable to get the Go working, so I wasted a full evening of time.

Friday evening I got to work getting the original Netduino going again, along with the motorshield, and a new piece of plexiglass. The end result was the photo seen above, a cell phone picture taken at something like 2 in the morning Saturday before Maker Faire, so I apologize for that :D

I ended up doing a little bit of coding, on the project (all sample code is hosted on Codeplex, at the time of this blog it is using Changeset 67198 (motor test project). I didn’t add a bunch of logic to the code, it basically has 4 programs, one that spins, goes, and repeats. Another that just spins. Another that goes forward then backward, and finally one that doesn’t do anything (stop). You can trigger through the programs using a button that was wired into the breadboard. Not the ideal setup, as the button was hard to get to while it was moving, but it was 2am and I just wanted to finish.

I made the programs fairly short because I figured that the area where it would be displayed wouldn’t be very big, unfortunately even with the short programs there wasn’t any way to safely have it running during the Maker Faire, so it for the most part remained unplugged the entire weekend. But it looked cool!

Speaking of looks, I took another piece of black plexiglass and cut it, shaped it on the belt sander, and then took the drill press to it to create holes for the standoff mounts, and somewhere to mount the Netduino/Shield to.

I also stuck an old (think original AAA battery powered, pre HD/960) GoPro camera to the front, this was all for show at this point, there was no chance I was going to get it wired up, and I really just needed the weight up there to keep the nose down. The back end was rather heavy due to the two battery packs, one for the Netduino one for the Motorshield, and it wanted to ride a wheelie without the camera up front.

Update (before I even posted the original blog) I stuck the GoPro 3D Case and two cameras up front to shoot some video and photos, you can see them below. This setup weighed the front end down heavily, and also, on a rough surface (bricks outside) started to cause problems for the tracks, I haven’t tried to figure out why yet, but they were coming off pretty regularly.

Here’s some video of the Netduino Tank in action, though I promise you it isn’t all that fancy yet Open-mouthed smile

and then of course 3D Video of what it sees (you’ll want to wear red/blue glasses for this one, or turn off 3D on youtube)

Photo Gallery

Parts List (quantity)

  1. Tamiya Tracked Vehicle Chassis Kit $20 (1)
  2. 9V Battery Case (1)
  3. AA Battery Case 4-AA (1)
  4. Plexiglass platform
  5. Long screws (4)
  6. Nuts, for above. (4)
  7. Aluminum spacers, mounted between base and platform (4)
  8. Small breadboard (1)
  9. Heat shrink
  10. Solid core wire
  11. Plexiglass Sheet

What’s Next?

1) I would like to add some sensors to it so that it can move around on its own a bit, and know when it should turn around.

2) I’d like to get the Wi-Fi-bac for the GoPro Hero 2 setup, whenever it comes out (this summer) and mount a Hero2 up front so I can stream video using the camera. This wouldn’t actually wire into the Netduino in any way, but I can imagine putting the GoPro on a servo system so that the Netduino could at least “point” the camera, at what, I don’t know yet.

3) It needs either a remote control (DotNetNuke module) and Wifi access or some other wireless access to the tank and send commands.

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)

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.

I see that the GoPro HD Hero2 came out with a new Firmware update on 12/15/2011. I’ve been waiting for a firmware update to enable the 3d functionality on the new cameras since I received them back in November.

I installed the Firmware update using CineForm Studio (see the steps to upgrade the firmware (as of 12/16/2011) below.

The best I can tell, this V.58 firmware update does not enable the 3D functionality on the Hero2. I spent some time playing around with it, and was unable to get the two cameras to properly sync up when connected with the sync cable. First I could only get one to boot up, but I was eventually able to get both booted after removing the sync cable and inserting it again.

I would love to try to record Christmas this year in 3d, though I doubt we’ll see another firmware update again before the end of the year. I think V.58 was released to fix some exposure issues on time lapse caused by a previous update, but I don’t know that for sure.

Hopefully in the future GoPro will take the time to post a Changelog for their Firmware updates.

Steps to upgrade GoPro HD Hero2 Firmware (follow at your own risk)

  1. Have CineForm Studio installed on your computer
  2. Turn off, un plug, have a full charge and SD card in the camera, have CineForm Studio off
  3. Turn on your HD Hero2
  4. Plug the camera into your computer via USB
  5. Open CineForm Studio
  6. Wait for the update available message to appear (if there is one)
  7. Click update

Please follow the directions carefully, and check http://gopro.com/support/hd-hero2-firmware-update/ for further instructions.

I am not responsible if you damage your camera (I’ve done it before to my own camera)

The weekend before Thanksgiving I decided to strap one of my new GoPro HD Hero2 cameras on to my bicycle helmet and take it with me for a ride. I ended up with 1.5 hours of video, rather than let you watch the entire boring (wind filled) ride, I took some of the clips and put them together into a short video.
Last Wednesday I went for a ride at lunch time with a coworker of mine. I decided to take the GoPro Camera along with me for the ride, though not attached to the bike itself, or to me, I attached it to a 3 foot pole, that I mounted to the front of the bike. If you’re thinking “boy, that sounds like it won’t work” you are correct. It didn’t work out very well, the pole wasn’t near stable enough for the camera, so it made for a very wobbly video of the ride. I still think it is interesting though, so I editing, sped up, slowed down, and uploaded it to YouTube. You can see it here.

Today was the first event in the San Francisco Region’s slush series. I decided to head out and try to dust some of the rust off, and last night decided to build a camera mount for the car. After seeing the GoPro HD Hero2 launch video, I decided it was time to try to start getting more interesting video.

Earlier this week I attempted to do something interesting with video on my bicycle for www.bicycletips.com but the video turned out pretty bad.

For the 350z I wanted to try to get the camera up and behind the car. Not just on top of the car, but a couple feet back and above the car. So I got the building, really I didn’t build much, just assembled some parts that I had, and that I picked up from the local Ace Hardware store here in Half Moon Bay.

Holy Cow! If you live in the San Francisco Bay Area and don’t have plans tomorrow, or if you do have plans, cancel them. You need to get the Maker Faire at the San Mateo County Event Center. Check out www.makerfaire.com for more info! I went this morning, and I am going to go again tomorrow, this time taking the family with me. This morning I headed over with my GoPro camera attached to my head, with the intention of time lapsing the day. I stuck it to the top of a trusty Boston Red Sox hat, which I hoped would last.

So if you read my postings a month or two ago you know I had trouble with the GoPro firmware last time around. Ended up bricking the camera and having to send it in.

Much better luck tonight! I got V 1.1.5 upgraded without any trouble. I wasn’t sure what the camera had on it that they sent me in exchange for my repair, so I wanted to make sure I was on the latest firmware for the trip to San Diego. I’m hoping to timelapse the drive.

We’ll see if the batteries (2 of them) last the trip, I doubt it, but we’ll see. I have the camera set for shooting every 5 seconds and plan to mount it facing out the windshield.

Thanks for all of you who “like” Project350z on Facebook! We’ve seen some good growth the past couple of days!

So I went to the autocross today, kind of a last minute thing, and boy am I glad I did.

I left the house at 11:30am, got there and changed tires and then ran around 2pm (or after due to a bunch of timing issues).

I was pleased with my runs, my time being faster than a few cars I was sick of being beat by (ST civics!). Though when I went to check the results I was in 6th out of 7 in the Index class I run. I run Index, not in the standard BSP class at SCCA events because I want to compete against the fastest of the fast, no offense to the regular BSP competitors.

6th of 7, eh, at least I wasn’t DFL. But then tonight when the results are posted I ended up 10th on the overall index for the event! Woot!

*happy dance*

I believe the first heat of the day had a drying course, and the event overall was smaller (122 drivers) but I’ll gladly take a 10th on overall index any day here in the Bay Area!

I’ll post videos from the event tomorrow. I would have had three angles, but my original GoPro is such a POS that it didn’t get a single recorded video.

The night before an autocross, and I’m stoked for tomorrow, even if it rains (as forecasted). I got a replacement GoPro HD camera today in the mail.

For those of you who don’t know, I had a problem with my GoPro camera, which I use a LOT! I use it for autocross videos, and time lapse videos of working on the car. A few weeks ago I was working on the car doing a standard time lapse, but the camera freaked out. I came to find out that there was a bug in the camera software that would show up with time lapse mode after 10k (I think) photos were taken. It was a known bug though, and there was a firmware update for the camera to fix the bug.

So I applied the firmware update, but something during the process failed and the camera ended up “bricking” which basically means it wouldn’t work. You couldn’t power it on, you couldn’t use it, nothing, it was as useful as a brick. Since I got the camera for xmas it was still under warranty so I contacted GoPro about getting it fixed, while it took a bit of back and forth via email with their customer service reps, they provided me with an RMA number to send it in.

This was a couple of weeks ago, right before a 2 day autocross and right before we were heading out of town for vacation, so I didn’t get the camera mailed out until Tuesday of this week. On Thursday I got an email from them saying that they had a replacement camera ready to mail out, but I hadn’t included a return address. I replied with our address, and then on Friday I got an email saying it would go out. It is nice that we live about 15 miles from their headquarters because the camera showed up today via USPS.

I’m not positive that the firmware fix has been applied to this camera yet, but I’m going to leave it as is for now. I want to use it at the autocross tomorrow, so I don’t want to run the risk of bricking it again!

So I ran into a few issues today with my GoPro HD. I was working on the car, and was going to do another time lapse, even picked up a second battery last night so that I was sure I would get as much as possible.

So this isn’t the blog post I had intended to write today, but I think it’s a useful one nonetheless.

For those of you who autocross, or partake in any other motorsports. How do you travel with your video equipment? Discussion on where you mount your cameras and such, and what types of cameras will be left for another set of blog posts, but for now, how do you get your equipment to a race?

If you’re a small time autocrosser like me, you likely aren’t towing your car around on an enclosed trailer with lots of storage space.

At this point I have 3-6 potential video cameras I could take/use at any one race. Two GoPro’s (one HD and one of the SUPER CRAPPY original versions), a Chase Cam/PDR, plus a Canon HV10, 5d Mark II and a point and shoot that will do video. Now granted, I will almost likely never put the 5d Mark II on the car, I do take it to events so that I can take photos.

So what’s the best way to get things to an event? Right now I’m packing things into a lowepro 300aw, and that is probably the best solution for the time being, but with all that equipment I’m going to have to trim back what I put in the bag (less lenses for the 5D).

What do you use? A Pelican case? A bag? Something else?

I spent the last two days taking it easy on my abused body. Yesterday we went into town and did some walking around Main Street. I then spent most of the evening working on the Engage: Publish and Wiki modules for DotNetNuke. Today I stayed home all day and worked on some much needed modifications to the Wiki module, I had hoped to get it ready for another beta today but I wasn't able to get everything done that I needed. We were supposed to get a few big storms in the past two days. The storm for Wednesday didn't amount to much, though the one this evening was quite a storm. We'll see how much snow it actually deposited on the mountain as we head off to Park City Mountain Resort again tomorrow. Hopefully it will have dropped at least a few inches over there, perhaps they will even update their blog mentioning the results! More pictures and such tomorrow, perhaps even video if I can get the damn GoProVideo camera...
So today I chose to rest my aching bones by sleeping in while the wife took off with her father. After the bro/sis in laws showed up we headed off to the slopes. They were fortunate enough to get a free lift ticket for today as they flew in today and filled out a form online before they came. Talk about a deal, they got to ski today for $30 (for rentals), while I spent $90 just for a half day pass and my rental. I felt much better today, though it took me a little while to get there. I got a new board and boots today, the whole setup felt weird, I couldn't get my right foot to work right so I took a seat and adjusted the bindings myself. Not really knowing what I was doing I had hoped that turning my right toe more towards the front (I ride regular not goofy) would help. Sure enough it did. Once adjusted the board felt just like yesterday. From there I was more comfortable and running around the slopes. I definitely took some harder falls today than I did yesterday but that can be attributed to the fact that I was pushing harder today than I was yesterday. I'm not sure what the plan is for tomorrow yet, we're getting some much needed snow now. If it lets up we might give it a go again tomorrow, otherwise we might wait until Thursday and spend tomorrow doing some other activities around town. No photos from today, I tried hooking up my new camera from GoProCamera.com today but I wasn't able to get the thing working. If I don't have any luck later this week I might have to return the thing. Hopefully it will work though and I will be able to get some cool action footage (read: me falling a lot) Till the next...
RSS URL

Chris Hammond

Chris Hammond

is a father, husband, leader, developer, photographer and car guy. Chris has long specialized in ASP.NET and DotNetNuke (DNN) development, so you will find a variety of posts relating to those topics. For more information check out the about Chris Hammond page.

If you are looking for DotNetNuke consulting please visit Christoc.com Software Solutions

Find me on Twitter, GitHub and LinkedIn.