Face it — you want a reflow oven. Even the steadiest hands and best eyes only yield “meh” results with a manual iron on SMD boards, and forget about being able to scale up to production. But what controller should you use when you build your oven, and what features should it support? Don’t worry — you can have all the features with this open source reflow oven controller.
Dubbed the Reflowduino for obvious reasons, [Timothy Woo]’s Hackaday Prize entry has everything you need in a reflow oven controller, and a few things you never knew you needed. Based on an ATMega32, the Reflowduino takes care of the usual tasks of a reflow controller, namely running the PID loop needed to accurately control the oven’s temperature and control the heating profile. We thought the inclusion of a Bluetooth module was a bit strange at first, but [Timothy] explains that it’s a whole lot easier to implement the controller’s UI in software than in hardware, and it saves a bunch of IO on the microcontroller. The support for a LiPo battery is somewhat baffling, as the cases where this would be useful seem limited since the toaster oven or hot plate would still need a mains supply. But the sounder that plays Star Wars tunes when a cycle is over? That’s just for fun.
Hats off to [Timothy] for a first-rate build and excellent documentation, which delves into PID theory as well as giving detailed instructions for every step of the build. Want to try lower-end reflow? Pull out a halogen work light, or perhaps fire up that propane torch.
After booting up his RetroPie system, [jfrmilner] had the distinct feeling that something was off. Realizing that the modern Xbox 360 controller didn’t fit right when reliving the games of his youth, he rounded up all his old controllers to make sure he always had the right gamepad for the game.
Wanting to keep the controllers unmodified — so they could still be used on the original systems — he had to do a bit of reverse-engineering and source some controller sockets before building his controller hub. Using shift-in registers, shift-out registers, and some multiplexers, he designed a large circuit selector — which acts as a shield for an Arduino Micro — so all the controllers remain connected. A potentiometer allows him to select the desired controller and a few arcade buttons which access RetroPie shortcuts really round out the hub. Check out the demo after the break!
Continue reading “Why Only Use One Controller When You Can Use ALL Of Them?”
With its backlit color screen and Master System compatibility, the Game Gear was years ahead of its main competition. The major downside was that it tore through alkaline batteries quickly, and for that reason the cheaper but less equipped Game Boy was still able to compete. Since we live in the future, however, the Game Gear has received new life with many modifications that address its shortcomings, including this latest one that adds an HDMI output.
The core of the build is an FPGA which is used to handle pixel decoding and also handles the HDMI output. The FPGA allows for a speed high enough to handle all the data that is required, although [Stephen] still has to iron out some screen-filling issues, add sound over HDMI, and take care of a few various pixel glitches. To turn this hack into a complete hodgepodge of adapters, though, [Stephen] has also added an SNES controller adapter to the Game Gear as well. Nintendo has featured Sonic in many of its games, so although we may have disagreed back in the early 90s we think that this Sega/Nintendo pairing is not crossing any boundaries anymore.
Game Gears have had their share of other modifications as well to make them more capable as a handheld system than they were when they were new. We’ve also seen them turned into a console system (they were Master System compatible, after all) and converted into other things entirely, too.
Continue reading “Game Gear HDMI with SNES Controller”
Who loves a good R2-D2 robot? Everyone, but especially young Star Wars fans who — frustratingly — have no problem spotting a controller and spoiling the illusion of an R2 unit brought to life. [Bithead942]’s concealed his R2-D2’s remote and re-establishes the illusion of an autonomous droid — no Jedi mind-tricks necessary.
[Bithead942] prefers to accompany his droid in traditional a Rebel Alliance pilot’s suit, so that gives him a bit of extra space under the jumpsuit to help conceal the controller. Dismantling a Frsky Taranis X9D controller, [Bithead942] meditated on how to use it while so concealed. In a stroke of insight, he thought of his unused Wiimote nunchucks, and launched into the build.
Continue reading “This Isn’t The R2-D2 Controller You’re Looking For”
[Paul de Groot] wrote in to let us know about a drop-in controller replacement he designed for those economical K40 laser engravers that are everywhere on eBay. With the replacement controller, greatly improved engraving results are possible along with a simplified toolchain. Trade in the proprietary software and that clunky security dongle for Inkscape and a couple of plugins! [Paul] felt that the work he accomplished was too good to keep to himself, and is considering a small production run.
Laser engravers are in many ways not particularly complex devices; a motion controller moves the head in x and y, and the laser is turned on or off when needed. But of course, the devil is in the details and there can be a surprising amount of stuff between having a design on your screen and getting it cut or engraved in the machine. Designing in Inkscape, exporting to DXF, importing the DXF to proprietary software (which requires a USB security dongle to run), cleaning up any DXF import glitches, then finally cutting the job isn’t unusual. And engraving an image with varying shades and complex dithering? The hardware may be capable, but the stock software and controller? Not so much. It’s easy to see why projects to replace the proprietary controllers and software with open-source solutions have grown.
Cheap laser engravers may come with proprietary controllers and software, but they don’t need to stay that way. Other efforts we have seen in this area include LaserWeb, which provides a browser-based interface to a variety of open-source motion controllers like Grbl or Smoothieware. And if you’re considering a laser engraver, take a few minutes to learn from the mistakes of other people.
A self-balancing robot is a great way to get introduced to control theory and robotics in general. The ability for a robot to sense its position and its current set of circumstances and then to make a proportional response to accomplish its goal is key to all robotics. While hobby robots might use cheap servos or brushed motors, for any more advanced balancing robot you might want to reach for a brushless DC motor and a new fully open-source controller.
The main problem with brushless DC motors is that they don’t perform very well at low velocities. To combat this downside, there are a large number of specialized controllers on the market that can help mitigate their behavior. Until now, all of these controllers have been locked down and proprietary. SmoothControl is looking to create a fully open source design for these motors, and they look like they have a pretty good start. The controller is designed to run on the ubiquitous ATmega32U4 with an open source 3-phase driver board. They are currently using these boards with two specific motors but plan to also support more motors as the project grows.
We’ve seen projects before that detail why brushless motors are difficult to deal with, so an open source driver for brushless DC motors that does the work for us seems appealing. There are lots of applications for brushless DC motors outside of robots where a controller like this could be useful as well, such as driving an airplane’s propeller.
Part of the problem with having an alarm system is its reliance on land line telephone service. Some of them are getting away from this practice, but there are still many legacy systems out there that require a check to be sent in to Ma Bell every month in addition to the alarm system fees. Like these antiquated systems, [jgyates] was having a similar problem with the generator at his home which could only be monitored with a link to a cell network. Now that there’s a Raspberry Pi in every house, however, [jgyates] has a generator monitor that isn’t beholden to the phone company.
The hardware setup is little more than connecting the communications lines from the generator’s controller (in this case, a Generac Evolution controller) to the serial communications pins on a Raspberry Pi 3. [jgyates] did most of the work in Python, and his code is able to monitor almost every aspect of this generator and report it over WiFi or Ethernet, as well as control the generator settings from anywhere that has an Internet connection.
Even if you don’t have a generator with this particular controller, it will be a good guide for converting a monitor of any type into one that doesn’t require a land line or cell network connection. To that end, there have been lots of projects that convert even simple, old, analog household devices to report data over the LAN.