Products > Test Equipment
Oscilloscope Zoom Out Quirk
<< < (71/113) > >>
tautech:

--- Quote from: Elasia on June 13, 2020, 09:13:16 pm ---
--- Quote from: tautech on June 13, 2020, 09:06:47 pm ---
--- Quote from: jemangedeslolos on June 13, 2020, 04:57:10 pm ---Now that the whole world has discovered the scope, his pros and cons, Siglent will release a corrective firmware.
Everyone will be amazed by Siglent, the speed of the brand to take into account demands from its customers and they will not be able to manufacture enough.

--- End quote ---
Where have you been ?  :-//
They can't produce enough of these already as members here will attest by sourcing any they could find from all over the world.
It's price point, feature set and core specs identified it was to be a strong contender in the DSO market even before release.

The only worry is how any zoom out feature might be implemented for those having trouble to adapt the existing tool set as it could possible impact on the features already available. We don't want that.

--- End quote ---

Why i keep saying it should just be a saved option setting to make it run in the mode you want.. they already got a large established universe so that would make no sense to make it default

--- End quote ---
There's good reason why Run mode memory depth is managed, to retain high throughput and reduce blind time.

Stop/captures are different and to enable larger captures the memory needed may have to be reassigned from other features......and maybe to their detriment.  :-//
Accommodations should only be made if datasheet specifications will not be impacted upon.


--- Quote from: jemangedeslolos on June 13, 2020, 09:26:54 pm ---...................
Sorry I was too busy setting my scope mem depth manually and play with horizontal window all day long  8)
...............

--- End quote ---
Navigate can help with that.  ;)
Elasia:

--- Quote from: tautech on June 13, 2020, 09:41:13 pm ---
There's good reason why Run mode memory depth is managed, to retain high throughput and reduce blind time.

Stop/captures are different and to enable larger captures the memory needed may have to be reassigned from other features......and maybe to their detriment.  :-//
Accommodations should only be made if datasheet specifications will not be impacted upon.


--- End quote ---

Step back a minute and think about it... what is the scope doing when you are in split screen zoom mode? You have the zoom area at your target resolution and its buffering the rest of the data so you can zoom out and see more if you choose

Now... what is wanted is the ability to be at your target resolution but be able to change your timebase to zoom out but without actually 'activating' zoom mode.  How do you do this? Activate zoom mode and hide the horizontal scroll bar, remove other zoom UI components.  Now what happens when someone changes to a higher timebase? it zooms out because it has the buffered data from someone saying they want more memdepth at a lower timebase...

Like i keep saying.. this is all UI illusion bits now with just how people want to use it.. it already has the power to do it because... IT ALREADY DOES IT!  Less for some weird reason that wouldn't work? I cant think of one anyway to fret over so really its just waiting for someone to prioritize such a thing and build the UI out for it as a second layout for zoom mode
nctnico:

--- Quote from: tautech on June 13, 2020, 09:41:13 pm ---
--- Quote from: Elasia on June 13, 2020, 09:13:16 pm ---Why i keep saying it should just be a saved option setting to make it run in the mode you want.. they already got a large established universe so that would make no sense to make it default

--- End quote ---
There's good reason why Run mode memory depth is managed, to retain high throughput and reduce blind time.

--- End quote ---
But that isn't always needed and deep memory is much more helpful to get certain measurements done. Waveforms/s doesn't matter if there is 5 minutes between a trigger anyway. I don't get why people keep obsessing over waveforms/s and blind time. For many kinds of measurements these don't even matter.

And added to what Elasia says: what if you want full memory depth and view a signals at 2 different points / using 2 different time/div settings? If you need to use the zoom window for force full memory you are losing the function zoom mode is intended for. In which world is that an improvement?
tautech:

--- Quote from: Elasia on June 13, 2020, 10:26:27 pm ---
--- Quote from: tautech on June 13, 2020, 09:41:13 pm ---
There's good reason why Run mode memory depth is managed, to retain high throughput and reduce blind time.

Stop/captures are different and to enable larger captures the memory needed may have to be reassigned from other features......and maybe to their detriment.  :-//
Accommodations should only be made if datasheet specifications will not be impacted upon.


--- End quote ---

Step back a minute and think about it... what is the scope doing when you are in split screen zoom mode? You have the zoom area at your target resolution and its buffering the rest of the data so you can zoom out and see more if you choose

Now... what is wanted is the ability to be at your target resolution but be able to change your timebase to zoom out but without actually 'activating' zoom mode.  How do you do this? Activate zoom mode and hide the horizontal scroll bar, remove other zoom UI components.  Now what happens when someone changes to a higher timebase? it zooms out because it has the buffered data from someone saying they want more memdepth at a lower timebase...

Like i keep saying.. this is all UI illusion bits now with just how people want to use it.. it already has the power to do it because... IT ALREADY DOES IT!  Less for some weird reason that wouldn't work? I cant think of one anyway to fret over so really its just waiting for someone to prioritize such a thing and build the UI out for it as a second layout for zoom mode

--- End quote ---
Way ahead of you on this.......any capture first needs available memory .......but it's already assigned for post trigger History !
Zoom out capture memory depth requirements cannot grab memory from thin air...it's already being used...post trigger !
So to implement capture zoom out another memory management strategy need be developed and this is being discussed privately.

Got a clever plan, we're all ears.  :popcorn:

maginnovision:
I guess we can thank Dave, might have standard memory management and options on siglents newer scopes at some point. God knows the salesman who was telling us we don't know how to use oscilloscopes didn't make anything happen.

I'm also not sure what's supposed to be so difficult with implementation. You already have a buffer for the waveform of variable(based on sample rate and capture time) size, you just need to implement it with a fixed, user selectable, size. Seems like something you could hack together pretty quick. How is x segments of y size any different than having x segments of y size?
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod