Experimental Physics and
Industrial Control System

"Hill, Jeff" <[email protected]> · Wed, 2 Apr 2014 15:03:35 +0000

Patrick,

GDD has application types designating purpose, and primitive types designating storage format. Most of the application types were created so that there could be translation to the types in the db_access.h. GDD was designed so that there could be compatibility between GDD and EPICS and also between GDD and another contemporary system (of GDDs) called CDEV. 

Working from memory,

"maxElements" - as I recall, the maximum number of array elements, which is provided when the channel connects
"enums" - array of strings labels for each enumerated state
"menuitem" one of the string labels for an enumerated state
"timeStamp" - an epics time stamp

"ackt", directly maps to DBR_PUT_ACKT
"acks" directly  maps to DBR_PUT_ACKS
"class" maps to DBR_CLASS_NAME (this maps to the type name of the enclosing object. In the IOC, the record name)

Jeff

> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> On Behalf Of Patrick Thomas
> Sent: Monday, March 31, 2014 8:06 PM
> To: EPICS Tech-Talk
> Subject: gdd application function table read functions
> 
> Hi,
> 
> In the PCAS, I was wondering what some of the gdd application function
> table read functions correspond to in the PV and what data types they
> should return. I am mostly unsure about these: "maxElements", "enums",
> "menuitem", "timeStamp", "all", "attributes", "ackt", "acks" and "class".
> 
> Thank you,
> Patrick

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System