RE: StreamDevice - disable INVALID/CALC alarm for @mismatch

["O'Hea, James \(DLSLtd, RAL, LSCI\) via Tech-talk" <tech-talk@aps.anl.gov>]

Hi Alex,

 

One solution is just to not associate the mismatch with a record and just swallow the junk

 

eg   @mismatch { in "%*s"}

 

James

 

 

From: Tech-talk <tech-talk-bounces@aps.anl.gov> On Behalf Of Sobhani, Bayan via Tech-talk
Sent: 04 November 2019 18:53
To: tech-talk@aps.anl.gov
Subject: StreamDevice - disable INVALID/CALC alarm for @mismatch

 

We have temperature sensors that sometimes send junk characters even though they are not supposed to. To compensate for this, I added an @mismatch routine to the IOC's protocol file which catches the junk characters. This handles it nicely except it puts the record into an Invalid alarm state

I understand this is expected behavior since the StreamDevice documentation says:

"It means that the device has sent something else than what the protocol expected. If the handler starts with an in command, then this command reparses the old input from the unsuccessful in. Error messages from the unsuccessful in are suppressed. Nevertheless, the record will end up in INVALID/CALC state (see chapter Record Processing)."

However, for our purposes we do not consider a fallback onto the mismatch function to be significant enough to put the record into an alarm state. Is it possible to prevent the @mismatch from taking the record into an alarm state?

Alex

 

-- 

This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom