IMDTouchKnowledge BaseShop main store

Troubleshooting

Why Vijeo Designer direct IO variables show faded

HMI and touchscreens Published 7 min read

Short answer

Faded, dotted %I and %Q values on a link where %M and %MW still read mean the v6.2 file upgrade broke the variable records' equipment and address linkage, not the communication path. Re-link and retype one I/O tag against the M221 equipment, fix the rest through the exported variable list, and rebuild the equipment entry only if the retyped tag still fades.

On this page
  1. What a faded, dotted value rules out
  2. Fix one %I tag by hand
  3. Re-linking the remaining 79 tags on an 80-tag list
  4. Rebuild the equipment entry when retyping fails
  5. Pitfalls that repeat on converted projects
  6. Acceptance test on the panel
  7. Questions asked

On a Modicon M221 in Machine Expert v1.2 SP1 with an HMIGTO6310/6315 panel on Vijeo Designer v6.2, an upgraded legacy project can show every direct I/O variable faded and dotted while the %M and %MW tags read normally. That split is the answer: the communication path, the equipment definition and the driver are alive, because memory-addressed tags still poll. The file upgrade broke how the converted variable records carry their equipment and address linkage, and no communication error is raised because nothing at link level is wrong. Fix one %I tag by hand, push the repair through the exported variable list, and rebuild the equipment entry only if the retyped tag still fades. Mirroring every I/O point into %M and %MW does work — the live memory tags prove it — but it turns a conversion defect into permanent PLC code; treat it as the last resort.

What a faded, dotted value rules out #

A faded, dotted value with no communication-error banner means the runtime never received a valid read for that one tag. A dead link or a protocol mismatch fails every tag at once, the %M and %MW ones included — and those still read, so the link, the equipment entry and the driver are all alive. A failure that splits exactly along address class leaves four mechanisms, in the order conversion upgrades usually produce them:

  • The upgrade rewrote the variable's address string or address type, and the driver rejects that address form.
  • The variable lost its link to the equipment and fell back to an internal data source, so nothing polls it at all.
  • The equipment entry now runs a driver revision that exposes the M221 memory areas but not the I/O image the way the old project addressed it.
  • The tag list was built against a symbol set the current M221 application no longer carries.

Importing the variables back changed nothing, and that points away from one corrupted record: importing the same file recreates the same address strings and the same equipment references. The shared fields — address form and equipment name — are where this fault lives.

Fix one %I tag by hand #

One tag proves which of the four mechanisms you have, and it sets the template every other tag gets copied from. Work it in this order:

  1. Back up the original legacy project file and the converted v6.2 file under separate names, and confirm both still open. If the legacy source is already lost and only the panel runtime survives, recovering an HMI program when the source file is lost is the job to settle first.
  2. Open one faded %I variable and check its data source: it must be the external equipment, not internal. If it reads internal, the upgrade dropped the link — point the variable at the M221 equipment entry and check the panel; a tag that comes alive there was the whole fault.
  3. Compare the variable against a working %M or %MW tag on three fields: the equipment name, the address notation and the data type the point needs. The I/O tag must reference the same equipment name the working tag uses.
  4. Retype the address by hand in the exact notation the Machine Expert project uses for that point, not the notation the converted record carries.
  5. Download to the panel and toggle the physical point. The tag counts as repaired only when its value follows the field state.

Two outcomes: a hand-retyped tag that reads live convicts the address strings the conversion produced, and the bulk edit in the next section is safe. A tag that still fades after a verified download convicts the equipment entry instead — skip the bulk edit and rebuild that entry first.

Re-linking the remaining 79 tags on an 80-tag list #

Inputs, with their sources: 80 faded %I and %Q tags (the reported case counts 80-plus variables needing a rewrite); 1 template tag already re-linked and proven live by hand; the untouched %M and %MW tags as the control group; Vijeo Designer v6.2 on an HMIGTO6310/6315 with the M221 on Machine Expert v1.2 SP1.

The rule in words: every direct I/O variable must carry three linkages at once — data source set to external, equipment set to the M221 entry the working tags use, and an address written in the notation the Machine Expert project uses. A record missing any one of the three is never polled, and the runtime renders it faded and dotted. The template tag proves which notation and which equipment name the other 79 need.

The arithmetic: right-click the Variables grid and use Export variables to write the list out. The file holds 80 rows; one is already fixed by hand, so the edit covers 80 - 1 = 79 rows, and the PLC needs 0 edits. Correct the address and equipment columns of the 79 faded rows against the template row, leave the memory rows untouched, import the file and confirm no rows are rejected — the same discipline as importing a PLC tag CSV into an existing HMI tag database. Download and test against field state. Total cost: 79 spreadsheet edits and one download. The mirror alternative on the same list costs 80 new %M or %MW assignments in the PLC plus 80 HMI address retargets — 160 edits — and every future I/O change repeats both halves.

The result: all 80 direct I/O tags read from the HMI side with zero edits to the M221 program, and the memory tags still read, which proves the equipment entry was never disturbed.

The decision: run this path first, and its threshold is the one-tag test upstream of it. If the hand-retyped tag still fades after a verified download, do not edit 79 rows on a broken premise — the defect is in the equipment entry, and that rebuild comes before any bulk edit. The mirror stays a last resort: it works, at 160 edits plus a scan-delayed copy in the PLC, against 79 edits and none.

Rebuild the equipment entry when retyping fails #

Reach for this only when the hand-retyped tag stays faded, or when the bulk import re-fades tags that had tested live.

  1. Record what the existing M221 equipment entry uses: protocol, driver, address or serial parameters, station settings.
  2. Create a new equipment entry with the driver Vijeo Designer v6.2 selects for the M221 and enter the same communication parameters. Leave the old entry in place for now.
  3. Re-point one I/O variable and one memory variable to the new entry and download. Both must go live. If only the memory tag comes alive, the driver you picked is not exposing the I/O image the way your addresses are written — check the driver's documented address ranges for the M221 and use the notation it lists.
  4. Re-point the remaining variables in bulk through the exported list, then delete the old entry only after every tag reads.

One M221-side check belongs here: a download from Machine Expert can rewrite the controller's communication settings, so confirm the port, address and protocol enablement the HMI relies on are unchanged. A changed setting fades memory tags too, so as long as the failure stays split along address class, the fault is in the HMI records — this check is for the case where that split disappears.

Pitfalls that repeat on converted projects #

  • Re-importing the same file recreates the same address strings and equipment references; only fields you actually change alter the result.
  • A tag created from a PLC symbol export can carry a different address form than a hand-entered direct address. Test both forms on one tag before editing 80.
  • An address for a module or channel absent from the Machine Expert I/O configuration never returns data, no matter how the HMI record is written.
  • The simulator can show tags faded simply because no source is present. Final validation happens on the panel with the PLC in RUN.
  • Memory mirrors read correctly and hide the defect, doubling the maintenance burden on every future I/O change.

Acceptance test on the panel #

  1. With the PLC in RUN, toggle each physical input and confirm the matching %I tag changes state on the panel within the normal refresh time.
  2. Command each output through a controlled test and confirm the %Q tag follows the actual output state; do this only with the machine in a state where no unexpected motion can occur.
  3. Confirm no tag on any screen is faded or dotted and that the untouched %M and %MW tags read as before — the control group is your proof the equipment entry survived the work.

The v6.2 upgrade that broke these records is exactly the step where validating HMI variables during a software migration earns its keep, so run that kind of tag-list check before the panel goes back into production.

Questions asked

Can an old Vijeo Designer project be converted to Vijeo Designer Basic instead?

No. Schneider Electric documents that Vijeo Designer and Vijeo Designer Basic are not fully compatible and that a project cannot be converted directly from one to the other. Staying on Vijeo Designer and repairing the upgraded project's variable linkage, as described here, is the supported path; moving to Basic means rebuilding the application rather than converting it.

Why do REAL variables show scrambled numbers instead of fading?

Different fault. REAL data that displays incorrectly, rather than fading, is documented as a word order problem: Vijeo Designer can present the two words of a REAL in the wrong order when reading from certain controllers such as an M340, so the digits scramble while the link itself works. Set the word order correctly for those variables; it needs no equipment re-linking.

Does the M221 program need changes to fix the faded I/O tags?

Not for the repair described here: the re-link and the equipment rebuild change only HMI variable records, and the controller keeps its addresses and logic. The only fix that touches the PLC is the memory-mirror fallback, which adds 80-plus new %M or %MW assignments plus an HMI retarget for each; keep it last, because every future I/O edit then repeats both halves.

Can indirect addressing variables reduce how many I/O records the project carries?

Yes, as a design choice made after the repair. An indirect addressing variable points at a base PLC address plus an offset, so one variable can serve a bank of similar addresses instead of one record per point. It does not repair the broken linkage in an upgraded project: fix the records first, then use indirect addressing where a bank of identical points justifies it.

What should I do if a working %M or %MW tag fades during the repair?

Treat it as evidence you touched the equipment or driver, not a variable: a record-level edit cannot fade a memory tag whose link is intact. Stop editing, restore the backed-up converted project file and restart from the one-tag test. That control group is why the working memory tags stay untouched until every I/O tag reads.

Keep reading

  • How-to

    Activating the XBTOT Target Family in Vijeo Designer 6.2

    Enter upgrade code VJDHTGTOPV62M in the full Vijeo Designer 6.2 edition under Help > About > License > Upgrade, restart the software, and XBT OT appears in the new-project target list. Vijeo Designer Lite 1.2 or 1.3 cannot list or unlock the family.

    HMI and touchscreens

  • Troubleshooting

    E-Designer to Exter Project Conversion and Transfer Path

    E-Designer cannot download to an Exter T150: the terminal accepts applications only from Information Designer. Convert the .mpa project through the maker's conversion service or a licensed Information Designer seat, verify the target, driver and objects, then export a .Dat project transfer file to USB or CF card that the T150 loads automatically. Replace the terminal with current hardware only when the terminal itself is the failing part.

    HMI and touchscreens

  • Troubleshooting

    E200 HMI recovery when the supplied file is a GOT project

    The E200 is an E-series terminal programmed with E-Designer, and it accepts only a native E-Designer project file with the .MPA extension. GT Designer3 opens GOT projects and can convert E-Designer projects toward the GOT, never the reverse, so recovery means obtaining the original .MPA from the machine builder or a backup, then downloading it over the documented serial cable.

    HMI and touchscreens