We always like finding new excuses reasons to use our test equipment, so we couldn’t help but be intrigued by this tip from [Joe Mosfet]. He uses the ever-popular Rigol DS1054Z to demonstrate the differences between a handful of brushless motors when rotated by his handheld drill at a constant RPM. Not only is he able to identify a blown motor, but it allows him to visualize their specifications which can otherwise seem a bit mystifying.
One wire from each motor is used as the ground, and channels one and two are connected to the remaining wires. Despite the DS1054Z having four channels, [Joe] is actually only using two of them here. The third channel being displayed is a virtual channel created by a math function on the scope.
After wiring them up, each motor got put into the chuck of his drill and spun up to 1430 RPM. The resulting waveforms were captured, and [Joe] walks us through each one explaining what we’re seeing on the scope.
The bad motor is easy to identify: the phases are out of alignment and in general the output looks erratic. Between the good motors, the higher the Kv rating of the motor, the lower voltage is seen on the scope. That’s because Kv in the context of brushless motors is a measurement of how fast the motor will spin for each volt. The inverse is also true, and [Joe] explains that if he could spin his 2450Kv motor at exactly 2450 RPM, we should see one volt output.
Beyond demonstrating the practical side of Kv ratings, [Joe] also theorizes that the shape of the wave might offer a glimpse into the quality of the motor’s construction. He notes his higher end motors generate a nice clean sine wave, while his cheaper ones show distortion at the peaks. An interesting note, though he does stress he can’t confirm there’s a real-world performance impact.
It’s not an entirely perfect Wrencher generator, as it has a lot of points to draw in the time available, resulting in a flickery Wrencher. (Update: take a look at the comments below, where he has posted an improved JSFiddle and advice on getting a better screen grab.) Thus the screen shot is an imperfect photograph rather than the usual grab to disk, for some reason the Rigol 1054z doesn’t allow the persistence to be turned up in X-Y mode so each grab only had a small part of the whole. But it draws a Wrencher on the screen, so we’re pretty impressed.
The piece that inspired this Wrencher can be found here. If you think you can draw one with a faster refresh rate, get coding and put it in the comments. We can’t promise individual coverage for each effort though, we’re Hackaday rather than Yet-another-scope-Wrencher-aday.
Oscilloscope art is a fascinating pursuit in which waveforms are generated for the X an Y channels of an oscilloscope to draw pictures on its screen. It’s somewhat distinct from vector computer graphics of the type you might see in older arcade machines or the Vectrex console, in that while it uses a similar approach to creating a display it has a very different purpose. Sometimes these works can be breathtakingly beautiful animations, and other times maybe not so much.
It’s an impressive piece of work that you can see in the video below or try for yourself, and your scribe’s Rigol was pressed into service to give it a go. After a bit of tweaking to find the right voltages and selecting slope triggering rather than edge triggering, we too were making squiggles appear on the screen.
Using a scope in X-Y mode is nothing new, of course. The technique is used to display everything from Lissajous patterns from an SDR to bouncing balls from an analog computer. Taken on as more of an exercise to learn how to use his new tool than a practical project, [bitluni]’s project starts by using two DACs on an ESP32 to create simple Lissajous patterns to learn about the scope’s controls. Next he built some code to display 3D point clouds, but learned that the native DAC code wasn’t up to the job. A little hacking improved the speed 27-fold, which was enough for great 3D images and live video from an I²S camera module. The latter was accomplished by grabbing frames from the camera and rendering them pixel by pixel, CRT style. The results are pretty clean, and there’s a lot to be learned about both using scopes as X-Y displays and tweaking the ESP32 for maximum performance.
When troubleshooting circuits it’s handy to have an oscilloscope around, but often we aren’t in a lab setting with all of our fancy, expensive tools at our disposal. Luckily the price of some basic oscilloscopes has dropped considerably in the past several years, but if you want to roll out your own solution to the “portable oscilloscope” problem the electrical engineering students at Cornell produced an oscilloscope that only needs a few knobs, a PIC, and a small TV.
[Junpeng] and [Kevin] are taking their design class, and built this prototype to be inexpensive and portable while still maintaining a high sample rate and preserving all of the core functions of a traditional oscilloscope. The scope can function anywhere under 100 kHz, and outputs NTSC at 30 frames per second. The user can control the ground level, the voltage and time scales, and a trigger. The oscilloscope has one channel, but this could be expanded easily enough if it isn’t sufficient for a real field application.
All in all, this is a great demonstration of what you can accomplish with a microcontroller and (almost) an engineering degree. To that end, the students go into an incredible amount of detail about how the oscilloscope works since this is a design class. About twice a year we see a lot of these projects popping up, and it’s always interesting to see the new challenges facing students in these classes.
What do a Rogowski coil, a magnetic core, and a hall effect sensor have in common? They are all ways you can make oscilloscope probes that measure current. If you think of a scope as a voltage measurement device, you ought to watch the recent video from Keysight Technology (see below). It is true that Keysight would love to sell you a probe, but the video is not a sales pitch, just general technical information about making current measurements with an oscilloscope.
Of course, you can always measure the voltage across a shunt resistor — either one that is naturally in the circuit or one you’ve put inline just for measuring purposes. But if you add a resistor it will change the circuit subtly and it may have to handle a lot of power.
The Keysight video points out that there are different probes for different current measurement regimes. High current, medium current, and low current all use different probes with different technologies. The video is only about 6 minutes long and if you’ve never thought about measuring current with a scope, it is worth watching.
The video shares some high-level details of how the current probes work — that’s where the Rogowski coil comes in, for example. Of course, you can’t expect a vendor to tell you how to build your own current probes. That’s OK, though, because we will. Current probes are often expensive, but you can sometimes pick up a deal on a used one.
We’ve seen plenty of oscilloscopes that look like repurposed cell phones. Usually, though, they only have one channel. The DS212, has two channels and a signal generator! [Marco] gives his review and a quick tear down in the video below.
The scope isn’t going to replace a big bench instrument, but for a portable scope with a rechargeable battery, it isn’t bad. The 1 MHz analog bandwidth combines with a 10 megasample per second front end and 8K of sample memory. The signal generator can produce basic waveforms up to 1 MHz. We were somewhat surprised the unit didn’t sport a touch screen, which is why you can see [Marco’s] fingers in the screenshot above. He seems to like the dual rotary encoder system the devices uses for navigation.
Where this really stands out is that it is open source for the the firmware running on the STM32 processor inside. We so rarely see this for commercially available bench tools and it makes this a fine hacking platform. It’s easy to imagine adding features like digital signals out and decoding digital data. It would be interesting to marry it with a WiFi chip and use it as a front end for another device over WiFi. Lots of possibilities. [Marco] shows that even though he’s not familiar with the STM32, he was able to add a custom waveform output to the device easily. This has the potential to be a custom troubleshooting platform for your builds. Lining up all of the sensing and signal generation settings for each specific type of test means you don’t need a guru to walk through the common failure modes of a product.