View Single Post
Old 11-04-2019, 12:23 PM   #2
Quoth
Still reading
Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.
 
Quoth's Avatar
 
Posts: 14,284
Karma: 105299897
Join Date: Jun 2017
Location: Ireland
Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper
It's not hard and most of the needed software has been available for years open source.
The problem is cost, especially a decent eink screen.
A decent case is harder than a PCB.
Certainly having decent battery life by having the system mostly sleep apart from touch and buttons needs thought. I'd use a tablet SoC for main part and a separate PIC to manage touch screen & buttons. I'd use IR too. It would only scan properly when an initial touch is detected.
I'd use AAA or AA NiMH so if camping with no charging you can put in Alkaline cells. I'd design the cover flap as part of the case because otherwise a case is adding more thickness at the back and sides.

I think putting extended descriptions rather than part ID on the PCB silk screen is a waste. It's an ereader! Put all the HW docs in the onboard user manual. The silk screen info on a bare PCB isn't enough to build one anyway.
Quoth is offline   Reply With Quote