Articles by Bryan Cockfield

When USB first came on the scene, one of the benefits was that essentially any four conductors could get you to the point where you could send information at 12 Mbps. Of course everything is faster these days, and reaching today’s speeds requires a little bit more fidelity in the cables. This simple tester makes sure that your modern cables are actually up to the task.
One of the design goals of this project is to automate away the task of testing cables or finding one that works, especially before thinking a problem with a device is somewhere in software, spending hours or days debugging, before realizing that it’s actually being caused by a hardware malfunction. The small PCB has two USB-C fittings to plug in both of the ends of a cable to, and between those connectors there is a number of LEDs. Each LED is paired to one the many conductors within the USB cable, and not only does it show continuity of these conductors but it can also show a high resistance connection via a dimly-lit or off-color display from an LED.
One of the other interesting facets of this build is the use of JITX, which is a software-defined electronics CAD tool which allows PCB design to be automated by writing out the requirements of the PCB into code, rather than drawing it manually. It’s worth a look, and a lot of the schematics of this particular project as well as some discussion on this software can be found on the project’s GitHub page. Incidentally, if this tester looks familiar, it’s probably because your’re thinking of the open source hardware USB tester created by [Álvaro Prieto]. […]

When building autonomous airborne vehicles like drones or UAVs, saving a little bit of weight goes a long way, literally. Every gram saved means less energy needed to keep the aircraft aloft and ultimately more time in the air, but unmanned vehicles often need to compromise some on weight in order to carry increased computing abilities. Thankfully this one carries a dizzying quantity of computer power for an absolute minimum of weight, and has some clever design considerations to improve its performance as well.
The advantage of this board compared to other similar offerings is that it is built to host a Raspberry Pi Compute Module 4, while the rest of the flight controllers are separated out onto a single circuit board. This means that the Pi is completely sandboxed from the flight control code, freeing up computing power on the Pi and allowing it to run a UAV-specific OS like OpenHD or RubyFPV. These have a number of valuable tools available for unmanned flight, such as setting up a long range telemetry and camera links. The system itself supports dual HD camera input as well as additional support for other USB devices, and also includes an electronic speed controller mezzanine which has support for quadcopters and fixed wing crafts.
Separating non-critical tasks like cameras and telemetry from the more important flight controls has a number of benefits as well, including improved reliability and simpler software and program design. And with a weight of only 30 grams, it won’t take too much cargo space on most UAVs. While the flight computer is fairly capable of controlling various autonomous aircraft, whether it’s a multi-rotor like a quadcopter or a fixed wing device, you might need a little more computing power if you want to build something more complicated. […]

It might seem quaint through the lends of history we have the luxury of looking through, but in the mid 1980s it was a major symbol of status to be able to communicate on-the-go. Car phones and pagers were cutting-edge devices of the time, and even though there were some mobile cellular telephones, they were behemoths compared to anything we would recognize as a cell phone today. It wasn’t until 1985 that a cell phone was able to fit in a pocket, and that first device wasn’t just revolutionary because of its size. It made a number of technological advancements that were extremely impressive for its time, and [Janus Cycle] takes us through some of those in this teardown video.
The Technophone came to us from Great Britain by way of a former Ericsson engineer named Nils Mårtensson. It was able to achieve its relatively small stature using a surface-mount PCB, which was a cutting-edge manufacturing process for the time. Not only did it use surface-mount components and boards, but the PCB itself has 12 layers and two sides and hosts two custom Technophone chips. The phone is relatively modular as well, with the screen, battery pack, and other components capable of easily disconnecting from the main board.
Some cleanup of the phone was needed after the teardown, but after removing some corrosion and replacing the nickel-cadmium battery with a few AA batteries, the phone was able to power on. There were some other surprises to find here as well. The phone includes an extensive menu, another rarity among mobile phones of the era, a fairly comprehensive set of setup and troubleshooting tools, and even hints that its EEPROM was at some point or other erased and given a software upgrade.
Since the mobile network technology that would have supported a phone like this has long since faded into obscurity, [Janus Cycle] was able to find a text file to open up some developer options, shared on BBS message boards in the early days of the Internet by people then known as phreakers. It’s an early example of cracking a mobile phone, which is interesting on its own, and the amount of tools available to those working on these devices further illustrates how far ahead these devices were in 1985.
[embedded content]
Thanks to [Michael] for the tip! […]

As electric cars continue to see increased adoption, one associated technology that was touted long ago that still hasn’t seen widespread adoption is vehicle-to-grid or vehicle-to-home. Since most cars are parked most of the time, this would allow the cars to perform load-levelling for the grid or even act as emergency generators on an individual basis when needed. While this hasn’t panned out for a variety of reasons, it is still possible to use an EV battery for use off-grid or as part of a grid tie solar system, and now you can do it without needing to disassemble the battery packs at all.
Normally when attempting to use a scrapped EV battery for another use, the cells would be removed from the OEM pack and reorganized to a specific voltage. This build, however, eliminates the need to modify the packs at all. A LilyGO ESP32 is used to convert the CAN bus messages from the battery pack to the Modbus communications protocol used by the inverters, in this case a Fronius Gen24, so the inverter and battery can coordinate energy delivery from one to the other automatically. With the hard part out of the way, the only other requirements are to connect a high voltage DC cable from the battery pack to the inverter.
[Dala], the creator of this project, has taken other steps to ensure safety as well that we’d recommend anyone attempting to recreate this build pays close attention to, as these battery packs contain an extremely large amount of energy. The system itself supports battery packs from Nissan Leafs as well as the Tesla Model 3, which can usually be found for comparably low prices. Building battery energy storage systems to make up for the lack of commercially-available vehicle-to-home systems isn’t the only use for an old EV battery, though. For example, it’s possible to use Leaf batteries to triple the range of other EVs like [Muxsan] did with this Nissan van.

[embedded content] […]

In the technologically-underpinned modern world, most of us interact with a battery of some sort every day. Whether that’s the starter battery in a car, the lithium battery in a phone, or even just the coin cell battery in a wrist watch, batteries underpin a lot of what makes society possible now. Not so in the early 1800s when chemists and physicists were first building and experimenting with batteries. And those batteries were enormous, non-rechargable, and fairly fragile to boot. Not something suited for powering much of anything, but if you want to explore what it would have been like to use one of these devices, follow along with [Christopher]’s build of a voltaic pile.
The voltaic pile is historically constructed using discs of alternating zinc and copper paired with an acidic electrolyte, but this build uses much more convenient metallic strips instead of larger discs. Tissues are used to facilitate absorption of the electrolyte solution, and a 3D-printed case is used to help hold everything together, with a spring mechanism built-in which keeps pressure on the alternating metallic strips. The electrolyte is nothing more than salt water here, which transports the ions from one end of the battery through the circuit to the other. With everything assembled in the 3D printed case, the voltaic pile creates almost 3 volts, although [Christopher] notes it should be making closer to 5 volts but there’s likely an internal short somewhere.
While voltaic piles don’t have much use anymore due to their limitations, [Christopher] intended this build to be used more of an educational demonstration than a practical application. It’s much easier to build this one than a more historically accurate one as well, and the use of springs and 3D printed parts means that it could be made to have a larger or smaller voltage by simply adding or removing cells within the pile. It’s also similar to the lemon or potato battery, the latter of which we’ve actually seen put to practical use in this 12V potato battery pack.
[embedded content] […]

Flying a glider, or similarly piloting a paraglider or hang glider, can all be pathways into aviation with a lower barrier of entry than powered flight. Sacrificing one’s engine does generate a few complexities, but can be rewarding as the pilot searches for various means of increasing altitude like ridge soaring or thermaling. You’ll need a special instrument called a variometer to know just how much altitude you’re gaining though, like this one which is built into commercially-available handheld GPS units.
These GPS units are normally intended for use on terra firma only, but [Oganisyan] has figured out a clever way to add this flight instrumentation to these units to help when operating a paraglider. An ATmega328 paired with a pressure sensor is added to the inside of the GPS units and communicates with an available serial interface within the units. To complete the modification, a patched firmware must be installed which adds the variometer function to the display. This upgrade is compatible with a handful of GPS units as well such as the BikePilot2+ or Falk Tiger.
For those who already own one of these GPS units, this could be a cost-effective way of obtaining a variometer, especially since commercially-available variometers tailored for this sort of application can cost around $200 to $500. It is an activity sensitive to cost, though, as it offers a much more affordable option for taking to the skies than any powered craft could, with an exception made for this powered paraglider which offers the ability for powered take off and flight extension using electric-powered props.
Thanks to [MartinO] for the tip! […]

While the Commodore 64 was an immensely popular computer for its time, and still remains a strong favorite within the retrocomputing community, there’s a reason we’re not using modern Commodore-branded computers today. Intense competition, company mismanagement, and advancing beyond 8-bit computers too late in the game all led to the company’s eventual downfall. But if you’re still a Commodore enthusiast and always wished you were able to get an upgraded C64, you might want to take a look at the Commander X16, a modern take on this classic computer.
We’ve actually seen the Commander X16 before, but this was back in its early days of prototyping and design. This video from [Adrian’s Digital Basement], also linked below the break, takes a look at how it’s come in the four years since [David Murray] started this project. At its core, it’s an 8-bit 6502-based computer like you’d find in the 1980s but built with new components. There are some more modern updates as well such as the ability to use an SD card as well as built-in SNES controller ports, but the real magic here is the VERA module. Built around an FPGA, this module handles graphics, some of the audio, and the storage capabilities and does all of these things much better than the original Commodore, while still being faithful to what made these computer great.
While the inclusion of the FPGA might offend some of the most staunch 8-bit purists, it turns out to be necessary due to the lack of off-the-shelf video chips and really makes this build shine in the end. It’s also capable of running 6502-based software from other machines too, including the original NES. The VERA module makes it possible to run other software too, including a sample of Sonic the Hedgehog from the Sega Genesis which [Adrian] demonstrates in his video. 6502-based computers are quite versatile as the Commander X16 demonstrates, and it’s even possible to build a rudimentary 6502 on a breadboard with just a few parts.

[embedded content] […]

Almost all entry-level physics courses, and even some well into a degree program, will have the student make some assumptions in order to avoid some complex topics later on. Most commonly this is something to the effect of “ignore the effects of wind resistance” which can make an otherwise simple question in math several orders of magnitude more difficult. At some point, though, wind resistance can’t be ignored any more like when building this remote-controlled car designed for extremely high speeds.
[Indeterminate Design] has been working on this project for a while now, and it’s quite a bit beyond the design of most other RC cars we’ve seen before. The design took into account extreme aerodynamics to help the car generate not only the downforce needed to keep the tires in contact with the ground, but to keep the car stable in high-speed turns thanks to its custom 3D printed body. There is a suite of high-speed sensors on board as well which help control the vehicle including four-wheel independent torque vectoring, allowing for precise control of each wheel. During initial tests the car has demonstrated its ability to  corner at 2.6 lateral G, a 250% increase in corning speed over the same car without the aid of aerodynamics.
We’ve linked the playlist to the entire build log above, but be sure to take a look at the video linked after the break which goes into detail about the car’s aerodynamic design specifically. [Indeterminate Design] notes that it’s still very early in the car’s development, but has already exceeded the original expectations for the build. There are also some scaled-up vehicles capable of transporting people which have gone to extremes in aerodynamic design to take a look at as well.

[embedded content] […]

The famous hoverboards of Back to the Future haven’t quite gotten here yet, but that hasn’t stopped anyone with a unique personal vehicle from using the name any time they need some quick marketing. The self-balancing scooter trend of the mid-2010s was the best example of this in recent memory, but there are also water-propelled platforms that use the popular name as well as a myriad of other more skateboard-like devices that never got off the ground at all. This project from [Damien Dolata], on the other hand, might be the most authentic prototype we’ve seen compared against the fictional version presented in the movie.
The hoverboard uses a set of rotating magnets, referred to in this build as magneto-rotational repulsors, which spin up to an extremely high rotational speed underneath the board. When above a metal surface, the spinning magnets generate eddy currents in the metal beneath them which create the strong magnetic field needed to levitate the board. Unlike the Lexus hoverboard system which used supercooling magnets, this is a much more affordable way of producing magnetic fields but is a little bit more complicated due to the extra moving parts.
As this is still in the prototyping stages, it has only been able to lift around 30 kg and hasn’t been tested in motion yet, but there are two small turbines built into the hoverboard to generate thrust whenever [Damien] gets to that point. It would require a larger metal surface to move across as well, which might be the main reason why it hasn’t been tested this way yet. For any native French speakers taking a look at this project, be sure to fill in any of our gaps in the comments below, and for other ways that eddy currents have been used in transportation take a look at this bicycle that uses them in its drivetrain.

[embedded content] […]

For a brief window of time in the mid-2010s, a fairly common joke was to send voice commands to Alexa or other assistant devices over video. Late-night hosts and others would purposefully attempt to activate voice assistants like these en masse and get them to do ridiculous things. This isn’t quite as common of a gag anymore and was relatively harmless unless the voice assistant was set up to do something like automatically place Amazon orders, but now that much more powerful AI tools are coming online we’re seeing that joke taken to its logical conclusion: prompt-injection attacks.
Prompt injection attacks, as the name suggests, involve maliciously inserting prompts or requests in interactive systems to manipulate or deceive users, potentially leading to unintended actions or disclosure of sensitive information. It’s similar to something like an SQL injection attack in that a command is embedded in something that seems like a normal input at the start. Using an AI like GPT comes with an inherent risk of attacks like this when using it to automate tasks, as commands to the AI can be hidden where a user might not expect to see them, like in this demonstration where hidden prompts for a ChatGPT plugin are hidden in YouTube video transcripts to attempt to get ChatGPT to perform actions outside of those the original user would have asked for.
While this specific attack is more of a proof-of-concept, it’s foreseeable that as these tools become more sophisticated and interconnected in our lives, the risks of a malicious attacker causing harm start to rise. Restricting how much access we give networked computerized systems is certainly one option, similar to sandboxing or containerizing websites so they can’t all share cookies amongst themselves, but we should start seeing some thought given to these attacks by the developers of AI tools in much the same way that we hope developers are sanitizing SQL inputs. […]