search

fair-acc / gr-digitizers

GNU General Public License v3.0
3 stars 3 forks source link

Bug when running ps3000 scope with < 500mV Range in Rapid Block mode #79

Closed alexxcons closed 1 year ago

alexxcons commented 3 years ago

Seens on dal005 (schottky system)

Triggering is done, samples are passed to the sink/client, but all samples are 0, the CPU load goes up and event-matching fails (only ~30 matched events)

500mV Range seems to work fine.

Reproducer:

Edit: Attached reproducer. Possible the concrete type of the ps3000 scope matters

According to scope manual, ± 100 mV to ± 20 V in 8 ranges should work. (For 3224 and 3424 : ± 20 mV to ± 20 V in 10 ranges) <-- What exact scope do we use ? Does the software consider the difference ? Possibly that diference matters !

Very confusing is, that the Digital Port is influenced by the Range-Value picked for the analog ports.

dal005.grc.zip

alexxcons commented 2 years ago

Possibly related to https://github.com/fair-acc/gr-digitizers/pull/98

RalphSteinhagen commented 2 years ago

[..] no pre-trigger samples [..]

You need a few samples before, otherwise you won't be able to see the rising trigger edge which technically lies on sample number '0' (or '-1').

alexxcons commented 2 years ago

[..] no pre-trigger samples [..]

You need a few samples before, otherwise you won't be able to see the rising trigger edge which technically lies on sample number '0' (or '-1').

Haha, that looks like it was a "problem sitting in front of screen" usecase :P I will re-test when I have time !

alexxcons commented 1 year ago

Haha, that looks like it was a "problem sitting in front of screen" usecase :P I will re-test when I have time !

Cannot reproduce this issue any more. The above reproducer .grc runs/triggers fine now on dal004 and dal005 (both 3403DMSO scopes). The use-case 'no pre trigger samples' not even seems to be a problem.

I went down to just having a single trigger-sample .. still works fine.

No idea what I tested before --> closing the issue.