Project

General

Profile

Bug #24377

Alarm Limits Don't Convey Nom/Tol

Added by Beau Harrison 3 months ago. Updated 3 months ago.

Status:
Assigned
Priority:
Normal
Assignee:
Category:
WebDPM
Target version:
-
Start date:
05/06/2020
Due date:
% Done:

0%

Estimated time:
Duration:

Description

Alarm limits are only ever reported as minimum and maximum and never as nominal and tolerance.

History

#1 Updated by Beau Harrison 3 months ago

Rich: "In MOOC, we only support MIN/MAX. If a NOM/TOL alarm block is downloaded to the front-end, it gets converted."

#2 Updated by Beau Harrison 3 months ago

Patrick Dowdle is reporting that L:ATOR.ANALOG_ALARM which is a nom/tol device is reporting the nom/tol values in the min/max fields of the JS DPM. I think what Rich is saying is that he expects the returned alarm limits to always be min/max. That doesn't appear to be the case.

#3 Updated by Richard Neswold 3 months ago

  • Status changed from New to Assigned

Beau posted a comment by me:

Rich: "In MOOC, we only support MIN/MAX. If a NOM/TOL alarm block is downloaded to the front-end, it gets converted."

It's actually worse than that. MOOC only supports MINMAX, unless the comments are lying:

vx-mooc:source:mooc++.h@96cffe5b#L662

MOOC defines MINMAX here:

vx-mooc:source:alarms.h@459e278f#L41

and the symbol isn't used anywhere in the codebase. This value is in the .K field of the analog alarm block. The only place in MOOC where this is referred is here:

vx-mooc:source:alarms.c@bc615d84#L1272

where it sets it to MINMAX unconditionally (and doesn't even use the MINMAX symbol to do it!) So to summarize: MOOC doesn't support NOM/TOL, and rather than return an error or converting a NOM/TOL alarm block, it interprets it as MIN/MAX.

#4 Updated by Beau Harrison 3 months ago

This seems to suggest that MOOC nom/tol devices are broken but I know that not to be true.

#5 Updated by Beau Harrison 3 months ago

There's a big caveat here that may not be obvious to users, all alarm limits are reported as min/max even if they are nom/tol. I don't think this is a problem.

Patrick's issue is specifically with a few devices on LIP (IRM) nodes. The min value is larger than the max values and doesn't align with the database in any way that I can see.

#6 Updated by Beau Harrison 3 months ago

The nom/tol values are coming back in the min/max fields but the DPM user doesn't have any way to know that it's a nom/tol device.



Also available in: Atom PDF