How Do You Find Modbus Addresses in Productivity Structures?

Production is restored once the exported tag list becomes the working register index: sort structure members outside the tag database viewer, remove collisions, update the project mappings, and export again to prove the result. The key distinction is that a missing row in the viewer is a visibility problem, not proof that the member has no Modbus assignment.

Stop relying on the usual quick fixes

Start with the fixes that consume time without producing a complete register map.

Do not spend the shift reinstalling software, changing communications settings, or editing the Modbus client. Those actions do not correct an incomplete tag-database view. Get the register inventory under control first.

Recognize the real failure mechanism

The project can map Modbus registers directly to elements inside user-defined structures. The reported tag database sort does not flatten those nested elements into the Modbus-address view, so the displayed list is incomplete even though the assignments remain part of the project.

This separates the symptom into two layers:

• Engineering display layer: The address sort omits nested structure elements.
• Runtime mapping layer: The configured member may still be exposed over Modbus.

The limitation affects address discovery and change control. It does not, by itself, prove a communications fault. A client reading the wrong value may be using an old address, colliding with another assignment, selecting the wrong register category, or interpreting an address convention differently.

The software response recorded in 2016 stated that structure Modbus addresses could not be searched or sorted in the tag database at that time. The request was passed to software development. A later installation reported the same working limitation and used the exported tag list in Excel, so verify the behavior in the installed software instead of assuming a feature was added.

Separate missing visibility from a bad mapping

The values 30000 and 40000 are category examples requested for an address-assignment workflow. Treat them as displayed register references, not automatically as protocol offsets. Modbus software packages can present human-readable references and transmitted offsets differently; prove the convention with a known point before bulk renumbering.

Export and flatten the complete register inventory

1. Freeze mapping edits. Stop simultaneous address changes while building the baseline. Record which project copy is being audited.
2. Export the complete tag list. Use the project’s tag export function. Do not limit the export to the top-level rows visible in the sorted database view.
3. Open the export in Excel. Preserve the original export as a read-only baseline and work from a copy.
4. Identify the member path and Modbus fields. Retain the full structure and element path. A short member name alone is not unique when several structures use the same definition.
5. Filter for assigned members. Remove blank address records from the working view, but keep them in the untouched baseline.
6. Separate register categories. Keep input references such as 30000 apart from holding references such as 40000. A numeric sort that mixes categories can make unrelated records look adjacent.
7. Convert the address field to a sortable value. If Excel imported it as text, create a helper column that produces a numeric sort key. Preserve the original address text beside it.
8. Sort by category, numeric address, and full member path. This exposes repeated addresses and produces a usable change worksheet.

Do not import a heavily edited worksheet merely because it looks correct. The export may contain project metadata or syntax outside the visible address columns. Use the worksheet as the audit and planning record unless the installed software documents a supported round-trip import process.

Resolve duplicates and plan the new map

Add working columns for current address, proposed address, register category, full member path, change reason, and verification status. This creates the two-column assignment concept requested in the source—variable and address—without losing the information needed to audit the change.

1. Flag every repeated combination of register category and address.
2. Decide whether each repetition is intentional or a collision. Do not delete one mapping merely because two rows match; first inspect the application purpose.
3. Group related structure members into the desired order.
4. Assign proposed addresses in the worksheet, keeping the intended register category visible.
5. Check whether each data item occupies more than one register by reading its configured data type and the software’s mapping rules. Do not assume every element consumes one register.
6. Look for overlaps, not just equal starting addresses. A multi-register element can collide with a later member even when the displayed starting values differ.
7. Search the complete export for every old address scheduled for reuse.

Automatic sequential assignment is safe only after register width, category, and address convention are known. A simple “previous address plus one” sequence can overlap multi-register values or place a member in the wrong category.

Apply controlled changes in the project

1. Save a recoverable project copy before editing the live map.
2. Work from the approved worksheet, one structure or logical block at a time.
3. Open each full member path and replace the old Modbus assignment with the proposed assignment.
4. Mark the worksheet row as entered, but not yet verified.
5. After each block, inspect the changed members directly in their structures. The incomplete global sort cannot serve as the acceptance check.
6. Build and transfer the project using the site’s normal controlled procedure.
7. Coordinate the corresponding address changes in the Modbus client. A correct server map still appears broken when the client continues polling the old references.

If production must return before the entire map is cleaned, change only the points required for operation and reserve their final locations in the worksheet. Keep the remaining old assignments visible as technical debt. Get it running, then fix it properly.

Verify the result from both sides

Use three checks. Passing only one leaves a blind spot.

1. Re-export the tag list. Build a fresh register worksheet from the edited project. Compare it with the proposed map and search for every retired address.
2. Check for overlaps. Sort again by category and address. Account for the register width of each mapped data type before marking a range clear.
3. Exercise known values. Select representative members, change or observe their source values, and confirm that the Modbus client reads the same points at the planned addresses. Include at least one structure member from every changed block.

For a shifted-address symptom, test one known point before changing the full client database. Record the project’s displayed reference, the client’s configured reference, and the observed value. That single end-to-end check identifies the convention in use without guessing.

Archive the post-change export with the project revision. Until the tag database can search and sort nested mappings directly in the installed release, that export is the register index for troubleshooting and future modifications.

Know when the worksheet is not enough

Stop here if the export omits the structure members, strips their Modbus assignments, or cannot identify their full paths. Manual copying from every structure may be required to recover the current map, but do not approve a bulk renumber from a partial inventory.

Also stop if the mapping rules do not reveal the register width of a data type, the client and project cannot be reconciled on address convention, or a correct project export does not match runtime behavior. Capture the project revision, a minimal affected structure, the exported tag list, the old and proposed mappings, and the observed client result before contacting official support.

FAQ