Re: IOC, QServ, and AMSG / alarm.message

[Michael Davidsaver via Tech-talk <tech-talk at aps.anl.gov>]

Hi Ivan,

On 2/13/25 08:21, Ivan Finch - STFC UKRI via Tech-talk wrote:
> Hello,
>
> We have setup a simple IOC with bi records triggered by forward links such as the following:
What you are trying to do should work.

Can you test with: https://urldefense.us/v3/__https://github.com/epics-base/pvxs/pull/100__;!!G_uCfscf7eWS!Z6EvnRv0uZpu2-5tpfa-eWbruUmdHDvYFuD2e3Hqz8btrWMPr7Mbd5da1kY-Kh2iqsPVIsllxL7xenGFhtxHi3Xfqg$  ?

...
> We’ve investigated setting the AMSG and NAMSG fields in the record, but suspect that this is intended to be set programmatically?
The idea is for device support to change to recGblSetSevrMsg()
in places where recGblSetSevr() is used to signal an alarm.

> int recGblSetSevrMsg(void *precord,
>                      epicsEnum16 new_stat,
>                      epicsEnum16 new_sevr,
>                      const char *msg, ...)
So printf() format strings can be used, although there is a
limit of 40 characters (aka. DB_AMSG_SIZE).


> Thank you in advance for any assistance you can provide,
>
> Ivan Finch
>
> ISIS Controls