EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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  <20212022  2023  2024  2025  2026  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  <20212022  2023  2024  2025  2026 
<== Date ==> <== Thread ==>

Subject: RE: Accessing Record fields from asyn driver
From: Mark Rivers via Tech-talk <[email protected]>
To: 'Ralph Lange' <[email protected]>, 'Torsten Bögershausen' <[email protected]>
Cc: "[email protected]" <[email protected]>
Date: Mon, 1 Mar 2021 14:26:55 +0000

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 <[email protected]> On Behalf Of Ralph Lange via Tech-talk
Sent: Monday, March 1, 2021 8:02 AM
To: EPICS Tech Talk <[email protected]>
Subject: Re: Accessing Record fields from asyn driver

 

Hi Torsten,

 

In the context of the OPC UA Device Support, I have had this requirement coming up, and I think it would be worthwhile doing a design for adding this functionality.

The next important step there would be thinking about a proper definition and an easy, generic yet comprehensive way of configuring this mapping.

Polling for changes or subscribing to metadata is probably too resource expensive (at least in the OPC UA case), but reading the metadata on (re)connection should be feasible.

 

If you have input to this, I'd be happy to hear about it.

 

Cheers,
~Ralph

 


Replies:
Re: Accessing Record fields from asyn driver Torsten Bögershausen via Tech-talk
RE: Accessing Record fields from asyn driver Mark Rivers via Tech-talk
References:
Accessing Record fields from asyn driver Torsten Bögershausen via Tech-talk
Re: Accessing Record fields from asyn driver Ralph Lange via Tech-talk

Navigate by Date:
Prev: Re: Accessing Record fields from asyn driver Torsten Bögershausen via Tech-talk
Next: Re: Accessing Record fields from asyn driver Torsten Bögershausen 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  <20212022  2023  2024  2025  2026 
Navigate by Thread:
Prev: Re: Accessing Record fields from asyn driver Ralph Lange via Tech-talk
Next: Re: Accessing Record fields from asyn driver Torsten Bögershausen 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  <20212022  2023  2024  2025  2026 
ANJ, 19 Mar 2026 · Home · News · About · Talk · Base · Modules · Extensions ·
· Distributions · Download · Documents · Links · Licensing ·