IMDHMIControls LibraryShop main store

Troubleshooting

Fixing 4-20 mA scaling on a Quantum AVI030 analog input

Controllers and I/O Published 5 min read

Short answer

On the Quantum AVI030 analog input, the raw range follows the channel resolution: 12-bit reports 0-4095 counts and 16-bit maps 4-20 mA to 6400-32000 counts. Neither 0-64000 nor a mismatched 0-4095 will scale or hold; set the block's raw limits to match the configured resolution and verify with 4, 12 and 20 mA test currents.

On this page
  1. The two documented raw ranges
  2. Why 0-4095 and 0-64000 both failed
  3. Match the block to the channel
  4. Worked example: scaling 0-20 on a 16-bit AVI030 channel
  5. If the reading still walks after days
  6. Questions asked

Set the scaling block to the raw range the channel resolution actually produces. On the AVI030, a 12-bit channel reports 0-4095 counts and a 16-bit channel maps 4-20 mA to 6400-32000 counts; 0-64000 matches neither. Match the block's raw limits to the resolution configured on that channel, then verify at live zero, mid-span and full scale from a loop calibrator. What follows is what the module reports, why both settings failed, the configuration steps, and a worked check with the arithmetic shown.

The two documented raw ranges #

The Modicon TSX Quantum AVI030-00 (140 AVI 030 00) is an eight-channel high-level analog input module; its inputs also take the zero-based current range and 10 V of either polarity, so the channel type has to match the transmitter before any scaling can be right. For a live-zero current channel there are exactly two raw ranges, set by the channel's resolution setting:

Channel resolution Raw counts over the loop span
12-bit 0 to 4095
16-bit 6400 to 32000

In 16-bit mode the module does not fill 0-65535, and it does not need to: the live-zero and full-scale endpoints sit on a straight count line that starts at zero current, which the worked example proves from the counts themselves. The arithmetic of scaling is portable and the raw limits are not — converting 0-4095 raw counts to engineering units on a Micro820 input is the same straight-line job over another platform's 12-bit span.

Why 0-4095 and 0-64000 both failed #

The two trials failed for different reasons, and both come back to one channel setting.

With 0-4095 in the block, the scaled value is wrong because a 16-bit channel is already above the block's ceiling at live zero: the count there is 6400, so the block sits saturated across the whole current span. That is what a 12-bit range against a 16-bit channel looks like.

With 0-64000, the module's full scale is half the block's span, so the two ends of the loop can never both be right, and a reading that looks correct at first and walks after a few days is the symptom of exactly that disagreement. Retire 0-64000: it is a documented range on neither resolution.

Match the block to the channel #

  1. Open the project in Unity Pro, or Concept on the older systems, and locate the AVI030-00 in the hardware configuration.
  2. Open the module's channel configuration and set the channel type to the live-zero current range. With the zero-based current range or a voltage range selected, the live zero is in the wrong place for a current transmitter.
  3. Read the resolution setting on that channel and decide which of the two raw ranges you are working with.
  4. Enter raw limits in the scaling block to match: 0/4095 for 12-bit, 6400/32000 for 16-bit. Leave the Eng limits at the process span, 0-20 in this case.
  5. Build and download so the configuration and the program land together; correcting the block while the channel stays at the other resolution reproduces the fault.
  6. Inject live-zero, full-scale and mid-span currents in turn and read the block output: 0, 20 and 10 on a 0-20 scale.

Before injecting test currents, put whatever this loop drives in a state where a wrong reading cannot move the machine; hand mode on the valve or drive is enough.

Worked example: scaling 0-20 on a 16-bit AVI030 channel #

Inputs, each with its source:

  • Channel set to the live-zero current type at 16-bit resolution — the configuration from steps 2 and 3 above.
  • Raw endpoints of 6400 counts at live zero and 32000 counts at full scale — the documented 16-bit range for this module.
  • Engineering limits of 0-20 — the Eng settings in the scaling block.
  • A test current of 12 mA from a loop calibrator — the mid-scale check.

The rule in words: the scaled value is the raw reading minus the count at live zero, divided by the count span, times the engineering span.

The arithmetic:

  • Count span: 32000 − 6400 = 25600 counts across the 16 mA span.
  • Slope: 25600 ÷ 16 = 1600 counts per mA. The same slope reaches zero current, because 4 mA × 1600 = 6400, the documented live-zero count.
  • Raw at the test current: 6400 + (12 − 4) × 1600 = 6400 + 12800 = 19200 counts.
  • Scaled value: (19200 − 6400) ÷ 25600 × (20 − 0) = 12800 ÷ 25600 × 20 = 0.5 × 20 = 10.0.

Result: 12 mA reads 10.0 on the 0-20 scale, at 25600 ÷ 20 = 1280 counts per engineering unit.

Decision: hold half a percent of span — 0.1 unit, 128 counts — as the pass tolerance at each test point. Readings of 0, 10.0 and 20.0 at the three test currents close the scaling fault; anything outside that tolerance means the raw limits still disagree with the channel's resolution, so fix that before touching the transmitter. The formula itself is portable — it is the same one behind scaling a 4-20 mA input to engineering units in CPM2 ladder — but the raw limits belong to this module alone.

If the reading still walks after days #

Once the three test points verify, a slow drift is not a scaling fault. Work the loop, not the block:

  • Confirm the loop supply holds voltage at the transmitter terminals under load.
  • Re-terminate the module connector and every junction box on the pair; a resistive joint moves counts with temperature.
  • Look for moisture or corrosion in the field enclosures on that run.
  • Verify one ground reference on the loop; a second path to ground adds current the transmitter never sent.

The decisive test: substitute the calibrator for the transmitter, hold 12 mA for a full shift, and watch the block. A steady 10.0 clears the module and points at the field loop; a reading that still walks against a known current source condemns the module, so swap it and re-run the three-point check.

Questions asked

Which signal types does the AVI030-00 accept besides 4-20 mA?

The eight inputs take the zero-based current range, the live-zero current range, and 10 V of either polarity. The channel type must match the transmitter, because the 6400-count live zero exists only on the live-zero setting; feed a 4-20 mA transmitter into a zero-based current channel and the offset shows up as a reading no scaling block will remove.

How do I tell which resolution a channel is using without opening the project?

Inject a known current and read the raw register. In 16-bit mode the counts run 1600 per mA from zero, so mid-span reads 19200 and full scale reads 32000; any raw value above 4095 rules out 12-bit on the spot. Then confirm the setting in the channel configuration, because the scaling block has to match it exactly.

What should the Eng limits be for a 4-20 mA transmitter?

The Eng limits are the process span, not the loop current. Keep 0-20 only if the operator is meant to read loop milliamps directly; otherwise enter the transmitter's span, for example 0-100 for an instrument rated 0-100 units. Raw limits follow the channel resolution; Eng limits follow the instrument and never change with resolution.

Can I leave 0-64000 in the block since it read correct at first?

No. At full-scale current a 16-bit channel sits at 32000 counts, the exact midpoint of a 0-64000 block, so half the block's span is unreachable and neither end can be right at the same time. Set 6400-32000, re-verify at both endpoints, and treat any data logged under 0-64000 as suspect until you recheck it against the transmitter.

Keep reading

  • Troubleshooting

    Troubleshooting non-linear 4-20 mA readings on an S7-1200 analog input

    A 4-20 mA loop is linear by construction, so counts swinging between 10 and 30246 mean the current at the terminal is not what the sensor LCD shows. On the SM 1231, 27648 counts is the top of the 4-20 mA range and 30246 decodes to 21.5 mA over-range fault current. Check the loop with a series meter, split sensor from module with a calibrator, and anchor NORM_X to 0 and 27648.

    Controllers and I/O

  • Selection guide

    Add 4-20 mA analog inputs when the CompactLogix rack is full

    Swap the installed four-channel analog input card for an eight-channel one when channel isolation matches; that adds four inputs against a need of three, with no rack, power-supply or enclosure change. If isolation rules the swap out, reposition the existing power supply to free an end slot. When the cabinet itself is full, add a POINT I/O analog module or IO-Link converters over EtherNet/IP.

    Controllers and I/O

  • Troubleshooting

    FX5U thermocouple readings need a dedicated TC input

    A Type K thermocouple on the FX5U built-in analog input cannot yield usable temperature: the voltage channel's count step is worth about 61 °C of Type K signal, and a reading near 200,000 means the program is reading the wrong operand or width, not temperature. Verify the raw 0–4,000 count path, then move the thermocouple to a dedicated input adapter with cold-junction compensation and read degrees directly.

    Controllers and I/O