Hi,
Thanks for your reply, I meet another peoblem.
The update rate is 10Hz, the number of element is 1360. FTVL is double.
The db I write is as follows:
record(waveform, "mytest")
{
field(NELM, 1360)
field(FTVL, "DOUBLE")
field (PINI, "YES")
}
and the scan rate I set is 0.1s in XML file, I also set the batch size is 1500, write period is 10s, buffer reserve is 3 and then run ArchiveConfig and ArchiveEngine tool to acquire the waveform data and write to mysql.
however, i can see only 1 data per 0.1s in mysql record. The correct number should be 1360 data per 0.1s and 13600 data per second.
I have no idea if I miss something.
Thanks in advance.
Zhefu
From: Mazanec Tomáš<mailto:[email protected]>
Date: 2018-06-27 16:47
To: lzf neu<mailto:[email protected]>; [email protected]<mailto:[email protected]>
Subject: Re: Question about RDB Channel archiver engine be used for the waveform channels
Hi
Yes, RDB channel archiver can store waveform data (as any other Channel Access PV data);
and users can retrieve the stored waveform data using e.g.: CSS DataBrowser (and waveform analyzer).
Answer to your 1.25GS/s requirement: If you have a HW good enough and the sampled data well partitioned into waveforms, then yes, it is possible to archive the data with use of one-or-more RDB archiver instances and with properly scaled SQL storage.
Detailed answer requires more information about how the waveforms are processed at IOC side -- in terms of their update rate, NORD, NELM, FTVL.
Tomas
________________________________
Od: [email protected] <[email protected]> za uživatele lzf neu <[email protected]>
Odesláno: úterý 26. června 2018 7:40:19
Komu: [email protected]
Předmět: Question about RDB Channel archiver engine be used for the waveform channels
Hi,
I have a question to consult you.
Can RDB Channel archiver engine stores the waveform data received by channel access and then get the history data back out? The waveform data presents for the voltages samples by the beamloss with sample rate 1.25Gs/s.
Any help will be appreciated and thanks in advance.
regards,
Zhefu
- Navigate by Date:
- Prev:
RE: Failed caput not notified when using ca_array_put_callback michael.abbott--- via Tech-talk
- Next:
New dxpSITORO module available Mark Rivers via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
<2018>
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
GeSys+Cexp on RTEMS 4.10+ Anton Derbenev
- Next:
New dxpSITORO module available Mark Rivers via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
<2018>
2019
2020
2021
2022
2023
2024
|