Ralph is addressing my situation. I should clarify that I'm using mbbi for
DTYP (raw) soft. My mbbi device's INP link references a 24-bit value
sourced by a separate (CAMAC) record. For example, I want to specify mbbi
values derived from 2 bits, starting at bit 9.
-ps
-----Original Message-----
From: Ralph Lange <[email protected]>
To: [email protected] <[email protected]>; [email protected]
<[email protected]>
Date: Friday, August 14, 1998 11:35 AM
Subject: Re: MBBI, SHFT, and GDCT
>> I am using gdct313 to define an MBBI record and there is no place on the
>> "Edit Attributes" form for specifying the number of bits to 'shift' the
raw
>> value (SHFT). mbbiRecord.dbd does not assign the SHFT field to a
>> promptgroup. Is there a reason for this omission ?
>>
>> This situation also applies to record types mbbo, mbbiDirect, and
>> mbboDirect.
>
>The SHFT value is device dependent. In most cases it depends on the
>structure of the associated device and can be calculated from the address
>information in the INP/OUT field. So device support usually sets SHFT in
>initRecord() after parsing the INP resp. OUT fields.
>
>Making the SHFT field DCT accessible would introduce redundancy and
>most likely increase error probability.
>
>The only problem could be Raw Soft Support, as there is no address
>information in the INP/OUT fields and SHFT will always be 0. Right?
>
>Ralph
>
- Replies:
- Re: MBBI, SHFT, and GDCT Ralph Lange
- Navigate by Date:
- Prev:
Re: MBBI, SHFT, and GDCT Ralph Lange
- Next:
Re: MBBI, SHFT, and GDCT Ralph Lange
- 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: MBBI, SHFT, and GDCT Marty Kraimer
- Next:
Re: MBBI, SHFT, and GDCT Ralph Lange
- 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
|