acquire commandline utility clarifications

Applications, development tools, FPGA, C, WEB
Post Reply
cadrev
Posts: 7
Joined: Mon Jan 18, 2016 10:37 am

acquire commandline utility clarifications

Post by cadrev » Sat Feb 06, 2016 11:04 am

Good day,

I'd like to ask for a bit of clarity regarding the acquire commandline function.

For example i used the ff: acquire 2048 8

the 2048 samples would mean that I'm sampling the signal 2048 times per second?

Nils Roos
Posts: 1441
Joined: Sat Jun 07, 2014 12:49 pm
Location: Königswinter

Re: acquire commandline utility clarifications

Post by Nils Roos » Sat Feb 06, 2016 1:15 pm

acquire 2048 8

the 2048 samples would mean that I'm sampling the signal 2048 times per second?
No, you are acquiring a total of 2048 samples at a decimation factor of 8 (which corresponds to 15.625 MSps sample rate). The first parameter defines the number of samples to record, the second the decimation factor, which translates into effective sample rate as rate = 125MSps / factor

cadrev
Posts: 7
Joined: Mon Jan 18, 2016 10:37 am

Re: acquire commandline utility clarifications

Post by cadrev » Sat Feb 06, 2016 3:20 pm

Nils Roos wrote:
acquire 2048 8

the 2048 samples would mean that I'm sampling the signal 2048 times per second?
No, you are acquiring a total of 2048 samples at a decimation factor of 8 (which corresponds to 15.625 MSps sample rate). The first parameter defines the number of samples to record, the second the decimation factor, which translates into effective sample rate as rate = 125MSps / factor


Thank you for your answer, so suppose I inputted a command:

> acquire 7629 16384

Am I correct to assume that I'll be getting approximately 7629 samples per seconds based on the equation of:
(125M/ 16384 ) = 7629. 395

Nils Roos
Posts: 1441
Joined: Sat Jun 07, 2014 12:49 pm
Location: Königswinter

Re: acquire commandline utility clarifications

Post by Nils Roos » Sat Feb 06, 2016 3:38 pm

Not quite, 16384 is not a supported factor. Have you tried calling acquire without parameters ? It will tell you the allowed values.

cadrev
Posts: 7
Joined: Mon Jan 18, 2016 10:37 am

Re: acquire commandline utility clarifications

Post by cadrev » Sat Feb 06, 2016 3:55 pm

Nils Roos wrote:Not quite, 16384 is not a supported factor. Have you tried calling acquire without parameters ? It will tell you the allowed values.
Yes, thank you for that, I was looking at the wiki and 16384 was listed on the dec list. I think this needs to be corrected. I've looked up on the red pitaya site and it was explained much clearly. Final question:
So supposed I used a decimation of 64 with an approximate sample of 1.9 MS/s, using the command:
>acquire 1900000 65
would give me 1.9M samples per seconds?

Nils Roos
Posts: 1441
Joined: Sat Jun 07, 2014 12:49 pm
Location: Königswinter

Re: acquire commandline utility clarifications

Post by Nils Roos » Sat Feb 06, 2016 5:35 pm

>acquire 1900000 64
would give me 1.9M samples per seconds?
It would sample at 1.9MSps, but it will not give you 1900000 samples, because the scope module does only acquire a maximum of 16384 samples per channel in one go.

cadrev
Posts: 7
Joined: Mon Jan 18, 2016 10:37 am

Re: acquire commandline utility clarifications

Post by cadrev » Mon Feb 08, 2016 4:55 pm

Nils Roos wrote:
>acquire 1900000 64
would give me 1.9M samples per seconds?
It would sample at 1.9MSps, but it will not give you 1900000 samples, because the scope module does only acquire a maximum of 16384 samples per channel in one go.
Thank you for the clarification :)

Post Reply
jadalnie klasyczne ekskluzywne meble wypoczynkowe do salonu ekskluzywne meble tapicerowane ekskluzywne meble do sypialni ekskluzywne meble włoskie

Who is online

Users browsing this forum: No registered users and 117 guests