Duplicating an HMI numeric display never advances its PLC address. The documented method is three steps: copy the object with Ctrl-drag, generate numbered tags with Fill Down in the Tag Database, then assign each copy its tag individually. Because Fill Down steps addresses without checking them, test it on three tags against the controller's data map before filling the full run.
Copying a numeric display on an HMI screen never advances its PLC address. Every pasted copy shows the same input as the original until you assign it a tag of its own. The documented way to build a run of displays is three separate operations: copy the object with Ctrl held down, use Fill Down in the Tag Database to generate numbered tags with stepped addresses, then open each copy and assign its tag. Fill Down steps the address without checking it, so the generated list must be matched against the controller's data map before the screen goes back into service. This page walks through the workflow, the three-tag test, and an eight-thermocouple example with the arithmetic done out.
The short answer
No. There is no single command that lays out a run of objects and steps their addresses at the same time. The job splits in two, and each half is documented. Copying an object duplicates its graphics and its tag assignment, so the copy keeps pointing at the same input. Fill Down, the button in the Tag Database window, works on tags only: highlight the external tag that carries the controller address, run Fill Down, and the help file states the result in one line: "The new tag is assigned the next PLC address." The same help entry notes that Fill Down checks nothing about the next address before assigning it.
Treat Fill Down as a generator, and the controller's data map as the checker. When the map shows one address unit per input and a uniform step across the run, Fill Down produces the right list. When the map shows anything else, the generated addresses point at the wrong words and every tag needs its address typed by hand.
What you need
- The controller's data map: the I/O table or card configuration that shows where each thermocouple input lands, its base address and its step.
- One tag in the Tag Database for the first input, with its address confirmed against that map and against the controller program.
- The first numeric display placed on the screen and formatted: digit count, decimal places, units.
- A checkoff sheet with three columns: screen position, tag name, PLC address.
- A 30-minute maintenance window to download the revised screen and verify it live.
Steps
- Confirm the first tag by hand. Enter the tag for input 1, type its address from the data map, and cross-check the address against the controller program. If the address format looks different from what you expected, why HMI tag address formats change between PLC protocols explains how formats shift between controllers and protocols.
- Run Fill Down on three tags. Highlight the first external tag and fill three rows. Three is enough to expose the step without building a screen on top of an unconfirmed list.
- Compare all three generated addresses with the data map, first row to last. If all three land where the map says the next inputs live, fill the rest. If any one is off, fill nothing more on this screen.
- Fill the remaining tags. With the step confirmed by the three-tag test, highlight the first tag again and fill down the full count of inputs.
- Copy the display object. Hold Ctrl and drag the object; each release of the mouse button drops another copy. Place copies until every input has a display.
- Assign tags one at a time. Open each copy, set its tag, and set its number format in the same pass: digit count, decimal places. First copy takes the first tag and so on down the screen.
- Cross-check the screen before downloading. Read each object-to-tag pair against the ordered address list on the checkoff sheet, and look hardest at the first row, the last row, and any row where the map changes from one card to the next.
Example: eight thermocouple inputs on consecutive 16-bit words
Say the controller's data map lists eight thermocouple inputs, one 16-bit word per input, first input at word address 1000, step of one word. The addresses here are an example to show the arithmetic; the real base address and step come from the map printed for your controller's I/O configuration.
The target list: TC01 at 1000, TC02 at 1001, continuing to TC08 at 1000 + (8 - 1) x 1 = 1007. Count check: 1007 - 1000 + 1 = 8 addresses, one per input. With the step confirmed by the three-tag test, Fill Down produces exactly this list, and the last row of the checkoff sheet reads TC08, 1007.
Now the case where the same fill misfires. If the eight inputs were stored as 32-bit values, two 16-bit words per input, the channels sit at 1000, 1002, 1004, up to 1000 + 2 x 7 = 1014. A one-word fill puts display 2 at 1001, one half of channel 1's value, and display 3 at 1002, one half of channel 2. Every number on the screen after the first is wrong, and wrong in a way that still looks like a temperature. If the tags scale the raw value to 0.1 °C, a raw count of 3000 formats as 300.0 °C, and each wrong half still formats with a decimal point and a plausible magnitude.
The conversion from raw counts to a scaled value is its own job; display a thermocouple temperature on an HMI panel works that arithmetic through.
Decision: one address unit per display and a uniform step means Fill Down fits. Any other step means you fill nothing and type each tag's address from the map.
How to check it worked
Check the screen against live values before the line depends on it. Eight real thermocouples rarely agree, so compare each display with the value the controller itself reports for that input at the same moment. A display that tracks the wrong neighbor, or never changes, is on the wrong tag or the wrong address.
Check in this order: the tag assigned to the object, then that tag's address, then the controller's map. An HMI numeric display that shows nothing walks the same order when a display reads blank. Tick a row on the checkoff sheet only after its live value matches.
One safety note belongs here. A display sitting on the wrong word can show a steady, believable number for hours while it hides a real over-temperature on that input, so verify each display against its input before the screen returns to service.
When Fill Down gives the wrong addresses
Stop filling and hand-edit in three cases:
- The three-tag test lands off the map. Type each tag's address from the I/O table and leave Fill Down out of this screen.
- The run crosses cards or address blocks. Fill each uniform run separately, then build a new first tag where the map changes and fill from there.
- The controller names its data points instead of numbering words. There is no numeric step for Fill Down to apply, so build one HMI tag per named point and match each name against the controller program.
Recommendation: Use Ctrl-drag copies with Fill Down when the controller's data map shows one address unit per display and a uniform step across the run; run the three-tag test before the full fill; assign every copy its tag by hand; and verify each display against its live input before the line depends on the screen. Where the step is anything but uniform, fill nothing and type each address from the controller's I/O table.
Questions
Does a copied numeric display get a new PLC address?
No. The copy keeps the tag it was given, so it shows the same input as the original until you assign it a different tag. The address changes only in the Tag Database, one tag per input. Pointing several displays at one tag is allowed on purpose, for a repeated setpoint or a header value, and every display pointed there tracks that one address together.
Can I array bit tags such as fault lights the same way?
Yes. The same three steps work for bit tags: copy the object with Ctrl held down, run Fill Down on the bit tags in the Tag Database, then assign each object its tag. Check bits by toggling each one in the controller while watching its light on the panel. A light that follows the wrong bit points to a wrong address in the filled list.
What number format should the filled displays use?
Match the format to the input's scaling. A value scaled to 0.1 °C needs one decimal place, and the digit count must cover the largest value the input can report plus a spare digit of headroom. Set the format on each copy in the same pass as its tag assignment, so format work does not become a second trip over the whole screen.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.