Re: Add new Alarm Status

["Schoeneburg, Bernd" <bernd.schoeneburg@desy.de>]

It is solved!!!  I forgot to load the new dbd file into the IOC.
Thank you for thinking......   There is still something to do for the 
clients, like probe....

Bernd

Am 04.10.2011 15:18, schrieb Schoeneburg, Bernd:
> Hi all,
> I am using base R3.14.11
>
> After adding some new alarm status to the files 
> base/src/sbStatic/alarm.h , alarmString.h and  
> base/db/menuAlarmStat.dbd  I did "make clean" to everything and 
> rebuild the whole base. After that base/dbd contained the new menu and 
> base/include contained all new header files.
> I did move lastEpicsAlarmCond and ALARM_NSTATUS to the new last alarms.
> Then I cleaned and compiled the ioc application with my base in 
> configure/RELEASE.
>
> So everything looks ok, but when my record sets such new alarm and a 
> client, which wants the string tries to read it, I get an error on my 
> IOC:
>
> Illegal choice PV: 22PC503_pid.STAT error detected in routine: 
> dbFastLinkConv(cvt_menu_st)
>
> Printing the reasons for this message shows:
>
> pdbFldDes=0xd9fc5bc pdbMenu=0xd920978 nchoice=22 
> papChoiceValue=0xfb0cc9c pchoice=0xfb0cca4
>
> ...shows that the number of choices of the status menu is still 22. 
> But it should be 25 now, because I added 3 new status.
>
> Is there still something hard coded or did I miss something?
>
> Bernd