USB oscilloscope for troublshooting?

That depends on the scan rate: when I used mine to measure battery state I ran the scan slowly enough the stretch the recovery signal across 30% or so of the scan, so the time for the scan to cross the screen was around 20 - 40 mS, and I fiddled with the scan trigger so that the voltage drop as the solenoid pulled in triggered a single shot scan,

I think most 'scopes can be set to this triggering mode and low scan speed, though its quite understandable that you'd not be familiar with this way of using a scope if you've never needed to observe such relatively slow events.

My scope's minimum scan speed is 200 mS/division, or 2 seconds to cross the whole screen, so I'd have been running it at 10-15 ms/division to do the battery condition check.

It helps to turn the brightness up enough that the whole scan is done before the image fades.

FWIW the triggering device was a timer used to 'dethermalise', i.e. bring down, a gliding model aircraft if it was still flying after a preset time, typically three minutes after a switch on the towhook was last operated as the model was launched from the top of its towline, so I set that to 6 seconds (its smallest interval) during battery testing. The battery being checked was a 4-5 cell NiCd used to drive the timer.

To see a trace, I simply flipped the towhook to start the timer and 6 seconds later the timer tripped and my scope drew a single trace across the screen, which was easily visible long enough to see the shape of the voltage drop and recovery and to measure the depth of the drop.

--
Martin    | martin at 
Gregorie  | gregorie dot org
Reply to
Martin Gregorie
Loading thread data ...

You can do that kind of thing, but you're limited by the sample rates and input range of the microcontroller, and also by the output bandwidth. For example you could make something to sample via an ADC pin and squirt out over SPI, but you need to worry about not dropping samples because the output is busy, and you also won't see any voltage that's too low or too high. For example in a power supply situation you might be worried about negative voltages or spikes above the power rails, which the ADC won't capture. Also the ADC resolution is typically low if you're running at high speeds. This is where a proper scope comes in handy.

If it's all you have and you don't have major demands, by all means give it a try.

Theo

Reply to
Theo

On Thu, 22 Apr 2021 04:44:10 -0000 (UTC), bob prohaska declaimed the following:

If you are willing to change platform, you might find more candidates...

formatting link
Unfortunately, that one only goes up to 1kHz -- didn't check for Windows vs Linux

formatting link

100kHz, but may be too heavily tied to Windows for display purposes

formatting link

2 channel but with its own display

formatting link
single channel

--
	Wulfraed                 Dennis Lee Bieber         AF6VN 
	wlfraed@ix.netcom.com    http://wlfraed.microdiversity.freeddns.org/
Reply to
Dennis Lee Bieber

I've got a bottom of the range Picoscope, and I'm very pleased with it. This thread prompted me to search for the Hantek 6022, which seems to cost a similar price to the Picoscope, but Picoscope has faster sample rates and a wider range of input sensitivities, so, in my estimation, it's better value for money than the Hantek.

But it all depends on what specification you need, and what compromises you're willing to make, money being one of them.

David

Reply to
David Higton

I'm impressed. Downloaded the tarball and had it built in a few minutes on an 8GB Pi4 running raspberrypi 5.10.17-v7l+ #1403 SMP Mon Feb 22 11:33:35 GMT 2021. Run without installing it reports:

bob@raspberrypi:~/OpenHantek-openhantek-e7e0c7b $ ./build/openhantek/OpenHantek libEGL warning: DRI2: failed to authenticate qt5ct: using qt5ct plugin QEGLPlatformContext: Failed to create context: 3009 libpng warning: iCCP: known incorrect sRGB profile BlueALSA detected - Disabling audio sandbox libEGL warning: DRI2: failed to authenticate

Not sure how important the errors are, I didn't install, nor mess with the devd permissions. It doesn't seem to recognize demo mode, has the flag option changed? I'd like to see the demo mode before running out and buying hardware.

Are there any other tests worth doing before buying some hardware?

Thanks for writing!

bob prohaska

Reply to
bob prohaska

That would work, but it's a bit more work than I wanted to tackle. I'm no programmer, by any stretch, and making front ends for A/D coverters isn't entirely simple, either. A sound capture device contains at least anti-aliasing filters, I'll have to add only attenuators.

At the moment the Hantek 6022 is looking rather promising.

The openhantek software compiled easily on the Pi4, but it won't run demo mode for some reason. I'd like to get a look at that before buying hardware.

Thanks for writing,

bob prohaska

Reply to
bob prohaska

Sorry, hit send by accident.

I can't help really, openhantek was in the sid repository so I just installed it with apt. I assume it is no longer maintained, as the Debian package database claims never to have heard of it. Probably best avoided then.

I haven't used it for a while, and it's not a problem as I need to maintain a portable Windows machine for a number of reasons, of which this scope was one. I have other niche hardware for which only Windows will do. And no, I'm not going to try Wine, I've had a go with it in the past, and it has always seemed rather flaky when dealing with unusual peripherals and fairly high speeds. I assume that programmers of the Windows drivers tend to cut corners.

--
Joe
Reply to
Joe

Xoscope just listens in on the audio stream, so if other ALSA audio programs work, it will too.

These sorts of adapters are cheaper and also work on the Pi (I've used one the same as this, but only the audio output):

formatting link

It even works on a old Linux installation via OSS (again only tested output).

Fair enough, your power supply monitoring is more of a data logging application anyway. Possibly the slowest speed setting on a CRO combined with a video recording of the screen would work. You'd need to have all the settings worked out fairly well though and that would be a hurdle for a first-timer.

--
__          __ 
#_ < |\| |< _#
Reply to
Computer Nerd Kev

One from bitscope?

formatting link

My operational area was protocol analyzing and the smallest (micro) worked well for me.

--
 Gerhard Reithofer - Techn. EDV Reithofer - http://www.tech-edv.co.at
Reply to
Gerhard Reithofer

Just got the DIGITNOW audio capture device. Audacity finds it without trouble and displays AC hum on the VU bargraph, so I'm pretty sure the hardware works. Dmesg reports [2795922.290892] hid-generic 0003:2034:0105.000A: input,hidraw3: USB HID v1.00 Device [Generic USB Microphone] on usb-0000:01:00.0-1.4/input2

and lsusb -t reports

/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 3: Dev 3, If 0, Class=Hub, Driver=hub/3p, 12M |__ Port 1: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 1: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 6, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 4: Dev 9, If 1, Class=Audio, Driver=snd-usb-audio, 12M |__ Port 4: Dev 9, If 2, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 4: Dev 9, If 0, Class=Audio, Driver=snd-usb-audio, 12M The device file corresponding to the sound capture device is /dev/hidraw3

However, xoscope looks for signal at /dev/comedi0, which isn't created. There's a dialog box which seems to invite device selection, but the only choices are NONE and COMEDI.

If I try something like sudo xoscope hidraw3 xoscope runs but says it can't read hidraw3.

It looks as if I'm either bungling the commandline syntax or the device filename. Or, maybe some intermediate software is required. Comedi manpages are present, but there don't seem to be any related executables.

If anybody's got a hint please post!

Thanks for reading,

bob prohaska

Reply to
bob prohaska

From the README:

"* You will need (optionally?) the ALSA and COMEDI libraries. If any (or all) of these libraries are absent, xoscope will build without that library's input capability.?"

If you compiled it yourself, maybe it didn't find the ALSA library on your system and built without ALSA support? If you didn't compile it yourself, well maybe you should...

"xoscope -h" should display the available options, "-A" is supposed to select the ALSA sound device (default is "default" - I'm not sure whether ALSA always automatically sets a "default" sound device).

--
__          __ 
#_ < |\| |< _#
Reply to
Computer Nerd Kev

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.