Re: PV in PCAS can not be archived by Channel Archiver

["Kasemir, Kay" <kasemirk@ornl.gov>]

Hi:

Archive tools tend to
* read the DBR_CTRL_... info for a channel
* subscribe to DBR_TIME_.. type
* ... using the DBE_LOG event

What you see with the default caget or camonitor is different.
You need to assert that your custom CA server serves those
CA request types that the archive system uses.

You can test that with caget and camonior to some extend:

# Read the online help
caget -h
camonitor -h

# Get the DBR_CTRL_... info for your channel.
# Here I use DBR_CTRL_DOUBLE.
# You need to use what applies to your channel.
caget -d 34 YourChannelName

# Subscribe using the DBE_LOG and ALARM events.
# Not sure if that's using DBR_TIME_.. or DBR_STS_... or ...?
camonitor -m la YourChannelName



Thanks,
Kay

On 11/9/11 08:13 , "Zhang Yuliang" <zhangyl@ihep.ac.cn> wrote:

>Hi Jeff,
>
>I am encountering a confused problem about archiving PV provided by a
>PCAS.  The value of pv can archive once and only once, and after that
>although the value of pv has changed, there is only one value in the
>channel archiver. It seems that the other values are discarded, and I
>check the stutus of the ca connetion, it is ok.
>
>The EPICS base used by the PCAS is 3.14.8.2, I want to know whether the
>pv of pcas can archived by Channel Archiver. The following are ca-test
>[pv] outputs:
>
>[zhangyl@timinglinux1 ~]$ ca_test IPV1_REC
>name:   IPV1_REC
>native type:    DBR_FLOAT
>native count:   1
>DBR_STRING      99
>DBR_SHORT       99
>DBR_FLOAT       99.0000
>DBR_ENUM        99
>DBR_CHAR        99
>DBR_LONG        99
>DBR_DOUBLE      99.0000
>DBR_STS_STRING   3  2   Value: 99
>DBR_STS_SHORT    3  2   Value: 99
>DBR_STS_FLOAT    3  2   Value: 99.0000
>DBR_STS_ENUM     3  2   Value: 99
>DBR_STS_CHAR     3  2   Value: 99
>DBR_STS_LONG     3  2   Value: 99
>DBR_STS_DOUBLE   3  2   Value: 99.0000
>DBR_TIME_STRING  3  2   TimeStamp: 2011/11/09 17:15:20.990038   Value: 99
>DBR_TIME_SHORT   3  2   TimeStamp: 2011/11/09 17:15:20.990038   Value: 99
>DBR_TIME_FLOAT   3  2   TimeStamp: 2011/11/09 17:15:20.990038   Value:
>99.0000
>DBR_TIME_ENUM    3  2   TimeStamp: 2011/11/09 17:15:20.990038   Value: 99
>DBR_TIME_CHAR    3  2   TimeStamp: 2011/11/09 17:15:20.990038   Value: 99
>DBR_TIME_LONG    3  2   TimeStamp: 2011/11/09 17:15:20.990038   Value: 99
>DBR_TIME_DOUBLE  3  2   TimeStamp: 2011/11/09 17:15:20.990038   Value:
>99.0000
>DBR_GR_STRING    3  2   Value: 99
>DBR_GR_SHORT     3  2
>               0        0       90       85       15       10   Value: 99
>DBR_GR_FLOAT     3  2    0
>           0.000    0.000   90.000   85.000   15.000   10.000   Value:
>99.0000
>DBR_GR_ENUM     Channel read request failed
>DBR_GR_CHAR      3  2
>               0        0       90       85       15       10   Value: 99
>DBR_GR_LONG      3  2
>               0        0       90       85       15       10   Value: 99
>DBR_GR_DOUBLE    3  2    0
>           0.000    0.000   90.000   85.000   15.000   10.000   Value:
>99.0000
>DBR_CTRL_STRING  3  2   Value: 99
>DBR_CTRL_SHORT   3  2
>               0        0       90       85       15       10        0
>    0 Value: 99
>DBR_CTRL_FLOAT   3  2    0
>           0.000    0.000   90.000   85.000   15.000   10.000    0.000
>0.000 Value: 99.0000
>DBR_CTRL_ENUM   Channel read request failed
>DBR_CTRL_CHAR    3  2
>               0        0       90       85       15       10        0
>    0 Value:   99
>DBR_CTRL_LONG    3  2
>               0        0       90       85       15       10        0
>    0 Value: 99
>DBR_CTRL_DOUBLE  3  2    0
>           0.000    0.000   90.000   85.000   15.000   10.000    0.000
>0.000 Value: 99.000000
>DBR_STSACK_STRING       Channel read request failed
>DBR_CLASS_NAME  Channel read request failed
>
>I noticed that there are Channel read request failed.
>
>Thank you!
>
>Zhang Yuliang 
>