mbbo record

["F. Gougnaud" <fgougna@sigx0.saclay.cea.fr>]

Hi,
I  use a mbbo record to write a value from 0 to 255 to a binary input/output 
device. In this record the state value fields ZRVL through FFVL are all
defaulted to 0  and the state string fields ZRST through FFST are all
empty string. So, the SDEF field is initialized to 0.

When I want to write a value greater than 15 with dbpf, the value is written
in the record but I get the following message:
-> dbpf "testmbbo","100"
DBR_STRING:          Illegal Value      
value = 0 = 0x0
-> dbgf "testmbbo"
DBR_STRING:          Illegal Value      
value = 0 = 0x0

The problem is the same with unix applications like caput, caget, medm, probe...
For instance : 
sigs34(1)% probe &
enum type.
textAdjustCallback : Bad value!

sigs34(2)% caget "testmbbo"
testmbbo                       Illegal Value

This is my record
-> dbtr "testmbbo"
ACKS: NO_ALARM      ACKT: YES           ASG:                BKPT: 0x00          
COSV: NO_ALARM      DESC:               DISA: 0             DISP: 0             
DISS: NO_ALARM      DISV: 1             DOL:CONSTANT        DTYP: ICV196        
EIST:               EISV: NO_ALARM      EIVL: 0x0           ELST:               
ELSV: NO_ALARM      ELVL: 0x0           EVNT: 0             FFST:               
FFSV: NO_ALARM      FFVL: 0x0           FLNK:CONSTANT 0     FRST:               
FRSV: NO_ALARM      FRVL: 0x0           FTST:               FTSV: NO_ALARM      
FTVL: 0x0           FVST:               FVSV: NO_ALARM      FVVL: 0x0           
IVOA: Continue normally                 IVOV: 0             LALM: 255           
LCNT: 0             MASK: 255           MLST: 255           NAME: testmbbo      
NIST:               NISV: NO_ALARM      NIVL: 0x0           NOBT: 8             
NSEV: NO_ALARM      NSTA: NO_ALARM      OMSL: supervisory   ONST:               
ONSV: NO_ALARM      ONVL: 0x0           ORAW: 255           ORBV: 255           
OUT:VME_IO #C0 S64 @                    PACT: 0             PHAS: 0             
PINI: NO            PRIO: LOW           PROC: 0             PUTF: 0             
RBV: 255            RPRO: 0             RVAL: 255           SCAN: Passive       
SDEF: 0             SDIS:CONSTANT       SEVR: NO_ALARM      SHFT: 0             
SIML:CONSTANT       SIMM: NO            SIMS: NO_ALARM      SIOL:CONSTANT       
STAT: NO_ALARM      SVST:               SVSV: NO_ALARM      SVVL: 0x0           
SXST:               SXSV: NO_ALARM      SXVL: 0x0           TEST:               
TESV: NO_ALARM      TEVL: 0x0           THST:               THSV: NO_ALARM      
THVL: 0x0           TPRO: 0             TSE: 0              TSEL:CONSTANT       
TTST:               TTSV: NO_ALARM      TTVL: 0x0           TVST:               
TVSV: NO_ALARM      TVVL: 0x0           TWST:               TWSV: NO_ALARM      
TWVL: 0x0           UDF: 0              UNSV: NO_ALARM      VAL: 255            
ZRST:               ZRSV: NO_ALARM      ZRVL: 0x0           
value = 0 = 0x0
-> 

I couldn't find this problem in tech-talk.
I use R3.13.1

Thanks in advance,
Francoise GOUGNAUD
CEA SACLAY
FRANCE