search

archiver-appliance / epicsarchiverap

This is an implementation of an archiver for EPICS control systems that aims to archive millions of PVs.
Other
37 stars 37 forks source link

PV without alarm cannot be archived #125

Open thomasms opened 2 years ago

thomasms commented 2 years ago

Hi, I have started using the archiver appliance (very nice!) but I noticed a small issue on my local machine and I am not sure if it is an issue with my setup or with the archiver appliance.

The issue relates to the fact if I have a PV (using PVA not CA) that is of the form:

archive:pv123 structure
    float value 15.3306
    structure arr
        double[] value [8.35062,11.7006,10.2576,11.4676,13.4204,6.80256,11.9137,9.96156,9.06209,6.55399,9.21183,8.75741,12.8767]
    structure mean
        float value 10
    structure sigma
        float value 2
    alarm_t alarm MAJOR DRIVER MAJOR problem
        int severity 2
        int status 2
        string message "MAJOR problem"
    time_t timeStamp 2021-08-19 15:48:40.064  -1
        long secondsPastEpoch 1629380920
        int nanoseconds 64050400
        int userTag -1

the archiver works fine and can archive the PV - so no issues here. The problem arises when I remove the alarm field and have something like this instead:

archive:pv123 structure
    float value 15.3306
    structure arr
        double[] value [8.35062,11.7006,10.2576,11.4676,13.4204,6.80256,11.9137,9.96156,9.06209,6.55399,9.21183,8.75741,12.8767]
    structure mean
        float value 10
    structure sigma
        float value 2
    time_t timeStamp 2021-08-19 15:48:40.064  -1
        long secondsPastEpoch 1629380920
        int nanoseconds 64050400
        int userTag -1

No matter how long I leave it it never registers in the archiver.

Does this mean it always expects an alarm field for every PV I want to archive? Or is this an issue with my setup?

slacmshankar commented 2 years ago

Probably an issue with the way we are setting up the monitors. Will look into it.