Troubleshooting
Why C-More Shows Tag Addresses You Cannot Set in Productivity
Short answer
That address is the System ID the Productivity controller assigned to the tag, not a field you can type into Productivity Suite. View it in the Tag Database column headers, and keep the workflow one-way: create and name tags in Productivity, export, then import into C-More.
On this page
- Why does C-More show an address I never entered?
- Where do I view the System ID in Productivity Suite?
- Can I choose or edit the System ID myself?
- How do I import Productivity tags into C-More the right way?
- What if I already created the tag in C-More first?
- How do I build screens before the PLC tag list is final?
- Why does an imported tag still show the old address?
- What should I verify before running the machine on these tags?
- Questions asked
That address-looking value beside your imported tag is the System ID the Productivity controller assigned to that tag. Productivity controllers are tag-based: you give each tag a name in Productivity Suite, and the controller assigns the System ID, which C-More then shows in its address column after import. There is no field in Productivity where you can type it back in, and none is needed. Below you will see where the ID lives, how to run the import in the one direction that works, and how to repair a C-More tag that was created before its controller tag existed — the exact situation with a Productivity 2000 processor such as a P2-550 driving an EA9-T8CL panel.
Why does C-More show an address I never entered? #
Because it is the System ID that the Productivity controller assigned to your tag when the tag was created — C-More lists it in the address column, but Productivity Suite never presents it as a field you can type or edit.
On a fixed-address PLC you pick the address and the HMI mirrors it, so hunting for the assignment field is the right instinct there. A Productivity controller inverts the relationship: you own the tag names, the controller owns the IDs, and C-More merely displays what arrived in the import file. The search ends nowhere because no such field exists in any Productivity series — 1000, 2000 or 3000. If you come from platforms where a mistyped bit fails at tag entry, that difference in philosophy is the whole story; fixing invalid bit address errors when adding HMI tags shows how those fixed-address platforms behave instead.
Where do I view the System ID in Productivity Suite? #
In the Tag Database window of Productivity Suite: left-click a column header and choose "System ID" to add the column, then read each tag's ID beside its name.
- Open the Tag Database of the project that produced the HMI tag export — the same saved project, not a copy on another machine.
- Left-click any column header and choose System ID.
- Find your tag by name, read the System ID beside it, and compare that value with the address shown in C-More.
A match confirms the import did its job. A missing tag, or a name that differs, means the export came from a different or older project: regenerate the export from the project that contains the intended tag before editing either database.
Can I choose or edit the System ID myself? #
No — the controller assigns System IDs when tags are created, so the workflow only works one way: build and name tags in Productivity Suite, then import them into C-More. No supported option sets the ID from the HMI side.
What you control is the name, and the name is everything. It is the join key that matches an imported C-More entry to its controller definition, and the key a later overwrite import uses to find and replace the same tag. Keep names identical on both sides, and treat Productivity as the single source of the tag list. Typing the C-More-shown value back into the controller would achieve nothing even if a field accepted it, because the controller is the authority that assigned that value in the first place.
How do I import Productivity tags into C-More the right way? #
Export the tag list from the saved Productivity project, import that CSV into the C-More tag database, then check every imported tag's name and address against the System ID column before using it on a screen.
- Create or import the tags in Productivity Suite and save the project.
- Export the tag database to the CSV file Productivity generates.
- In the C-More programming software, import that CSV into the tag database.
- Verify each entry: the name exists in the Productivity Tag Database, the C-More address equals that tag's System ID, and the datatype matches on both sides.
This one-way flow is the normal path for every project, first panel or fiftieth. When the import is clean, the C-More address column needs no interpretation at all: it is a display of values the controller already owns.
What if I already created the tag in C-More first? #
Repair it with a name-matched overwrite import: create the same tag name in Productivity, save and export, then import into C-More with "Overwrite Existing Tags" selected — the name stays and the address updates to the controller's System ID.
The "Overwrite Existing Tags" option makes any imported tag name replace an existing tag of the same name; that documented behavior is what turns a name collision into a repair.
Worked example: during screen building you created a C-More tag named Tank2_Level and gave it an arbitrary address just to get the object working. The Productivity project now defines Tank2_Level as a real controller tag.
- Create, or confirm, a tag named Tank2_Level in Productivity Suite and save the project.
- Export the tag database to a fresh CSV from that saved project.
- Import the CSV into C-More with "Overwrite Existing Tags" selected.
- Read the C-More entry: the name is still Tank2_Level, and the address column now equals the System ID shown beside Tank2_Level in the Tag Database.
One rule protects you here: C-More allows several tag names to reference one address, but never one name referencing two different addresses, so a name cannot silently split in two. After an overwrite import, check any other names that still point at the old arbitrary address — those controls now read data nothing writes.
How do I build screens before the PLC tag list is final? #
Bind controls to placeholder internal tags that share a prefix such as INTERNAL_ — one placeholder per datatype you will use — then swap them for real controller tags after the import, finding every placeholder with Tag Cross Reference.
INTERNAL_ is a working convention, not a reserved word; the point is a prefix you can search. On an EA9, the cross-reference dialog sorts its columns, so sort by screen number and the placeholders group into a work list, screen by screen. The cross-reference tells you where a placeholder is used, never which production tag replaces it: choose by the control's function and datatype against the Productivity database, and check every reference a placeholder serves — several controls on several screens do not all take the same final tag just because they shared a placeholder.
Why does an imported tag still show the old address? #
Almost always one of two causes: the CSV came from an older saved project, or the import ran without "Overwrite Existing Tags" selected — regenerate the export from the current saved Productivity project and import again with the option on.
| What you see | Why | What to do |
|---|---|---|
| C-More address appears nowhere as an editable field in Productivity | It is the controller-assigned System ID | Add the System ID column and match by tag name |
| Same tag name in both databases, different address | C-More entry predates the controller tag, or the CSV is from an older project | Name-matched overwrite import from the current saved project |
| Name and address match, but the control misbehaves | Control points at another tag, a placeholder, or a datatype differs | Check the control's tag assignment, its cross-reference entry, and datatypes on both sides |
| Several C-More names share one address | Multiple names may reference one address | Confirm each alias is intentional and backed by the right Productivity tag |
When the name and the System ID both match and one control still misbehaves, stop re-importing the database: the binding on that object is the fault, and the cross-reference will show which tag it actually points at.
What should I verify before running the machine on these tags? #
Import once from the final saved Productivity project, then walk the C-More tag list name by name against the System ID column, datatype by datatype, and treat any tag that commands an output as unproven until you watch it move the right device.
- The import came from the final saved project, not an earlier export.
- Every C-More tag name exists in the Productivity Tag Database, spelled identically.
- Each C-More address equals the System ID beside that name.
- Every datatype agrees on both sides of the binding.
- A cross-reference sorted by screen number shows no INTERNAL_ placeholders left.
- Output-commanding tags were exercised with the machine in a state where an unexpected start cannot hurt anyone.
The walk is the same name-by-name discipline as validating HMI variables during a software migration, applied to a single panel.
Questions asked
Can two C-More tag names point to the same Productivity tag?
Yes. The tag rules allow several names to reference one address, while one name may never carry two different addresses. Aliases are therefore legal but silent: after an overwrite import, any leftover name still pointing at the old arbitrary address reads the wrong data with no error, so list your aliases and check each one on purpose.
What happens if I edit the address of an imported tag directly in C-More?
Nothing stops you, and nothing warns you afterwards. The name keeps reading like your controller tag while the address no longer equals its System ID, so the object on screen works with whatever you typed. Undo the edit and repair the tag with a name-matched overwrite import instead of hand-editing the address column.
Does the same import path work for Do-more Designer projects?
Yes. C-More supports importing Do-more Designer project tags using the same export-then-import pattern. The rule does not change with the source package: the controller-side software owns the tag list, and C-More consumes it, so always import from the current saved project.
Is INTERNAL_ a reserved prefix in C-More?
No. It is a working convention: internal tags named with a prefix you will recognize are easy to pick out of the Tag Cross Reference once the real controller tags exist. Any consistent prefix works; the point is that one search for the prefix finds every placeholder in a single pass.