Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Display, control and valueAlarm fields not set for monitors #46

Open
dhickin opened this issue May 5, 2016 · 1 comment
Open

Display, control and valueAlarm fields not set for monitors #46

dhickin opened this issue May 5, 2016 · 1 comment
Labels

Comments

@dhickin
Copy link
Contributor

dhickin commented May 5, 2016

When you create a channel monitor to a pvaSrv PV requesting the display, control or valueAlarm fields then these fields are not filled in:

$ pvget -m -r "field()" double01
double01
epics:nt/NTScalar:1.0 
    double value 0
    alarm_t alarm INVALID RECORD UDF_ALARM
    time_t timeStamp <undefined> 0
    display_t display
        double limitLow 0
        double limitHigh 0
        string description 
        string format 
        string units 
    control_t control
        double limitLow 0
        double limitHigh 0
        double minStep 0
    valueAlarm_t valueAlarm
        boolean active false
        double lowAlarmLimit 0
        double lowWarningLimit 0
        double highWarningLimit 0
        double highAlarmLimit 0
        int lowAlarmSeverity 0
        int lowWarningSeverity 0
        int highWarningSeverity 0
        int highAlarmSeverity 0
        double hysteresis 0

whereas for gets they are:

$ pvget  -r "field()" double01
double01
epics:nt/NTScalar:1.0 
    double value 0
    alarm_t alarm INVALID RECORD UDF_ALARM
    time_t timeStamp <undefined> 0
    display_t display
        double limitLow 0
        double limitHigh 10
        string description 
        string format %.1f
        string units Counts
    control_t control
        double limitLow 0
        double limitHigh 10
        double minStep 0
    valueAlarm_t valueAlarm
        boolean active false
        double lowAlarmLimit 2
        double lowWarningLimit 4
        double highWarningLimit 6
        double highAlarmLimit 8
        int lowAlarmSeverity 0
        int lowWarningSeverity 0
        int highWarningSeverity 0
        int highAlarmSeverity 0
        double hysteresis 0
@dhickin dhickin added the bug label May 5, 2016
@dhickin
Copy link
Contributor Author

dhickin commented May 10, 2016

#47 ensures that the correct data is initially.
#49 will ensure it is there is a change to a property field and then a change to value, alarm or timeStamp then the change will be picked up. The change will not be picked up without a change to value/alarm/timeStamp without more work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant