…begins a couple years ago when I started the Omnicopter. To fly the copter, I needed a remote. So, I built the Omnimote (right). It was a Panda-II powered remote that used XBee to communicate with the copter. It also had a small (slow) FEZ Touch display that was useful for displaying some info but had limited ability as a touch screen due to it being a resistive touch screen and it was just too slow to be depended on for use during flight.
As I’ve built other projects since then, it’s become more and more evident that I have a need for a universal device that can communicate and display information with other projects.
In the past year, most of my focus has been drawn toward the Gadgeteer platform for electronics prototyping. It’s a much more flexible and productive platform than anything else that exists at the moment and has dozens of powerful modules (subcircuits) that can be attached to it. Gadgeteer has become my go-to platform when developing electronics projects.
I’ve been doing quite a bit of Gadgeteer evangelizing the past year by giving presentations at our local .NET users’ group and at conferences. I’m also starting the Nashville Microcontrollers users’ group. So, the desire to have a truly portable and compact solution for demoing Gadgeteer in addition to something that is useful for my other projects has become a little more important.
However, one piece has been missing to allow me to build the Gadgetab of my dreams – a large capacitive touch display. GHI Electronics recently solved that problem with the release of their CP7 module – a 7” capacitive touch display. So, let the building begin!
The design goal was to build a tablet type device that could be useful as a remote, demo device, have some room for storage, be battery powered, and look nice – lots of software & sawdust.
The Mounting Plate
It just happened that I’d been talking to Steve Presley, who is starting up a custom CNC & 3D printing service, about building some mounting boards for Gadgeteer projects. I gave him some dimensions and he went to work. A few days later, I received a perfectly CNC machined piece of 1/4” blue acrylic in the mail and I went to work building the box that would house it.
Constructing the Box
I started by taking a scrap piece of 3/4” walnut and cut it into three pieces. Two long pieces (9 3/4”) would serve as the top & bottom sides of the box. A 6” piece was cut for the other two sides of the box.
The 6” piece was resawed using the table saw to produce two thinner pieces for the end sides of the box where the openings would exist.
After resawing, the side pieces were ripped into two pieces to allow for the space on the sides where the external connectors would be located.
Next, I used the router table to mill several dados in the pieces where they would fit together.
Time for a test fit. Perfect fit! :)
Let’s glue it up!
While the sides were drying, I worked on the top & bottom. I found a wide piece of 7/8” walnut and cut it to 9 1/2” x 7”.
I then resawed it on the bandsaw to produce two pieces roughly 3/8” thick. A quick pass on the thickness planer to smooth out the saw marks and ensure they were flat and they’re ready to go.
After giving the glue 24 hrs to harden, I took the clamps off and glued up the top & bottom. Glue was brushed on to ensure 100% coverage of the glued surfaces. Too much glue is better than two little. The right amount of glue will produce some squeeze out that will help ensure you have no gaps.
Using some scrap plywood as cauls to help ensure even pressure and to prevent the wood from clamp damage, I then clamped it up. Lots of pressure is essential here to ensure there’s no gaps and everything stays together.
Wait another 24 hours then take off the clamps. Note all the extra glue on the box. Also, I forgot to wax my scrap plywood and it glued to the box along the edges. Not a problem…
Using a hand plane and a card scraper, I removed the extra glue and plywood. Looking better, huh?
Next, I put a 3/8” roundover bit in the router table and rounded over all the edges of the box to make it comfortable to hold in my hands.
Using an orbital sander, I smoothed out any problem areas using 80 grit sandpaper then followed up with 120 grit sandpaper over the entire box. No reason to smooth it any further at this point. We’ll save the fine sanding for later.
Time to cut a whole for the CP7 display. Since it’s hard to see pen marks on the dark walnut, I add some green tape to the areas to be cut and then mark out the opening for the display.
Drill some holes in opposite corners big enough to fit a jigsaw into.
Cut out the opening using a jigsaw then remove the tape.
Time for a test fit. NICE!
So, you’ve probably been asking yourself… “Self, how’s he going to open that box since it’s glued together?” Simple, we’re going to cut it in half. Fortunately, we only have to saw two sides of this box since the other two are already open in the middle. We line up the saw blade so that it cuts perfectly with the edge of the opening and set the blade height so that it’s just a hair short of cutting all the way though. We don’t want to cut all the way though or the box will flop around when we cut the other side and will create unwanted damage from the saw blade. Cut both sides.
Using a hand saw, we’ll carefully cut out the hair thin piece that’s holding the two parts together. The box will likely pop apart shortly after you begin sawing.
Clean up the remaining bits of the thin strip using a box cutter.
Time for a test fit of the mounting plate. Oh yea!
Those joysticks need holes now…
Using a Forstner bit on the drill press, I make quick work of that task.
The joystick bases are semi-spherical and need a little more space. So, using a drum sander attachment on the Dremel tool we make the hole openings concave.
Time to cut the dovetails… We start by routing a dado where the dovetail sliders will run. This will remove a lot of the wood and make the actual dovetail slot much easier for the dovetail bit and prevent it from breaking. We do this in two passes. Cutting half the height in each pass. We repeat these steps for all four dovetail slots (two on the top and two on the bottom)
And finally, install the 1/2” dovetail bit and cut the slots.
Lookin’ good?
Now the tricky part… We have to cut the sliders so that they fit perfectly and don’t allow any slop and make the box appear lose. We cut some rectangular strips out of hickory (for color contrast) that are exactly the height from top to bottom of the slot and are exactly 1/2” wide. Keeping the dovetail bit at the same height, we adjust the fence so that it aligns over the bit such that the bottom corner of the bit lines up perfectly with the bottom edge of the hickory strip. Run each strip across the bit four times to cut the double dovetail slider.
Test fit. SMOOTH!
After sanding the entire box with 220 grit then some 400 grit sandpaper, it’s time to start applying the finish. I apply one heavy coat of Watco Danish Oil first and let it sit 24 hrs. Be sure not to leave any standing oil.
After the first coat dries, I lightly sanded the whole thing in 400 grit sandpaper. Then I repeated this process with four coats of satin wipe-on polyurethane. Then I attached the CP7 using the double-stick tape that is supplied. AFTER the CP7 is mounted, apply a coat of paste wax to the box and polish it to a smooth sheen.
This has been a fun project that yielded a platform that I’m sure you’ll see as an essential of many future projects. So, stay tuned and keep making!
Special Thanks
Steve Presley – for milling a perfectly fitting acrylic base plate. If you have any custom CNC or 3D printing needs, contact Steve.
Skewworks – for making the best UI controls available for .NET Micro Framework and letting me try out his new Tinkr controls.
GHI Electronics – for building the best Gadgeteer components and for setting the gold standard in customer support. They’ve also built the best NETMF/Gadgeteer community on the planet. Got Gadgeteer questions? Bring them to tinyclr.com.
Microsoft’s Channel 9 Coding 4 Fun site featured this project!
This is a project that’s been in the back of my mind for a long time but I just never seemed to find the time to build it. When I saw the new ATX Breakout Board by Dangerous Prototypes, I was inspired to get the project started.
This build is for my home office which I plan to eventually be completely decorated in fine hardwood (built by yours truly). So, I wanted this piece to be a blending of fine furniture and high tech. With that goal in mind, I got to work.
The dimensions of the box were based on the dimensions of my Rigol DS1052E oscilloscope which will sit on top of it for now. It’s a little deeper due to the requirements of the ATX power supply that sits inside. If my lumber had been a little wider, I would have liked for the box to been maybe an inch deep than it is. I didn’t end up with as much clearance as I would have liked inside the box.
The casing is made from a single piece of scrap walnut and the grain is maintained around the perimeter of the box. The top and sides are joined with a miter joint and the bottom fits on with a large box joint and is screwed on.
<-- No, that is not OSHA approved footwear.
Then I used a 1/4” straight bit on my router table to cut 3/8” deep dados for the front and back panels to fit into.
Note that after a test fit, I later realized that the dados needed to be extended all the way through the feet of the box so that the front & back panels could be removed after everything was glued up. One of my design goals was to make it so that I could easily remove & modify the front and back panels later if I come up with other things I want to add. This list has started already….
After cutting the front & back panel blanks out of 1/4” hardboard, it was time for a test fit. The bottom was sanded a bit to make it easy to put on & off then it was time to start the glue up. I used a tape clamp method to glue up the miter joints. To do this, you just fit the top & sides together tightly while laying on a flat table and then put some 2” masking tape the full length of the joint.
Flip the parts over and glue thoroughly and spread with a glue brush so that both sides of the joint are fairly heavy in glue. It’s better to have too much glue than too little since the squeeze out will help fill in any cracks you may have in your joint.
Since the box bottom is held on with screws and is not glued, I was able to take advantage of this and use the screws to hold the box together while the glue dried.
I gave the box 24 hours to dry before doing anything else with it. In the meantime, I started work on the front panel.
The ATX Breakout Board breaks out +12V, +5V, 3V3, –5V, and –12V. I had some premium screw down banana plug studs that I had bought for this project months earlier. The breakout board comes with some cheap banana plugs. So, they went into my parts bin.
I laid out the parts on the front panel and drilled all the holes for the banana plugs, LEDs, main switch, and the breakout board. I wanted everything mounted on the front panel so that if I wanted to make any adjustments, I would only have to unplug the power supply and slide out the front panel without worrying with parts attached to the case in other places.
The ATX Breakout Board comes with a push button switch soldered on. This wasn’t going to be of any use to me since I planned an external toggle switch. Unfortunately, the switch that came on the board was going to be in the way of my power supply. So, it had to be removed. This wasn’t a simple task. In the end, I decided that destroying the switch was going to be the easiest and most time efficient solution. I would recommend to Dangerous Prototypes that they leave this switch unsoldered. It’s a lot easier to solder the switch on than it is to remove.
Once the glue was good and dry, I put a large roundover bit in my router table and rounded over all the outside edges of the box and sanded it down to 400 grit and finished the walnut with a first coat of Danish Oil and then a couple coats of rub on polyurethane.
The power supply is mounted to the top of the box with an angle bracket and screws. A piece of wood was glued to the bottom inside of the box that is equal in height to the spacing between the power supply and the bottom as a way to hold up the front side of the power supply. The back side is held up by the back panel.
Note the air holes drilled in the bottom at the front of the power supply.
The power supply has a built-in blue LED glow :)
The green LED in the top left corner is the mains power indicator.
The plugs aren’t labeled yet. I’m still searching for a more elegant way to do that than just sticking on labels. I may actually end up having a piece of 1/4” plywood laser cut & etched at some place like Ponoko to make a new front panel. The empty area to the left of the plugs is dying to have a logo or something etched on it!
This has been a fun project and I especially like the blending of woodworking & technology. These are the types of projects I had in mind when I started “Software & Sawdust”. I plan to do a lot more like it in the future. Stay tuned!
EDIT: As many have pointed out and I failed to mention in the original post, the DP ATX Breakout Board has 1.25 amp polyfuses which seriously limits the power supply in it’s current state. I’m in the process of sourcing replacements for those polyfuses that will allow better utilization of the full capacity of the ATX power supply.
7/18/2012 – Woo! Hoo! The folks over at Dangerous Prototypes blogged about this project.
With such short notice of the Red Bull Creation contest and so little time before the deadline, I had to come up with a project quickly that would fit into activities I already had planned for the Independence Day holiday weekend. Also, there wasn’t time to order parts so it had to be a project that we could build with parts I already had or could obtain locally.
“A Better Fish Trap” was envisioned. I had planned a fishing trip with the kids and this project would be fun for us all and should be a fairly quick build that shouldn’t occupy my entire weekend.
When I go fishing there’s really only one type of fishing I’m interested in – CATFISHING! Aside from saltwater fishing, there’s nothing better than sticking some chicken liver on a hook and tossing it out to the depths of a lake and waiting…for a monster cat. Depending on how hungry the fish are feeling, you may wait minutes or hours before a hungry catfish finally takes the bait. Depending on how relaxed you are, this could result in a missed opportunity.
With “A Better Fish Trap”, you’ll never lose another opportunity to yank a big fish out of the water. The project was to build a stand that you would prop your fishing pole on. When a fish bites the bait and causes the pole to be yanked, a “tug sensor” (aka momentary switch) would be switched and the Bullduino would play an alarm through a couple of Red Bull speakers (empty Red Bull cans with piezos inside them) to awaken alert the fisherman. Since it is also popular to fish for catfish at night using multiple rods, I also added some RGB blinky LEDs to the bottom of the cans that provide a visual indicator of which pole needs the attention. What catfish could resist the call of disco lights and piezo music?
Here’s the submitted video with build details in the last part of it. If anything isn’t obvious, feel free to comment below and I’ll fill in the gaps.
2012 Red Bull Creation–A Better Fish Trap
Electrically, the Bullduino is very under-utilized. If I’d had time to order parts, I would have probably gone overboard and ordered an accelerometer to use instead of the momentary switch. This would have perhaps made the physical build a bit simpler and created more programming work. This might have made the project a little more interesting academically. However, the project worked perfectly as it is designed. Here’s the full schematic.
The arduino code is equally simple. Basically, it waits for the momentary switch to be triggered and then responds by activating the blinky RGB LEDs and playing tones through the piezo speakers. Examples of doing both are in the built-in Arduino examples but if you would like the code, feel free to ask and I’ll send it to you.
This was a quick fun project that I got to have fun & share with the family. Many thanks go out to the Red Bull folks for helping to inspire so many with such a wonderful contest. I’m already looking forward to next year’s Bullduino!
Four days ago I learned of the Red Bull Creation contest. I thought “Cool. It’s great to see caffeine pushers out inspiring minds to be creative!”.
Then I went to their website. It was immediately clear that these guys mean business and they have some serious talent working on their behalf. The retro OS site is probably the coolest thing I’ve ever seen on the web. Have you ever been to a web site that has a command line shell for navigation???
If you fill out the application and they pick you as a contestant then you get a really cool Red Bull custom Arduino microcontroller board. So, I filled out the application without really thinking what I would build.
Yesterday, I received an email saying that they were sending me a Bullduino and I had until July 3rd to build something and submit a video! That’s seven days to come up with an idea, build something, and then create a two minute video. Two of those days are on a weekend. I’ve spent that much time just putting together the video for other contests.
My first thoughts were that the board wouldn’t even arrive in time to even start building. Forget having time to order parts. Then it occurred to me that this is all part of the plan. In the final round, the top entries that are submitted will have Red Bull camera crews come to their house/shop/hackerspace to film them for 72 hours as they build their final entry. This is not a contest where you have three months to polish something off. This is a contest of off the cuff ingenuity. Love it.
So, it would seem that this first round has the same theme – think fast and build something great using only the parts you have lying around or can round up quick. This wasn’t really in my schedule for the weekend before Independence Day but maybe a light bulb will go off and I’ll come up with an idea that I can do quickly.
To my amazement, the board was shipped overnight and arrived today! Maybe there is hope that I can salvage a project out of it. The packaging of the board and the board design continued the high quality precedent set by the website. I’m starting to get a little excited about this now.
Inside a FedEx overnight envelope was a thin brown box with the wise words of Yoda laser etched into the brown cardboard cover – “TRY NOT. DO, OR DO NOT. THERE IS NO TRY.” I’ll be framing that for my office :)
Awesome! Getting a little more excited. The cover is held on with some weak double-sided tape to reveal the Bullduino that hides inside.
How cool is that? Immediately, I’m thinking “Battarang?” Down boy…we only have six days left. Hmmm…
The case is a four-layer (plus the top) laser cut corrugated cardboard sandwich that’s taped on the edges. Nice and simple yet very elegant.
Taking out the board, reveals yet another surprise. Underneath the PCB, on the bottom of the box, is laser etched “YOU’LL NEED THIS TOO: goo.gl/eB7on”. Following the URL leads to a download for the Bullduino.inf driver file.
At this point, I just had to plug the board into a USB cable and install the driver. Once it was plugged in, two green LEDs illuminated. The top one started flashing a pattern that repeated after 10 seconds or so. I realized this must be a Morse code message.
Despite over 15 years in Boy Scouting, I’ve never learned to read Morse code. So, I made a video so I could slow it down.
Even by slowing the video down to 1/8th speed it proved to be a challenge for me. After play/pause/rewind… for about 20 minutes, it then occurred to me that someone has probably already figured this out since I was so late to receive my board. Sure enough…the folks over at the Harford Hackerspace already cracked the code and determined that it says “‘Wouldn’t lou prefer a good game of chess?” They speculate that the “lou” may be a clue to something else hidden in the board.
Back to the board…well, actually the backside of the board. The main processor is a ATMEGA328. Of course, it has an Arduino pin form factor. A few things immediately jumped out at me as unusual. First are the three sets of pads in the middle of the board labeled “CONN5”, “CONN6”, and “CONN7”. At first glance, I’m not sure what these are for. They certainly aren’t standard on any Arduino I’ve seen.
Secondly, in the top left corner is a little yellow round part. It is the reset button. They definitely decided this would be a good place to save a few bucks. It takes a little more effort to get a good press on it than it does a normal momentary switch used on most Arduino boards.
That’s all for now. Now to figure out what to do with it! Let the fun begin!
I woke up this morning to a great surprise. I received a letter from Make: magazine informing me that I’d been selected as one of the members of their new beta team.
I’m honored and excited to be a member of this team of about 100 members worldwide that will have the privilege of building projects for the magazine before the articles are published as a way of beta testing the build instructions.
Make: decided to start this team back in March and I thought it sounded very much in-line with what I do in my spare time anyway so I filled out the application. Apparently, so did about 1100 other folks. So, I feel very lucky to have been chosen.
What does this mean? Well, I don’t fully know yet. What I do know is that I’ll randomly be delivered a project and all it’s parts & pieces and asked to build it and discover if the instructions need to be improved and report back. We get to keep all the projects and part of our job is to show them off to friends & family and get input back.
We’re allowed to blog about our experiences building the projects. So, be looking to hear all about it here and I’ll be looking for feedback from you. It’s not clear to me yet whether we can blog while we’re testing or after the magazine has been published. So, check back every day just in case ;)
Make: can be considered the handbook of the Maker Movement. If you’re not familiar with this movement, there’s a good overview of it here. I’ve been a Maker all of my life. In the past we’ve been called tinkerers, hackers, warranty voiders, nerds, geeks…. I like this new name and the positive movement that it has created.
I’m teaching a NETMF Gadgeteer lab for the Nashville .NET User’s Group this week. Our gracious sponsors have purchased several FEZ Hydra Basic Kits made by GHI Electronics that we’ll be using to introduce everyone to the Gadgeteer world.
The FEZ Hydra Basic Kit consists of:
So, the challenge is what can we build with just these components?
THE PLAN
We’re going to build a simple project that will use the green LEDs on the outer ring of the LED7R module as a gauge to show the light level that is reported by the LightSense module. In the center of the LED7R module is a bright red LED. I’m going to use the Joystick module to vary the brightness of this LED.
CREATING THE PROJECT
Before we can start assembling pieces and writing code, there are some prerequisites that we need to ensure you have on your laptop. Install all of these if you don’t have them already. Make sure that you are running the latest versions.
Visual Studio 2010 (or later). Any flavor will do including Express.
Now that we have all of the bits installed, open Visual Studio and go to File –> New –> Project. From the “New Project” dialog, we’ll choose the “Gadgeteer” section underneath the “Visual C#” group and we’ll create a new project using the “.NET Gadgeteer Application” template.
After we click “OK”, a new Gadgeteer project will be created and the Gadgeteer GUI designer appears showing an image of the FEZ Hydra mainboard. If we open the Toolbox we will see a list of modules under the “GHI Electronics” section. We’ll select the Joystick module and drag & drop it onto the white area somewhere around your mainboard. Then we’ll do the same for the LED7R module and the LightSense module.
If we left-click on the socket (the orange box) on our module then compatible sockets on our mainboard will be highlighted in green. We can then drag the connector to the compatible socket that we want to plug the module into and click. The sockets will then turn blue and a blue wire will be drawn between them. Repeat for the other modules.
Now we’ll connect our physical components & cables up to match the connection decisions we made in the GUI designer. Also, we’ll plug our SP power module (the red one) into the D socket (#2) and connect the USB cable to it and to our computer.
TIP: The name below each module in the GUI is the variable name that you’ll use in code to reference the module. If you want to change it, you can do so by click the name in the GUI a couple times to get into edit mode. If you change it after code has been written then your code will automatically update.
Let’s write some code!!!
HELLO WORLD!
Now that everything is connected and powered up, we should see a red LED on our power module, on our mainboard, and on our LED7R module.
Next, let’s make sure that our project is configured to run on our Hydra and not the emulator. In the Solution Explorer, we’ll right-click on our project and go to Properties. In the Properties page, choose the “.NET Micro Framework” tab on the left. We’ll choose the “USB” Transport option. When we do this, the “Device” should automatically populate with “FEZ Hydra_Gadgeteer” (assuming we only have one mainboard connected to our PC). Save your options and close the page.
Hit F5! If everything is connected correctly, the default program should compile and deploy to the Hydra and in our Debug Window we should see a lot of memory information flash by and then finally you should see…
LED7R MODULE
We’ll start by writing a quick test of our LED7R module. Note that I have renamed my module from it’s default name to “led” in the code below.
The LED7R module has the following methods available to it:
Animate()
Cycles through all the LEDs on the module in a circular pattern. There are parameters to determine speed, direction, whether the lights are to be turned on or off, and an option to leave the lights on or to turn them off before moving to the next one.
TurnLightOn()
Turns an LED on. It has one parameter – the number of the LED to turn on. Note the “D” numbers printed next to the LEDs on the module. They are the index numbers.
TurnLightOff()
Turns an LED off. Same parameter as TurnLightOn().
Let’s add some code to test out our LEDs. In the Program.cs file in ProgramStarted() let’s add the following code below the Debug.Print line that was added automatically.
1: // Cycle through the lights to show we're alive.
2: led.Animate(100, true, true, false);
3: led.TurnLightOff(6); // a bug causes the last light to stay on...
Hit F5 to compile, deploy, & run the code and you should see the LEDs on the module light up in a clockwise direction.
LIGHTSENSE MODULE
Now that we know our LED7R module is working fine, let’s do something with our LightSense module. The LightSense module has two methods. Both are used for polling the sensor to capture it’s settings.
ReadLightSensorPercentage()
Returns the light level as a percentage value from 0.0 (dim) to 1.0 (bright).
ReadLightSensorVoltage()
Returns the light level as a measure of voltage from the sensor (0V-3.3V).
As you can tell from the methods, to do anything with the meter we are going to have to poll it on a regular basis. For this we’ll need a timer. At the bottom ProgramStarted() let’s add the following:
1: // Light meter
2: var timer1 = new GT.Timer(100);
3: timer1.Tick += OnLightMeterTick;
4: timer1.Start();
And let’s add a new function to our Program class…
1: privatevoid OnLightMeterTick(Timer timer)
2: {
3: var lightLevel = (int) lightSensor.ReadLightSensorPercentage();
4:
5: for (var ndx = 1; ndx < 7; ndx++)
6: {
7: if (ndx <= lightLevel/100.0*7)
8: {
9: led.TurnLightOn(ndx);
10: }
11: else
12: {
13: led.TurnLightOff(ndx);
14: }
15: }
16: }
Run the code again and you should now see the LED7R do it’s initialization loop and then the number of LEDs lit should vary depending on the brightness that the LightSense is reading. Try moving your hand over the LightSense module. The number of LEDs lit should decrease.
Having fun yet?
JOYSTICK MODULE
It’s time to put our hands on this thing! I bet you never thought you’d be able to actually touch a C# project :D
The Joystick module moves in X & Y directions and has a button we can use when the stick is pushed downward. We’re going to use the Y (up & down) direction of the Joystick to dim the red LED in the middle of our LED7R module. Fully explaining the Joystick module is beyond the scope of this post. I’ll do that in the near future.
But wait! If we take another look at the LED7R module we’ll notice that there isn’t a method we can use to dim LEDs. What to do? We’ll use an optical trick called persistence of vision (POV) to make the LED appear dim by using a timer to pulse the light on & off many times per second and vary the length of time that it is on between pulses.
Add the following to ProgramStarted():
1: // Monitor joystick to update red LED brightness.
2: var timer2 = new GT.Timer(10);
3: timer2.Tick += OnRedBrightnessTick;
4: timer2.Start();
And let’s add this new function to our Program class…
Run the program and now when you move the Joystick up & down you should see a slight variation in the brightness of the red LED in the middle of the LED7R module.
Surely, you’re having fun now???
You may be asking yourself why we used Timers instead of just putting a loop in our ProgramStarted() event. This is one area where Gadgeteer is very different than traditional NETMF projects. Read this blog post for an excellent explanation and you’ll save yourself some frustration down the line.
WHAT NEXT?
Well, that’s up to you! I’ve given you a simple example of a couple things you can do with the FEZ Hydra Basic Kit. Now, take this example and improve it or come up with something better (a game maybe?). Be sure to leave a comment on this post and tell me what you did or even better post a link to a video.