Right now, I'm attempting to group multiple records into a single structure for improved organization of data. Essentially letting us only need to import this PV structure rather than importing several records manually. As for what client(s) will consume this data structure. That would primarily be other IOCs themselves that are on the same subnet, but in different machines.
Sincerely,
Dhruv Srinivas
-----Original Message-----
From: Michael Davidsaver <mdavidsaver at gmail.com>
Sent: Saturday, July 8, 2023 6:05 PM
To: Srinivas, Dhruv <srinivas1 at llnl.gov>
Cc: tech-talk at aps.anl.gov
Subject: Re: Question on Accessing Data in Custom PV Structures
On 7/7/23 14:03, Srinivas, Dhruv via Tech-talk wrote:
> To whom it may concern,
>
> I’m attempting to create custom PVStructures which contain differing normative types. At the moment, I’ve created the below code in an IOC which creates a PV Structure with 2 NTScalars and 1 NTScalarArray.
Can you say something about what you are trying to accomplish, and what kind of client(s) will consume this data structure?
> record(ai, "rec:X") {
>
> field(VAL, "20")
>
> field(HIGH, "30")
>
> field(HSV, "MINOR")
>
> info(Q:group, {
>
> "CustomDataStructure": {
>
> "X_Scalar": {
>
> +channel:"VAL"
>
> }
>
> }
>
> })
>
> }
>
> record(ai, "rec:Y") {
>
> field(VAL, "40")
>
> info(Q:group, {
>
> "CustomDataStructure": {
>
> "Y_Scalar": {
>
>
> +type:"scalar",
>
>
> +channel:"VAL",
>
>
> +id:"MyTestingPVA2PVA",
>
> }
>
> }
>
> })
>
> }
>
> record(aai, "input_this") {
>
> field(NELM, "4")
>
> field(FTVL, "INT64")
>
> field(INP, "[1,2,3,4]")
>
> info(Q:group, {
>
> "CustomDataStructure": {
>
> "Z_Aray": {
>
> +channel:"VAL"
>
> }
>
> }
>
> })
>
> }
>
> At the moment, this does create the PV Structure, and I can access it through “pvget”. However I’m unsure if this is the right way to do this. Can someone with more experience with Epics v7 correct me if so? Also, I’m not sure how to go about accessing parts of “CustomDataStructure”. Namely how would I go about accessing the value for Y_Scalar through CustomDataStructure?
>
> I’ve also copied the output of pvget below. I apologize for the lengthy post, but I thought it was best to provide as much context as possible.
>
> * pvget CustomDataStructure
>
> CustomDataStructure MyTestingPVA2PVA
>
> structure record
>
> structure _options
>
> uint queueSize 0
>
> boolean atomic true
>
> epics:nt/NTScalar:1.0 X_Scalar
>
> double value 20
>
> alarm_t alarm
>
> int severity 0
>
> int status 2
>
> string message UDF
>
> structure timeStamp
>
> long secondsPastEpoch 631152000
>
> int nanoseconds 0
>
> int userTag 0
>
> structure display
>
> double limitLow 0
>
> double limitHigh 0
>
> string description
>
> string units
>
> int precision 0
>
> enum_t form (0) Default
>
> int index 0
>
> string[] choices [Default, String, Binary, Decimal,
> Hex, Exponential, Engineering]
>
> control_t control
>
> double limitLow 0
>
> double limitHigh 0
>
> double minStep 0
>
> valueAlarm_t valueAlarm
>
> boolean active false
>
> double lowAlarmLimit nan
>
> double lowWarningLimit nan
>
> double highWarningLimit 30
>
> double highAlarmLimit nan
>
> int lowAlarmSeverity 0
>
> int lowWarningSeverity 0
>
> int highWarningSeverity 0
>
> int highAlarmSeverity 0
>
> byte hysteresis 0
>
> epics:nt/NTScalar:1.0 Y_Scalar
>
> double value 40
>
> alarm_t alarm
>
> int severity 0
>
> int status 2
>
> string message UDF
>
> structure timeStamp
>
> long secondsPastEpoch 631152000
>
> int nanoseconds 0
>
> int userTag 0
>
> structure display
>
> double limitLow 0
>
> double limitHigh 0
>
> string description
>
> string units
>
> int precision 0
>
> enum_t form (0) Default
>
> int index 0
>
> string[] choices [Default, String, Binary, Decimal,
> Hex, Exponential, Engineering]
>
> control_t control
>
> double limitLow 0
>
> double limitHigh 0
>
> double minStep 0
>
> valueAlarm_t valueAlarm
>
> boolean active false
>
> double lowAlarmLimit nan
>
> double lowWarningLimit nan
>
> double highWarningLimit nan
>
> double highAlarmLimit nan
>
> int lowAlarmSeverity 0
>
> int lowWarningSeverity 0
>
> int highWarningSeverity 0
>
> int highAlarmSeverity 0
>
> byte hysteresis 0
>
> epics:nt/NTScalarArray:1.0 Z_Scalar
>
> long[] value [1,2,3,4]
>
> alarm_t alarm INVALID DRIVER UDF
>
> int severity 3
>
> int status 2
>
> string message UDF
>
> structure timeStamp
>
> long secondsPastEpoch 631152000
>
> int nanoseconds 0
>
> int userTag 0
>
> structure display
>
> double limitLow 0
>
> double limitHigh 0
>
> string description
>
> string units
>
> int precision 0
>
> enum_t form (0) Default
>
> int index 0
>
> string[] choices [Default, String, Binary, Decimal,
> Hex, Exponential, Engineering]
>
> control_t control
>
> double limitLow 0
>
> double limitHigh 0
>
> double minStep 0
>
> valueAlarm_t valueAlarm
>
> boolean active false
>
> double lowAlarmLimit nan
>
> double lowWarningLimit nan
>
> double highWarningLimit nan
>
> double highAlarmLimit nan
>
> int lowAlarmSeverity 0
>
> int lowWarningSeverity 0
>
> int highWarningSeverity 0
>
> int highAlarmSeverity 0
>
> byte hysteresis 0
>
> Sincerely,
>
> Dhruv Srinivas
>
> srinivas1 at llnl.gov <mailto:srinivas1 at llnl.gov>
>
- Replies:
- Re: Question on Accessing Data in Custom PV Structures Michael Davidsaver via Tech-talk
- References:
- Question on Accessing Data in Custom PV Structures Srinivas, Dhruv via Tech-talk
- Re: Question on Accessing Data in Custom PV Structures Michael Davidsaver via Tech-talk
- Navigate by Date:
- Prev:
RE: [EXTERNAL] Re: Real-Time Spectral Analysis of streaming data in EPICS operator screens. Evans, Richard K. (GRC-H000) via Tech-talk
- Next:
Re: Question on Accessing Data in Custom PV Structures Michael Davidsaver 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:
Re: Question on Accessing Data in Custom PV Structures Michael Davidsaver via Tech-talk
- Next:
Re: Question on Accessing Data in Custom PV Structures Michael Davidsaver 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
|
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·