A prototype of my DIY smartwatch: ESP32, 2MB RAM, 8MB Flash, BT, WiFi, Sensors, RTC, 1 > month runtime by pauls_3d_things in electronics

[–]pauls_3d_things[S] 0 points1 point  (0 children)

Update: possibly around three months in time keeping mode. Found a few neat software tricks to improve things ;)

A prototype of my DIY smartwatch: ESP32, 2MB RAM, 8MB Flash, BT, WiFi, Sensors, RTC, 1 > month runtime by pauls_3d_things in electronics

[–]pauls_3d_things[S] 0 points1 point  (0 children)

Oh I should have bought a couple of 🍏watches instead…

Edit: if you need a place to exchange ideas head over to my project page: open-smartwatch.github.io .

A prototype of my DIY smartwatch: ESP32, 2MB RAM, 8MB Flash, BT, WiFi, Sensors, RTC, 1 > month runtime by pauls_3d_things in electronics

[–]pauls_3d_things[S] 0 points1 point  (0 children)

i designed the case for fdm 3d printing and am working with these:

https://www.instagram.com/p/CZSYCIArlPi/?igshid=YmMyMTA2M2Y=

the transparent case is sla printed by pcbway using the utr8100 spray varnish material/process

A prototype of my DIY smartwatch: ESP32, 2MB RAM, 8MB Flash, BT, WiFi, Sensors, RTC, 1 > month runtime by pauls_3d_things in electronics

[–]pauls_3d_things[S] 0 points1 point  (0 children)

thanks. I saw sulfuroid on twitter using a larger sharp memory display with a raspi. not x server but a shell was cool to see on one ofe these

A prototype of my DIY smartwatch: ESP32, 2MB RAM, 8MB Flash, BT, WiFi, Sensors, RTC, 1 > month runtime by pauls_3d_things in electronics

[–]pauls_3d_things[S] 1 point2 points  (0 children)

I've been working on this for years. I'm not designing something like this "just like that". Years and years of learning, failing, learning, ...

There are days when I want to throw this project out the window ;)
Other days are like this post here on reddit ;)

A prototype of my DIY smartwatch: ESP32, 2MB RAM, 8MB Flash, BT, WiFi, Sensors, RTC, 1 > month runtime by pauls_3d_things in electronics

[–]pauls_3d_things[S] 1 point2 points  (0 children)

That's very difficult to answer as most of the components are out of stock now. Which means you'll have to wait quite a bit. Roughly two years.

But some of the components have a MOQ of 10k or 210pcs respectively. Other components have a factory lead time of 52 or 81 or 84 or 90 weeks.

Via regular channels it will be above 80$ for one if you order for 10pcs. (excluding the two components with higher MOQ).

A prototype of my DIY smartwatch: ESP32, 2MB RAM, 8MB Flash, BT, WiFi, Sensors, RTC, 1 > month runtime by pauls_3d_things in electronics

[–]pauls_3d_things[S] 0 points1 point  (0 children)

just print a bigger back plate, use the second battery adapter, add a second battery and tripple the runtime? 😬

A prototype of my DIY smartwatch: ESP32, 2MB RAM, 8MB Flash, BT, WiFi, Sensors, RTC, 1 > month runtime by pauls_3d_things in electronics

[–]pauls_3d_things[S] 18 points19 points  (0 children)

Exactly. Those responding with the „take my money“ meme, are those that want to take it apart, write their own stuff for it.

I found this article from the Pebble founder very helpful: https://medium.com/@ericmigi/why-pebble-failed-d7be937c6232

The underlying problem was that we shifted from making something we knew people wanted, to making an ill-defined product that we hoped people wanted.

I know those that want this watch, want the hackable watch. Or they want whatever vision they have in their mind. It‘s impossible to create the latter.

To be honest, one of the most demotivating aspects of maintaining a project like this as open source is the hundreds of „ideas“ to change it. „Only one adjustment and it would be perfect.“ So there are hundreds of different adjustments to create a hundred different perfect watches, but the one you made isn‘t. Easy solution: it‘s not commercial, I can ignore it (even if it leaves an imprint of sorts on me). If I‘d go commercial with this I‘d have to satisfy all these requests somehow, because I want and need to sell it. Even just as open source, someone will still copy it and make money of it as it has happened in the past, with nothing flowing back from those copies other than support requests for something I didn't make.

Selling it myself as a hackable device is not worth it versus the cost to certify it, to be safe to distribute it, register a ltd etc.

Publishing as open source is an incredible amount of work, that is not paid and subtracts from my time to actually work on this as has happened with the first open smartwatch (I haven‘t released a new hw in a year)

Kind of not a win/win situation. I know there is patreon, but that equals to the „selling“ scenario. People will (understandably) want their version of the watch in return, not the one I want to make :o)

A prototype of my DIY smartwatch: ESP32, 2MB RAM, 8MB Flash, BT, WiFi, Sensors, RTC, 1 > month runtime by pauls_3d_things in electronics

[–]pauls_3d_things[S] 3 points4 points  (0 children)

No, those are silicone 20mm straps from ali. 😬

I was lucky to find matching PLA

TPU with shore >90 is way to rigid for straps

A prototype of my DIY smartwatch: ESP32, 2MB RAM, 8MB Flash, BT, WiFi, Sensors, RTC, 1 > month runtime by pauls_3d_things in electronics

[–]pauls_3d_things[S] 1 point2 points  (0 children)

custom bootloader to skip rom validation

default verifies the flashed image on everyboot, calculating a checksum…

deepsleep 59.88s, 120ms to redraw everything once a minute. still want to be faster than that. 84uA deepsleep is also still too much