How-to
Displaying a Do-More String on a C-More EA9 Panel
Short answer
Use the C-More EA9 Dynamic Text object bound to the Do-More short-string tag, and give it a trigger tag that is on whenever the text should update: ST1, the always-on Do-More system bit, works immediately, while a page C-Bit set on at page open and off at page close in the Event Manager ties the display to the open screen.
On this page
- How do I display a Do-More string on a C-More EA9 panel?
- How do I bring the Do-More string tag into the C-more project?
- What do I enter for the string tag and the character count?
- Why does the Dynamic Text object need a trigger tag?
- Should the trigger be the ST1 always-on bit?
- How do I tie the trigger to the page with a C-Bit?
- How do I confirm the display works before calling it done?
- Questions asked
Use the C-More EA9 Dynamic Text object, bind it to the Do-More short-string tag, and give it a trigger tag that is on whenever the text should update: the object only reads the string while its trigger condition is active. ST1, the always-on Do-More system bit, is the quickest trigger that works. When the text should follow the open screen instead, drive a page C-Bit from the Event Manager - on at page open, off at page close - and use that bit as the trigger. Both are correct; the C-Bit is the better permanent choice because it also tells PLC logic which page the operator has open.
How do I display a Do-More string on a C-More EA9 panel? #
Use the Dynamic Text object: it exists for this exact job, displaying text retrieved from a tag name assigned to PLC registers that hold ASCII data. A static text object shows characters typed into the project, and a numeric display is the wrong object for a string.
The question behind this procedure was exactly that pairing - a Do-More controller, a short string, and a 6-inch EA9 panel - and none of the steps depend on screen size. The short version:
- Bring the string tag into the C-more tag database.
- Place a Dynamic Text object and bind the string tag with its character count.
- Choose the trigger tag: ST1 to prove the binding, a page C-Bit to finish the job.
- Download and run the four-step page test.
How do I bring the Do-More string tag into the C-more project? #
Create the string in Do-more Designer as a String Structure HEAP Item - the documented example is named Line1BarCode - and add that tag name to the C-more tag database, so the panel addresses the string by name instead of by hand-computed registers.
Do-more symbolic addressing is what makes this possible: the string structure lives as a HEAP Item in the controller, and the C-more documentation walks through adding a tag name for exactly that Line1BarCode string. When you add the tag, the data type on the panel side must match the controller side. The rule is general - a D integer defined with BCD tag type in the PLC must map to a BCD tag in the HMI, not to a signed or unsigned integer - and it holds for strings: a short string in SS memory maps to a string tag, never a numeric one. The same both-sides checking is what exposes word order inside 32-bit values, a separate mapping problem covered in how to swap words on a C-More 32-bit Modbus tag.
What do I enter for the string tag and the character count? #
Assign the tag that stores the first two characters of the string, and set the tag length to the total number of characters - the length is a character count, not a register count, and it includes spaces and separators.
C-more packs ASCII at two characters per 16-bit register, which is why the tag's base address is documented as holding the first two characters of the string. Worked example: the fault text PUMP FAULT is 10 characters - P, U, M, P, space, F, A, U, L, T. At two characters per register, 10 characters ÷ 2 characters per register = 5 registers of controller memory. The tag length field gets 10, and the object gets sized to show 10 characters.
If the text is clipped, the length setting or the object width is wrong; fix those before touching the trigger. And when characters go missing from the front of the string while the rest displays, that is a storage-offset fault rather than a trigger fault - the failure mode walked through in C-more text entry losing first characters in PLC memory.
Why does the Dynamic Text object need a trigger tag? #
Because the trigger is a separate control input to the object, not the string value: the object reads the PLC string only while the trigger condition is active, so a correctly selected string can sit on the panel and never appear.
This is the step that makes a good binding look broken. Monitor the configured trigger bit in the controller while the page is open, then branch on what you see:
- Trigger off: the object never receives its active condition. Prove the path with a known-active bit such as ST1, or build the page C-Bit in the next section.
- Trigger on, text absent or wrong: the fault is in the tag binding, the string contents, or panel-to-controller communication. Stop adjusting trigger logic that is already active.
Should the trigger be the ST1 always-on bit? #
Yes - ST1 works and is the right first move: the Do-More ST1 system bit is always on, so the trigger condition is permanently active and the object reads the string continuously; its one limitation is that it carries no information about which page is open.
Use ST1 on the first download to prove the binding, and keep it if continuous availability is what you want - that is a complete running configuration, not a workaround. Move to the page C-Bit when the text belongs to one screen, or when controller logic should know which page the operator has open. The decision in one line: ST1 for the simplest working display today, the C-Bit for the finished page-aware display.
How do I tie the trigger to the page with a C-Bit? #
Give the page its own C-Bit, turn that bit on when the page opens and off when the page closes - both configured in the Event Manager - and select the same bit as the Dynamic Text trigger, so the string is read exactly while that screen is visible.
- Assign one distinct C-Bit to the page that holds the Dynamic Text object.
- In the Event Manager, add the page-open event for that page with an action that sets the C-Bit on.
- Add the page-close event for the same page with an action that sets the C-Bit off.
- Open the Dynamic Text object's trigger configuration and select that C-Bit as the trigger tag.
- Repeat with a fresh bit for each page that needs its own trigger.
The bit number written into the Event Manager action and the bit selected as the trigger tag must be the same C-Bit; a mismatch shows up as a bit that toggles in the controller while the text stays dead. Then verify the events actually change the bit during navigation, because a configured bit that never changes behaves exactly like a permanently off - or permanently on - trigger.
How do I confirm the display works before calling it done? #
Run the panel and watch the bit and the text together: on page open the C-Bit goes on and the string appears, on navigation away it goes off, on return both respond again, and a changed PLC value shows up as changed text.
- Write a known value into the Do-More string, open the page, and confirm the C-Bit turns on and the text matches.
- Navigate to another page and confirm the C-Bit turns off.
- Return to the page and confirm the bit and the text respond again.
- Change the controller string to a second known value while the page is open, and confirm the text follows.
If the display worked with ST1 but fails with the page bit, put ST1 back temporarily to recover the known-good behavior, then repair the Event Manager events separately. One safety note belongs here: if this string carries alarm or status wording, finish all four steps before leaving the display in service, because an operator acting on stale screen text is the hazard this test exists to prevent. With the four steps passing, make the C-Bit the permanent trigger and keep ST1 as your fallback proof for the next time a display stops updating.
Questions asked
Can the live string go on a push button instead of a text box?
No. Native C-More EA9 objects do not support dynamic text on push buttons, so the button caption cannot be driven by the PLC string. Place the Dynamic Text object next to the button as its own element on the page; that is the supported way to show the live value at the control.
The text shows wrong characters instead of nothing - is that the trigger?
The binding, not the trigger. The tag's base address holds the first two characters of the string, so a start point that is off by one register shifts every character pair and turns readable text into garbage. Re-enter the tag against the string's true base, confirm the length equals the full character count, and leave the trigger alone - it was doing its job.
Can several pages share one C-Bit trigger?
Yes, when the pages are deliberately related: a detail or popup page that belongs with its base page can share the base page's bit. Give every independent page its own bit, because separate bits are also the only way controller logic can tell which page the operator has open.
Does an odd character count change the register math?
Yes, round up. A 9-character string still needs whole registers: 9 characters divided by 2 characters per register gives 4.5, so it occupies 5 registers with the second position of the last register unused. The tag length stays at the true count of 9 - round the register math, never the character count.