Why normal block mode?

Post your C and C++ discussions here
Post Reply
heng
Newbie
Posts: 0
Joined: Mon Jun 11, 2012 7:08 pm

Why normal block mode?

Post by heng » Thu Jul 05, 2012 1:04 pm

Reading the programming manual, there is some discussion about the rapid block mode versus the block mode. The suggestion is that if you can't do with the several tens of ms delay in setting up the block mode, then you should use the rapid block mode.

My question is, why would I ever use the normal block mode? Does it provide something that the rapid block mode does not?

Martyn
Site Admin
Site Admin
Posts: 3333
Joined: Fri Jun 10, 2011 8:15 am
Location: St. Neots

Re: Why normal block mode?

Post by Martyn » Thu Jul 05, 2012 1:23 pm

Block Mode will capture one block of data to the scopes memory before transferring it to the PC. The available memory is used for the single block and gives a higher horizontal resolution.

Rapid Block Mode captures a number of blocks of data to the scopes memory before downloading these to the PC. The available memory is shared between the blocks therefore limiting the horizontal resolution.
Martyn
Technical Support Manager

heng
Newbie
Posts: 0
Joined: Mon Jun 11, 2012 7:08 pm

Re: Why normal block mode?

Post by heng » Thu Jul 05, 2012 2:41 pm

If ps3000aSetNoOfCaptures is set to 1, or ignored, and ps3000aMemorySegments is set to 1, is there any fundamental difference between the 2 modes?

Martyn
Site Admin
Site Admin
Posts: 3333
Joined: Fri Jun 10, 2011 8:15 am
Location: St. Neots

Re: Why normal block mode?

Post by Martyn » Fri Jul 06, 2012 7:30 am

Fundamentally those two modes are the same
Martyn
Technical Support Manager

heng
Newbie
Posts: 0
Joined: Mon Jun 11, 2012 7:08 pm

Re: Why normal block mode?

Post by heng » Fri Jul 06, 2012 3:53 pm

Ok, thanks. Might I suggest that such a note is put in the documentation? I spent a little while thinking about this and it would have been helpful to have the docs tell me.

Post Reply