The Scale with Parameters (SCL) instruction in Logix 5000 performs a linear map from raw analog counts to engineering units. Misconfiguration almost always starts at Input Min and Input Max: those fields are not milliamps or volts. They are A/D counts reported by the analog module for the selected electrical range. Using 4 and 20 as count boundaries produces nonsense process values that look like transmitter faults.

Output = ((Input − Input_Min) ÷ (Input_Max − Input_Min)) × (Scaled_Max − Scaled_Min) + Scaled_Min

Resolution and count ranges

Bit resolution sets the theoretical full-scale integer span, but Rockwell modules often use offset or proprietary scales. Always take counts from the module data table in the installation manual, not from assumed power-of-two math alone.

Calculating Input Min / Max for live-zero signals

For a sub-range signal on a wider full-scale card:

Input_Min = (Signal_Low ÷ Signal_FullScale) × FullScale_Counts
Input_Max = (Signal_High ÷ Signal_FullScale) × FullScale_Counts

Worked example — 1746-NI4 in 4–20 mA mode with 0–20 mA full scale at 16384 counts:

• Input_Min = (4 ÷ 20) × 16384 ≈ 3277
• Input_Max = 16384
• For 0–20 bar: Scaled_Min = 0, Scaled_Max = 20

The same raw boundaries support a shifted engineering range such as −1 to +6 bar when the transmitter span requires it.

Effective resolution and “13.67 bits”

Operating 4–20 mA on a 0–20 mA full-scale 14-bit span uses only 13107 of 16384 counts. log₂(13107) ≈ 13.67 bits. That loss is intrinsic to live-zero offset on a wider ADC window, not a configuration bug. Cards that re-range the ADC to 4–20 mA natively (for example 1756-IF16 in 4–20 mA channel mode) recover fuller effective resolution across the 16 mA active span.

Studio 5000 configuration steps

1. Open module properties and record the configured input range and data format.
2. Look up the integer counts for the low and high signal endpoints.
3. Enter transmitter engineering limits as Scaled_Min / Scaled_Max.
4. Map the channel tag to SCL Input and a REAL process tag to Output.
5. Use a separate CPT only when unit conversion belongs outside the linear map.

SCL versus CPT in practice

SCL remains the clearer choice for a single linear transmitter map because the four boundaries sit in one instruction and document themselves for the next technician. CPT is preferable when the scaling expression must include an intermediate offset, square-root flow relationship, or multi-step unit conversion inside one equation. Execution time difference is negligible on modern Logix controllers; readability and change control matter more. Do not mix module engineering-unit scaling and SCL on the same channel unless one path is intentionally bypassed—double scaling is a common commissioning error that looks like a transmitter calibration fault.

Count-span math vs live engineering units

Source 4 mA and confirm Scaled_Min, source 20 mA and confirm Scaled_Max, then check midpoint. Deviation means wrong count boundaries or wrong channel range selection. Prefer module engineering-unit scaling when the span is fixed; keep SCL when runtime re-ranging or mixed raw tags are required. Reference 1756-RM003 for the instruction and the analog module user manuals (1746-UM005, 1756-UM009, 1769-UM002) for count tables. Analog scaling standards should travel with the same documentation used for other Logix PLC and PAC assets.