Test and Measurement Forum

The C code uses API calls that are different from the ones in the original LabVIEW example. Do you have a LabVIEW example of Rapid Block Mode?
thx.
Laurent

PS: do you have a skype # please. This is very inefficient to advance on this by posts. Thx. You can email it directly. Thx.

The rapid block Labview example is posted on this thread. As mentioned, it uses multiple calls to ps4000GetValueBlock. The C example uses a single call to ps4000GetValueBlock. Both ways are valid and achieve the same result.

As per earlier conversation, the LabVIEW example you mention uses multiple API calls. This may be valid but it is not what we want to achieve. It is expected that multiple calls will generate more overhead both in the call and in the data stream resulting in more time for data transmission from the digitizer to the PC than a single call. I am not proficient in C enough to decipher the details of the code. What I can see is that the functions calls in the C code are different from the ones in the LabVIEW example that uses the "API Call-2" version of "API Call". It seems to me that since it is a LabVIEW thread, support should be made with LabVIEW solutions.
Thx.

Thank you Mr Robin, your Rapid Block mode for 4000 series, I can changed to 5000 series.



Eka

Dear Mr Robin,


I am succes convert rapid block 4224 to 5203 with convertion dll and wrap file. But I have a problem, I cannot recive 2 CH1, only ch1 was found. Could you give me information to resive all the chanel in the same time.


Best Regard,


ekawaldi

Hi

The 4000 example works for two channels, so it should be straightforward to get both channels working for the 5000.

What exactly are you having problems with?

Robin

Hi Robin,
I am just following up your comments to capture trigger times in rapid block mode for PS4000?
Is this correct that PS4000 is not capable to capture the
elapsed time between each trigger event (or resulting block/waveform) in rapid block mode? if so, what does "ps4000GetValuesTriggerChannelTimeOffsetBulk64" do?
according to the manual this function is designed to capture the time each trigger for each individual waveform occurred. is this correct?
I got confused,

/p

The ps4000GetValuesTriggerChannelTimeOffsetBulk64 function is used to calculate the deviation of the trigger time from the sample time, in order to eradicate jitter.

The way of achieving what you need to do would be to use a system timer such as GetTickCount in the CallBack function, to get the tick count on the first and last trigger, then calculate the elapsed time from there.

Hello Chris!

I have just made this same question in another post, but just in case you may recieve it faster replying here, there it goes again...

I am having some similar problem to the one described here.

I am working with a PicoScope PS 5203, so that the API I am using is "PS5000", but I guess it should work in a similar way to the PS4000.

I want to retrieve the time offset between trigger times and the first sample in its memory segment (Rapid Block Mode). My aim is to reduce the effect of the jitter, which is a mayor problem in our application.

To do this I am using the function "ps5000GetValuesTriggerTimeOffsetBulk64". The function seems to work fine, but all I get in response in the "times" field are zeros.

An important thing: I am using AN EXTERNAL TRIGGER signal. Is there any problem with this?

I see in the description of "ps5000GetTriggerTimeOffset" that this does not work with the external trigger, and I am starting to think that the same condition may apply to "ps5000GetValuesTriggerTimeOffsetBulk64".

Thanks in advance for your time,

Mikel