12-09-10
It’s nearly Build18 time again. Here’s a couple hints as to what I’ll be working on.
Hint 1: I’m a SRAM guy
Hint 2: I can’t afford a $2000-$3000 upgrade
Hint 3:
Hint 4:
P.S - I swear I’ll post an update on the final status of last year’s project. Here’s a picture though.
01-14-10
It’s 5:40 am and I just got out of the robotics club. I’ve got class in a couple hours so in the interest of being able to retain information tomorrow, I will forgo a blog post for tonight and instead write something tomorrow.
Today (very) briefly: Got wireless working, cut out a whole Arduino, fully planned jacket stitching, finished new laser mount (version 3.0), went to a cool tech talk, looked into cheaper communications packages.
01-13-10
Today was a fairly productive day, though not as productive as I would have hoped. I made some headway on all aspects of my project, but didn’t get very far in on any of them.
I was able to delegate some of the sewing for the jacket to my wonderfully crafty girlfriend and she was able to sew on both sets of LEDs. Unfortunately, I wasn’t able to stop by her apartment so I don’t have any pictures to upload yet. Fear not, though, as I will have some tomorrow! I have yet to design the circuit for the Lilypad Arduino, XBee carrier and power supply, but that should come very soon (hopefully tomorrow, er today. I really need to stop writing these at 2-3am).
On the XBee front, I was able to get my two XBees communicating with the help of some fellow Build18 participants. It’s a great feeling when you have two computers talking over hardware you configured, even if it’s the most unnecessarily complex IM protocol/client in existence. Now that my communication problems are over with, I can set my attention back to writing code and designing the circuits needed to interface the two major subsystems.
Despite the absence of two of the three lasers I will need to complete the project, I have begun designing the laser mounting system. This is a nice challenge for me as I don’t often get to use my mechanical design and machining skills. I’m a bit out of practice, but I drafted a design by hand, modeled it on the computer, and eventually milled some prototypes. Unfortunately, the Roboclub shop was out of drill bits large enough to support the laser. I learned this only after spending four to six hours milling the parts and saving the large hole for last. Needless to say, I was upset. Thanks to friend and fellow Robotics Club officer Dan Shope, I have a new design that will be significantly easier to machine and much more likely to be finished tomorrow. I will upload the drawings of my first prototypes tomorrow and hopefully some pictures of the new design as well.
One part of my project that I haven’t focused much on yet (with the exception of keeping up these fairly regular blog posts) is the publicity aspect. I’m beginning to see myself advertising my project more and more which is kind of cool. I attended a meeting of the ECE department’s Student Advisory Council with some other Build18 participants (not entirely because of the free food, I swear!) and gave a little spiel on my project. I’m getting better at making my elevator pitch for the project; I can describe it well in about 45 seconds to a minute. An interesting thing I learned at the meeting was that one of the Build18 sponsors (Qualcomm, I believe, but it could also be Google or Sparkfun) would be sponsoring an award for one of the projects. I’m super excited! There are a lot of cool projects so it’s good to see someone will be recognized. I also learned that although there is a project demo session in 2-3 days, there will be a final unveiling at the end of the year. This means that I might have a chance to put some real effort into the aesthetics of my project which I’m also really excited about! Can you say vacu-forming?
I apologize if this post seems a little scattered, but it’s about 3:20am and I’m not quite awake any longer. In any case, expect pictures of the jacket in progress, drawings (and possibly pictures) of both the failed and not-so-failed prototype laser mounts, and an update on the XBee circuits
01-11-10
This is going to be a shorter post than yesterday because not much progress was made.
Today was the first day of classes so I had a good chunk taken out of my normal hacking time. In any case, I wasn’t able to get past some problems I’ve been having with the XBee chips and getting wireless communication to work. Despite that, I acquired (thanks to my ever-patient girlfriend) a hoodie to use as the base for the turn signal jacket and got some planning done for the laser mounts that I’ll have to machine either tomorrow or the next day. Additionally, I got the acrylic I’ll be using to turn the point from the laser pointers into a line that will be visible on the street.
In order to have something pretty (aka a picture) to post, here’s the test circuit I promised yesterday (click the picture to read the annotations better).
Test Circuit for turn signal code
If there’s interest in a schematic, I can post one. I think it’s pretty clear from the picture what connects where, but if you’d like a schematic, let me know in the comments. It’s a bit too late right now for me to draw one up because I’m sure I’ll make a mistake in my sleep-deprived state.
That’s all for today. Expect a breakthrough on wireless communication and some pictures of the jacket coming together (knock on wood) tomorrow.
12-26-09
This is going to be a short post, but I thought it might be a good idea to update you all with the Bill of Materials I sent off to the admins of Build18. (Note: There will be some part exchanges as we’re trying to get as much stuff as possible from Sparkfun, one of the Build18 sponsors)
Bill of Materials (click for larger version)
This isn’t the final B.O.M, but it gives you a pretty good idea of what I’m doing. The original lasers I purchased are no longer sold on Amazon, but this one looks like the ones I got (although I can’t vouch for the actual laser itself). One thing to note is that my budget for this project was $250. I’m pretty sure that with less prototyping-oriented gear and a longer build period, the cost of this project could easily go under $100, possibly even cheaper depending on your source for the lasers.
I may post some additional minor updates before I get back to school and actually begin working on the project.
Build18 is coming up and I’m super excited. For those not familiar with Build18, it’s ”a week-long event of building, hacking, and electrical play. No rules and no pre-reqs: just you, your project ideas, and the stuff you need to build them” hosted by the Electrical and Computer Engineering department at Carnegie Mellon. I was really sorry when I missed out on building something last year so I’m coming at this year’s event with a bit more than healthy amount of enthusiasm.
So far, I’m still in the brainstorming phase. I’ve decided on a project combining my passions for electronics and biking. After a couple of close calls with traffic, I began wondering what sorts of things would make me, as a cyclist, feel safer and more visible to drivers.
As an engineer, my first goal is to get a sense of what gaps exist in current technologies. I’ve done a bit of surveying, but I need a larger sample size to really get a handle on what’s needed (I’m looking at you, comments box). Additionally, I’ve begun to look into what situations create the most danger for cyclists. My hope is that by looking at crash statisics, I can figure out the area that would most benefit from some sort of technological advance. (Please note that I think being safe on the road is a shared responsibility, not solely a driver/cyclist/pedestrian responsibility)
A parallel course in my brainstorming process is looking at what people have already thought of, or actually produced. This is to make sure I’m somewhat original in my idea, as well as seeing if there’s a product I can improve upon. Some really awesome bike-safety projects exist, such as the turn-signal jacket, bike speed jacket, bike brake lights, and laser bike lane.
After some preliminary research on bicycle crashes, I noted a couple interesting statistics:
I would really like to come up with some application that deals with the more fatality-prone situation that occurs at intersections, but I have yet to come up with something that would really be effective. I’ve pondered the signals that cars give to each other to indicate intent (turn signals, brake lights, reverse lights, horns, hand gestures, etc.), but almost none of these counter the issue of avoiding a car that runs red lights or stop signs. Additionally, much of the issue is that the right-of-way is not being yielded at intersections, both by motorists and cyclists. As I cannot think of a solid solution for intersections, my focus is beginning to shift towards the non-intersection case.
So far, my ideas are most along the lines of the Laser bike lane project. I think it’s a good start, but it doesn’t fully realize the idea of a ’safety bubble’ around the cyclist. A (somewhat dated, but still relevant) study by The Pedestrian and Bicycle Information Center found that approximately 28% of crashes occur when the motorist and bicycle are on a parallel path, thus the idea of a bubble around cyclists could really be applied to this situation.
My implementation would combine a number of the projects I listed above into what I believe would be a more effective package overall. I would have side-facing lasers indicating boundries on either side of the bike with the ability to blink in sync with a turn signal set by the user (and possibly residing on a jacket), as well as changing color to red when the cyclist begins braking. A rear-facing semicircle would create a signal to drivers to not creep up on cyclists.
Project Feature List (so far):
In any case, this is all a work in progress. A more technical post will be on the way once I start finalizing a design and selecting components. Feel free to make suggestions. Feedback is totally encouraged!
Sources of bike crash statistics:
