Troubleshooting
HMI Shows Only V-Memory for PLC String Tags
Short answer
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.
On this page
- Why the tag list stops at V-memory
- Fix: point the project at the Do-more serial protocol
- Worked example: unblocking SS0 on a 3-inch C-More micro with K-Sequence selected
- Why STR2INT is not the fix here
- Prove it on the panel, not only in simulation
- If the string still does not appear
- Scaling numeric entry afterward
- Questions asked
Dynamic Text offers only V-memory because the HMI project is speaking the wrong protocol. K-Sequence is the AutomationDirect protocol for the DirectLogic PLC families; that selection offers none of the Do-more CPU's string memory, so the tag browser never shows SS0. Select the Do-more serial protocol in the project's PLC communication setup and the string locations appear; in the reported case that single change fixed the display, and no STR2INT conversion was needed. Check the protocol before touching the PLC program.
Why the tag list stops at V-memory #
A display object can bind only to memory the selected protocol addresses. The tag browser is built from the project's device and protocol configuration, so a project set to K-Sequence offers the V-memory that selection speaks and nothing more. The Do-more string locations, SS0 among them, are not part of what K-Sequence offers, so the string data type never reaches the Dynamic Text object's data-source list.
That makes this a protocol-selection fault, not a missing-driver fault. The panel software does ship a driver for the Do-more; the project simply is not using it. The distinction matters because the two faults have different fixes, the missing-driver case being the one covered in when the HMI software has no driver for your PLC.
Fix: point the project at the Do-more serial protocol #
- Open the project's PLC communication setup, the screen where the panel software defines the connected device and its protocol.
- Read the selected protocol. K-Sequence on a project that talks to a Do-more CPU is the fault.
- Change the selection to the Do-more serial option, listed for the Do-more as "Automation Direct Do-more serial".
- Save the project, then reopen the Dynamic Text object's data-source selection. The Do-more string locations, SS0 among them, are now offered.
- Download the corrected project to the panel and confirm the object shows live text before calling the job done.
Worked example: unblocking SS0 on a 3-inch C-More micro with K-Sequence selected #
Inputs:
- Operator panel: a 3-inch C-More micro, the station from the reported case.
- PLC: a Do-more CPU holding message text in string locations such as SS0.
- Panel software: C-More Micro Designer 3.51 build 00.03, the version reported to display Do-more strings once the protocol is correct.
- Protocol as found in the project: K-Sequence.
- Symptom: the Dynamic Text data source offers V-memory only, with no string data type.
Rule in words: the offered data types equal the memory the selected protocol addresses. K-Sequence offers no Do-more string memory; the Do-more serial protocol does.
The trace, written out:
- Protocol is K-Sequence, so the offered memory is V-memory only, the string data type is absent, SS0 cannot be selected, and Dynamic Text cannot display the PLC text.
- Change the protocol to the Do-more serial option, so the offered memory now includes Do-more strings, SS0 becomes selectable, the text object binds to it, and the project downloads.
Result: with the protocol corrected, the string became selectable and the display worked in programming and simulation at 3.51 build 00.03; the reported case closed on that single change.
Decision: for Dynamic Text limited to V-memory against a Do-more CPU, the protocol selection is the fix, and no conversion instruction belongs in the repair. If the corrected project still offers no strings, the remaining fault sits in the software version or the project's communication setup, not in the data type.
Why STR2INT is not the fix here #
STR2INT converts string characters into a numeric value. Converting SS0 into a V-memory number so a K-Sequence project can read it stacks a translation on top of the wrong driver: the panel still runs the wrong protocol, and the HMI now reads a number instead of the text. The reported fault needed no conversion at all. Reserve STR2INT for logic that genuinely needs the numeric value of characters, as a deliberate choice in the PLC program, never as a display workaround.
Prove it on the panel, not only in simulation #
The 3.51 build 00.03 success was in programming and simulation only; no hardware test was part of the report. Simulation proves the project and its tag binding; it does not exercise the serial link. After downloading to the panel, check its communication status, then compare the displayed text with the live contents of SS0: write a known test string under controlled conditions, confirm the panel shows exactly that text, then restore the operating value. If the panel and PLC exchange nothing at all after the download, treat it as a link fault and work through fixing HMI PLC communication timeout over serial rather than blaming the tag.
If the string still does not appear #
When the Do-more serial protocol is selected and saved but the browser still offers no strings, work this list in order:
- Confirm the protocol in the project that was downloaded to the panel, not just the copy open in the editor.
- Confirm the object is a text display object, not a numeric one, and that the tag it references is the string the PLC program actually writes.
- Read the panel's communication diagnostics; a link fault can blank live values even with a correct project.
- Check the design software version against the reported working one, 3.51 build 00.03.
Tag-addressing oddities inside C-More projects usually trace back to device and import configuration, the same class of cause as why C-More shows tag addresses you cannot set in Productivity. Stop there and take the project version, protocol and diagnostics to the vendor's support channel rather than adding conversion logic that masks the symptom.
Scaling numeric entry afterward #
The question that follows this repair is whether numeric entry fields scale on the micro panel as they do on the full-size panels. If the entry object in your project offers no scaling, the PLC does it: let the panel write the raw integer and scale it in ladder before use, the same arithmetic as how to scale a PLC integer into an HMI display value applied in reverse for entry.
Questions asked
Which PLCs is K-Sequence actually for?
K-Sequence is AutomationDirect's operator-interface protocol for the DirectLogic families — DL05, DL06, DL105, DL205, DL350 and DL405 — with the HMI acting as master on the link. It was never the native path into a Do-more CPU, so a project configured for it has no Do-more string memory to offer the tag browser.
Does the 3-inch panel size have anything to do with the fault?
No. The filtering happens in the project's protocol selection, not in the panel hardware, so any C-More micro project pointed at K-Sequence while the strings live in a Do-more CPU hides the string data type the same way. The fix is identical at every panel size: select the Do-more serial protocol and rebind the text object.
When is STR2INT the right instruction to use?
Use it when ladder logic needs the numeric value of characters — a recipe quantity or a number typed as text — not to make text displayable on a panel. In that case the conversion is a deliberate part of the PLC program, and the HMI reads the converted numeric location instead of the string.
Do-more serial is selected and the string still does not appear. What next?
Confirm the protocol in the project that was actually downloaded, not only the copy open in the editor, then recheck the object type and the tag the PLC program writes. If those are correct, read the panel's communication diagnostics and verify the design software version — 3.51 build 00.03 is the reported working one — before suspecting the data type.
Can a wrong protocol selection hide other tag types too?
Yes. A tag browser offers only the memory the selected protocol addresses, so a driver mismatch can hide counters, timers, bits or strings depending on the PLC. Treat a data-type symptom in an HMI as a driver-selection question first and verify the protocol before changing data types or adding conversion code.