Experimental Physics and Industrial Control System
|
We're looking at device support written by a vendor, and there is a
database template that includes in a mbboDirect record with the .SHFT
field given a value in the EPICS runtime db. Since our database
configuration tool, tdct, doesn't provide for creating a DB with the
SHFT field set for that particular record type, I started looking...
In the record reference manual for 3-14 record reference manual, it says
"the SHFT value is set by device support and is not configurable by the
user". The information in the accompanying table supports this,
indicating in the 'DCT' field of the table 'NO' for the SHFT field of
the record type.
In the R3.14.12.3 dbd file for the mbboDirect, there exists the entry
"promptgroup(GUI_MBB)", suggesting that a database configuration tool
should be allowed to set the SHFT field. When the database is loaded on
an IOC, and the SHFT field has been initialized at dbLoadRecords time,
the field behaves as one might expect for that circumstance.
Is that the intended behavior, and the docs are out of sync, or the
other way around?
If the SHFT field should really only be set by device support, is there
a strong convention for that? The method I recall is to infer from a
bitmask supplied in the .OUT field, by counting the number of clear
least significant bits. Are there other conventions or preferences?
Rod Nussbaumer
Group Leader, Controls
TRIUMF
Vancouver, Canada
- Replies:
- RE: mbboDirect record and SHFT field Mark Rivers
- Re: mbboDirect record and SHFT field Dirk Zimoch
- Re: mbboDirect record and SHFT field Ralph Lange
- Navigate by Date:
- Prev:
Re: Questions regarding CA protocol specification and phylosophy Michael Davidsaver
- Next:
Re: How to use Archiver Appliance to archive PVs of only the latest period of time Shankar, Murali
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
<2017>
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Questions regarding CA protocol specification and phylosophy Michael Davidsaver
- Next:
RE: mbboDirect record and SHFT field Mark Rivers
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
<2017>
2018
2019
2020
2021
2022
2023
2024
|
ANJ, 21 Dec 2017 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|