Remote control boats can be great fun, and come in all manner of forms. There are unpowered sailcraft, speedboats that scream under the power of internal combustion, and of course, those that move under electric power. The brushless motor revolution of the past 20 years in particular has proven capable of creating some exciting RC watercraft, and [Matt K] decided he wanted to get on board.
[Matt] had owned a Kyosho Jetstream 1000 for several years, but found the nitro engine to be temperamental and not the most fun for high-jinx down at the lake. An old-school brushed motor setup with mechanical speed control similarly failed to excite. However, after experiencing the power of brushless in RC planes, [Matt] knew what he had to do.
Using an online calculator, [Matt] determined that his earlier nitro powerplant was putting out roughly 900 watts. When it came to going brushless, he decided to spec a Turnigy powerplant with twice as much power, along with the requisite speed controller. There was some work to do to integrate the new motor with the original propeller driveshaft and water cooling system, but in the end [Matt] ended up with a much faster boat that is a lot less hassle to set up and run.
Perhaps though, your RC boat needs brains, over brawn? Perhaps it’s time to look at autonomy…
Video after the break.
Continue reading “RC Boat Goes Brushless For Speed & Reliability”
Coffee is the lifeblood of hackers, IT workers, and apparently, IT workers who are also hackers. [Omerfarukz] is clearly the latter. He works as part of a large team spread over multiple floors, all with coffee machines, any one of which is fair game. The problem is knowing which one has coffee that is ready to pour. He needed a non-invasive way to monitor the coffee machines.
After contemplating a few solutions, he opted for one which wouldn’t offend the coffee gods. The machines use a high current to produce their heat, so he adapted some old remote control power sockets for the machines to plug into which would now monitor the current. A high current means the coffee is brewing and he knew that brewing takes one minute per cup, so the duration of the high current tells him the number of cups.
Having had no success with a current sensing transformer, he opted for an ACS712 chip, at heart a Hall effect sensor which outputs a voltage proportional to the test current. That goes to the IO pins of an ATtiny, and from there via serial to an ESP8266 and thence to Google Firebase for processing and notifying of IT workers in need of stimulation. For those wishing to partake, he’s posted the circuit on Github.
We’ve seen a few other non-invasive ways to do this monitoring. For example, there’s weighing the machines using a bathroom scale and the more manual phone-notifying alarm button.
Over the years, we’ve seen dozens of projects that sell themselves as an ‘Open Source’ cellphone, a hackable cellphone, or some other confabulation of a microcontroller, screen, and a cellular module. The WiPhone is not one of these projects. That’s not to say it’s not an Open Source phone that’s intended to be hackable. No, this is a DIY phone that doesn’t make cellular calls, because this is a phone that only works with SIP and VoIP apps. It’s a WiPhone, and something a lot of us have been waiting for.
The hardware for this WiFi enabled phone is extremely minimal, but there are some interesting tricks up its sleeve. Instead of letting the main microcontroller handle capturing all the button presses, the team behind the WiPhone are using a SN7326 key-scan controller. This cheap part is able to scan 64 buttons, although there are only 25 buttons on the phone. The audio board is a WM8750BL, a cheap codec with a stereo microphone interface and a 400 mW speaker driver. The display is a simple SPI TFT, and apart from the microcontroller, that’s about it.
But it’s the microcontroller that makes it, and for that we turn to the incredible ESP-32. This chip has enough power to play Doom, be a Game Boy, and in this case, make and receive calls from a VoIP provider, scan and connect to WiFi networks, and yes, it can even play snake.
While this is just about the simplest phone you can imagine, and it only works where there’s a WiFi network, a device like this could be invaluable. And really, these days how far are you from a WiFi network you’re already connected to anyway?
When you show up at a party wearing this bare PCB watch, there are effectively two possible reactions you might receive from the other people there. Either they are going to snicker at the nerd who’s wearing a blinking circuit board on their wrist in public, or they are going to marvel at the ridiculously low part count. We’ll give you one guess as to which reaction you’d likely get at any event Hackaday is involved in.
Designed and built by [Electronoobs], this extremely simple watch consists of a ATmega328P microcontroller, a dozen LEDs with their associated 200 Ω resistors, and a battery. There’s also a single push button on the front which is used to not only set the watch, but turn the LEDs on when you want to check the time. Short of dropping down to one LED and blinking out the time, it’s hard to imagine a timepiece with fewer components than this.
You’re probably wondering how [Electronoobs] pulled this off without an external clock source for the ATmega328P chip. The chip actually has an internal 8 MHz oscillator that can be used, but you need to flash the appropriate bootloader to it first. Accordingly, the backside of the PCB has both SPI and a UART solder pads for external bootloader and firmware programming.
As you might expect, there’s a downside to using the internal oscillator: it’s not very good. The ATmega328P spec sheet claims a factory calibrated accuracy of ±10%, and [Electronoobs] has found that equates to a clock drift of around 15 seconds per day. Not exactly great, but considering the battery only lasts for two days anyway, it doesn’t have much of an impact in this case.
Compared to other “analog” LED watches we’ve seen, the simplicity of this build is really quite remarkable. The closest competitor we’ve seen so far is this slick binary watch.
Continue reading “An Arduino Watch Without A Clock”
This is your last chance to get your project together for the Human Computer Interface Challenge in this year’s Hackaday Prize. We’re looking for innovative interfaces for humans to talk to machines or machines to talk to humans. These are projects that make technology more intuitive, more fun, and a more natural activity. This is your time to shine, and we’re accepting entries in the Human Computer Interface Challenge in this year’s Hackaday Prize until August 27th. This is your last weekend to work on your project, folks.
This is one of the best years of the Hackaday Prize yet, with almost one thousand projects vying for the top prize of $50,000 USD. That doesn’t mean everyone else is going home empty handed; we’ve already awarded $1000 prizes to twenty projects in each of the first three challenges, and this coming Monday, we’ll be figuring out the winners to the Human Computer Interface challenge. Twenty of those finalists will be awarded $1000 USD, and move onto the final round where they’re up for the Grand Prize.
Don’t miss your last chance to get in on the Human Computer Interface Challenge in this year’s Hackaday Prize. We’re looking for an interface that could be visual, auditory, haptic, olfactory, or something never before imagined. We’re sure we’re going to see an Alexa duct taped to a drone, and that’s awesome. We’re taking all comers. Don’t wait — start your entry now.
Continue reading “This Is Your Last Chance To Design The Greatest Human Computer Interface”
We’re living in the world of connected devices. It has never been easier to roll your own and implement the functionality you actually want, rather than live with the lowest common denominator that the manufacture chose.
In a previous article I walked though a small python script to talk to a BLE light and used it to cycle through some colors. Now I want to delve deeper into the world of Internet Connected BLE devices and how to set up a simple Internet-Of-Things light. With this example in hand the sky’s the limit on what you can build and what it will be able to do.
Join me after the break as I demonstrate how to use NodeJS to bridge the digital world with the physical world.
Continue reading “How to Mash Up BLE, NodeJS, and MQTT to Get Internet of Things”
Implementing PoE is made interesting by the fact that not every Ethernet device wants power; if you start dumping power onto any device that’s connected, you’re going to break things. The IEEE 802.3af standard states that the device which can source power should detect the presence of the device receiving power, before negotiating the power level. Only once this process is complete can the power sourcing device give its full supply. Of course, this requires the burden of smarts, meaning that there are many cheap devices available which simply send power regardless of what’s plugged in (passive PoE).
[Jason Gin] has taken an old, cheap passive PoE splitter and upgraded it to be 802.3af compatible (an active device). The splitter was designed to be paired with a passive injector and therefore did not work with Jason’s active 802.3at infrastructure.
The brain of the upgrade is a TI TPS2378 Powered Device controller, which does the power negotiation. It sits on one of two new boards, with a rudimentary heatsink provided by some solar cell tab wire. The second board comprises the power interface, and consists of dual Schottky bridges as well a 58-volt TVS diode to deal with any voltage spikes due to cable inductance. The Ethernet transformer shown in the diagram above was salvaged from a dead Macbook and, after some enamel scraping and fiddly soldering, it was fit for purpose. For a deeper dive on Ethernet transformers and their hacked capabilities, [Jenny List] wrote a piece specifically focusing on Raspberry Pi hardware.
[Jason]’s modifications were able to fit in the original box, and the device successfully integrated with his 802.3at setup. We love [Jason]’s work and have previously written about his eMMC adventures, repairing windows tablets and explaining the intricacies of SD card interfacing.