Bike Headlight

It gets dark early up here in winter, so I've got a little more to say about flashlights. About a year ago my wife and I sold my old Nissan Altima and I used the proceeds (and then some) to buy a nice bicycle for commuting to work. At this time of year, when I first got the bike, it's just getting bright enough when I come home from work that I didn't need much of a headlight, so I thought I was all set up with the cheap headlight from Fred Meyer. As winter came this year I quickly learned just how dark it gets by 5 PM up here in the northwest. I needed a better headlight.

Being the cost-conscious engineer that I am, I did my due diligence researching and looking around before I decided on a solution. There was no way I wanted to pay upwards of a hundred dollars for a headlight. For a while I thought about making my own headlight, but then I found a website that talked all about using flashlights as bicycle headlights (UPDATE: safer for work link, with more ideas). These were cheaper than the parts lists on instructables, more robust, and with this setup you could still easily use it as a regular hand-held flashlight when you weren't biking. I was sold. I headed down to our new Lowe's and got the Task Force 3 Watt LED Flashlight and some conduit hanger and rigged it all up:

I used some JB Weld to make sure the two hangers held together (at the enthusiastic recommendation of the Lowe's guy) and it works great. The flashlight is really bright, especially for only $25. The downside is that it rattles. It's not just the batteries, as the website states, it's something inside the on/off switch endcap. I haven't taken it apart to see if I can figure it out. I love having a light that bright and the rattles don't bother me very much. I worry more about blinding oncoming drivers. It's awesome.

I found a nice addition to my lighting system at Walmart not too many weeks later. They sell a bunch of different Coleman flashlights using Cree XR-E LEDs (the instructables people concur that those are the best). I bought a headlamp for $25 that is even brighter than that Task Force from Lowe's. I seriously could get by with just that on my rides home from work, but I use both now. The Task Force is more focused and goes farther, the headlamp beam spreads out more and lights up the road right in front of me better. With them both blazing I feel ready for the darkest of dark. Lights are cool.

Comments

Post a Comment

Popular posts from this blog

SystemVerilog Fork Disable "Gotchas"

This is a long post with a lot of SystemVerilog code. The purpose of this entry is to hopefully save you from beating your head against the wall trying to figure out some of the subtleties of SystemVerilog processes (basically, threads). Subtleties like these are commonly referred to in the industry as "Gotchas" which makes them sound so playful and fun, but they really aren't either. I encourage you to run these examples with your simulator (if you have access to one) so that a) you can see the results first hand and better internalize what's going on, and b) you can tell me in the comments if this code works fine for you and I'll know I should go complain to my simulator vendor. OK, I'll start with a warm-up that everyone who writes any Verilog or SystemVerilog at all should be aware of, tasks are static by default. If you do this: module top; task do_stuff ( int wait_time); #wait_time $display ( "waited %0d, then did stuff" , wa
Read more

'git revert' Is Not Equivalent To 'svn revert'

I just learned that if you have some changes in your working tree that you want to get rid of, you don't type 'git revert' like you might guess. No, that's what cvs, subversion, mercurial, and bazaar (to name a few) use revert to mean, but not git. With git, revert is used to undo actual commits. Thankfully, you can undo your revert with another 'git revert', I just learned. So let me repeat to be clear, if you have changes to your working files that you want to abandon, DO NOT do this: git revert HEAD That will undo your last commit. Do this instead: git reset --hard HEAD I'm glad I have that straightened out now. I'm wondering if /etc was really a good place for me to start out playing with git. UPDATE: Nearly two years later and I'm still getting comments on this. I'm glad I've been able to help people out this way. The discussion in the comments is good, and one thing I'd like to point out is that I now always use
Read more

Git Rebase Explained

Image
Introduction Rebase is a helpful git command that can be used to turn a branchy two-headed version history into an easy to follow linear one. A linear history is much easier for a human eye to follow and a human brain to understand. Rebase is a very safe command to use, despite some fear that people have about it. This post should explain how rebase works and clear up any misunderstandings about it. Rebase Basics The short summary of rebase is that it cuts commits out of the git history and reconnects them somewhere else. Let's say the common scenario comes up: you commit a change to the main branch of a repository, you then run  git fetch , and in come a couple changes that other people made on the main branch. If your commit is version 46f and the others that just came in on the fetch are versions ef9 and 4a2, your version history might look like this: The main branch now has two heads, 46f and 4a2. You can run  git rebase  to disconnect your commit from version d88 and connect i
Read more