How-to
How to Display Dynamic PLC Messages on a PanelView 800
Short answer
Write the selected label into one MicroLogix 1100 string element sized to the longest configured message, map one string-type HMI tag to that element in Connected Components Workbench, and assign that tag to the String Display object's Read Tag. Priority is a ladder decision: when several rungs write the same element in one scan, the last executed write is what the terminal shows.
On this page
Put the words in the PLC, not on the screen. Write whichever label applies into one string element in the MicroLogix 1100, ST9:0 in this example, create one string-type tag in Connected Components Workbench pointed at that element, and assign that tag to the String Display object's Read Tag. The panel then shows whatever the controller last wrote, which is what you want with close to 30 command buttons: one display object, one tag, and a message table that lives in the ladder. The rule that decides everything else: when several rungs write that element in the same scan, the last executed write is what the terminal shows, so message priority is a ladder decision.
Choose one string element over a multistate indicator #
A multistate indicator displays text selected by the value of one integer tag: two states for open and closed, four if you add opening and closing. That is the right object when a single encoded value already describes the machine. Here, close to 30 independent command bits would first have to be compressed into one integer in the ladder, and every new button would add a state row in the HMI project as well. One string element plus a String Display is the smaller system: the panel side never grows, and each new label costs one entry in a controller message table.
Your buttons already cross the boundary in the write direction under the rules for toggling PLC BOOLs from HMI screens across the display boundary; the message simply crosses back in the read direction. The same one-tag shape carries other controller-text jobs, such as displaying the 1756-DNB StatusDisplay as text on an HMI.
Before writing rungs, decide what the message reports: the last accepted command, the currently active command, or confirmed machine state. A pressed button labeled for closing a door proves an operator asked, not that the door closed, so never present a request as a confirmed state on a screen someone uses to judge safe access.
Size the element from the longest label #
The element is sized by your longest label, and that same number sizes the display object, so measure it once, now.
- Write the message table first: every accepted button or state paired with its exact operator text, all thirty of them.
- Count the characters of the longest label, spaces included.
- Set the display element, ST9:0 in this example, to hold at least that count, and record the count for the object sizing later.
- Choose the no-selection behavior: retain the last label, show a neutral text, or clear the string. For a last-command display, retain.
Worked example from a thirty-label list: "DOOR IS OPEN" is 4 + 1 + 2 + 1 + 4 = 12 characters, "DOOR IS CLOSED" is 4 + 1 + 2 + 1 + 6 = 14 characters, and a longest label such as "HYDRAULIC PRESSURE LOW" is 8 + 1 + 8 + 1 + 3 = 22 characters. The element is sized for 22 characters, not for the 12-character door text, and if the label list will grow, add that margin now. The absolute ceiling is the string element length of the MicroLogix 1100, defined in its user documentation under string (ST) data files, publication 1763-RM001; a label longer than that ceiling gets shortened or split, never silently truncated.
Let scan order do the arbitration on purpose #
The MicroLogix solves rungs top to bottom, and every executed write to the display element replaces what the rung above it wrote. When two rungs fire in the same scan, the lower one wins, and the String Display has no part in the choice: it shows whatever the element holds. So build the priority you want, with the messages that must win at the bottom of the message logic. If a pump label rung and a door label rung are both true in one scan and the door rung sits lower, the panel shows the door label; swap the rungs and the panel shows the pump label.
- Confirm every trigger address against the actual project. Notes showing a door-open bit as B3:0/2 and a door-close bit as B3:03 do not identify the second bit: it means either B3:0/3, bit 3 of word 0, or B3:3, word 3, and logic built on the guessed one labels the wrong event.
- Store the labels once in a label table in the controller, positions 0 through 29, in a file of their own so the display copy never targets its own source table.
- For a last-command display, trigger on the command's transition with a one-shot contact rather than the held bit, write the label once, and let it stand until the next accepted command.
- For a live-state display, evaluate the state bits every scan and write the current state's label unconditionally.
- Move whole string elements, never characters. The documented MicroLogix 1100 pattern loads the chosen element number into S:24 from an integer such as N7:4 and copies the indexed source, shown as #ST9:0, into the display element. With the table indexed that way, one copy rung serves all thirty labels, and priority moves into the logic that feeds the index: when two conditions are true, that logic must pick one.
- Follow one pattern. Mixing event-written and state-written labels in one element without a clearing rule produces messages neither pattern would show on its own.
Map the tag and the object in Connected Components Workbench #
The panel side is one tag and one object.
- In the CCW Project Explorer, expand the PanelView 800 terminal node and double-click Tags.
- Create an HMI tag with string data type whose controller address is the display element, ST9:0, on the existing MicroLogix 1100 Ethernet connection.
- Place a String Display object on the message screen.
- Assign the string tag to the object's Read Tag.
- Size the object's visible area for the longest label, the 22-character count from the sizing step, at the font you will actually ship.
- Validate the project, fix every address, type and connection fault it reports, then download. Validation is a consistency check, not a communications test: a configuration of exactly this shape validates even with nothing attached to prove the live link.
One import trap: tags brought in from a Micro800 project can arrive split into a length address (.Len) and per-character addresses (.Data/x). The Read Tag takes the whole string tag, never those parts.
Test the path in one fixed order #
- Go online with the MicroLogix and press one button; confirm its command bit changes, B3:0/2 for the door-open button.
- Inspect the display element: it must hold the complete expected text before the panel is touched.
- Open the message screen: the String Display must match the element exactly.
- Send a long label, then a short one; check for clipped text and for characters left over from the longer message.
- Where the process allows it, make two conditions true together: the lower rung's label must be the one shown.
- Navigate away and back: the object must show the element's current value, not the value from the previous visit.
If the element is right and the panel is wrong, stop editing ladder: trace the controller connection, the tag address, the tag type and the Read Tag assignment, in that order.
Symptoms that point at one specific layer #
Each symptom below points at exactly one layer of the path.
- The element never changes: the selection logic, not the panel.
- The element is right, the panel is stale or empty: connection, tag address, tag type or Read Tag assignment.
- A short label carries tail characters from the previous long one: something writes characters without the length; replace it with the whole-element copy.
- The message names actions the machine did not perform: the text is driven by requests; drive it from feedback instead.
- One condition always beats the rest regardless of importance: scan order is arbitrating silently; reorder the rungs or the index selection on purpose.
Questions asked
Would a multistate indicator be simpler for thirty messages?
No, not for thirty independent command bits. A multistate indicator maps one integer's value to text, so the ladder would first have to compress all those bits into a single number, and every new button would also need a new state entry in the HMI project. The string route keeps the whole message table in the controller: one string element, one tag, one display object, and one more table entry per button.
Why does only one message appear when two buttons are pressed together?
The MicroLogix executes rungs in order, and each executed write overwrites the same string element, so the last rung executed decides what the panel shows. If a door message must outrank a pump message, place the door write lower in the program. With an indexed copy serving all labels, the same choice moves into the logic that selects the index. The display itself has no priority function.
How do I keep an old, longer message out of a shorter one?
Copy whole string elements, data and length together, instead of writing characters. A whole-element copy of a 12-character label completely replaces a 22-character one. If shorter messages still carry tail characters from longer ones at the panel, something in the logic is touching character storage without updating the length; find that write and replace it with the element copy.
How long can one label be on this setup?
Your own message list sets the working number: the longest configured label, 22 characters in the worked example, not the 12-character door text. The hard limit above that is the controller's documented string element length, described in the MicroLogix 1100 user documentation under string data files, publication 1763-RM001. If a future label would exceed it, shorten the label or split the message rather than truncating it.
Can a second screen show the same message?
Yes. Put a String Display object on the second screen and assign the same string tag to its Read Tag. Both objects read the same controller element, so a screen opened later shows the current message, not a stale one. Size each object for the longest label, because the visible area belongs to each object, not to the shared tag.