Configuring AOI Minimum Engineering Value in Studio 5000

Configuring AOI Minimum Engineering Value in Studio 5000 Logix Designer

When commissioning or modifying an Add-On Instruction (AOI) for analog input scaling in Studio 5000 Logix Designer, engineers frequently need to change the minimum engineering value (EUMin) to match transducer, transmitter, or process requirements. When the new value refuses to persist after a download, the root cause is almost always an external write source — typically an HMI tag — overwriting the AOI instance parameter. This reference details the diagnostic and corrective workflow for that scenario.

Overview: AOI Structure for Analog Scaling

An analog input AOI typically exposes the following parameters used for raw-to-engineering-units conversion:

The scaling math inside the AOI typically follows:

Val_PVEU = ((Inp_PV - Cfg_RawMin) / (Cfg_RawMax - Cfg_RawMin)) * (Val_PVEUMax - Val_PVEUMin) + Val_PVEUMin

Because Val_PVEUMin is defined as Input/Output, it can be written by external logic — including HMI faceplates, PanelView Plus tags, or FactoryTalk View SE HMI tags — which is the primary source of the symptom described in the field report.

Prerequisites

1. Studio 5000 Logix Designer version 32.00 or later (AOI editing behavior is consistent from v20 onward; verify against Logix Designer Programming Manual (1756-RM084) for the firmware in use).
2. RSLogix 5000 / Logix Designer project file with the AOI definition open and the controller online (or offline with a recent program backup).
3. FactoryTalk View Studio or PanelView Plus 6/7 editor access if the HMI is suspected as the write source.
4. Read/Write privileges in the Logix Designer security model (Configure → Security).
5. A verified backup of the controller program prior to making online edits.

Root Cause: HMI or External Logic Writing to the AOI Parameter

When a value typed into the Logix Designer Tag Browser or the AOI instance properties reverts to its prior value within one scan, the cause is a competing write source. Common write sources in priority order are:

1. HMI tag (FactoryTalk View SE/ME, PanelView Plus, or third-party OPC client) writing to Program:AOI_Instance.Val_PVEUMin.
2. Another AOI or routine in the same program using a MOV, COP, or BTD instruction targeting the parameter.
3. A periodic MSG instruction or produced/consumed tag update from another controller.
4. The AOI's own initialization logic re-asserting a default value on first scan (controlled by the .Cfg_Initialize or similar boolean input).

Step-by-Step: Editing the Minimum Engineering Value

Step 1 — Open the AOI Instance

1. In the Controller Organizer, expand Program → Routine containing the AOI call.
2. Right-click the AOI instruction on the rung and select Open Instruction, or click the Properties dialog for the tag instance.
3. Navigate to the Parameters and Local Tags tab.

Step 2 — Attempt the Tag Browser Edit

1. Open the Tag Browser from View → Tag Browser (or right-click the routine and select Monitor Tags).
2. Filter to the AOI instance name (e.g., AI_1090) and locate .Val_PVEUMin.
3. Double-click the value field, enter the new engineering value (e.g., -40.0), and press Enter.
4. Observe the value. If it reverts within one scan, proceed to Step 3.

Step 3 — Identify the Competing Write Source

1. Right-click Val_PVEUMin in the tag database or the instruction faceplate and select Cross Reference (Ctrl+E).
2. Inspect every result. Note that an empty cross-reference result does not prove the absence of external writers — it only proves there are no internal project writers.
3. Open the HMI project (FactoryTalk View Studio → Explorer → the active HMI server) and search for the tag name Program:AI_1090.Val_PVEUMin or the symbolic alias used on the faceplate.
4. In FactoryTalk View SE, browse the HMI tag database; in PanelView Plus 6/7, open the PanelView Editor project file (.MER) and use Find/Replace.

Step 4 — Change the Value from the HMI Source

The simplest, lowest-risk fix is to update the value at the source that the controller is actually reading.

1. Modify the HMI tag's initial value or default to the new EUMin (e.g., -40.0).
2. If the HMI writes via a numeric input object bound to a transient expression, change the expression's operand directly.
3. Download the HMI project to the runtime server (FTView SE: Restore on the HMI server; PanelView: transfer the runtime file).
4. Verify on the controller that .Val_PVEUMin now reads the new value persistently.

Step 5 — Alternative: Break the HMI Write Path

If the HMI write is not desired at all, isolate the parameter:

1. In the AOI definition, change Val_PVEUMin from Input/Output to Input only. This prevents external tag writes but breaks any other consumer expecting to read the value back through the same tag path.
2. Save and download the AOI. The editor will prompt to update all AOI instances.
3. Re-attempt the tag browser edit to confirm the new value persists.

Verification Procedure

1. Force the AOI to a known state by setting Inp_PV = 0 (or Cfg_RawMin) and confirm .Val_PVEU = .Val_PVEUMin exactly.
2. Force Inp_PV = Cfg_RawMax and confirm .Val_PVEU = .Val_PVEUMax.
3. Force a mid-scale value (e.g., Inp_PV = (Cfg_RawMin + Cfg_RawMax) / 2) and confirm a linear interpolation.
4. Monitor the parameter in the tag browser for at least 30 seconds to confirm no external writes are overwriting the new value.
5. Check the controller's Event Log for any tag-routing alarms that may indicate a write conflict between the AOI input pin and an external producer.

Editing the AOI Definition Default vs. Instance Default

Per the Rockwell Automation Knowledge Base Answer ID 823179, modifications to the AOI's default parameter values propagate to all instances on next download. To make a global change:

1. Open the AOI definition (double-click the AOI under Add-On Instructions in the Controller Organizer).
2. Switch to the Parameters and Local Tags tab.
3. Change the Default Value column for Val_PVEUMin to the new scaling minimum.
4. Verify Verification → Finalize All Edits shows no errors.
5. Download to the controller. The dialog will warn that all AOI instances will be updated — confirm if the new default is intended to apply project-wide.

If only one instance must differ (e.g., a transmitter with a different range), do not change the AOI default. Modify only the specific instance's tag in the program routine or via the HMI as covered in Step 4.

Cross-Reference Limitations Matrix

Common Pitfalls and Field Notes

• Forgetting the HMI runtime cache. Editing the HMI tag database in FactoryTalk View Studio does not propagate to a running HMI server until Restore is performed. A running PanelView Plus 7 with cached tag values will continue writing the old number.
• AOI direction mismatch. If the parameter is declared Output in the AOI definition, it cannot be written externally at all — a tag browser edit will fail silently or produce a runtime error.
• Online edit rejection. Guarded online edits (Logix Designer v33+) may refuse to change a parameter value if the controller is in Run mode and the change requires a finalization. Switch to Program mode if allowed by process conditions.
• Alias tag confusion. HMI projects frequently use symbolic aliases (e.g., TT_1090_EUMin) that map to the full path Program:AI_1090.Val_PVEUMin. Searching the HMI for the alias will resolve the binding.
• Multiple AOIs with the same name. In programs with replicated AOI calls per instrument loop, changing the value on instance AI_1090 does not change AI_1091. Verify the correct instance before assuming the edit stuck.

Logix Designer Version Notes

Related Parameter Adjustments

After updating Val_PVEUMin, review and confirm the following related parameters in the same AOI instance:

• Val_PVEUMax — upper engineering value; must be consistent with transducer range.
• Cfg_RawMin / Cfg_RawMax — must match the analog input channel configuration in Studio 5000 (e.g., 0–20 mA = 0–27648 counts).
• Cfg_AlarmLow / Cfg_AlarmHigh — process alarm setpoints expressed in engineering units.
• Cfg_ScaleType — linear, square root (for differential pressure flow), or custom curve.

FAQ