IMDTouchKnowledge BaseShop main store

Troubleshooting

C-more text entry loses first characters in PLC memory

HMI and touchscreens Published 7 min read

Short answer

Losing exactly the first two characters means the string is offset by one 16-bit V-memory word, because the DL260 stores two ASCII characters per word. Read the string back at the PLC: if the DL260 holds the full text, the receiving panel's ASCII String tag starts one word late; if the PLC value already starts late, move the writing panel's entry tag onto the string's first word.

On this page
  1. Why does a C-more text entry lose exactly the first two characters?
  2. Where do I split the fault, at the panel or at the PLC?
  3. How do I read the string back out of the DL260?
  4. What must the entry tag and the display tags agree on?
  5. What exactly do I change to fix it?
  6. How do I share one entry across several C-more panels?
  7. How do I prove the fix on every panel?
  8. Questions asked

When a C-more text entry loses exactly the first two characters on the way into a DL260, the string sits one V-memory word off from where the panels read it — the one-word offset that deletes a leading character pair and nothing else. Read the stored string back at the PLC before touching either panel: if the DL260 already holds the text without its first two characters, correct the writing panel's entry tag; if it holds the complete text, correct the receiving panel's read tag. The steps below give the test that splits the fault and the one change that restores the text for every panel on the link.

Why does a C-more text entry lose exactly the first two characters? #

Two characters vanish together because the DL260 stores the string in consecutive 16-bit V-memory words at two ASCII characters per word, so any tag that begins one word late, or writes one word late, swallows the leading pair and passes the rest of the text through unchanged.

Each word is 16 bits and each ASCII character needs 8, so the pairing is fixed at 16 ÷ 8 = 2 characters per word. A five-character entry such as AB123 occupies 5 ÷ 2 = 2.5, rounded up to 3 words, with the last word holding the fifth character and one empty slot. Begin a tag one word into that range and the panel serves characters three onward — the symptom, reproduced by arithmetic alone.

The mechanism lives in the tag, not in the keypad: the text entry object's job is to put the submitted text into the PLC registers from the tag's start address onward, and its two object styles change how the operator types the string, not where the characters land. The same one-word signature appears on unrelated hardware, where it lands the pair somewhere stranger still — see the write-up on a PanelView 300 ASCII entry that wrote its first two characters into a MicroLogix string length.

Where do I split the fault, at the panel or at the PLC? #

Look at the DL260 first: if the PLC already holds the text without its first two characters, the writing panel's entry tag is at fault; if the PLC holds the complete text, the receiving panel's read tag is at fault. The PLC is the shared copy every panel reads, so its stored value decides which tag gets edited.

Three checkpoints settle it, and each is a value you can write down:

  • The exact text the operator submitted, including the first two characters.
  • The string range in the DL260 programming software, read immediately after the entry.
  • The text shown on a receiving panel.

Read the result against the case list:

  • PLC complete, panel short — receiving-side fault: that panel's tag start address, length or character offset.
  • PLC already missing the first two characters — writing-side fault: the entry tag's start address or its character-to-word mapping.
  • Value shifting between checks — a second writer: another panel object or a PLC instruction overwriting the same words.

A display-side patch cannot restore characters the PLC never received, which is why this check comes before any tag edit.

How do I read the string back out of the DL260? #

Enter a five-character test string such as AB123 and open the string's area in the DL260 programming software immediately after the entry: five characters occupy 3 words at two characters per word, so exactly three words should change.

Call the string's intended first word V2000 for this example and use whatever address your program actually reserves. The expected layout is AB in V2000, 12 in V2001 and 3 in V2002 — 5 characters ÷ 2 per word = 2.5, rounded up to 3 words. Run the test in order:

  1. Write down the submitted text, including AB.
  2. Note the entry tag's configured start address and character length.
  3. Enter AB123 at the panel, then read the range around the tag address in the programming software.
  4. Record the first three words that changed, with the character pair each one holds.
  5. Compare the word that received AB with the start address configured on every panel's display tag.

If three words change but AB sits in the second one, the entry wrote one word late. If AB sits in the first word and a panel still drops it, that panel reads one word late. If the changed words do not decode as character pairs at all, compare them against the DL260 manual's ASCII instructions chapter before moving any address — the program may be building the string with its own layout.

What must the entry tag and the display tags agree on? #

One data type, one start address, one length: every panel needs an ASCII String tag with the same start address as the string's first V-memory word and the same character count as the entry tag; a tag one word late serves characters three onward.

What you observe Where the fault sits The change that fixes it
PLC holds all 5 characters; one panel shows from the 3rd That panel's read tag starts one word late Move its start address back onto the first word, V2001 to V2000 in the example
PLC holds characters 3 onward; AB never arrived The entry tag wrote one word late Move the entry tag's start onto the word that received AB
Panels disagree with each other Two different tag definitions or two different ranges Compare each tag against the PLC value, never against another panel

While each tag is open, check any setting that shifts where its characters begin, and note the configured length against the words the test saw change. If ladder logic moves or rebuilds the text, its source and destination ranges must begin at that same first word; the DL260 manual's ASCII instructions chapter documents the layout its string instructions use.

What exactly do I change to fix it? #

Change one field on the one tag the test condemned: move its start address onto the word that actually received the first two characters, leave the length alone, download the panel project by the normal transfer procedure, and rerun the AB123 test.

The decision, case by case:

  • Read-side fault: the receiving panel's tag start moves one word earlier, V2001 to V2000 in the example, so its first word is the one holding AB.
  • Write-side fault: the entry tag's start moves onto the word that received AB, so the next entry puts character one at the string's first word.
  • Second writer found: point the overlapping write somewhere else or remove it; never relocate the shared string to escape a collision, because every panel's tag would have to move with it.

Record the original tag settings before the edit, change nothing in the PLC program for this fault, and rerun the test on the writing panel before touching the next screen.

How do I share one entry across several C-more panels? #

Store the text once, in the DL260, and point every panel's string tag at that same first word: the entry panel writes to it, every other panel reads from it, and no panel keeps a private copy that can drift.

When the tag editor offers only V-memory as the address for the PLC's string tags, that restriction is the driver binding the tag to consecutive words — the guide to HMIs that show only V-memory for PLC string tags covers how that mapping behaves. Reserve the range once in the program, begin any ladder copy of the text at the same first word, and treat the DL260's stored value as the master, because it is the one copy all of the panels see.

How do I prove the fix on every panel? #

Rerun the AB123 entry and then a longer one — 10 characters need 5 words — checking three places each time: the DL260's stored words, the text on the writing panel, and every receiving panel, until all show the same complete text.

The long pass matters as much as the first: 10 ÷ 2 = 5 words, so it exercises the whole range and proves the tail survives — a tag whose start was fixed but whose length was left short passes AB123 and truncates the long string. Judge each panel against the DL260's stored words, not against another panel, because the PLC holds the only shared copy. If the text feeds something operators act on, such as a lot number or a recipe name, confirm the corrected string at the DL260 before releasing the line. Keep every passing tag's start address in the project notes; the fault returns the same way it arrived, through a tag edited off the shared first word.

Questions asked

One missing character versus two missing characters — do they mean different faults?

Yes. Each V-memory word carries two ASCII characters, so a start address off by a whole word hides exactly two, and that is the fault this article fixes. A single missing character, or an odd count, points instead at how the bytes sit inside each word or at a length element the string reserves; settle that from the DL260 manual's ASCII instructions chapter and the panel driver's string format before editing addresses.

Does the DL260 need an ASCII instruction before a panel can store text?

No. The text entry object writes the submitted string straight into the consecutive PLC registers given to it, so the program only needs to leave that range reserved and untouched. If ladder logic also builds, moves or compares the text, those ASCII instructions follow the layout documented in the DL260 manual, and the panel tags must begin at the same first word that logic expects.

How many V-memory words does an entry of a given length need?

Count two characters per word and round up: 5 characters take 3 words because the last word carries the fifth character plus one empty slot, 8 characters take 4, and 10 characters take 5. Set the same character count on the entry tag and on every panel's display tag so the whole range matches. Word-level mapping is the rule across these string registers; a CLICK TXT register, mapped the same way, even requires the panel tag to be at least two characters.

One panel shows all the characters now — are the others fixed too?

No. Each panel's ASCII String tag carries its own start address and length, so a correction on one panel leaves another panel reading one word late. Check every panel against the DL260's stored string, never against another panel's screen, because the PLC holds the only copy all of the panels share, and record each tag's start address in the project notes so a later edit cannot reintroduce the offset.

Keep reading

  • Troubleshooting

    HMI Shows Only V-Memory for PLC String Tags

    Dynamic Text offers only V-memory because the HMI project was configured for K-Sequence, the DirectLogic-family protocol, while the strings live in the Do-more CPU. Select the Do-more serial protocol in the panel software's communication setup, then point the text object at SS0; no STR2INT conversion is needed.

    HMI and touchscreens

  • How-to

    Where to save C-more panel IP settings in the project

    The C-more project does store the panel's IP address and subnet mask: enter them under Setup > Touch Panel Network > Ethernet Port and save the project. That entry is a record, not a lock — the panel's System menu can still change the live values — and it is separate from the PLC destinations, so a controller address change still means editing each affected project and re-transferring it to every panel.

    HMI and touchscreens

  • How-to

    How to Create and Export GX Works3 Labels for a C-More HMI

    Define the name as a global label in the GX Works3 label editor and give it a device target such as Y5; typing the name on a coil only creates an untargeted entry. Export the global label CSV, then hand-map each row into the C-More tag import template, because the two CSV schemas do not match. Separately, confirm the C-More Mitsubishi driver covers the FX5 before trusting any serial retry.

    HMI and touchscreens