We’ve been watching the development of the ESP32 chip for the last year, but honestly we’ve been a little bit cautious to throw all of our friendly ESP8266s away just yet. Earlier this month, Espressif released version 2.0 of their IoT Development Framework (ESP-IDF), and if you haven’t been following along, you’ve missed a lot.
We last took a serious look at the IDF when the chips were brand-new, and the framework was still taking its first baby steps. There was no support for such niceties as I2C and such at the time, but you could get both cores up and running and the thing connected to the network. We wanted to test out the power-save modes, but that wasn’t implemented yet either. In short, we were watching the construction of a firmware skyscraper from day one, and only the foundation had been poured.
But what a difference eight months make! Look through the GitHub changes log for the release, and it’s a totally new ballgame. Not only are their drivers for I2C, I2S, SPI, the DAC and ADCs, etc, but there are working examples and documentation for all of the above. Naturally, there are a ton of bugfixes as well, especially in the complex WiFi and Bluetooth Low Energy stacks. There’s still work left to do, naturally, but Espressif seems to think that the framework is now mature enough that they’ve opened up their security bug bounty program on the chip. Time to get hacking!
Depending on your opinion of these little critters, that could be a good thing or a bad thing. We don’t deny that mice are cute as all get-out, but when they do damage to foodstuffs that you’ve put an entire summer’s effort into growing, harvesting and preserving, cute isn’t worth much.
Our preference for taking care of rodent problems is either bioremediation or rapid cervical dislocation, but if you’re more of the catch-and-release type, this trap is for you. It’s just a 2-liter soda bottle on a wire pivot and mounted to a scrap wood frame; when the offending critter unwisely enters the neck of the bottle, its weight flips the bottle down and blocks the exit. Release is as simple as removing the bottle from the frame and letting Monsieur Jingles wiggle free. The questions of where to release and how many times you’ll keep catching the same mouse are left as an exercise for the reader.
Remember – a live catch trap is only humane if it’s checked regularly. To that end, maybe something like das Katzetelegraf could be added to this trap.
I’m writing a series of articles on resin casting as an extension to my experiences with the instructions found in the wonderful Guerrilla Guide. However, mistakes were made. Having run out of my usual mold release I went to a back-up jar that was lying around from a casting project long, long ago in a workshop far, far away.
I’m refining a technique of making a mold the quick and dirty way. Everything was going well, the sprues looked good and the master released from the silicone. It was time to do the second half of the mold. As usual I applied a generous amount of mold release. Since it was the first time this mold was to be used I went ahead and did all the proper steps. Rubbing off the dried release and applying a few more coats just to be sure.
I was completely unaware that I was applying mold release designed for urethane molds only. In other words I thoroughly covered my silicone mold in silicone bonding agents. I remained unaware until trying to separate the halves of the mold and found them thoroughly joined. After going through the stages of grief I finally figured out where it all went wrong.
Oh well. I’m ordering some of my regular pick, Stoner A324, and that should do the trick. There’s also Mann- Ease Release 200. While having probably the best name a release agent can have, it doesn’t work as well and needs approximately 100 years to dry. After this setback I’d rather just, grudgingly, learn my lesson and order the correct thing.
So now that we know the right way to fix this is to order the right product, is there a hack to get around it? Does anyone have a homebrew trick for release agent that can be used in a pinch? Leave your comments below.
The new EP from ASIC, alias [Patric] from Fablab Zürich, is out as PDF before it’s out in other forms of digital download, and the trailer video (embedded below the break) looks fantastic.
The release draws on this Instructable by Amanda Ghassaei to turn the music into PDFs suitable for feeding into a laser cutter, and we think it’s classy that she gets a shout-out on the label’s release page. Everything else about the album will be released under a Creative Commons license to boot.
Py3k breaks backwards compatibility with previous releases in order to reduce feature duplication and promote one obvious way of getting things done. The first major change is that print is now a builtin function and not a statement. int and long have been unified, and integer division now returns a float. Py3k uses concepts of “text” and “data” instead of “Unicode strings” and “8-bit strings”. You can read about many of the changes in What’s New In Python 3.0. Some new features have been backported to Python 2.6 so you can start implementing them in your current code to ease the transition. 2.6 also has the -3 command line switch to warn you about features that are being removed or changed. Finally, the tool 2to3 is a source-to-source translator that should automate a lot of the changes.