One fine day, one of our team members was riding his bike to center city to go to his favorite Indian restaurant. However, he was on his phone to navigate to this restaurant. However, poor Humpty Dumpty had a big fall and cracked his phone and spine while at it. If only there was a safer way for him to navigate while on his bike!
Thus, Romit and I would like to create GPS Lights for your bike!
What it does
This project will entail of lights that go onto the bar handles of the bike that will light up based on which direction you should head. If the biker is going straight, then both lights should be lit up. We plan on using Arduino, Bluetooth, LED light strips, and a dummy app that uses the Google-Maps API. The steps we will take are: 1) Figure out Google Maps API, 2) Create a dummy app that incorporates Google Maps API, 3) Connect lights via bluetooth from phone, 4) Sending data from phone to lights so that it changes based on the information it receives and connect app to arduino.
By April 3rd, we will have the dummy app with the Google API finished. By April 17th, we will have the LEDs connected to the application via bluetooth.
Our project, “Blink”, was a GPS light system for your bike. The project gave bike riders the option of getting turn-by-turn directions without having to hold their phones in one hand while riding a bike. Before riding you open up the website for the project and entered your start and finish destination. The website would get directions and send them to your light system on the bike. You would then get on the bike and ride while the lights directed which way to go. There were 3 sets of lights (for left, right, and straight) and they got brighter as you got closer to your destination. The product also had the ability to turn on a blinking light if there was a sudden change in orientation of the bike, indicating you may have fallen, to alert those in the vicinity.
To be turned into a real product, we felt that we should definitely use different technology. The Arduino produced many restrictions that made us do more work or gave us unsolvable problems. For example, just reading and sending the directions became a 6-7-hour task instead of a task that should’ve taken no more than a couple hours. Further, Arduino does not provide a good way to get velocity which made us hardcode bike speed. Finally, we would have to minimize the size of the electronics and create a proper display interface to let the rider know how far away the turn is rather than rely only on the brightness of the LED. We didn’t really see any room for improvement on what we had created, but there is always room to grow in terms of adding more features and making the product more feasible!