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