Experimental Physics and
Industrial Control System

OK, I was too hasty in my reply to Torsten!

 

We could create a new asynMetadata interface, similar to asynOption.

 

typedef struct asynMetadata {

    asynStatus (*writeString)(void *drvPvt, asynUser *pasynUser,

                              const char *key, const char *val);

    asynStatus (*readString)(void *drvPvt, asynUser *pasynUser,

                             const char *key, char *val, int sizeval);

    asynStatus (*writeInt32)(void *drvPvt, asynUser *pasynUser,

                             const char *key, epicsInt32 val);

    asynStatus (*readInt32)(void *drvPvt, asynUser *pasynUser,

                            const char *key, epicsInt32*val);

    asynStatus (*writeFloat64)(void *drvPvt, asynUser *pasynUser,

                               const char *key, epicsFloat64 val);

    asynStatus (*readFloat64)(void *drvPvt, asynUser *pasynUser,

                              const char *key, epicsFloat64 *val);

} asynMetadata;

 

There would be well-defined, but extensible, values for “key”.  With asynOption on serial devices key can be “baud”, “parity”, etc.  For asynMetadata the keys could be “egu”, “low_alarm”, “high_alarm”, “min_value”, “max_value”, etc.

 

Mark

 

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Ralph Lange via Tech-talk
Sent: Monday, March 1, 2021 8:02 AM
To: EPICS Tech Talk <tech-talk at aps.anl.gov>
Subject: Re: Accessing Record fields from asyn driver