Troubleshooting
Fixing Data Table Too Small Errors After a PanelView Plus Conversion
Short answer
When a converted PanelView Plus application reports a data table too small or missing for every imported tag, the fault is the runtime communication path, not the PLC data files. Set up the runtime shortcut manually after import and give the gateway card and its alias unique IP addresses; in one documented upgrade that single change made the online tag folders appear immediately.
On this page
- Read the error scope before touching the PLC
- Build the runtime communication path by hand
- Give the gateway card and its alias different addresses
- Prove the route with a one-tag application
- Confirm the gateway model and firmware
- When the data table really is the limit
- Verify the repair in order
- Questions asked
When a converted PanelView Plus application fills its event list with Data Table N7:100 in SLC at 10.10.10.100 is too small or missing, and the same wording repeats for every imported tag, the fault is the runtime communication path, not the SLC data files. The PanelView Standard import recreates screens and tags; it does not create the runtime shortcut, and a gateway addressing error can block the route even after you build one. In one documented DH+ upgrade, the gateway's alias address had been set to the same IP as the gateway card, and giving the alias a unique address made the online tag folders appear immediately. Fix the path before you resize anything in the controller.
Read the error scope before touching the PLC #
The message names one address, but the scope of the failures identifies the fault. The wording concerns the read request, not the file: the same entry appears when the request never reaches the controller at all, which is exactly what the duplicate-IP case produced. Decide with this table before editing anything.
| Failing scope | Most likely fault | First move |
|---|---|---|
| Every imported address, several data-file types | Runtime shortcut, gateway route, duplicate IP, unreachable DH+ station | Stop editing the PLC and fix the path |
| Only N7 addresses | Imported tag syntax or wrong destination station | Check address spelling and the shortcut target |
| Only elements at the top of one file, such as N7:100 and above | Integer file genuinely shorter than the request | Check the file length in the controller |
| One-tag test works, converted application fails | Shortcut assignment or per-tag syntax | Compare the test shortcut against the application's |
List which tags fail before you act. A failure across several data-file types is a routing problem until a one-tag test proves otherwise. If the conversion in FactoryTalk View Studio aborts before you ever reach runtime, that is a separate fault covered by Fixing the older-format MER file conversion error.
Build the runtime communication path by hand #
The converted project arrives without runtime communications, so you create them manually.
- Open the project's runtime communication setup in FactoryTalk View Studio and create the shortcut the imported tags reference.
- Point the shortcut across the Ethernet driver to the gateway, then through the gateway to the DH+ station number of the SLC.
- Check the runtime side specifically, because a successful browse while developing does not copy itself into the runtime configuration.
- Browse online through the configured path and confirm the SLC enumerates with its data files as folders.
- Download to the terminal and re-check there, since the terminal resolves the path at runtime, not at design time.
A browser that stays empty although the shortcut exists is its own fault; FactoryTalk Linx tag browser empty after shortcut setup walks through it. Folders that appear duplicated or missing rather than empty point elsewhere again — missing and duplicated tag-selection folders covers that variant on the FactoryTalk View SE side.
Give the gateway card and its alias different addresses #
A DH+ gateway such as the AN-X2-AB-DHRIO exposes more than one configurable Ethernet identity: the card's own address and an alias the route uses. They are separate entries and must hold separate addresses. In the reported upgrade the alias had been assigned 10.10.10.100, the card's own address, and every tag read failed with the too-small-or-missing wording across all data tables. Moving the alias to an unused address on the same subnet brought the online tag folders up at once, and the project was finished the same day.
Before any PLC edit, open the gateway configuration and confirm the card address and the alias address differ. If they match, change the alias, apply the configuration, and let the connections rebuild. Apply address changes with the machine in a safe state, because the operator view can drop while the endpoints re-associate. If you also re-address the PLC or other nodes during this work, expect the follow-on faults described in HMI comms errors after a PLC IP address change.
Prove the route with a one-tag application #
Build an empty application containing one numeric display, or one bit used as a blink, pointed at a known-good address on the target DH+ station, and run it on the terminal. Change the value in the controller and confirm the display follows it; for the bit, confirm both the on and off states.
- Test fails: the fault is the route, the gateway or the addressing. Stay out of the converted application.
- Test passes while the converted application fails: the fault is the shortcut assignment or the imported tag syntax. Compare the test shortcut against the application's, then check the tags themselves.
Confirm the gateway model and firmware #
Read the model and firmware revision from the installed unit and its configuration pages before planning any update. Runtime browsing on the terminal has not always traversed this class of bridge the way a desktop browse does, which is why the revision matters. The manufacturer's compatibility notes for your exact unit, not the model name alone, decide whether the terminal you run is supported at the firmware you have.
When the data table really is the limit #
Worked example, illustrative: the error text tells you which element is requested. N7:100 is element 100 of integer file 7, so the file must span elements 0 through 100.
- Required length = 100 + 1 = 101 elements
- One integer element is one word, so the request spans 101 words
- A file configured at 64 elements ends at N7:63, and the request lands 100 − 63 = 37 elements past the end
If the controller project shows such a short file and the failures stop at the top of that one file, raise the length to at least 101 elements and download. Input and output image tables are the exception: their length follows the I/O configured in the rack, so a read that outruns them is fixed by shortening the request, not by editing a table size. Resize a data file only when the failing tags are confined to the tail of that single file.
Verify the repair in order #
- The card and the alias each answer only at their own address; an intermittent ping is a fail, not a pass.
- An online browse through the runtime path lists the SLC and its data files as folders.
- The one-tag application runs on the terminal and tracks a changed value, and a blink bit shows both states.
- The converted application shows live values for at least one tag of each data-file type; any family that still fails moves the boundary to that file.
- Imported references keep the colon in addresses such as N7:100 and brace tag references correctly in expressions; malformed punctuation fails tags one at a time even when the route is sound.
Questions asked
How do I confirm the alias is duplicating the card IP?
Open the gateway configuration and read both addresses side by side; the card and the alias are separate entries. From any PC on the subnet, compare the hardware address your ARP table reports for that IP across several refreshes, because two different hardware addresses answering one IP confirms a duplicate. An address that pings intermittently is the same symptom.
Does enlarging the N7 file ever fix this error?
Only when the failures stop at the top of one file. Element N7:100 needs a file of at least 101 elements, so if the controller project shows fewer, raise the length there and download. When every file type fails at once, resizing changes nothing because the request never reaches the controller. Input and output image tables are the exception: their length follows the I/O configured in the rack, so you shorten the request instead of editing a size.
Why does browsing work on my computer while the terminal still errors?
The browse in the development environment and the browse the terminal performs at runtime use different driver software on different paths. A successful desktop browse proves the controller, the data files and your office route exist; it proves nothing about the shortcut the runtime actually uses. That is why the one-tag application has to run on the terminal itself before you trust the route.
Which gateway firmware supports PanelView Plus 6 and 7 on DH+?
For the AN-X2-AB-DHRIO, the manufacturer's compatibility notes report operation with PanelView Plus 6 and PanelView Plus 7 terminals from firmware 8.10 onward. Read the model and revision on your installed unit before planning an update, and apply it with the line in a safe state. If your revision is older, treat the update as a planned job rather than a mid-fault troubleshooting step.