We’re not exactly what you’d call naturalists here at Hackaday, so to us, the idea that hot pepper seeds need to germinate in hot conditions sounds suspiciously like a joke. The sort of thing somebody might tell you right before they try to sell you an elevator pass, or cram you into a locker. But we don’t think [Dean] would have gone through so much trouble if it wasn’t true. You’re still not going to sell us an elevator pass, though. Not again.
According to [Dean], the Carolina Reaper pepper seeds he bought from Puckerbutt Pepper Company (truly a name you can trust) recommend that they be germinated at a temperature between 80 and 85 degrees Fahrenheit for up to eight weeks. To make sure they were maintained at the optimal temperature for as long as possible, he decided to get a heating pad he could place under the seeds to keep them warm. He just needed some way to make sure the heat only kicked on once the soil temperature fell out of the sweet spot.
To get an accurate reading, [Dean] ended up going with a waterproof K-type thermocouple connected to a SainSmart MAX6675 module that could be buried amongst the seeds. When the soil temperature drops below 82.5 F, it kicks on the heating mat through an IoT Relay by Digital Loggers. He even added in a capacitive soil moisture sensor and a couple of LEDs so he could tell from across the room if he needed to water what he loving refers to as his “Hell Berries”
Some bittersweet news today as we get word that Israel’s Beresheet spacecraft unfortunately crashed shortly before touchdown on the Moon. According to telemetry received from the spacecraft right up until the final moments, the main engine failed to start during a critical braking burn which would have slowed the craft to the intended landing velocity. Despite attempts to restart the engine before impact with the surface, the craft hit the Moon too hard and is presumably destroyed. It’s likely that high resolution images from the Lunar Reconnaissance Orbiter will eventually be able to give us a better idea of the craft’s condition on the surface, but at this point the mission is now officially concluded.
The Beresheet Lander
It’s easy to see this as a failure. Originally conceived as an entry into the Google Lunar X Prize, the intended goal for the $100 million mission was to become the first privately funded spacecraft to not only touch down on the lunar surface, but navigate laterally through a series of powered “hops”. While the mission certainly fell short of those lofty goals, it’s important to remember that Beresheet did land on the Moon.
It didn’t make the intended soft landing, a feat accomplished thus far only by the United States, Russia, and China; but the fact of the matter is that a spacecraft from Israel is now resting on the lunar surface. Even though Beresheet didn’t survive the attempt, history must recognize Israel as the fourth country to put a lander on the surface of our nearest celestial neighbor.
It’s also very likely this won’t be the last time Israel reaches for the Moon. During the live broadcast of the mission, after it was clear Beresheet had been lost, Prime Minister Benjamin Netanyahu vowed his country would try again within the next two years. The lessons learned today will undoubtedly help refine their next mission, and with no competition from other nations in the foreseeable future, there’s still an excellent chance Israel will be able to secure their place in history as the fourth country to make a successful soft landing.
Beresheet’s view during descent
Of course you’ve got to get to the Moon before you can land on it, and in this respect, Beresheet was an unmitigated success. We previously covered the complex maneuvers required to put the craft into lunar orbit after riding to space as a secondary payload on the Falcon 9 rocket; a technique which we’ll likely see more of thanks to the NASA’s recent commitment to return to the Moon. Even if Beresheet never attempted to land on the surface, the fact that it was able to enter into a stable lunar orbit and deliver dramatic up-close images of the Moon’s surface will be a well deserved point of pride for Israel.
This won’t be the last time that hundreds of millions of dollars worth of high-tech equipment will be lost while pushing the absolute edge of the envelope, and that’s nothing to be upset over. Humans have an insatiable need to see what’s over the horizon and that means we must take on a certain level of risk. The alternative is stagnation, and in the long run that will cost us a lot more than a few crashed probes.
The ESP family of microcontrollers is absolutely on fire right now, with a decent chunk of the projects that come our way now based on one of the impossibly cheap WiFi-enabled boards. In fact, they are so cheap and popular that we’ve started to see a somewhat unexpected trend; people have a tendency to use them as drop-in replacements, despite the more modern boards being considerably more powerful than required. The end result is a bunch of projects in which the ESP is simply underutilized. It’s not a big deal, but somewhat disappointing to see.
But we can assure you this ESP32 alarm clock created by [Pangodream] is absolutely not one of them. He’s packed an impressive number of features into this unassuming little timepiece, and it’s really an excellent example of how much these boards are capable of without breaking a sweat. From DIY touch sensors to the Android application used to configure the clock over the network, this project is overflowing with neat hardware and software tricks worth taking a closer look at.
Inside the 3D printed case, the clock features a BH150 light sensor, the very popular DHT-11 for detecting temperature and humidity, as well as a ILI9341 2.8 inch LCD for the display. In a particularly clever touch (get it?), [Pangodream] used three coins connected to the digital pins of the ESP32 as capacitive sensors. These allow him to interact with the click just by tapping the top of the case, and saved him the trouble of adding traditional switches or buttons. We might have put some indentations in the top case to make identifying which of the three “buttons” you’re pushing, but we suppose the invisible interface does make things look a little more futuristic.
But if even that is too much physical touching for you, then [Pangodream] has come up with a fairly robust system for controlling and interacting with the clock over the network. It’s not just a convenient way of setting the time, a good number of the clock’s functions can be polled and configured in this manner; everything from the sensitivity of the touch sensors to how many times it will beep when the alarm goes off. To make things easier, he’s even wrapped it all up in a handy Android application for on the go configuration.
We often talk about the advantages of modular hardware here at Hackaday; the ability to just order a few parts online, hook them up with some jumper wires, and move onto the software side of things is a monumental time saver when it comes to prototyping. So anytime we see a new module that’s going to save us time and aggravation down the road, we get a bit excited.
Today we present the very slick I2CNavKey developed by [Saimon], a turn-key interface solution for your builds that can’t quite get away with a couple toggle switches. It not only gives you a four-way directional pad with center button, but a rotary “wheel” like on the old iPods. All of which you can access easily and with a minimum of wiring thanks to the wonders of I2C.
But even that might be selling the module short. This isn’t just a couple of buttons on a breakout board, the I2CNavKey is powered by its own PIC16F18345 microcontroller and features three configurable GPIOs with PWM support (perfect for an RGB LED) plus 256 bytes of onboard EEPROM storage.
[Saimon] has released the entire project as open source hardware for your hacking pleasure, but you can also get them as ready-to-use modules on Tindie for $18 USD [Editor’s Note: Because of a typo we originally we left the 1 out of the price]. Whether you’re a paying customer or not, you get access to the project’s absolutely phenomenal documentation, including a nearly 30 page manual that contains everything you’d ever want to know about the I2CNavKey and how to integrate it into your project. If all hardware was documented with this level of dedication, the world would be a much nicer place for folks like us.
It might be difficult for modern audiences to believe, but at one point Microsoft Windows fit on floppy disks. This was a simpler time, with smaller hard drives, lower resolution displays, and no hacker blogs for you to leave pessimistic comments on. A nearly unrecognizable era, to be sure. But if you’re one of the people who looks back on these days fondly, you might wonder why we don’t see this tiny graphical operating system smashed into modern hardware. After all, SkiFree sure ain’t gonna play itself.
The adventure starts when [redsPL] helped a friend install libreboot and coreboot on a stack of old ThinkPads by using the Raspberry Pi as an SPI flasher, a pastime we’re no strangers to ourselves. Once the somewhat finicky software and hardware environment was up and running, it seemed a waste not to utilize it further. Especially given the fact most firmware replacements only fill a fraction of the X200’s 8 MB chip.
Of course, Windows 3.1 was not designed for modern hardware and no proper drivers exist for much of it. Just getting the display resolution up to 1024×768 (and still with only 256 colors) required patching the original video drivers with ones designed for VMWare. [redsPL] wasn’t able to get the sound hardware working, but at least the PC speaker makes the occasional buzz. The last piece of the puzzle was messing around the zip and xz commands until the disk image was small enough to sneak onto the chip.
Visitors to the Wizarding World of Harry Potter at Universal Studios are able to cast “spells” by waving special interactive wands in the air. Hackers like us understand that there must be some unknown machinations happening behind the scenes to detect how the wands are moving, but for the kids wielding them, it might as well be real magic. So when his son asked to have a Harry Potter themed birthday party, [Adam Thole] decided to try recreating the system used at Universal Studios in his own home.
Components used in the IR streaming camera
The basic idea is that each wand has a reflector in the tip, which coupled with strong IR illumination makes them glow on camera. This allows for easy gesture recognition using computer vision techniques, all without any active components in the wand itself.
[Adam] notes that you can actually buy the official interactive wands from the Universal Studios online store, and they’d even work with his system, but at $50 USD each they were too expensive to distribute to the guests at the birthday party. His solution was to simply 3D print the wands and put a bit of white prismatic reflective tape on the ends.
With the wands out of the way, he turned his attention to the IR imaging side of the system. His final design is a very impressive 3D printed unit which includes four IR illuminators, a Raspberry Pi Zero with the NoIR camera module. [Adam] notes that his software setup specifically locks the camera at 41 FPS, as that triggers it to use a reduced field of view by essentially “zooming in” on the image. If you don’t request a FPS higher than 40, the camera will deliver a wider image which didn’t have any advantage in this particular project.
The last part of the project was taking the video stream from his IR camera and processing it to detect the bright glow of a wand’s tip. For each frame of the video the background is first removed and then any remaining pixel that doesn’t exceed a set brightness level if ignored. The end result is an isolated point of light representing the tip of the wand, which can be fed into Open CV’s optical flow function to show [Adam] what shape the user was trying to make. From there, his software just needs to match the shape with one of the stock “spells”, and execute the appropriate function (such as changing the color of the lights in the room) with Home Assistant.
Overall, it’s an exceptionally well designed system considering the goal was simply to entertain a group of children for a few hours. We almost feel bad for the other parents in the neighborhood; it’s going to take more than a piñata to impress these kids after [Adam] had them conjuring the Dark Arts at his son’s party.
With the destruction of the Microsat-R reconnaissance satellite on March 27th, India became the fourth country in history to successfully hit an orbiting satellite with a surface-launched weapon. While Microsat-R was indeed a military satellite, there was no hostile intent; the spacecraft was one of India’s own, launched earlier in the year. This follows the examples of previous anti-satellite (ASAT) weapons tests performed by the United States, Russia, and China, all of which targeted domestic spacecraft.
Yet despite the long history of ASAT weapon development among space-fairing nations, India’s recent test has come under considerable scrutiny. Historically, the peak of such testing was during the 1970’s as part of the Cold War rivalry between the United States and then Soviet Union. Humanity’s utilization of space in that era was limited, and the clouds of debris created by the destruction of the target spacecraft were of limited consequence. But today, with a permanently manned outpost in low Earth orbit and rapid commercial launches, space is simply too congested to risk similar experiments. The international community has strongly condemned the recent test as irresponsible.
For their part, India believes they have the right to develop their own defensive capabilities as other nations have before them, especially in light of their increasingly active space program. Prime Minister Narendra Modi released a statement reiterating that the test was not meant to be a provocative act:
Today’s anti-satellite missile will give a new strength to the country in terms of India’s security and a vision of developed journey. I want to assure the world today that it was not directed against anybody.
India has always been against arms race in space and there has been no change in this policy. This test of today does not violate any kind of international law or treaty agreements. We want to use modern technology for the protection and welfare of 130 million [1.3 Billion] citizens of the country.
Further, the Indian Space Research Organisation (ISRO) rejects claims that the test caused any serious danger to other spacecraft. They maintain that the test was carefully orchestrated so that any debris created would renter the Earth’s atmosphere within a matter of months; an assertion that’s been met with criticism by NASA.
So was the Indian ASAT test, known as Mission Shakti, really a danger to international space interests? How does it differ from the earlier tests carried out by other countries? Perhaps most importantly, why do we seem so fascinated with blowing stuff up in space?