6 ms·
i've been wanting that for years myself, and with the advent of sharp's memory-in-pixel lcd displays and ambiq's subthreshold-logic arm microcontrollers, it's b
by kragen 2y ago
i've been wanting that for years myself, and with the advent of sharp's memory-in-pixel lcd displays and ambiq's subthreshold-logic arm microcontrollers, it's become possible to make it work under a milliwatt, which means it can run purely on solar power without batteries, using parallel nand flash for mass storage at a low duty cycle. i haven't progressed beyond the earliest prototyping stage myself; my design notes on the so-called zorzpad (mostly in spanish) are in http://canonical.org/~kragen/sw/zorzpad.git/ http://canonical.org/~kragen/sw/zorzpad.git/ and za3k vance has been working on a project inspired by it called the zorchpad https://blog.za3k.com/tag/zorchpad/ https://blog.za3k.com/tag/zorchpad/
the primary objective of the zorzpad is longevity, with a design lifetime of 53 years. to reach that objective i think i can't use batteries, charging ports, or off-the-shelf keyswitches. this forces a lot of compromises on the system design; i haven't found a processor with an mmu that can run at under a milliwatt
("zorzpad" is a pun on "thinkpad"; it's pronounced "thorthpad" in some spanish dialects, so it's the opposite of a thinkpad)
i think e-ink displays probably use way too much power. for years i've been looking for solid power consumption numbers, but in their absence, dividing an amazon swindle's battery life by its battery capacity suggests that they use about 100 milliwatts. the zorzpad's e-ink displays are about a tenth as big, use about a thousandth as much power (100 microwatts), and can be updated at 60 hertz (though the datasheet only guarantees 20)
if you aren't worried about going batteryless, or about mass production, you could literally buy an alphasmart neo and wire its keyboard and display up to an esp32 or something
- e63f67dd-065b 2y agoMy understanding is that eink only uses power on refresh; if you don’t change the image, the pigments remain where they are and draw no power.
- kragen 2y agoyes, that's right. so there's a refresh rate crossover point at which e-ink actually uses less power. my calculations from the very uncertain information i have is that it's around 20 minutes. that is, if you update the display once every five minutes, the e-ink display will use significantly more power than the memory-in-lcd display updating 60 times a second. there are real limits to the utility of a computer that needs several minutes to redraw its display; though i wouldn't venture to say that it's useless, you can't do anything similar to a conventional gui on it
- kristopolous 2y agoThe hisense e-ink phones are known to have week long battery lives (A5 and A9) so I'm thinking not all e-ink is the same. I know there's e-ink nerds out there and forums dedicated to it but I don't actually know the different types (here's an overview I think: https://en.wikipedia.org/wiki/Electronic_paper https://en.wikipedia.org/wiki/Electronic_paper). Maybe the good stuff is harder to find
- kragen 2y agothe amazon swindle is known for a month-long battery life, so a week is easily believable. but you're talking about how to solve a different problem if batteries are an option, e-ink is a super-low-power option because it uses 100 milliwatts or maybe 10 milliwatts at a cellphone size, while a conventional backlit color lcd uses 1000. but to run off solar panels, indoors, my power budget for the whole zorzpad is 1 milliwatt, and the screen can only have a fraction of that
- pushfoo 2y agoTL;DR: I love this idea and have two questions: 1. For early iterations / similar projects, could all-metal screw terminals[1] accept power internally? 2. Would supporting UXN/Varvara[2] be an option? More on these questions below after initial comments. ## Initial Comments > if you aren't worried about going batteryless, or about mass production, you could literally buy an alphasmart neo and wire its keyboard and display up to an esp32 or something I could, but it's a limited in availability. The keyboard is pretty important in my opinion. > memory-in-pixel lcd displays I vaguely remember hearing about this, but don't have the EE knowledge to judge the benefits of these. Data sheet for anyone interested: https://www.sharpsde.com/fileadmin/products/Displays/Specs/LS027B7DH01_31Oct23_Spec_LD-2023X11.pdf https://www.sharpsde.com/fileadmin/products/Displays/Specs/L... ## 1. The screw terminal: Disclaimer: I'm not an EE specialist. My understanding is that if the power loss isn't too great, an all-metal internal screw terminal[1] might improve device durability: * The power source could be replaceable. AA, AAA, LiPo, solar, etc * If you don't solder to the metal part, even sandpaper or a conveniently shaped rock could remove oxidation * For a case, internal screw terminals could turn a charging port into an easily replaceable component ## 2. UXN/Varvara: From your blog, I see an "artemis apollo 3 board"[3] is being used. From a Sparkfun page[4], it seems to have enough ram to host graphical Varvara. I was initially doubtful of UXN despite loving the idea, but: 1. The UXN community seems to have built a self-hosting ecosystem[5] of: * development and GUI ROM launching tools * text, font, and graphics editors * music sequencing tools 2. The UXN VM is light: 64k system ram, 4-bit 2-plane color, and misc state and debug 3. The core UXN VM is simple: a minimal implementation fits in under 150 lines[6] of C89 [1]: https://en.wikipedia.org/wiki/Screw_terminal https://en.wikipedia.org/wiki/Screw_terminal [2]: https://wiki.xxiivv.com/site/varvara.html https://wiki.xxiivv.com/site/varvara.html [3]: https://blog.za3k.com/zorchpad-update-cardboard-mockup-mk1/ https://blog.za3k.com/zorchpad-update-cardboard-mockup-mk1/ [4]: https://www.sparkfun.com/artemis https://www.sparkfun.com/artemis [5]: https://github.com/hundredrabbits/awesome-uxn https://github.com/hundredrabbits/awesome-uxn [6]: https://wiki.xxiivv.com/etc/uxnmin.c.txt https://wiki.xxiivv.com/etc/uxnmin.c.txt
- kragen 2y agoi'm glad to hear you find it appealing! i'll explain some of my thinking on these issues, some of which is specific to my own eccentric objectives (nobody designs computers to last decades) and some of which is more generally applicable screw terminals or post terminals are a good idea if you're going to have charging and want longevity. but charging implies batteries. and batteries themselves induce lots of failures; they typically have a design lifetime of two years, more than an order of magnitude too low for the zorzpad. by itself that's not a fatal flaw, because you could replace them, but it becomes fatal in combination with either of the two supplementary flaws: 1. battery shelf life is limited to about 10 years, except for lithium thionyl chloride and so-called 'thermal batteries' that use a molten-salt electrolyte (kept frozen during storage). consequently, if your computer needs batteries, after 10 years you're dependent on access to not just a market but a full-fledged industrial economy to keep your computer running. a friend of mine in rural romania has been trying to build a usable lead-acid battery from scratch to provide energy storage for his solar panels, and it's motherfucking difficult without that supply chain 2. batteries have a lot of failure modes that destroy the devices they power. overheating, swelling, leaking corrosive electrolytes, and too much voltage are four of them. if these failure modes were very rare (like once in 100 battery-years) that might be okay, but they aren't for me these are fatal flaws, but for others they may not be. if you can afford batteries, you can run for one hell of a long time on a single 18650 lipo on a milliwatt. a coin cell can deliver a milliwatt for a month as for uxn, uxn is the first attempt at frugal "write once, run anywhere" that's good enough to criticize. everyone should read devine's talk about its aspirations (https://100r.co/site/weathering_software_winter.html https://100r.co/site/weathering_software_winter.html) however, uxn is not frugal with cpu, or fast, nor is it good for programmer productivity, and it’s not all that simple. It’s designed for interpretation, which inherently means you’re throwing away 90% or 95% of even a single-threaded cpu, and it’s not designed as a compilation target, which means that you’re stuck programming at the assembly-language level. This is pretty fucking fun, but that’s because it makes easy things hard, not hard things easy; the offgrid notes lionize oulipo (https://100r.co/site/working_offgrid_efficiently.html https://100r.co/site/working_offgrid_efficiently.html) as a result of the efficiency problems, the platforms with complete uxn implementations (see https://github.com/hundredrabbits/awesome-uxn#emulators https://github.com/hundredrabbits/awesome-uxn#emulators) are the luxurious ones: microsoft windows, linux, amigaos, the essence operating system, anything that can run sdl or lua and love2d, gameboy advance, nintendo 64, nintendo ds, playdate, and the nook ereader: all 32-bit or 64-bit platforms with ram of 4 mebibytes or more, except that the gba only has 384 kibibytes, and there were amigas with as little as 512k (though i don’t know if they can run uxn). more limited machines like the gameboy, ms-dos, and the zx spectrum do not have complete uxn implementations (384k is the same amount of ram as the apollo3, so it's probably feasible, as you say) the uxn machine code is basically forth. forth is pretty aesthetically appealing to me, and i've gotten to the point where forth code is almost as easy for me to write as c code (though i have to look things up in the manual more often and have more bugs). however, it's much, much harder for me to read forth than it is to read c. it's harder for me to read forth code than to read assembly for any of 8086, arm, risc-v, i386, or amd64. possibly i just haven't written enough forth to have the enlightenment experience yet, but currently my hypothesis is that forth is just hard to read and that's it, and that the really great thing about forth is not actually the language but the interactive development experience the varvara display model is not a good fit for the memory-in-pixel displays, which only have one bit per pixel, while varvara requires two. also, evaluating things 60 times a second is not a good fit for low-power systems of any kind. and i'm not sure how well the existing varvara applications will work at 400×240 or tolerate a requirement to use fonts many pixels tall in order to be readable (a lot of the above notes are from xpasm.md in http://canonical.org/~kragen/sw/pavnotes2.git/ http://canonical.org/~kragen/sw/pavnotes2.git/ if you're interested in the context) as for tools for software development, program launching, editing text, editing fonts, editing other graphics, and sequencing music, i'm confident i can write those myself if i have to. i've written a compiler in a subset of scheme that compiles itself, a compiler in a forth-like language that compiles itself, various toy text editors, various virtual machines in under 150 lines of code, and various pieces of music synthesis software, and i've designed a few fonts of my own (though not using software i wrote) maybe i should set up a patreon for this or something, maybe people would be interested in supporting the project
- contingencies 2y agoAwesome art project. Where did you get 53 years from? I think, for longevity as a design criteria, including the documentation including design files is the best and most significant strategy. Mechanical: machine everything out of solid metal, over-spec the springs, seals and potential ingress point precision. Electronics: fat traces, replacement-optimized through hole components, socket-mounted chips, over-rated everything, passive cooling, conformal coating, arrays of smaller components in preference to single large components. Fasteners: easy grip broad head twistable screws only, potentially to double as stands, this ensures accessibility until fingers become obsolete. Software: ROM base system with physical restore function, dual ROM with mutual checksum if required, RAM for everything else. Digital storage/retrieval: Solid state only. Physical output: Optional low-longevity RS232 receipt printer for retro effect. Power: Solar + supercaps and/or a corded pull-out analog watch-style shake-to-charge assembly and/or a thermal charger utilizing thermals from combustion and/or a pneumatic charger utilizing common compressed air interfaces as a power source.
- kragen 2y agothanks! your ideas are mostly pretty good i agree that the machine should be fully self-describing, like darius bacon's 'book in itself'. of course, that won't help you if it won't turn on... rather than just conformal coating and seals, i'm thinking i'll not just conformally coat the boards, but also pot the whole assembly in something like silicone or toilet-ring wax, so that the potting material can be removed, but otherwise it's trivially ip68. except for the keyswitches, but the keyswitches can be a magnetic type that doesn't have any exposed electrical contacts or any springs solar-powered devices generally don't have to worry too much about cooling, though. or if they do it's from the heat they passively absorb from the sun, not from anything they dissipate internally. if your solar panels are 10% efficient (the best you can get out of amorphous silicon, which is the only kind that works under indoor lighting) and cover 30% of your device, they only harness 3% of the illuminance, which is later converted to heat in the circuitry. the other 97% is either reflected or converted into heat immediately. so the heat produced internally is only about 5% of the heat it has to deal with. now think about how much heat you feel on your skin from indoor illumination; we're talking about 5% of that socket-mounted chips tend to induce a lot of unreliability, so i don't favor them. desoldering surface-mount chips is a bit of a pain but still done routinely in cellphone repair shops around the world. but i want it to make it to its design lifetime without replacing components, and one reason for that is that i don't want to depend on the economy. (consider what components were commonplace in 01971 and how many of them are hard to obtain nowadays — and that was 53 years of relative peacetime. imagine trying to get parts today in moscow.) unlike batteries, chips do have a long shelf life, so you could conceivably stockpile chips today for future repairs. but if you're going to do that, probably the best place to stockpile them is on circuit boards inside the device, so you don't have to solder anything to fail over to them. that's not applicable for every device, but fortunately things like voltage regulators have very low failure rates, and you can still probably build in redundancy at a higher level. that's what we did when i worked on satellite systems: of n identical systems onboard, we only needed one to survive to run the satellite. there were even multiple power buses, so that even a failure that shorted a voltage rail to ground would only disable part of the satellite as i understand it (not having taken the measurements yet myself) over-rating is especially important for bypass capacitors in this context — not because they're prone to failure (unless you're using tantalums) but because capacitors have enormously higher leakage near their rated voltage if you want to build such a thing and have a mechanical charging option, i think a pullstring like 20th-century children's windup toys is the best option. it's compact, the spring constrains how much force you can apply to the generator and runs it at a predictable speed, and the pullstring grommet constrains the direction of force applied to the mechanism so that kofi annan can't break it by applying side-loading to your crank handle like he did with olpc. but i don't think electromechanical generators are likely to fit into the reliability budget for screws, i think protruding screws would catch on my pockets. but there are lots of ways to fasten things together in reopenable ways, especially if you don't need seals. if you did want to use conventional milled-head screws, well, i filed a flathead screwdriver out of a bolt a few months ago. i used a file, a vise, and a steel bolt. but exposed screws would tend to rust unless you made them out of titanium or something, which isn't an option for me a metal case has advantages and disadvantages. being able to take input power inductively (qi style) or communicate over rf could be useful, which you can't do with an all-metal case. metals are not very chemically stable, except for gold, silver, platinum, iridium, palladium, lead, nickel, aluminum, titanium, tin, and chromium. most of these have major disadvantages of their own, though titanium would be a pretty good option. many plastics are very chemically stable, including polypropylene, polyester terephthalate, silicones, and epoxy resins, and the epoxies in particular can be glass-fiber reinforced up to steel-like strengths and stiffnesses. so that was my plan why 53? i just like 53
- nine_k 2y agoI wonder what's the point to run.batteryless? With such a small power budget, the device should accumulate energy when it can harvest more than it needs to consume, and use it when the lighting conditions deteriorate. It would only take a really small battery, but would seriously increase usefulness.
- kragen 2y agoi've discussed the reliability problems of batteries further in https://news.ycombinator.com/item?id=40805573 https://news.ycombinator.com/item?id=40805573, but, as an intuition pump, consider that when cellphone repair shops advertise particular repairs, the particular repairs they advertise most are battery replacement, charging port replacement, and broken screen replacement
- nine_k 2y agoSo use a battery of a standard form factor and make it easy to replace. E.g. one AAA battery per device is easiest. Most coin-sized lithium batteries are also rechargeable, explicitly or implicitly.
- kragen 2y agoyou don't seem to have really understood my points, because you aren't engaging with them; as it happens, you're also mistaken about coin-sized lithium batteries (though any battery can be slightly recharged)
- thetoon 2y agoWhat do you mean by implicitly? Last time I checked, most of button/coin-like batteries (CR2032 and the such) aren't know to be rechargeable, unless you specifically get rechargeable ones.
- nullc 2y agoHave you given much though to the idea that parts which are inexpensive and shelf stable could just be bulked up? Long lifetime won't save you from parts that just get damages from wear and tear. For something like a keyboard, it might be better to have a box of spares, rather than trying to build for 53 years of use and abuse... just as an example.
- kragen 2y agoyeah, it might be a reasonable choice for mechanical parts like keyswitches and hinges. i think keyswitches with a wearout life of a billion cycles keyswitches isn't infeasible either, but testing them to verify the cycle life could be challenging