PicoScope 7 Software
Available on Windows, Mac and Linux
3206D does not show real time data
3206D does not show real time data
Hi,
I am using pico 3206D .I want to trigger the device using a extarnal trigger and want to measure a high frequency pulse (500MHz).What i think i could not capture the real time data.may be there is some time duraton delay between trigger occur and capturing.I want to capture a single wavefrom with a single memory segment .
my API calling sequence is
setting external triiger..channel and other staff then
ps3000aRunBlock(....)
while (true) {
ps3000aIsReady(handle_s, &is_ready_s);
if (!is_ready_s) {
_sleep(timeIndisPosedMS_s * (1e-9));
} else if (is_ready_s)
break;
}
SetDataBuffer(...)
ps3000aGetValuesBulk(..);
Stop(handle_s);
but if i chose 50us timebase in the main pico6 softwere and my application i got some missmaching in the wavefrom except the voltage level and i did not found any triiger point in my written softwere also.What will the possible solution.Thank in advanced.
I need exactly how the picture (attusted) is!
I am using pico 3206D .I want to trigger the device using a extarnal trigger and want to measure a high frequency pulse (500MHz).What i think i could not capture the real time data.may be there is some time duraton delay between trigger occur and capturing.I want to capture a single wavefrom with a single memory segment .
my API calling sequence is
setting external triiger..channel and other staff then
ps3000aRunBlock(....)
while (true) {
ps3000aIsReady(handle_s, &is_ready_s);
if (!is_ready_s) {
_sleep(timeIndisPosedMS_s * (1e-9));
} else if (is_ready_s)
break;
}
SetDataBuffer(...)
ps3000aGetValuesBulk(..);
Stop(handle_s);
but if i chose 50us timebase in the main pico6 softwere and my application i got some missmaching in the wavefrom except the voltage level and i did not found any triiger point in my written softwere also.What will the possible solution.Thank in advanced.
I need exactly how the picture (attusted) is!
- Attachments
-
Re: 3206D does not show real time data
Hi Anik86p,
The Bandwidth of the PicoScope 3206D is 200MHz, This means that pure sinewaves of 500MHz will be beyond what the PicoScope can capture according to its specifications, and therefore Pulses of 500MHz will be way beyond what the PicoScope is capable of capturing (see the information under 'Bandwidth' here: https://www.picotech.com/library/applic ... e-tutorial).
Are you sure you meant 500MHz? When did you buy the PicoScope?
Regards,
Gerry
The Bandwidth of the PicoScope 3206D is 200MHz, This means that pure sinewaves of 500MHz will be beyond what the PicoScope can capture according to its specifications, and therefore Pulses of 500MHz will be way beyond what the PicoScope is capable of capturing (see the information under 'Bandwidth' here: https://www.picotech.com/library/applic ... e-tutorial).
Are you sure you meant 500MHz? When did you buy the PicoScope?
Regards,
Gerry
Gerry
Technical Specialist
Technical Specialist
Re: 3206D does not show real time data
thank you for the reply ,but it works fine with the picoscope 6 softwere,may be i did some internal calculation wrong.I sent you an text file where is my test code .My UI show real voltage measurement example ,a DC battery nicely but can not capture real time fast moving data measurement.I am trying to capture a simple wavefrom in a specifiq time like 50us from a Power Amplifier (Frequency
0.001 to 500 MHz) with a external trigger .the trigger works but it seems there is a delay between the trigger occur and the data capture .may be here the real data missed out and i get noice.i sent a photo what i sometime got with a low timebase!Please give me a idea how i can solve th issau
0.001 to 500 MHz) with a external trigger .the trigger works but it seems there is a delay between the trigger occur and the data capture .may be here the real data missed out and i get noice.i sent a photo what i sometime got with a low timebase!Please give me a idea how i can solve th issau
- Attachments
-
-
- pico_demo.txt
- (871 Bytes) Downloaded 416 times
Re: 3206D does not show real time data
Hallo,
Somehow my previous problem is solved but not 100%.I have a simple question on the two API.
PICO_STATUS ps3000aGetTimebase
(
int16_t handle,
uint32_t timebase,
int32_t noSamples,
int32_t * timeIntervalNanoseconds,
int16_t oversample,
int32_t * maxSamples,
uint32_t segmentIndex
)
PICO_STATUS ps3000aRunBlock
(
int16_t handle,
int32_t noOfPreTriggerSamples,
int32_t noOfPostTriggerSamples,
uint32_t timebase,
int16_t oversample,
int32_t * timeIndisposedMs,
uint32_t segmentIndex,
ps3000aBlockReady lpReady,
void * pParameter
)
In this two API the timebase value should be same?
In my application i calculate timebase depanding on total interval i need.
my timebase_calculation formula: const uint32_t time_base_r = (range_.magnitude() * 125) + 2;//**here range_ in micro format.Example for a 50 us reading my timease will be 6252**
But the problem is if i apply the same time base value on the two API i did not get any value.
But if i set any timebase value only ps3000aGetTimebase API and set 0 at ps3000aRunBlock timebase then i get a real reading .but the readng is fixed somehow .If i change timebase value i also get the same reading d means its look same in my UI .example if i set timebase 5000 and 1000 i get the same reading only timeIntervalNanoseconds change,What is the best solution and what i should do to solve it?Thanks in advance.
*I am using Block mode not ETS or other mode.
Somehow my previous problem is solved but not 100%.I have a simple question on the two API.
PICO_STATUS ps3000aGetTimebase
(
int16_t handle,
uint32_t timebase,
int32_t noSamples,
int32_t * timeIntervalNanoseconds,
int16_t oversample,
int32_t * maxSamples,
uint32_t segmentIndex
)
PICO_STATUS ps3000aRunBlock
(
int16_t handle,
int32_t noOfPreTriggerSamples,
int32_t noOfPostTriggerSamples,
uint32_t timebase,
int16_t oversample,
int32_t * timeIndisposedMs,
uint32_t segmentIndex,
ps3000aBlockReady lpReady,
void * pParameter
)
In this two API the timebase value should be same?
In my application i calculate timebase depanding on total interval i need.
my timebase_calculation formula: const uint32_t time_base_r = (range_.magnitude() * 125) + 2;//**here range_ in micro format.Example for a 50 us reading my timease will be 6252**
But the problem is if i apply the same time base value on the two API i did not get any value.
But if i set any timebase value only ps3000aGetTimebase API and set 0 at ps3000aRunBlock timebase then i get a real reading .but the readng is fixed somehow .If i change timebase value i also get the same reading d means its look same in my UI .example if i set timebase 5000 and 1000 i get the same reading only timeIntervalNanoseconds change,What is the best solution and what i should do to solve it?Thanks in advance.
*I am using Block mode not ETS or other mode.
Re: 3206D does not show real time data
Hi Anik86p ,
Actually, ps3000aGetTimebase( ) is a check for your benefit, so that you can pass the values that you should be passing to ps3000aRunBlock( ). You use it to make sure that you have selected the correct values to use for Timebase (to get the sampling interval you need) and the correct value to use for noSamples (to get all of the samples you need). So although, technically, if the timebase values are different, RunBlock will still work (if the other arguments are correct), you should use the same value for the 2 functions, as it will allow you to easily create code to select different Sample intervals and valid numbers of samples for your captures.
Your Timebase calculation is correct (for Timebase values of 3 and above) but I would not use the term 'Range_magnitude', you should just call it 'Sample Interval'.
Unless you have got your calculations wrong, I doubt that you are capturing 500MHz signals on slow timebases with even with PicoScope 6. In your previous post, your data file looks like noise, with just one sample point captured (you're bound to capture 1 sample from any fast waveform at some point) but you haven't captured any meaningful waveform, just one point on a waveform.
I would suggest that you post a psdata file, from PicoScope 6, here of your 'working' capture, so that we can see what is going on.
Regards,
Gerry
Actually, ps3000aGetTimebase( ) is a check for your benefit, so that you can pass the values that you should be passing to ps3000aRunBlock( ). You use it to make sure that you have selected the correct values to use for Timebase (to get the sampling interval you need) and the correct value to use for noSamples (to get all of the samples you need). So although, technically, if the timebase values are different, RunBlock will still work (if the other arguments are correct), you should use the same value for the 2 functions, as it will allow you to easily create code to select different Sample intervals and valid numbers of samples for your captures.
Your Timebase calculation is correct (for Timebase values of 3 and above) but I would not use the term 'Range_magnitude', you should just call it 'Sample Interval'.
Unless you have got your calculations wrong, I doubt that you are capturing 500MHz signals on slow timebases with even with PicoScope 6. In your previous post, your data file looks like noise, with just one sample point captured (you're bound to capture 1 sample from any fast waveform at some point) but you haven't captured any meaningful waveform, just one point on a waveform.
I would suggest that you post a psdata file, from PicoScope 6, here of your 'working' capture, so that we can see what is going on.
Regards,
Gerry
Gerry
Technical Specialist
Technical Specialist