Success. I got my two #CANPico boards to communicate with each other using #MicroPython. The logic analyzer was able to pick up the data from the wire. Thanks, @kentindell for an awesome framework. Next up: hooking everything up to a Toyota Camry.
I upgraded my #childhood#lego#train to use #Pybricks#MicroPython. It stops at train stations now. No rail loops required. The passengers are happy about this --- considering they've been asleep like that for about 20 years...
Watch out, I'm a hardware designer now! My first board is here and it works!
Super happy with the "ambient light" effect:) There's one LED shining at the back into the hand, and another behind the screen, giving the impression of light passing through the PCB. Quite mesmerizing.
I still need to put side LEDs on (one for each of the touch pads), but those tiny SK6812-4020 turned out to be way beyond my amazing soldering skills 😅
I may have spent more of today than I'll admit in creating tiny beepy things with #MicroPython that chirp in accordance with Dolbear's “law” of cricket chirp rate vs temperature
What's the easiest camera module to interface to the #raspberrypi#pico that you can get access to the image from #micropython or #circuitpython with?
the #usefulsensors#tinycodereader is great for normal qrcodes but working on decoding rMQRs and usefulsensors said they have no plans for a new rMQR decoding module or different firmware to do that so going to need to roll my own solution
#MicroPython in the browser with #WASM is such an exciting possibility.
Catching up with what's been going on in PyScript over the last ~year and delighted to see that their MicroPython tech demo has worked its way into the core.
These are some profiles of one of their official demonstrators that runs both MicroPython and Pyodide in the same webpage (although Pyodide is given more work to do). Excluding network time, time to load MicroPython is <10 msec, and Pyodide is ~8000 msec 🤯
The computerized Necchi Supernova is #sewing! I couldn't call it any further along than version 0.1 or so, but I'm excited to see a proof of concept nevertheless. Next up, writing better firmware rather than a #micropython prototype. #electronics
Weird experiments with #nimib and #python continue. This time I have a hacky example of using #pyscript (with #micropython backend) inside a #nimib.py notebook (the try and catch ImportError is a workaround because I cannot have a context manager without yield, I will probably change the api to use something else, maybe a decorator on a function): https://nimib-land.github.io/nimib.py/bunny_meets_whaley.html
So for me, a #Python developer (with quite a bit of #MicroPython experience), this made the whole keeb firmware hacking an order of magnitude more accessible. You know, for really customizing stuff, not just editing a DeviceTree file and then wait for GitHub to build my firmware because local development is discouraged (looking at you, ZMK) …