These days you can get just about any kind of radio controlled vehicle as a ready-to-run model. Cars, trucks, excavators, you name it. Open the box, charge the batteries, and you’re ready to roll. Even with all these modern conveniences, there is still a special breed of modelers who create their own models using only a few off-the-shelf parts.
[Rini Anita] is exactly that rare breed, creating this aluminum RC truck from scratch. The truck itself is a cab-over — short for Cab Over Engine (COE), a style seen making local deliveries worldwide. He starts with the ladder frame chassis, which is constructed using an extruded aluminum channel. This is the same material you’d normally use for the door tracks in retail store display cases. The electronics and standard RC fare: a receiver, electronic speed control, and a servo for steering. Batteries are recycled lithium cells. The main gearbox and drive axle look to be sourced from another RC vehicle, while leaf springs and suspension components are all custom built.
The truck’s body is a great example hand forming metal. First, a wooden form was created. Sections for the windows and door panels were carved out. Sheet aluminum was then bent over the wood form. Carefully placed hammer blows bend the metal into the carved sections – leaving the imprints of doors, windows, and other panel lines.
Throughout this build, we’re amazed by [Rini]’s skills, and the fact that the entire job was done with basic tools. A grinder, an old drill press, and a rivet gun are the go-to tools; no welder or 3D printer to be found. This puts a project like this well within the means of just about any hacker — though it may take some time to hone your skills! For his next truck, maybe [Rini] can add a self driving option!
Continue reading “Building An Aluminum RC Truck From Scratch”
A robot that performs surgery is a serious thing. One bug in the control system could end with disaster. Unless of course, you’re [Michael Reeves], in which case disaster is all part of the fun. (Video, embedded below.)
Taking inspiration from The da Vinci Surgical System, [Michael] set out to build a system that was faster, while still maintaining precision. He created a belt drive gantry system, not unlike many 3D printers, laser cutters, or woodworking CNC machines. Machines like this often use stepper motors. [Michael] decided to go with [Oskar Weigl’s] ODrive and brushless motors instead. The ODrive is on open source controller which turns off the shelf brushless motors — such as those found in R/C planes or hoverboards, into precision industrial servos. Sound familiar? ODrive was an entrant in the 2016 Hackaday Prize. [Michael] was even able to do away the ubiquitous limit switch by monitoring current draw with the ODrive.
It all adds up to a serious build. But this is [Michael “laser eye” Reeves] after all. The video is meant to be entertaining, with a hidden payload of education and inspiration. The fun starts when he arms the robot with a giant kitchen knife and performs “surgery” on a pineapple. If you want to know what happens when mannequins and fake blood enter the picture, then watch the video after the break.
Continue reading “Surgery Robot Is A Real Cut Up”
We all know that COVID-19 is stressing our health system to the limit. One of the most important machines in this battle is the ventilator. Vents are critical for patients experiencing the worst symptoms of respiratory distress from the virus. Most of the numbers predict that hospitals won’t have enough ventilators to keep up with the needs during the height of the pandemic.
Now anyone with a walkman or iPod can tell you what they do when there is one music device and two people who want to listen: Plug in a Y-connector. Wouldn’t it be great if you could do the same thing with a medical ventilator? It turns out you can – – with some important caveats.
Way back in 2006, [Greg Neyman, MD and Charlene Babcock, MD] connected four simulated patients to a single ventilator. Ventilators connect to a patient with two tubes – an inflow and an exhaust. Using common parts available in just about any hospital, the doctors installed “T-tube” splitters on the inflow and exhaust tubes. They tested this with lung simulators and found that the system worked.
There were some important considerations though. The patients must be medically paralyzed, and have similar lung capacity — you couldn’t mix an adult and a child. The tubing length for each patient needs to be the same as well. The suggestion is to place the patients in a star pattern with the ventilator at the center of the star.
[Dr. Charlene Babcock] explains the whole setup in the video after the break.
Interestingly enough, this technique went from feasibility study to reality during the Las Vegas shooting a few years ago. There were more patients than ventilators, so emergency room doctors employed the technique to keep patients alive while equipment was brought in from outside hospitals. It worked — saving lives on that dark day.
The video and technique remind us of Apollo 13 and the CO2 scrubber modifications. Whatever it takes to keep people alive. We’ve already started looking into open source ventilators, but it’s good to see that medical professionals have been working on this problem for years.
Continue reading “Saving 4 Patients With Just 1 Ventilator”
What do you do with 144 7-segment displays? If you’re [Frugha] you put them all together to create an epic clock. Each display has 8 individual LEDs — 7 segments, and a decimal point. Put that all together, and you’ve got 1152 individual LEDs to control. This presented a problem, as [Frugha] wanted to control the clock with a single Arduino Nano. Even charlieplexing won’t get you that many I/O lines.
The solution was a nifty little chip called the MAX7219. The ‘7219 speaks SPI and can control 64 individual LEDs. [Frugha] used 18 of them in the clock, giving him full control over all his LEDs. That’s pretty impressive, considering the last matrix 7-segment display we saw required 48 Arduinos!
Another problem is memory – 1152 “pixels” would quickly overrun the 2KB RAM in the ATmega328. This is a clock though — which means only digits 0-9 and a colon. [Frugha] picked a nice font and hand-coded lookup tables for each digit. The lookup tables are stored in ROM, saving precious RAM on the Arduino.
A clock wouldn’t be any good if it wasn’t accurate. A Tiny RTC supplies battery-backed time data. [Frugha] wrapped everything up with a neat layout on a custom PCB. Sure, you could put it in a case, but we think a clock this crazy deserves to be left open – so you can see it in all its glory.
Persistence is what a hacker needs to make it to their goal. That’s exactly what it took for [Erik] to make an untethered VR backpack system.
Starting way back in the Spring of 2019, [Erik] began working on an untethered VR system. Sure, the Oculus Quest was coming out, but it wouldn’t be compatible with the game library of PC based systems. [Erik] decided he wanted the best of both worlds, so he decided to build a backpack that carries a computer powerful enough to drive the Rift S.
The initial system was to use a cut-up backpack, an HP mini PC with an external Nvidia 1060 GPU, and a basic DC-DC converter. The result? Just about nothing worked. The HP’s boot process didn’t play well with an external GPU.
[Erik] went through several iterations of this project. He switched over to a standard PC motherboard and tried a few different DC-DC converters. He settled on a device from HDPLEX rated at 200 watts continuous. The converter plugs directly into a standard 24-pin ATX motherboard power connector and isn’t much larger than the connector itself.
The old backpack with its added padding and wood frame gave way to a Zotac VR go backpack. Only the straps and frame of the Zotac are used, with [Erik’s] custom parts mounted using plywood and 3D printed parts. The outer frame is aluminum, with acrylic panels.
Power comes from 7000 mAH LiFe batteries, with each pack providing an hour of runtime. The Backpack can hold two packs though, so wiring them up in parallel should double that runtime.
We have to say this is an extremely well-documented build. [Erik] explains how he chose each component and the advantages (and pitfalls) of the choices he made. An example would be the RAM he picked. He chose DDR4 with a higher spec than he needed, just so he could undervolt the parts for longer run-times.
Not everything in VR is fun and games though – you can ditch that monitor and go with a VR desktop.
If you’ve built a few PCs, you know how frustrating troubleshooting can be. Finding a faulty component inside the cramped confines of a case can be painful — whether its literal when sharp edges draw blood, or just figurative when you have to open that cramped case multiple times to make adjustments.
[Colonel Camp] decided to make life a bit easier by building this PC test bench which makes component troubleshooting much easier and can be built with old parts you probably have lying around. [Camp] was inspired by an old Linus PC Tech Tips video on the same topic. The key to the build is an old PC case. These cases are often riveted together, s a drill makes quick work of disassembling the chassis to easily get to all of the components. The motherboard pan and rear panel/card cage become the top shelf of the test bench, while the outer shell of the case becomes the base and a storage area. Two pieces of lumber support the upper shelf. The build was primed and painted with several coats of grey.
[Camp] built up his testbench with a modest motherboard, cooler and a 970 video card. He loaded up Manjaro Linux to verify everything worked. The basic hardware has already been replaced with a new system including a ridiculously huge cooler. But that’s all in a day’s work for a test bench PC.
We’ve seen some wild workbenches over the years, and this one fits right in for all your PC projects. Check out the video after the break!
Continue reading “DIY PC Test Bench Puts Hardware Troubleshooting Out In The Open”
Who wouldn’t want a robot that can fetch them a glass of water? [Saral Tayal] didn’t just think that, he jumped right in and built his own personal assistant robot. This isn’t just some remote-controlled rover though. The robot actually listens to his voice and recognizes his face.
The body of the robot is the common “Rover 5” platform, to which [Saral] added a number of 3D printed parts. A forklift like sled gives the robot the ability to pick things up. Some of the parts are more about form than function – [Saral] loves NASA’s Spirit and Opportunity Mars rovers, so he added some simulated solar cells and other greebles.
The Logitech webcam up front is very functional — images are fed to machine learning models, while audio is processed to listen for commands. This robot can find and pick up 90 unique objects.
The robot’s brains are a Raspberry Pi. It uses TensorFlow for object recognition. Some of the models [Saral] is using are pretty large – so big that the Pi could only manage a couple of frames per second at 100% CPU utilization. A Google Coral coprocessor sped things up quite a bit, while only using about 30% of the Pi’s processor.
It takes several motors to control to robot’s tracks and sled. This is handled by two Roboclaw motor controllers which themselves are commanded by the Pi.
We’ve seen quite a few mobile robot rovers over the years, but [Saral’s] ‘bot is one of the most functional designs out there. Even better is the fact that it is completely open source. You can find the code and 3D models on his GitHub repo.
Check out a video of the personal assistant rover in action after the break.
Continue reading “DIY Personal Assistant Robot Hears And Sees All”