IMDTouchKnowledge BaseShop main store

Troubleshooting

Why Weintek HMI Tags Fail to Update With an Omron CJ1M

HMI and touchscreens Published 8 min read

Short answer

A clean download and system traffic in EasyDiagnoser prove the transfer path, not tag exchange. With a CJ1M-CPU12 and an ETN11, fix the link in order: the documented CJ/CS/CP FINS driver and its destination fields, one known D-word read, then request and reply diagnostics that name which of four stages fails.

On this page
  1. Why does the download succeed while tags stay dead?
  2. What should I confirm before changing any settings?
  3. Which Omron driver does a CJ1M with an ETN11 need?
  4. How do I set the FINS destination on the ETN11?
  5. Can I import CX-Programmer tags instead of typing addresses?
  6. How do I prove one word before trusting any tag?
  7. What do the EasyDiagnoser results point to?
  8. How do I fix the failed stage without breaking the working path?
  9. Questions asked

Treat this as a PLC-communication fault, not a download fault. A project that compiles and downloads to the MT8070iH proves only the transfer path, and the system traffic EasyDiagnoser reports is panel housekeeping, not tag exchange. Tags stay dead when one of four stages fails: request generation, delivery to the ETN11, controller acceptance, or value interpretation. Work them in that order — confirm the driver and the FINS destination, prove one known D-word, then read the request and reply diagnostics before changing anything else. On a CJ1M-CPU12 with an ETN11, the usual fault is the FINS destination fields naming something other than the CPU, or an address whose memory area the panel and the controller read differently.

Why does the download succeed while tags stay dead? #

Because the two functions use different connections: the download moves the project from your PC to the panel, while tag traffic must run from the panel to the ETN11 over FINS, through four stages a download never exercises.

The system traffic in EasyDiagnoser is the panel's own housekeeping — it shows the runtime is alive, not that the controller answered anything. The transfer path can be perfect while the runtime device points somewhere else entirely. The four stages are:

  1. Request generation — the runtime builds a read for an object assigned to the configured PLC device.
  2. Delivery — the request reaches the ETN11 across the network.
  3. Controller acceptance — the CJ1M's CPU returns an answer with no error status.
  4. Value interpretation — the returned bytes are matched to the memory area, address and format the object expects.

The split is the one behind separating the HMI transfer method from the PLC driver: transfer settings say how the project reaches the panel; device settings say how the panel reaches the PLC.

What should I confirm before changing any settings? #

Record the four identities first — a CJ1M-CPU12, an ETN11, an MT8070iH and the exact editor version installed — because a fix built for the wrong CPU, module or editor generation wastes the bench time you could spend testing.

Check the equipment labels against the CX-Programmer project and the HMI target selection. The editor reported in the field as EB800 needs its full product name and version read from its own information screen; driver documentation follows the installed generation, not the example you found. Then trace the Ethernet path: record the panel, ETN11 and engineering-PC addresses with their masks and any gateway, and check the link indicators and switch ports.

Worked example (illustrative addresses), ETN11 at 192.168.1.5, panel at 192.168.1.10, mask 255.255.255.0:

  • Panel network: 192.168.1.10 AND 255.255.255.0 = 192.168.1.0
  • Module network: 192.168.1.5 AND 255.255.255.0 = 192.168.1.0
  • Both ends sit on 192.168.1.0, so delivery is direct and no gateway takes part.

Move the panel to 192.168.10.10 and its network becomes 192.168.10.0 (192.168.10.10 AND 255.255.255.0). Nothing routes 192.168.1.x to it, every request dies at delivery, and the engineering PC — still on 192.168.10.x — keeps downloading and pinging without complaint. Subnets that do not match are the fault: correct the panel's address or configure the documented gateway before touching the driver.

Last, separate the two destinations. Note which address receives HMI downloads and which address the runtime PLC device is configured to reach; a panel accepts downloads all day while its runtime device points somewhere else.

Which Omron driver does a CJ1M with an ETN11 need? #

The driver documented for OMRON CJ/CS/CP controllers over FINS on Ethernet — Ethernet names the cable and the port, not the application protocol, so a serial Host Link driver for the same CPU will not move one word through the ETN11.

FINS is Factory Interface Network Service, Omron's messaging protocol between controllers on FA networks; every read and write the panel makes is a FINS request. The default FINS/TCP port given in FINS driver documentation is TCP 9600. Weintek's OMRON CJ/CS/CP connection guide documents this driver's address syntax, its tag import, and its support for Extend Addressing Mode — get the guide revision that matches your editor version, and where its menu names differ from what your installed editor shows, trust the editor.

Decision: if the selected driver is not the CJ/CS/CP Ethernet (FINS) one, reselect it and re-verify every address afterwards, because address syntax belongs to the driver and moves with it.

How do I set the FINS destination on the ETN11? #

Enter the module's IP address for delivery, then set the FINS destination fields — network, node and unit — so the request names the CPU and not merely the module; an IP that reaches the ETN11 still leaves the controller unidentified.

These fields sit with the PLC device settings in the project's system parameters, and their values come from the controller's configuration: the network and node the ETN11 belongs to, and the unit the request targets. A request whose unit field lands on the communications module is answered by the module itself, not by the CPU that owns the D memory — traffic flows, nothing updates. Do not copy the three values from another installation.

For what the module does with those fields once a request arrives, the ETN11 FINS protocol over Ethernet page walks the frame layout the ETN11 parses. Save the settings, reopen the device configuration, and confirm the stored values before building the test screen.

Can I import CX-Programmer tags instead of typing addresses? #

Yes — the documented route is the tag import on the driver settings page, which reads a *.cxr file exported from CX-Programmer, but it picks up only addresses that carry a tag name, and the address type has to be set for each.

The documented sequence in the current guide: open the editor, set the driver parameters in [System Parameter Settings], click [Import Tags], select the *.cxr file, then check the tags the project needs. Those menu names are documented for EasyBuilder Pro; if your editor reports itself as EB800, use the equivalent import in that generation. The import takes memory-area selection out of your typing, which removes one of the four stages before the first test. Unnamed raw addresses in CX-Programmer are skipped — name the symbols there and export again, or type those addresses manually with the driver's address selector, choosing the memory area separately from the number.

How do I prove one word before trusting any tag? #

Put one read-only numeric display on a spare D-word and watch the same word online in CX-Programmer: the link is proven only when the panel shows the number the programming software shows — one object, one memory area, one format.

Choose a word that changes on its own, such as a cycle counter on D100 (example address). Record its area, address, current value and data interpretation. Keep the display a word-sized integer; leave multiword values, scaling and bit extraction out of the first test. Make any forced value change in a maintenance window with the machine stopped — the first test needs no write at all, because a naturally changing word answers the same question. Download, then observe both sides together and record which of four results you see: correct value, different value, stale value, or a communication error.

A symbol name is not automatically an HMI tag. The object must resolve to a supported memory reference, and an address the editor accepts can still name an area the CJ1M answers differently than the object expects.

What do the EasyDiagnoser results point to? #

The four possible outcomes each name one stage: no request for the test object means generation, requests without replies means delivery, replies carrying an error status means controller acceptance, and clean replies with a wrong value means interpretation.

What EasyDiagnoser shows Stage that failed Next check
No request for the test object Request generation Active screen, the object's device assignment, communication enable settings
Requests with no replies Delivery Panel and ETN11 addresses, the FINS destination fields, module diagnostics
Replies carrying an error status Controller acceptance Record the exact status text and decode it with the protocol documentation
Clean replies, wrong value displayed Interpretation Requested memory area, address, length and display format against the monitored word

Read the ETN11's diagnostic status alongside the panel's result, and record the actual error text rather than assuming a code. Where the diagnostic view lacks packet detail, use the device error information and, if your plant authorizes it, a network capture. The discipline is the same one that fixes a hardware controls error on an HMI Ethernet link: read what the driver reports before editing objects.

How do I fix the failed stage without breaking the working path? #

Change one setting group at a time and rerun the identical one-word test after each change: the driver or destination for a protocol fault, the routing fields for a routing fault, the object's address for a memory fault — then widen the tag set.

Save both projects and record the current device settings first, and keep the one-word screen as the reference. Apply ETN11 configuration changes through the documented procedure and the operating conditions it states. Once the word read passes, add tag types one at a time — bit objects, multiword numbers, scaled values — checking bit number, word order and format on each.

The decisions, case by case: a subnet mismatch is fixed at the address, never in the driver; a wrong driver is fixed by reselection plus a full address re-check; wrong FINS fields are fixed from this controller's configuration, not from another install; a missing request is fixed on the object; an error status is decoded before anything is edited; a clean reply with a wrong value is fixed in that object's area, length or format. After the word test passes, a dead tag is an object-level address or format problem, not a link problem.

Questions asked

Why does the project compile and download fine if the PLC settings are wrong?

Compilation and download touch only the panel. The editor checks each object's address against the selected driver's syntax, then writes the project to the panel over the transfer connection; the PLC is never contacted. A wrong driver, a wrong FINS destination or an address naming the wrong memory area passes all of that untouched and appears only as a dead tag at runtime.

Does a successful ping to the ETN11 prove the HMI link will work?

No. Ping proves IP delivery to the module and nothing more. If ping succeeds while tags stay dead, delivery is not the fault, which narrows the search to the FINS layer: the selected driver, the network, node and unit fields, and the memory area in each address. That is the fastest narrowing this symptom gives you.

Why did the CX-Programmer tag import bring in only some of my addresses?

The documented import reads a *.cxr file and picks up only addresses that carry a tag name, with the address type set for each. Unnamed raw addresses are skipped silently. Name the missing symbols in CX-Programmer, export again and re-run the import, or type those addresses manually with the driver's address selector.

What port does FINS over TCP use through the ETN11?

The documented default for FINS/TCP is TCP port 9600, and the UDP transport uses the same number by default. If a managed firewall, an IT-controlled switch or a router sits between the panel and the ETN11, that port must be open in both directions, or requests die at delivery while everything else on the network works.

Does the CJ1M extended memory work through this driver?

Yes, the Weintek CJ/CS/CP driver supports Extend Addressing Mode, so a project that uses extended memory areas is not by itself the reason tags fail. Confirm the driver selection and the FINS destination first; extended addressing only matters once single-word reads already work and specific objects still misbehave.

Keep reading

  • Troubleshooting

    Fixing an HMI Date and Time Tag That Fails Over S7

    When ordinary tags read and write but a Siemens date and time tag returns a communication error, the driver imported the tag but cannot transfer that data type. Copy the clock into ordinary component variables in PLC logic and read and write those from the HMI. The Ethernet side needs no changes.

    HMI and touchscreens

  • How-to

    Setting Up a Weintek MT6050IP With a Delta DVP28SV PLC

    Use EB8000 for the MT6050IP, because EasyBuilder Pro does not list it. Create the project, select the exact panel model, configure the Delta DVP28SV as the PLC device with serial settings copied value-for-value from the wired port, then bind objects to the device areas the Delta driver already exposes. Model, connection and address are three separate checks.

    HMI and touchscreens

  • Troubleshooting

    Fixing Weintek HMI to Mitsubishi FX PLC Communication

    A Weintek panel that shows communication errors against an FX0N, FX1N, FX2N or FX3 CPU is nearly always wired with the wrong cable pinout for the port pair. Match the HMI COM port and PLC port to the Weintek PLC Connection Guide, set GX Developer parameters only for adapter boards, and keep the 1 m cable.

    HMI and touchscreens