-
Notifications
You must be signed in to change notification settings - Fork 9
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
epid final_value signal not found #325
Comments
The class is defined: apstools/apstools/synApps/epid.py Line 34 in 8fbbbd9
|
epid record documentation: https://cars9.uchicago.edu/software/epics/epidRecord.html |
The documentation appears to be wrong. It says that the CT field is a ULONG in clock ticks, and that it is accessible from Channel Access. However, this is from the epidRecord.dbd file:
So CT is in fact it is an epicsTimeStamp structure with the attribute DBF_NOACCESS. Source code never lies :-). |
You (re)teach a valuable lesson today. |
In this issue, the object created in a bluesky session does not show the apstools/apstools/synApps/_common.py Lines 41 to 63 in 56cd7ce
But this is my mistake since the apstools/apstools/synApps/_common.py Lines 66 to 78 in 56cd7ce
and this class is not included in the definition of the epid support here: apstools/apstools/synApps/epid.py Line 34 in 56cd7ce
|
The Apparently not: https://wiki-ext.aps.anl.gov/epics/index.php/RRM_3-14_dbCommon |
The common record fields need to have the same type in every record. VAL does not, since it might be a double, a string, or an array of some type depending on the record. |
That underscores the finding that The |
... as a read-only signal: with |
When using the
epid
object at APS 8-ID-I, we did not find thefinal_value
(.VAL
) signal.The text was updated successfully, but these errors were encountered: