Show HN: Open-Source eInk Bike Computer
248 points - yesterday at 5:18 PM
Hey all, i just launched my Eink Bike computer project and think it is cool.
Another tidbit, in the crazy things that AI has done... It has helped create a ANT (common sensor wireless protocol used in workout/biking) implementation for ESP32 by messing around with undocumented registers: https://github.com/RaemondBW/esp32-ant
Comments
I've always wanted to use a round display and an 18650 to plop a mini bike computer into my headset (replacing the cap). There was a Kickstarter years ago for a project doing that, but it seems to have fizzled out
For me, the next step for this is taking all the sensor data recorded for a ride, and loading it into my own fitness tracking database that I own, control, and isn't tied to someone else's profits.
eInk is the right display tech. I think this will do really well. It might need a UV filter.
That said, I don't love needing a separate device (hence, I don't own any bike computer). This is just my preference, but I really prefer to just plop my phone on my handlebars. So I'm building a bike computer app for iPhone: https://x.com/mholt6/status/2090529441944687087 (trying to get Apple to approve my developer account / business info, but they're hung up on my website of all things).
Phones are definitely not ideal in terms of display and energy use, but, I have found that with proper optimizations, energy use is a non-issue. To offset display problems, the app has several ride modes: a rich map display with 3D road or satellite view; a high-contrast wireframe map that looks great at both high and low refresh rates because it has no analog-style gauges; an instrument panel dashboard view; and a voice-only mode that has big touch zones for on-demand voice updates, using a state of the art mobile voice synthesis model. For connected radars, the app also renders radar data and has a screen like Tesla/Rivian's autonomy displays.
The app automatically manages thermals by switching modes to preserve battery life.
In my testing so far, by managing energy, making really good voice feedback, and using high-contrast screens (every mode other than the "rich" map), even a dimmed iPhone display is quite a usable bike computer in high-altitude sunlight.
But man, that eInk looks so clean and nice. Definitely the superior display! Nice work and I hope to learn some things from it!
EDIT: Woah, you got ANT+ support using BLE radio? I am not surprised that that is possible, but dang, that must have been a clever LLM.
But I don't see how they both fit together honestly.
The pros of eInk:
- low energy usage -> don't matter, current GPS units have +30 hours of battery life already
- low eye strain -> don't matter, you don't look at the screen for hours at a time
- visibility -> don't matter, current GPS units adapt to ambient light
- angle visibility -> don't matter, the screen is right in front of you
The cons of eInk:
- refresh rate -> yeah, I don't want the map display to be laggy
- visibility in the dark -> tunnels, tree cover... I don't want to my GPS to be invisible
- lack of color -> colors provide lots of information on the map display
Anyway, as long as you have fun doing this and some people enjoy it also, congrats!My use case is a bit more basic than most. I am nearly always on routes I know and just want a few basic stats, but…
I require a bike radar to work. I use a Varia. I like the beep, and need the indication for a car behind. Is there any compatibility with this?
If this question is already answered somewhere, apologies.
The mess of different implementations makes it really hard to hack on and share this kinda stuff.
AI does make it really easy to figure out these protocols now so that’s nice I guess. I just flipped my bike upside down and hooked up a logic analyzer and it took LLM no time to figure it out… it is really impressive
My thought was I'd love to set an HR zone and then connect it to my e-MTB and have it change power to keep me in a zone.
The refresh rate on my device was horrible, and the models (this was a few months ago) struggled to create a historical line plot of my HR.
I hope we can get a better suited hardware though. Larger buttons, smaller device overall. 4.7" sounds huge, almost size of a phone.
the dealbreaker for me is whether it could eventually work with the Garmin Vario radar (which the Wahoo supports with a nice visualization) -- that is _literally_ a life saver and I no longer ride without it.
Anyway one thing I think would be nice is if the GPS radio can become a peripheral. Then with that architecture could the head unit just get GPS from your phone?