Author Topic: Pausing and inspecting signals on USB oscilloscopes  (Read 979 times)

0 Members and 1 Guest are viewing this topic.

Offline midixTopic starter

  • Contributor
  • Posts: 46
Pausing and inspecting signals on USB oscilloscopes
« on: September 26, 2022, 02:51:45 pm »
Very likely, I'm doing something wrong or the software is designed badly.

I have OSC482 from Loto Instruments. Seemed like a decent scope for occasional experiments.

Now I'm trying to debug a practical problem (and learn as I go). There is a device sending MIDI protocol bytes. Essentially it's UART start-8-stop at 31250 baud rate.

The device is sending a byte 0xFE about every second.
I connected my scope to the optocoupler that receives the data. I could see something coming in, yay. But the data flashes by too fast. That's what the triggers are for, right? I can set a trigger, it will pause the input and then I preview it zooming and scrolling left & right. I had to fiddle a bit with the time division settings because the osc disables the trigger for some time values. Finally, I managed to enable the trigger, move its handle to the expected voltage (around 2V), set it to trigger on fall-off (because UART is high by default) and hit Single button to capture a packet.

I see it has been captured in the cache - there is a peak in the preview. But I cannot select it in any way to investigate in the main view! There seems to be no way to scroll the frozen view back in time nor any way to activate those cached frames and inspect them.



I know that OSC482 has software and not hardware trigger, so it can be inaccurate. But this time it seems mostly a software problem. I had to hit Single like a thousand times to finally get lucky and get a byte in the main view. At the same time, I see it did capture a byte in every small preview rectangle, I just cannot access them somehow.

Then I thought it would be easier to record a fragment and then inspect it... no luck, the recording seems to have the same problem - I cannot pause it and scroll to wherever I want (or scrolling could be hidden somewhere).

I also tried out UART decoding feature, setting all the parameters as needed (31250, start, 8 bytes, stop, no parity), but it did not yield any bytes. Maybe this function is not supposed to work with the analog probe.

This makes me consider upgrading to a better oscilloscope, but I'm not sure if it's worth it. OSC482 seems to be totally enough for me with its hardware specs. I wish there was alternative software for OSC482.
I don't have a place for a full-size scope and also I'm visually handicapped, so computer scopes are much more convenient for me. Analog Discovery 2 or PicoScope seem to be the safest choices, but they are a bit too pricey though.

Still, I'm wondering, how would the same scenario work with AD2 or PicoScope? Do other scopes have the ability to easily zoom / scroll the view back&forward in time after capturing a triggered signal (assuming the signal was captured with proper resolution)?
« Last Edit: September 26, 2022, 03:10:57 pm by midix »
 

Offline jwet

  • Frequent Contributor
  • **
  • Posts: 447
  • Country: us
Re: Pausing and inspecting signals on USB oscilloscopes
« Reply #1 on: September 26, 2022, 04:43:07 pm »
There is an open source scope software project called SigRok that might support your hardware.  Your particular scope is listed directly but there a lot of the USB scopes are pretty similar.  They also have an active forum where you could ask some questions about your hardware.  Might be a good place to start.  I used it for a multimeter interface a long time ago and it was pretty solid.  Good luck.
 

Offline ledtester

  • Super Contributor
  • ***
  • Posts: 3032
  • Country: us
Re: Pausing and inspecting signals on USB oscilloscopes
« Reply #2 on: September 26, 2022, 08:09:41 pm »
It appears there is someone from Loto Instruments on the forum -- see this thread:

https://www.eevblog.com/forum/testgear/how-to-promote-an-usb-oscilloscope-to-individual-engineers-i-am-the-loto-instru/

Also, on their web site: http://www.loto-ins.com/en/

there is an email address at the top which might be a source of help.

Update: Oh -- I see you're already aware of that thread!
 

Offline Gyro

  • Super Contributor
  • ***
  • Posts: 9410
  • Country: gb
Re: Pausing and inspecting signals on USB oscilloscopes
« Reply #3 on: September 26, 2022, 08:54:04 pm »
Wow, that UI sucks. Any chance of getting your money back?

It really would be worth trying to get it running under Sigrok Pulseview (if not).


Edit: It looks as if it is planned... https://sigrok.org/wiki/Loto_OSC802 (at least the 802, it may be worth submitting a request).
« Last Edit: September 26, 2022, 09:04:16 pm by Gyro »
Best Regards, Chris
 

Offline midixTopic starter

  • Contributor
  • Posts: 46
Re: Pausing and inspecting signals on USB oscilloscopes
« Reply #4 on: September 26, 2022, 09:22:13 pm »
Unfortunately, my dispute time on Aliexpress is over. And, technically, there's not much to complain about - it's working as advertised, it's just not working the way I imagined it should.

That sigrok wiki page hasn't been updated for almost 3 years, so I don't have much hope. However, I see Loto updating their own software sometimes, so maybe they will improve it one day.
 

Offline james_s

  • Super Contributor
  • ***
  • Posts: 21611
  • Country: us
Re: Pausing and inspecting signals on USB oscilloscopes
« Reply #5 on: September 26, 2022, 09:56:54 pm »
I've never liked UIs that try that hard to emulate a physical device. You end up with the worst of both worlds, trying to operate an emulated knob with a mouse pointer is like trying to operate a real one with a stick.
 

Offline thm_w

  • Super Contributor
  • ***
  • Posts: 6272
  • Country: ca
  • Non-expert
Re: Pausing and inspecting signals on USB oscilloscopes
« Reply #6 on: September 26, 2022, 09:58:19 pm »
For MIDI decoding, likely better off getting a $10 USB logic analyzer that is compatible with sigrok. If your budget is not that high.
Of course, good to have both LA and scope in some cases.

I've never liked UIs that try that hard to emulate a physical device. You end up with the worst of both worlds, trying to operate an emulated knob with a mouse pointer is like trying to operate a real one with a stick.

Yeah I see no need for the vitual knob, unless its for VERY senile EE's that can only use an analog scope or something.
Probably best to just copy what Picoscope does, left/right arrows and a dropdown box.
« Last Edit: September 26, 2022, 10:00:14 pm by thm_w »
Profile -> Modify profile -> Look and Layout ->  Don't show users' signatures
 

Offline midixTopic starter

  • Contributor
  • Posts: 46
Re: Pausing and inspecting signals on USB oscilloscopes
« Reply #7 on: September 27, 2022, 06:56:13 am »
Loto replied on Youtube. It turns out, you have to hit Stop device button and then, finally, those PC cache thumbnails become available and you can scroll the signal into view. A bit convoluted, but it works. As I understand, that's mostly necessary only for their lower-end models with software triggers because those fail to "focus" the signal into the main view. But even with a properly focusing trigger you might want to be able to scroll a long signal, and then you have to stop the device.

I agree with the concept that it's not good to emulate physical UIs because what works well in the physical world is not that convenient on a computer. For example, turning a knob feels natural in the physical world, but on a PC it's a bit awkward mouse gesture. Sliders feel much better for the purpose.

I just tried Picoscope and Analog Discovery software in Demo mode. I liked Picoscope 7 (Early Access) better because it's more intuitive. In the very first minute, I understood what I'm doing and what's the meaning of most of the controls, and how to zoom and pan the signal.
With AD Waveforms it felt somewhat more convoluted. You have to figure out what those unnamed dropdowns do, and some of them change the functionality of other dropdowns and buttons. Of course, Waveforms is powerful and it can be a great tool for a person who is using it daily and has "muscle memory" for it, but Picoscope might be better for occasional users who want to immediately recognize all the controls.

For MIDI decoding, likely better off getting a $10 USB logic analyzer

Yup, I have a cheap logic analyzer. But this time I suspected one of the devices in my chain is generating dirty square waves or baud rate might be a bit off, so I wanted to inspect the health of the signals with an analog scope first.
« Last Edit: September 27, 2022, 07:03:06 am by midix »
 

Offline midixTopic starter

  • Contributor
  • Posts: 46
Re: Pausing and inspecting signals on USB oscilloscopes
« Reply #8 on: September 27, 2022, 11:26:28 am »
I found a detailed user manual for Sainsmart DS series which is rebranded LOTO.

Here's how it's supposed to work officially:

Quote
9.2.4 Waveform buffer and left/right shift
When the acquisition is paused, the slider of the waveform memory buffer appears in the lower
right corner of the waveform area. This slider shows the ratio and the position of the waveform
data currently displayed on the screen, related to the size of the entire data buffer. The entire
length of the slider represents the entire data buffer. The position and length of the light slider
represents the data block displayed in the current drawing area relative to the entire data buffer.
The length of the light slider can be used also to understand the ratio between the display data
respect the total acquired data.
With the mouse you can drag the slider left and right in the entire data buffer, to show new
areas of interest. Another way to move within the memory buffer is to use the left and right arrow
keys of the keyboard. ( Shortcut key(Ctrl + <-) / (Ctrl + ->) - Waveform move between left and
right).

So, not the most convenient thing but at least possible when you manually stop the device every time after it has hit a Single trigger.
 

Offline midixTopic starter

  • Contributor
  • Posts: 46
Re: Pausing and inspecting signals on USB oscilloscopes
« Reply #9 on: September 27, 2022, 12:12:08 pm »
So finally it works, and I even can use UART decoder with custom baud rate on the analog probe. Nice.

And now I see what's wrong with my setup - for some reason, it matches twice the expected baud rate - I can decode the actual byte AA I'm sending only when I set baud rate 62500 and not 31250, as needed by MIDI. Ouch, one of my Arduinos it ticking too fast, very likely it got confused with the fuses and the crystal frequency.
 

Offline thm_w

  • Super Contributor
  • ***
  • Posts: 6272
  • Country: ca
  • Non-expert
Re: Pausing and inspecting signals on USB oscilloscopes
« Reply #10 on: September 27, 2022, 09:58:53 pm »
For MIDI decoding, likely better off getting a $10 USB logic analyzer

Yup, I have a cheap logic analyzer. But this time I suspected one of the devices in my chain is generating dirty square waves or baud rate might be a bit off, so I wanted to inspect the health of the signals with an analog scope first.

LA will tell you if baud rate is a bit off in this case, since LA sample rate is up to ~20MHz.
Its also easy to drop in horizontal measurement and it will show you the frequency (baud) of the signal at the top. Although I'm sure this Loto tool can do the similar, since you showed it with measurements at the bottom already.

But yeah, noisy signals you'd want scope.
Profile -> Modify profile -> Look and Layout ->  Don't show users' signatures
 

Offline vk6zgo

  • Super Contributor
  • ***
  • Posts: 7563
  • Country: au
Re: Pausing and inspecting signals on USB oscilloscopes
« Reply #11 on: September 28, 2022, 12:14:40 am »
I've never liked UIs that try that hard to emulate a physical device. You end up with the worst of both worlds, trying to operate an emulated knob with a mouse pointer is like trying to operate a real one with a stick.

An excellent description of the problem!

I, from time to time, use a remote ham transciever (just for reception, so far, as I don't trust the microphone on the laptop).
Attempting to turn the emulated VFO knob is very frustrating for that same reason.
They do, at least offer the option of clicking to change the frequency by various increments.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf