Verbose prints during runBlock and getRapidBlockData

Post your MATLAB discussions here
Post Reply
DaveC
Newbie
Posts: 0
Joined: Wed Mar 03, 2021 4:29 pm

Verbose prints during runBlock and getRapidBlockData

Post by DaveC »

I'm using the 5444D to capture data and both the runBlock and getRapidBlockData calls are generating lots of command window printouts. Here are the code and command window printouts. Also it appears that the runBlock call waits around for the scope to trigger. How do I suppress the printouts and poll for the capture completion?
CODE %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
stat = invoke(picoBlk,'ps5000aIsReady');
if (stat == 0)
start = 0;
seg = 0;
display('A');
tic;
[nSamp ovr, chA, chB, chC, chD] = invoke(picoBlkR, ...
'getRapidBlockData',picoCfg.numCapt,picoCfg.dnSamp, ...
picoCfg.dnMode);
toc;
display('B');
tic;
picoCalc;
toc;
display('C');
pause(0.1);
end
if (etime(clk,captureStart) >= captureDelay) %if capture timer done
display('X');
tic;
stat = invoke(picoBlk,'runBlock',0);
toc;
display('Y');
captureStart = clk;
end
end
PRINTOUT %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
A
getRapidBlockData: Setting up data buffers...
getRapidBlockData: Retrieving data...
getRapidBlockData: Retrieving digital port data and assigning to port array.
getRapidBlockData: Converting to millivolts and assigning to channel array.
getRapidBlockData: Data succesfully retrieved.
Elapsed time is 0.044853 seconds.
B
Elapsed time is 0.028395 seconds.
C
X
runBlock:- Collecting block of data:
Timebase: 14
Pre-trigger samples: 128
Post-trigger samples: 896
runBlock: Waiting for device to become ready...
runBlock: Device ready.
Elapsed time is 0.022967 seconds.
Y

Post Reply