How-to
How to Create and Export GX Works3 Labels for a C-More HMI
Short answer
Define the name as a global label in the GX Works3 label editor and give it a device target such as Y5; typing the name on a coil only creates an untargeted entry. Export the global label CSV, then hand-map each row into the C-More tag import template, because the two CSV schemas do not match. Separately, confirm the C-More Mitsubishi driver covers the FX5 before trusting any serial retry.
On this page
- Why the HMI cannot read your ladder
- Create the label in the Global label table
- Export the Global label CSV
- Convert the export into the C-More tag import format
- Worked example: mapping buzzer to Y5 on an FX5 with C-More
- Confirm the C-More driver covers the FX5 before any retry
- When the serial link still will not pass
- Questions asked
GX Works3 gives the HMI nothing from your ladder by itself. You create the names in the Global label table, give each one a device target such as Y5, export the Global labels to CSV, and then rebuild those rows by hand in the C-More tag import template — the two CSV formats do not match, so a direct import fails with a missing-tag-name error. That part fixes your tag database. Whether the panel then talks to the PLC is a separate driver question, and on an FX5 it is open: the C-More FX Series driver lineage covers FX1, FX2 and FX3, C-More support describes RS-422 as the interface it backs with the FX5, and Modbus is the alternative to prove.
Why the HMI cannot read your ladder #
A comment on a contact is documentation that never leaves the project. A label is different: it is a named row in a label table bound to a device, and only bound names with targets survive an export the HMI can use. GX Works3 keeps two tables — Global labels, visible project-wide, and Local labels, scoped to a single program. Every name the panel needs goes in the Global table.
The trap that costs an afternoon: typing a new name directly on a contact or coil can create the table entry, with a warning, but leaves the target empty. Until you open the table and assign the device, the name is not bound and exports without an address. Once the target is set, the label appears over the element in a different color — that is your visual confirmation the binding exists.
Create the label in the Global label table #
- Open the Global label table before drawing more ladder. Working table-first is the supported flow; retrofitting names onto an imported ladder is what left both lists unpopulated.
- Add a row and type the name with no spaces — buzzer, not buzzer output.
- Assign the device target in the target column — Y5 for the warning buzzer coil.
- Use that label in the rung instead of the raw device. If a name was created from the ladder first, open the table now and fill in its target.
- Repeat for every device the panel must see, keeping all of them in the Global table.
Export the Global label CSV #
- With every HMI-facing row carrying both a name and a target, export the Global labels to a CSV from the label editor.
- Open the file and check each row: name present, target present. A row without a target contributes nothing to the panel — fix it in the table or drop it from the export.
- Count the data rows. That count is your acceptance number for the import on the C-More side.
Convert the export into the C-More tag import format #
The GX Works3 export and the C-More tag format are different schemas: the columns do not line up, and a file copied straight across fails with a missing-tag-name error because the name lands outside the column the import reads. Build the file in the panel's own shape:
- In the C-more programming software, export the current tag database — even a nearly empty one — and keep its header row as the template.
- Map one label per row: label name into the tag-name column, device target into the address column in the format the selected Mitsubishi driver documents for that device.
- Save as comma-delimited .csv or .xls. Saving from Excel means the UNICODE file format with a .csv extension, per the C-more import help.
- Import through File → Import → Tag Name Database, and compare the reported tag count with the row count from your export. Equal is clean; short means a row is misaligned — rebuild that row against the template.
- Treat a missing-tag-name message as an empty or shifted name column. It is a file defect, not a PLC problem.
If the panel already holds tags, merge behavior matters as much as format; the rules for importing a PLC tag CSV into an existing HMI tag database follow the same template discipline.
Worked example: mapping buzzer to Y5 on an FX5 with C-More #
Inputs, each with its source:
- Label name: buzzer — the name from your ladder, no spaces.
- Device target: Y5 — the output coil driving the warning buzzer, from your I/O assignment.
- Export file: Global label CSV out of GX Works3, one row.
- Target file: C-More tag import template, built from the panel software's own tag export.
- Transport: the installed 4-wire RS-422 link between FX5 and C-More.
Rule in words: one Global label with a device target becomes exactly one C-More tag row — the label name becomes the tag name, and the device target becomes the address in the selected driver's documented notation. Nothing else in the CSV carries over.
Arithmetic, written out:
- Global labels defined with targets: 1
- Data rows in the exported CSV: 1
- Data rows in the import file: 1, plus the template header row
- Tags the C-More import must report: 1
So 1 exported = 1 mapped = 1 imported, and the panel's reported count must read exactly 1.
Result: one C-More tag named buzzer holding Y5's address under the selected Mitsubishi driver.
Decision: the tag count after import must equal the label rows exported — here, 1 = 1. Any shortfall, or a missing-tag-name error, is a misaligned row in the file; fix the row and re-import before touching the cable. Then point a lamp object at buzzer: when the link passes, the lamp follows Y5. If the tag is clean and the lamp stays dark, the defect is the driver or the link, never the CSV.
One safety note: a lamp mirroring the buzzer is indication only — alarm annunciation and any shutdown stay hardwired to the PLC outputs, never routed through the HMI.
Confirm the C-More driver covers the FX5 before any retry #
What the field reports and vendor support give so far: the FX5 appears in the C-More supported-protocol list; the FX Series driver underneath it was developed around FX1, FX2 and FX3; support had not tested FX5 when asked, describes RS-422 as the FX5 interface, and suggested Modbus RTU or Modbus TCP while noting it had not tested Mitsubishi's Modbus implementation.
Decision: treat FX5 through the FX1/2/3-era driver as unverified and stop burning serial retries on it. Plan the job on Modbus — RTU over the serial port you already wired, or TCP over the Ethernet port — and keep the native RS-422 driver as the fallback to retest once C-More confirms FX5 coverage in writing.
The FX5 side is documented: the MELSEC iQ-F FX5 User's Manual (MODBUS) gives the setup method for Modbus serial communication in chapter 6.1 and the TCP equivalent for the Ethernet port. Map a defined memory range to Modbus registers, mirror that range with an INT array of the same length, and prove the PLC end with a Modbus TCP scanner before pointing the HMI at it — one scanner read separates a PLC configuration fault from an HMI fault. If you later move 32-bit values this way, word order is its own C-More question; see how to swap words on a C-More 32-bit Modbus tag.
When the serial link still will not pass #
- Four-wire RS-422 is one twisted transmit pair and one twisted receive pair. Your + terminal is Mitsubishi's A marking, but one marked terminal does not give the full pinout: take the terminal designations for the exact FX5 port and the exact C-More interface, wire pair to pair with consistent polarity, and use twisted-pair cable. The two schemes already tried — SD+ to SD+ and SD+ to RD+ — differ on precisely the crossover question, so settle it from the pinouts, not by swapping. The same pair discipline shows up in the FX3G front-port RS-422 HMI connection that reports PLC off.
- Both ends must match protocol, baud, data bits, parity and stop bits. The settings already tried — 38.4 kbit/s with 8E1 under Modbus, plus the available Mitsubishi serial protocols — are field trials, not validated values; they prove nothing either way.
- The governing rule: a failed poll run through a driver never built for the FX5 tells you nothing about the cable. Driver first, wiring second, settings third — in that order.
Questions asked
Can I add a label directly on a contact or coil in the ladder?
Sometimes. Typing a name with no spaces on the element can create the table entry with a warning; other entry points refuse an unknown name outright. Either way the binding happens in the label table: open it, assign the device target there, and the label then displays over the coil in a different color. Treat table-first as the normal flow and ladder entry as the shortcut.
What file types does the C-More tag import accept?
The import takes comma-delimited .csv or .xls, and a file saved from Excel must use the UNICODE file format with a .csv extension. Be careful with other C-more file exchanges: the recipe transfer file is tab-separated 16-bit Unicode despite its .csv name. Always generate one file from the software's own export first and copy that shape exactly.
Should I run Modbus TCP instead of RS-422 with the FX5?
Modbus TCP is the cleanest path to prove. The FX5 Modbus documentation covers both serial and TCP setup: map a defined memory range to Modbus registers, mirror it with an INT array of the same length, and test the PLC with a Modbus TCP scanner first. Once the scanner reads your registers, any remaining failure belongs to the HMI side, not the PLC configuration.
Do Local labels export for the HMI?
No. Local labels are scoped to a single program inside GX Works3; the panel-facing set is the Global label table. Build every name the HMI needs as a Global label with an assigned device target, and export that table. Mixing HMI names into Local labels is what leaves them out of the export.
The tag imported cleanly but the lamp on the panel never changes. What does that prove?
A clean import proves the tag database only. Live data needs a driver that actually covers the FX5 and a passing physical link. With a correct tag and a dark lamp, stop editing the CSV: work the driver choice first, then the wiring, then the serial settings, in that order.