Products > Test Equipment

SDS1204X-E scope freezing when collecting waveform

<< < (6/11) > >>

bd139:
Mine always succeeds. I tried it up to 200.

But the moment you close the connection that's it.

Hence pointer fun.

bd139:

--- Quote from: 2N3055 on June 21, 2022, 02:41:13 pm ---I would prefer to gather quality info so Siglent can easily reproduce and fix the deficiency if there is one...

--- End quote ---

They have the info required:

1. The device that it's appearing on.
2. The software version
3. A test case that is reproducible by multiple people.

Now they need to:

1. Hook up a debugger to a scope
2. Run the same steps we have
3. Catch the crash in a debugger.
4. Work out what did it.

We can't do 3 and 4 because it's closed source.

Well we can but we can only speculate and use naughty disassembly tools and then wave our fists angrily.

Our bit is done.

bdunham7:

--- Quote from: AnarchistWolf on June 21, 2022, 02:30:33 pm ---Okay, so i have my trigger set a freq and im reading the waveform produced by a laser pulsing and some decay time.
Again maybe i dont understand this well enough but the scope is constantly being triggered on that freq. I am not stopping it and retriggering it every waveform capture.

(Unless its just doing that automatically and again im to new to know about it.)

--- End quote ---

OK, I have one of these scopes so walk me through exactly how you are setting it. 

The general idea is that there is a trigger event, then the scope performs one capture (one screen worth in the case of this model).  That trigger event can be simple or complex--if you press 'trigger setup' then 'trigger type' (left-most bottom button under screen) you'll see the available types.  The default is 'Edge' and unless you've changed it, that's what you are likely using. 

 If the scope is in 'Normal' mode, it will only perform a capture when there is a trigger.  'Auto' will perform a capture after a set interval if there is no trigger event--this is useful for setting the scope up initially, but captures like you are doing should always be done in the normal mode.  After the trigger event and capture, there is a short period before the scope can get its act together and be ready for another trigger.  It will ignore any trigger events during this retrigger time.  The holdoff setting increases this retrigger time to an arbitrary value that you select.  There are several reasons for doing this and it may or may not help with your issue.

AnarchistWolf:
I have the trigger setting in edge-falling, it is also set to auto.

I will mess around with the normal trigger mode and holdoff delay (I appreciate the suggestion).

Ill update you once I run a few tests.

Best,
W

AnarchistWolf:
Same problem occurs. I even set it to 500ms (Which is out of the range i need to work in). I did 50 captures and after it finished it froze the instrument.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod