You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be good to have PVs containing the current minimum and maximum for numeric GenICam features. These could also potentially be propagated to the DRVL and DRVL fields of the records for GenICam features, and perhaps the abstract records as well.
Perhaps the GenICam Implemented flag could also be added which could even set the record alarm state to INVALID.
This would not be too hard to implement. The Python script could automatically generate the _MIN, _MAX, and _VALID records. The parameter library would have 2 or 3 more entries for each GenICam parameter. ADGenICam would write these values to the parameter library as it does with the VAL field each time the features are read.
The text was updated successfully, but these errors were encountered:
It would be good to have PVs containing the current minimum and maximum for numeric GenICam features. These could also potentially be propagated to the DRVL and DRVL fields of the records for GenICam features, and perhaps the abstract records as well.
Perhaps the GenICam Implemented flag could also be added which could even set the record alarm state to INVALID.
This would not be too hard to implement. The Python script could automatically generate the _MIN, _MAX, and _VALID records. The parameter library would have 2 or 3 more entries for each GenICam parameter. ADGenICam would write these values to the parameter library as it does with the VAL field each time the features are read.
The text was updated successfully, but these errors were encountered: