IMDTouchKnowledge BaseShop main store

Troubleshooting

Fixing unsupported device errors when downloading an MER file

HMI and touchscreens Published 7 min read

Short answer

The unsupported device warning at MER creation is a compatibility fault, not a network fault: in the reported case a V32 controller with a V10 terminal was cleared by upgrading the terminal to V11. Then aim ME Transfer Utility at the HMI node, not the PLC, and keep the .mer in the standard Runtime folder.

On this page
  1. What does the unsupported device detected warning mean?
  2. Do the controller and HMI firmware versions have to match?
  3. Which node should the communication shortcut point at?
  4. Where should ME Transfer Utility send the file?
  5. Does it matter where the .mer file sits before transfer?
  6. How do I verify the whole chain is fixed?
  7. Questions asked

The warning that pops up when an MER file finishes building is a compatibility fault, not a network fault. In the installation that produced this chain of errors, a controller at V32 with a PanelView Plus 7 900W terminal at V10 was the unsupported pair, and upgrading the terminal to V11 cleared the warning at creation. The download that followed still failed until the transfer destination was the HMI node — 192.168.1.21 there — rather than the PLC, and the .mer sat in the standard Runtime folder instead of on an external drive. Work the faults in that order: warning at creation, version pairing, shortcut selection, transfer destination, file location, then verification.

What does the unsupported device detected warning mean? #

It is a compatibility message raised while the runtime file is being built — the configured driver, the selected terminal model or the controller pairing is outside the supported set — and it is fixed in the project settings, never by cabling.

The warning appears at the end of .mer creation, before a single byte moves to the terminal, and it comes from the project's communication configuration and runtime target. That is why no cable swap, reboot or IP change clears it. Rockwell Automation documents the same message in FactoryTalk View ME Studio V14 when a V13 MER file is created, which places the check inside the build, at version-pairing time.

The message can also come from the driver configuration. Documented instances of the warning state the supported set in the text itself — "Only the Ethernet driver and Serial DF1 drivers are supported" — so a classic or leftover driver entry in the browse tree triggers it even when your displays test fine.

Read the symptom before touching anything:

  • Warning at the end of .mer creation: check the driver set and the version pairing in the project.
  • Displays test fine in Studio but the terminal rejects the file: compare the Design and Runtime shortcuts, then the terminal target.
  • Transfer utility calls the destination an invalid device: check the destination selection, then the terminal model or Standard/Performance option.
  • The HMI node appears, then drops out of the browse: let the browse settle and confirm reachability.
  • Destination reachable, transfer still fails: move the .mer into the standard Runtime folder.

Do the controller and HMI firmware versions have to match? #

No — the two version counters are independent and never need to be equal: what must hold is that the terminal firmware and its runtime support the controller firmware, and in the reported case V11 on the terminal was the level that worked against a V32 controller.

Rockwell Automation publishes, for each FactoryTalk View release, the terminal firmware revisions the runtime supports and the controller pairings it validates; that release documentation is the requirement the warning enforces. The runtime version you select for the .mer is part of the same check, and a mismatch there is a separate fault covered in fixing an HMI MER runtime version mismatch.

Worked example, reported installation: the controller ran V32 and the terminal ran V10, and the warning appeared the moment .mer creation finished. Upgrading the terminal moved it one major level, 11 − 10 = 1, and the warning cleared with the numbers still far apart, 32 ≠ 11. Decision for that exact pairing: upgrade the terminal to V11 and leave the controller alone; for any other pairing, read the supported combinations off the release documentation before upgrading either side.

After any firmware change, delete and recreate the Design and Runtime shortcut paths, because routes retained from the previous configuration are a known source of repeat faults. If the upgrade utility refuses the newer firmware, that revision limit is its own problem, covered in when the firmware upgrade utility cannot upgrade an HMI terminal.

Which node should the communication shortcut point at? #

The controller itself, not its Ethernet port: expand the route past the network module, apply the shortcut to the controller node, then copy the Design shortcut to Runtime before the .mer is created.

A controller network port shows in the browse tree and can be selected as the path even though it is the wrong endpoint. In the reported case the fix was to apply the shortcut to the PLC three nodes up from the device initially selected. Build the configuration on the native FactoryTalk Linx Ethernet driver rather than a classic browse, because the warning's supported set is Ethernet and Serial DF1 only, and delete any stale driver entry under the backplane node before rebuilding.

Then copy the Design shortcut to Runtime and test one or two displays from Studio before creating the .mer. That test proves the design path from the engineering computer, not the terminal's runtime path, but it removes tag syntax and controller availability from the fault set.

Where should ME Transfer Utility send the file? #

At the HMI node — 192.168.1.21 in the reported installation — never at the PLC or its network port, because the utility moves the runtime file to the terminal, and the terminal then opens its own path to the controller.

The browse selection in the transfer utility is the file destination, not the PLC shortcut, so the two selections are separate jobs. If the utility rejects the destination as an invalid device, open the ME Runtime project settings inside Studio and confirm the configured terminal model is the physical unit and the Standard or Performance compile option matches its class.

Before browsing, ping the terminal from the transfer computer. If the ping fails, stop: fix the physical link, the interface addressing or the terminal power, because no project change repairs reachability. In the browse, click the Ethernet network icon and let the three indicator boxes blink for 10 to 15 seconds so devices previously detected but no longer visible drop off the list. If the terminal is visible but the download still will not start, the remaining causes are covered in why an HMI is detected but the project download fails.

Does it matter where the .mer file sits before transfer? #

Yes — a .mer launched from an external drive is a documented cause of transfer failure, so move the file into the standard Runtime folder on the engineering computer and retry before changing anything else in the project.

The utility resolves the transfer from the standard Runtime folder; an external drive or a mapped network path breaks that resolution, and moving one file is faster than any project rebuild. A flash-drive load on the terminal is a legitimate alternate transport when you can stop the running application — it changes how the file travels, not the compatibility checks that caused the warning. Rebooting the engineering computer and creating a fresh .mer are last steps, taken after the display test and the shortcut comparison, never before.

How do I verify the whole chain is fixed? #

The terminal loads the .mer with no unsupported-device or invalid-device message, starts the application, and reads and writes controller tags in both directions through a Runtime shortcut that ends at the controller node.

  1. Recreate the Design and Runtime shortcuts and confirm both end at the controller node, not its Ethernet port.
  2. Test one or two displays in Studio on the design path.
  3. Create the .mer at the runtime version the upgraded terminal accepts and store it in the standard Runtime folder.
  4. Ping the terminal, browse, wait out the 10 to 15 second settle, then select the HMI node.
  5. Transfer, and note the stage of any rejection — before transfer, during file movement, or at application load — because the stage names the remaining fault.
  6. On the terminal, exercise a read display and a write control, testing the write against a tag that cannot move the machine, or with the machine in a safe state.

Record the version pair with the project archive. If the file arrives and loads but the values stay dead, the fault has moved to the runtime path: why an MER download shows no live data on the HMI.

Questions asked

Can I edit the .mer file on the terminal to clear the error?

No. The .mer is the compiled runtime package, not the editable project. Correct the terminal model, the Standard or Performance selection and the communication shortcuts in FactoryTalk View Studio, create a new .mer, and transfer that file; nothing changed inside the terminal repairs the source project.

Is loading the .mer from a USB flash drive a valid alternative?

Yes, when you can stop the running application on the terminal and reach its load menu. The flash drive carries the same compiled file to the same place, so it saves transfer time but bypasses nothing: terminal and controller still have to be a supported pair or the application fails at load.

What should I record once the download works?

Write down the controller firmware version, the terminal firmware version, the terminal model, the Standard or Performance compile option, and the runtime version of the .mer. Keep that list with the project archive; the next firmware or studio upgrade then starts from a known working combination instead of a guess.

Why does the warning name a driver when my displays test fine?

Because the check reads the communication configuration as a whole, and a leftover driver entry in the browse tree can trigger it even while your live tag test passes on the design path. Delete the stale driver entry, rebuild both shortcuts on the supported Ethernet driver, and create the .mer again.

Keep reading

  • Troubleshooting

    Fixing a Vijeo Designer USB transfer filesystem path error

    The [HMIS] filesystem path error means the software resolved the wrong transfer destination, and the connection-abort line is only its consequence. Because the failure sits on one workstation, compare that PC's target selection, transfer method and installed version against a working one before touching the Runtime installer, and keep the two-to-three-times-slower USB-key route as a fallback.

    HMI and touchscreens

  • Troubleshooting

    Fixing an HMI Project Upload That Reports Communication Failed

    Treat a failed HMI project upload as three separate branches: the installer's parallel-port dongle driver message is a licensing fault, a "communication failed" report before any progress is a transfer-path mismatch, and a "file system error" after the panel answers is a storage or destination fault. Identify the layer from the message and the moment it appears, fix that layer only, and retest. A dongle fault never blocks the cable, and a successful ping never proves the transfer service is up.

    HMI and touchscreens

  • Troubleshooting

    Fixing PanelView 600 DH+ errors 208 and 685

    Errors 208 and 685 on a PanelView 600 talking to a ControlLogix 5555 over DH+ are address failures, not cable failures: the HMI requests PLC/SLC file numbers the controller has not mapped. Assign each requested file number a controller-scoped array long enough for every requested element and bit, and skip the BTR/BTW block-transfer logic - it does not fix HMI addressing.

    HMI and touchscreens