(Another thing to hate about Outlook: I meant to CC everybody, so this is a resend.)
From: Shen, Guobao [mailto:[email protected]]
> But I do not understand why you want to implement TIME and
> CTRL separately.
> The TIME returns IOC time stamp, and CTRL return value,
> status, severity, and so on.
> It means we have to get time stamp using
> caget(pv_name, datatype, format=FORMAT_TIME).stamp,
> and get its value, status, and severity using another channel access
> caget(pv_name, datatype,
> format=FORMAT_CTRL).value/status/severity
>
> The value might be changed when we do second channel access.
Well, this is entirely down to what channel access provides. The channel access DBR_CTRL_ (or DBR_GR_) formats don't deliver timestamps, that's fixed in channel access. If you want timestamps you have to use a DBR_TIME_ format, there's no choice. All cothread does is package these options in a pretty way: you always get all the information that channel access delivers.
In fact, doing a camonitor on a CTRL format is going to be frustrating: my experience is that most servers send the full data (units, precision, etc) on the first update ... and then send blanks or zeros thereafter. But this is all down to the whim of channel access and the server.
However, you've missed one thing: when you ask for FORMAT_TIME, you also get status and severity at the same time. You only use FORMAT_CTRL if you want to read the units/enums/precision/whatever.
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
- References:
- Re: EPICS Python client application survey Shen, Guobao
- Navigate by Date:
- Prev:
Re: EPICS Python client application survey Matt Newville
- Next:
RE: EPICS Python client application survey Dalesio, Leo
- 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
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: EPICS Python client application survey Shen, Guobao
- Next:
RE: EPICS Python client application survey michael.abbott
- 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
2021
2022
2023
2024
|