IMDTouchKnowledge BaseShop main store

Troubleshooting

Why EasyBuilder Asks for a Tag CSV for a Mitsubishi Q PLC

HMI and touchscreens Published 4 min read

Short answer

EasyBuilder asks for a tag CSV because the selected Mitsubishi driver is the label-based one, and GX Developer cannot export labels in that format - its converter refuses label-based projects. Switch the project to the Q-series Ethernet driver and address D, X and Y devices directly, with no CSV at all. If you want symbolic names, open the Q project in GX Works2 and export the label CSV from there.

On this page
  1. Why the prompt appears
  2. Why GX Developer will not export the file
  3. Fix A: switch to device addressing
  4. Fix B: export the label CSV from GX Works2
  5. Prove it with one device read
  6. Mistakes that waste time
  7. Questions asked

EasyBuilder asks for a tag CSV because the Mitsubishi driver selected in the project is the label-based one - not because a Q-series PLC needs a tag file to communicate. The Q-series Ethernet driver for the same CPU reads D, X and Y devices directly and never prompts for a CSV. GX Developer cannot produce the file: its converter refuses to open a label-based project, and a project with no labels defined has nothing to export. Commit to one of two paths: switch the project to the device-address driver and map devices directly - the fast fix - or open the Q project in GX Works2, define the labels, and export the label CSV from there.

Why the prompt appears #

The Mitsubishi support in the HMI software has two addressing paths. A label-based driver imports symbolic names from a CSV tag file before it can reference anything; a device-address driver references the PLC's native memory - D registers, X inputs, Y outputs - by address, with no import step. The prompt tells you the first one is active.

It is not evidence that labels are mandatory for the CPU. Talking to a Q03UDECPU over Ethernet works on both paths, and only the naming of the data differs. Check the device selection in the project, note the exact driver and its addressing mode, and only then decide whether any export is needed.

Why GX Developer will not export the file #

Two separate facts block the export.

The GX Developer export route runs through GX Converter and the menu item [Export to TEXT, CSV format file], which covers ladder programs and device comments. The GX Converter Version 1 operating manual is blunt: "GX Converter cannot be started up with projects using labels." A label-based Q project therefore has no GX Developer route to a CSV of any kind, tag file or otherwise.

The other blocker is simpler: labels may never have been created. Label use in GX Developer starts with the "Select Label" step; if it was skipped, the project holds device references only and there is no label list to export. Exporting labels to CSV is a GX Works2 capability, which is the practical reason to move the project when symbolic names are what you want.

Fix A: switch to device addressing #

  1. In the project's device settings, replace the label-based Mitsubishi selection with the Q-series Ethernet driver for this CPU family.
  2. Confirm the driver's addressing mode is device addresses, not label import.
  3. Enter the PLC IP address and communication settings exactly as configured on the CPU side - read them from the PLC parameter area of the engineering tool, not from memory.
  4. Map each HMI object to the D, X or Y device the ladder already uses.
  5. Compile and download; no tag-import step should appear anywhere in the build.

For a machine whose program is already written against device numbers, this is the whole fix.

Fix B: export the label CSV from GX Works2 #

  1. Open the Q project in GX Works2.
  2. Define the labels for the data the HMI needs, including the data types.
  3. Export the labels to CSV.
  4. Give that file to the tag import where the software asks for it, then check that a few labels resolve to the devices you expect.

Choose this path when you actually want symbolic names on the HMI - for screens maintained by people who do not read the ladder. It is more setup than Fix A and adds a file that must be kept in sync whenever the labels change.

Prove it with one device read #

Before mapping the rest of the screens, test one known device and watch its value in the PLC programming tool at the same time.

Worked example: the PLC holds -1 in D100 as a 16-bit signed integer, and the HMI numeric object mapped to D100 shows 65,535. A 16-bit word holds 0 to 65,535 unsigned and -32,768 to +32,767 signed. The bit pattern 0xFFFF reads 65,535 unsigned; read as signed, 65,535 - 65,536 = -1. The link, the driver and the address are all correct - the object's format is unsigned. Set it to signed word and the display reads -1.

When you move on to writes, use a device that drives nothing on a running machine, because a test value written to an output device can actuate hardware. If the corrected value still needs engineering units, do the conversion at the object - see scaling a PLC integer into an HMI display value.

Mistakes that waste time #

  • Renaming a device-comment export or hand-typing the columns. The importer checks the file's structure, so a wrong layout fails whatever the extension says.
  • Migrating the PLC project before checking whether the driver offers device addressing at all.
  • Troubleshooting the network by editing tags. A tag or format error shows as a wrong value; a network fault shows as no response. Fix the first, then the second - diagnosing intermittent HMI to PLC Ethernet comms hangs covers the second kind.
  • Building screens on a guessed driver. If the list offers no Q-series Ethernet option for the exact CPU, stop and confirm support in the software's documentation first.

Questions asked

Where do the Q03UDECPU Ethernet settings live on the PLC side?

In the parameter area of the engineering tool. For a CPU's own Ethernet port the settings are module parameters of the CPU; a separate Ethernet module keeps its IP and communication settings in its own module parameter area instead. Set them, write to the PLC, and restart as the tool directs before testing the HMI link.

Can a device comment export be renamed to a .csv tag file?

No. Device comments annotate devices inside the project; a label CSV names data for the HMI importer, and the two files have different columns. The importer checks structure, so a renamed comment export fails whatever its extension says.

Does switching to GX Works2 change the ladder in the Q project?

No. GX Works2 opens the same Q project and leaves the ladder and device references as they are; you add the labels on top and export them. The HMI keeps reading the same D, X and Y devices whether it reaches them by address or by label.

Is the tag CSV needed for the HMI to read X and Y devices?

No. On the device-address driver, X and Y are referenced directly, the same as D. Watch the object type: X and Y are single bits, so lamp objects suit them, while a numeric object expecting a word belongs on a D register.

Keep reading

  • How-to

    Testing HMI Simulation Against a Live PLC

    A standalone HMI simulator proves screens and navigation, not communications. Test against a live controller only through a documented online-simulation mode or a physical panel, and verify every read at two data states and every write at the controller before release.

    HMI and touchscreens

  • Troubleshooting

    Why HMI Indicators Stay Off Over Modbus RTU Polling

    Indicators on internal tags animate from HMI memory with no serial traffic; an indicator bound to a PLC tag needs a completed Modbus RTU read of the right address in the right data area. Confirm the PLC bit changes, then read the request and response, then fix the address at one known point.

    HMI and touchscreens

  • Selection guide

    Selecting a Modbus TCP HMI Panel for an Existing Controller

    A replacement HMI qualifies when its Modbus TCP client driver reproduces the working panel's tag map exactly: data area, raw address, word order and write behavior. A connection that polls proves reachability, not correctness — prove one known tag and one supervised write before rebuilding the screens.

    HMI and touchscreens