Tracer SC Can’t Control the BOPs on An MP503

Issue:

Tracer SC can't control the BOPs on an MP503

Resolution:

When you create the equipment template for the MP503, what network variables did you bring into Tracer SC?

For the BOPs on the MP503, you have two choices for each BOP: Generic Binary Output Request 1 and Generic Binary Output Override 1 (which correspond to nviBOPxRequest and nviBOPxOverride, where x is 1 to 4). 

If you install both choices for the BOP, Tracer SC puts both points in service and the Override will take precedence over the request.  If you want the request to control, the nviBOPxOverride should be put out of service or not mapped.

If you install just the Generic Binary Output Request, Tracer SC puts this point in service, but it also puts the Generic Binary Output Override in service too (with a value set to 0000 which equates to OFF).

There is a priority as to which nvi gets to control the BOP. The nviBOPxOverride takes precedence over the nviBOPxRequest. As such, if the Generic Binary Output Override is in service, you will never be able to control the BOP using Generic Binary Output Request. 

Example of network Variables with BOP1 and 2 Request and BOP2 Override Mapped in template.

Example of template for above:

Notes:

nviBOPxRequest is stored in VM. If a power cycle occurs, the override will be released.

nviBOPxOverride is stored in NVM (EEPROM). Writes to this will persist over a power failure. Usage of this variable should be restricted since it is stored in EEPROM which is write limited (don't want to burn it up).

Changes:

Other Question/Problem/Cause Statements:

• Tracer SC can't control the BOPs on an MP503

Facts:

• Tracer MP503
• Tracer SC

Additional Technical Support Only Information

Original wave: wave82999