Experimental Physics and
Industrial Control System

Jure Varlec via Core-talk <core-talk at aps.anl.gov> · Mon, 08 Mar 2021 20:21:14 -0000

Another possibility I see for adding direct access to the TIME field
while avoiding the drawback of keeping additional fields up to date is,
like in the first proposal, to handle it similar to SPC_DBADDR. But
instead of using a public field that would need to be updated after
every processing, use a private filed inside dbCommonPvt. This field
would only be updated when needed; as far as I can tell the appropriate
time is whenever SPC_SBADDR is handled. Specifically, dbEntryToAddr()
would, instead of calling the record's cvt_dbaddr(), convert
epicsTimeStamp to UINT64 and return a pointer to that as DBADDR.

Does this make sense? The way I see it, that's the only way to access
the value of the waveform, and thus should be sufficient as the only way
to access the converted value of the timestamp. Is my understanding
correct?

-- 
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/1182091

Title:
  Make TIME field directly accessible

Status in EPICS Base:
  Triaged

Bug description:
  Users often request the ability to access the TIME field directly.
  It could be provided as an array of 2 32-bit values, possibly with a specific string in ISO-8601 form say.

To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1182091/+subscriptions

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System