Pixy2 Is Super Vision For Arduino Or Raspberry Pi

A Raspberry Pi with a camera is nothing new. But the Pixy2 camera can interface with a variety of microcontrollers and has enough smarts to detect objects, follow lines, or even read barcodes without help from the host computer. [DroneBot Workshop] has a review of the device and he’s very enthused about the camera. You can see the video below.

When you watch the video, you might wonder how much this camera will cost. Turns out it is about $60 which isn’t cheap but for the capabilities it offers it isn’t that much, either. The camera can detect lines, intersections, and barcodes plus any objects you want to train it to recognize. The camera also sports its own light source and dual servo motor drive meant for a pan and tilt mounting arrangement.

Continue reading “Pixy2 Is Super Vision For Arduino Or Raspberry Pi”

The How And Why Of Laser Cutter Aiming

Laser aficionado [Martin Raynsford] has built up experience with various laser cutters over the years and felt he should write up a blog post detailing his first-hand findings with an often overlooked aspect of the machines: aiming them. Cheap diode laser cutters and engravers operate in the visible part of the spectrum, but when you get into more powerful carbon dioxide lasers such as the one used in the popular K40 machines, the infrared beam is invisible to the naked eye. A secondary low-power laser helps to visualize the main laser’s alignment without actually cutting the target. There are a couple of ways to install an aiming system like this, but which way works better?

[Martin] explains that there are basically two schools of thought: a head-mounted laser, or a beam combiner. In both cases, a small red diode laser (the kind used in laser pointers) is used to indicate where the primary laser will hit. This allows the user to see exactly what the laser cutter will do when activated, critically important if you’re doing something like engraving a device and only have one chance to get it right. Running a “simulation” with the red laser removes any doubt before firing up the primary laser.

That’s the idea, anyway. In his experience, both methods have their issues. Head-mounted lasers are easier to install and maintain, but their accuracy changes with movement of the machine’s Z-axis: as the head goes up and down, the red laser dot moves horizontally and quickly comes out of alignment. Using the beam combiner method should, in theory, be more accurate, but [Martin] notes he’s had quite a bit of trouble getting both the red and IR lasers to follow the same course through the machine’s mirrors. Not only is it tricky to adjust, but it’s also much more complex to implement and may even rob the laser of power due to the additional optics involved.

In the end, [Martin] doesn’t think there is really a clear winner. Neither method gives 100% accurate results, and both are finicky, though in different scenarios. He suggests you just use whatever method your laser cutter comes with from the factory, as trying to change it probably isn’t worth the effort. But if your machine doesn’t have anything currently, the head-mounted laser is certainly the easier one to retrofit.

In the past, we’ve covered a third and slightly unconventional way of aiming the K40, as well as a general primer for anyone looking to pick up eBay’s favorite laser cutter.

X-Ray Vision For FPGAs: Using Verifla

Last time I talked about how I took the open source Verifla logic analyzer and modified it to have some extra features. As promised, this time I want to show it in action, so you can incorporate it into your own designs. The original code didn’t actually capture your data. Instead, it created a Verilog simulation that would produce identical outputs to your FPGA. If you were trying to do some black box simulation, that probably makes sense. I just wanted to view data, so I created a simple C program that generates a VCD file you can read with common tools like gtkwave. It is all on GitHub along with the original files, even though some of those are not updated to match the new code (notably, the PDF document and the examples).

If you have enough pins, of course, you can use an external logic analyzer. If you have enough free space on the FPGA, you could put something like SUMP or SUMP2 in your design which would be very flexible. However, since these analyzers are made to be configurable from the host computer, they probably have a lot of circuitry that will compete with yours for FPGA space. You configure Verifla at compile time which is not as convenient but lets it have a smaller footprint.

Continue reading “X-Ray Vision For FPGAs: Using Verifla”

Tractor Drives Itself, Thanks To ESP32 And Open Source

[Coffeetrac]’s ESP32-based Autosteer controller board, complete with OLD OLED display for debugging and easy status reference.
Modern agricultural equipment has come a long way, embracing all kinds of smart features and electronic controls. While some manufacturers would prefer to be the sole gatekeepers of the access to these advanced features, that hasn’t stopped curious and enterprising folks from working on DIY solutions. One such example is this self-steering tractor demo by [Coffeetrac], which demonstrates having a computer plot and guide a tractor through an optimal coverage pattern.

A few different pieces needed to come together to make this all work. At the heart of it all is [Coffeetrac]’s ESP32-based Autosteer controller, which is the hardware that interfaces to the tractor and allows for steering and reading sensors electronically. AgOpenGPS is the software that reads GPS data, interfaces to the Autosteer controller, and tells equipment what to do; it can be thought of as a mission planner.

[Coffeetrac] put it all together with everything controlled by a tablet mounted in the tractor’s cab. The video is embedded below, complete with a “cockpit view” via webcam right alongside the plotted course and sensor data.

Continue reading “Tractor Drives Itself, Thanks To ESP32 And Open Source”

Soyuz Failure Leaves Questions Unanswered

The Russian space program experienced its first serious incident on a manned mission in 35 years when Soyuz MS-10 failed during ascent on October 11th, 2018. The abort system worked as designed, and crew members Aleksey Ovchinin and Nick Hague landed safely approximately 430 km from the launch site in Baikonur. Beyond being put through unusually high G forces, the two men suffered no injuries and will have their mission recycled for a future flight.

From an abort standpoint, the event went as well as could possibly be expected. The fact that the crew walked away unharmed is a testament to the emergency systems on the rocket and spacecraft, and serve as a reminder of why these functions are designed into manned rockets even if they are rarely (if ever) used. The success is especially impressive considering the Soyuz’s launch abort tower, the solid fuel rocket designed to pull the spacecraft away from the failing booster rocket, had already been jettisoned before the event occurred. The spacecraft was instead pulled to safety by the secondary abort thrusters, which were added to the vehicle’s design in 1975 as a contingency and until now had never been used in a real-life scenario.

What Went Wrong?

But while the safe return of the crew was naturally the first priority for all agencies involved, the questions soon turned to the Soyuz itself. What caused the loss of the rocket? Is it a defect which could be present in the other Soyuz rockets currently under construction? Perhaps most importantly, when could the Soyuz fly again? As it’s currently the only way to put humans into space, the International Space Station is completely dependent on regular Soyuz flights, and a delay in the program could endanger the orbiting outpost.

Now, with the initial findings of the Russian incident investigation being made public, we’re starting to get answers on some of those questions. The official report so far agrees with the conclusions many “Armchair Astronauts” made watching the live stream of the launch, and the evidence suggests that the core issue is the same which doomed previous Russian vehicles.

Continue reading “Soyuz Failure Leaves Questions Unanswered”

The Negative Rail Explained

With the high availability of modular components and incredible wealth of information and tutorials online, it’s now easier than ever for hackers and makers to assemble complex electronic projects without getting bogged down with the theory behind it all. But the downside is that the modern electronic hobbyist often doesn’t have as deep an understanding of the low-level concepts that they would have if they had to build everything from scratch. This can be a problem when they try diagnosing and repairing faults, or when they start to branch out into reverse engineering.

Which makes “Building Blocks” by [David Christensen] a very compelling series. Every week he will be demonstrating a new circuit on his blog, complete with a plain English explanation of how and why it’s used. In this first installment of the series, he’s tackling a concept most of us have seen when poking around in more complex electronic devices, but maybe never really gave much thought to: the negative rail.

What exactly is the negative rail, anyway? It’s pretty easy to understand the positive rail in a circuit and its relation to ground; even multiple positive rails, such as in devices which use both 5 V and 3.3 V, are simple enough to wrap your head around. Unfortunately when something drops below that logical 0V reference, it isn’t quite as intuitive. But as [David] explains, the negative rail in a circuit is critical for dealing with bipolar signals, such as audio, which ride above and below the 0 V center point.

[David] goes over a few methods used to create the negative rail, from the classic center-tap transformer to using a buck-boost converter. But not content with just describing how these circuits work, he walks the reader through the creation of a charge pump circuit that you can drop into your next project if you find yourself in need of the elusive voltage. After explaining and diagramming it, he builds the circuit on a scrap piece of copper clad board and puts it through some benchmarks to prove it matches the theory he laid out.

If you’re in the mood for more negative talk, check out the battle our very own [Steven Dufresne] had with voltages of varying polarity when building his BB-8 robot.

All The Goodies You Need For Your RTL-SDR

When the RTL2832-based USB digital TV sticks were revealed to have hidden capabilities that made the  an exceptionally cheap software-defined radio receiver, it was nothing short of a game-changing moment for the home radio experimenter. The RTL might not be the best radio available, but remains a pretty good deal for only $10 from your favourite online supplier.

Having bought your RTL SDR, you will soon find yourself needing a few accessories. A decent antenna perhaps, an HF upconverter, and maybe an attenuator. To help you, [IgrikXD] has come up with a repository containing open-source implementations of all those projects and more. There’s an HF upconverter handily in both SMD and through-hole versions, as well as a wideband active antenna. A resonant antenna for a single band will always out-perfom a wideband device if your interest lies on only one frequency, but when your receiver has such a wide range as that of the RTL it’s irresistible to look further afield so the wideband antenna is a useful choice.

The RTL SDR is a device that just keeps on giving, and has featured innumerable times here since since its first appearance a few years ago. Whether you are into passive radar or using it to decode data from RF-equipped devices it’s the unit of choice, though we rather like it as a piece of inexpensive test equipment.

Via Hacker News.

Header image: Joeceads [CC BY-SA 4.0].