CalScope time ?!
-
- Posts: 23
- Joined: Thu Jun 26, 2014 12:46 pm
CalScope time ?!
Hi all
In the webapp of the Cal scope the time line can have a big area ( up to 500seconds an more) but my graph stops at 9 second is that normal? how can i see a bigger area on my desktop?
greez kuengla
In the webapp of the Cal scope the time line can have a big area ( up to 500seconds an more) but my graph stops at 9 second is that normal? how can i see a bigger area on my desktop?
greez kuengla
-
- Posts: 55
- Joined: Tue Jun 24, 2014 3:06 pm
- Location: Dourdan (France)
Re: CalScope time ?!
Hi !
I have never used this app, but 500s it seems very huge ! Even 9 second ... How many points does it represent ?
I have never used this app, but 500s it seems very huge ! Even 9 second ... How many points does it represent ?
-
- Posts: 23
- Joined: Thu Jun 26, 2014 12:46 pm
Re: CalScope time ?!
Hi see the attachments at +- 9seconds it stops and if i download the data traces it stops at +- 1 second
You do not have the required permissions to view the files attached to this post.
-
- Posts: 55
- Joined: Tue Jun 24, 2014 3:06 pm
- Location: Dourdan (France)
Re: CalScope time ?!
What is your sampling frequency ? 125MS/s ?
-
- Posts: 23
- Joined: Thu Jun 26, 2014 12:46 pm
Re: CalScope time ?!
I dont know it must be the default value
-
- Posts: 55
- Joined: Tue Jun 24, 2014 3:06 pm
- Location: Dourdan (France)
Re: CalScope time ?!
So it should be 125MS/s.
With this sampling frequency, in 1 sec you acquire 125,000,000 points. Data are acquired on 14 bits ==> 2 octets. The size of the buffer is 250,000,000 octets ==> 238,42Mo.
It is strange, because it means data are transfered into the RAM. I'm maybe wrong but I don't think so
With this sampling frequency, in 1 sec you acquire 125,000,000 points. Data are acquired on 14 bits ==> 2 octets. The size of the buffer is 250,000,000 octets ==> 238,42Mo.
It is strange, because it means data are transfered into the RAM. I'm maybe wrong but I don't think so
-
- Posts: 23
- Joined: Thu Jun 26, 2014 12:46 pm
Re: CalScope time ?!
yes i understand it i can't see more becuase 8.58 second is the time i can reach with the maximum decimation =)
-
- Posts: 55
- Joined: Tue Jun 24, 2014 3:06 pm
- Location: Dourdan (France)
Re: CalScope time ?!
So it is normal.
Why ?
Because, the max decimation is 65,356 (cf. acquire.c). So you have a Fs = 125,000,000/65,536 = 1,907.348Hz
And, you have a FPGA memory size of 16,384 points. So it is equal to a time of 16,384/1,907.348 = 8.589s
This is the explication. You have to read all the data which are saved into the FPGA memory before saving news data. Or, the other solution is to use the RAM so save data ^^. But without it, I don't think you can read data in streaming.
Why ?
Because, the max decimation is 65,356 (cf. acquire.c). So you have a Fs = 125,000,000/65,536 = 1,907.348Hz
And, you have a FPGA memory size of 16,384 points. So it is equal to a time of 16,384/1,907.348 = 8.589s
This is the explication. You have to read all the data which are saved into the FPGA memory before saving news data. Or, the other solution is to use the RAM so save data ^^. But without it, I don't think you can read data in streaming.
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 7 guests