Experimental Physics and Industrial Control System

>Not saying that this specific tag should not be 64 bits wide, but to change an existing approved design,
>I would like to see a minimum amount of justification and discussion.

A time tag change from 32 to 64 bits makes no difference to those who simply use pvAccess via qsrv/pvaSrv since the EPICS database never provided a value, anyway.

And even though the time stamp is part of most updates, if I understand correctly this change will hardly affect the network package size because when you leave the tag at its default value of 0 and don't change, the monitor deltas won't include the tag, only the secs & nanosecs, correct?

The SNS beam line neutron data does use the user tag for a sequence number, incremented by server to allow double-checking for missing updates. So our software might need to be updated. I believe this could be done beam line by beam line, won't be a show stopper.

-Kay

Replies:

Re: Adding userTag to epicsTimeStamp Marty Kraimer

Re: Adding userTag to epicsTimeStamp Michael Davidsaver

References:

Adding userTag to epicsTimeStamp Johnson, Andrew N.

Re: Adding userTag to epicsTimeStamp Ralph Lange

Re: Adding userTag to epicsTimeStamp Marty Kraimer

RE: Adding userTag to epicsTimeStamp Mark Rivers

Navigate by Date:

Prev: RE: Adding userTag to epicsTimeStamp Mark Rivers

Next: Build failed in Jenkins: epics-base-3.16-mac-test #155 APS Jenkins

Index: 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: Adding userTag to epicsTimeStamp Mark Rivers

Next: Re: Adding userTag to epicsTimeStamp Marty Kraimer

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017>  2018  2019  2020  2021  2022  2023  2024