I'm happy that more people finding my daily work interesting(embedded stuff).
The main reason i'm sticking around with embedded, seeing your code manifest to physical action is just...fun. No matter how good is your simulator/emulator, nothing beats real life.
Yeah, those panels are quite delicate, so they need a "maintainence" waveform(full refresh/flashing) for every now and then, to wiggle those stuck droplets.
Also when pushing for high refresh rate, you may need to use higher voltage, to make the droplets rise/fall faster. But sometime, those droplets are driven too hard and kind of stuck forever, so yeah, that's a trade off.
I have a question, hope it's not too sensitive, how do you guy protect your secret waveform ? One with enough tool and determination can just measure voltage at pixel and reverse the whole thing, the chinese can do that in less than a week i bet.
The refresh rate of eink is kind of...muddy. It depends on temperature and target contrast. With the right waveform and voltage, you can push it pretty far(like 30hz+).
The thing is, Eink's waveform is kind of secret afaik, everyone has different tuning.
They did not release any documents about their data model that is used to control their headphones. TBF almost every company does that, but unlike Apple, almost all of them have app on both platform(IOS/Android) to manage their devices so there is little reason to reverse engineer at first place.
You write program(usually in C), compile it into machine code(to .hex or .bin file), then "flashing" it using debugger tool. This IC will execute your program.
Wearable MCU is sometime stupidly good. Recently i learned that the new Pepple watch use SF32lb55. It has dual mode bluetooth with LE Audio, all the fancy like pmic, battery charger, usb, 2.5D GPU etc, it also has insanely large memory(16MB flash/8MB PSRAM on some packages). The whole MCU costs like $3.
If you dive into even more niche, NDA-Only MCU, We have BES2700 MCU, which is even better
Gun is stupidly to make. You just need a robust tube, a small hole in the end to trigger and you are done. Ofc it won't fire good, but still should be considered a gun
>Yet a lot of people make and watch serious educational and informational videos
a picture is worth a thousand words. Of course your text article can have pictures, but how can you sure you include all the "useful" pictures. Then there is animation which is impossible to do with static picture.
Interesting, yesterday i was asking it about Nintendo Switch "hax". And it gives me all the resource i need to procceed. It nags me about "ethic" and stuff, but nothing more than that.
Probably debouncing, when anything/any events happen, you have to ask yourself, did this event truly happens, or just some weird glitch and can safely ignore it.
i was thinking of using FPGA to control led matrix, the algorithm is not hard, it's just there are too many pin to control, they need high clock rate if you want high color depth, a using MCU bit bang is not really a choice.
The main reason i'm sticking around with embedded, seeing your code manifest to physical action is just...fun. No matter how good is your simulator/emulator, nothing beats real life.