Thanks for the answer. Unfortunately I am not even able to make it work in the official PicoScope6 software. I tried a lot of combinations. The window pulse width you mentioned above didn't do the job.
Hi, I was partially successful. But I realized that I have to tell the whole truth about the task: After the pico was triggered I would like to send out a signal with the waveform generator (wfg). This does work with one constraint, the signal (from wfg) is send AFTER the input signal is back to zer...
Hi y'all, having my C++ code using the advanced trigger works wonderful since two years. Now I would like to extend it using the pulse width qualifier settings. The attached picture describes what I expect to achieve: - Picoscope PS6404D - negative signal on channel A - if signal stays under thresho...
Can you estimate when there might be a fix available? If it is measured in days or in weeks would be fine already. Based on your answer I would implement the workaround or leave it and wait.
Dear all, I need to use four picoscopes 6404D in a C++ written program. A lot of development has already happend but using picoscopes 6403 for that because the 6404Ds have been used elsewhere. So far everthing worked fine. Today I got the 6404Ds and I figured out the following. I try to explain by u...
It does not make sense if the error in the sampling rate is really 2ppm and not more, and this is the question. Showing you the entire code would not make sense. Actually the pico-settings are set as in the Labview examples which are coming with the SDK. The system is not turned off in consecutive d...
Well, I'm not using the Picotech Software, but the Labview SDK. The data was taken during the SuperKEKB commissioning a while ago and just recognize this while analyzing the data. To give you an idea: a pico 6404D has been in use and we measured circulating particle bunches in the SuperKEKB collider...
Dear all, I use a Pico 6404D to record 1 million samples in block mode with 0.8 ns sampling rate. Now, the signals in my waveform have a design distance of 9.838 us, but with my Pico I measure a distance of 10.060 us. This means I am off by 222 ns. To explain this, I checked the data sheet and found...