Troubleshooting
Getting Citect SCADA talking to a Mitsubishi iQ-R PLC
Short answer
Fix the transport before anything else: the Citect MELSECQ port on TCP_BOARD must match the iQ-R's SLMP connection module exactly — protocol, port number and IP address. If tags above device 65,535 fail, that is the MELSEC Q protocol's 16-bit address ceiling, and no setting fixes it; move to Mitsubishi's OPC MX UA server with a Citect OPC client driver.
On this page
- Why will Citect SCADA not connect to my iQ-R over the MELSEC Q driver?
- How do I configure the SLMP connection module on the iQ-R side?
- What settings does the Citect MELSECQ port need?
- Why does the channel still fail when the IP address is right?
- Why do low addresses read while higher ones fail?
- How do I prove the link before loading the whole tag database?
- When should I stop fixing the MELSEC Q driver and use OPC UA instead?
- Questions asked
Citect SCADA reaches a Mitsubishi iQ-R PLC through the MELSECQ protocol over a TCP_BOARD port talking to an SLMP connection module on the PLC's Ethernet interface — and the two ends must agree on transport, port and IP before a single tag moves. When they agree, low device numbers read normally; when tags above device 65,535 fail, you have hit the MELSEC Q protocol's 16-bit address ceiling in the old Citect driver, which no Ethernet setting repairs. This article walks the fix in the order you meet it: read the failure, configure the SLMP module, match the Citect port, prove the link, then decide whether the direct driver survives your tag list or the OPC MX UA server path takes over.
Why will Citect SCADA not connect to my iQ-R over the MELSEC Q driver? #
In almost every failed install the SLMP connection module on the PLC does not match the Citect port definition — wrong transport, wrong port number or no connection entry at all — so match those three things before touching drivers or tags. Read the failure first, because the three ways this link breaks need three different fixes.
| What you see | What it usually means | First check |
|---|---|---|
| Channel never connects | No listener, wrong IP or port, or blocked traffic | Compare the SLMP module's IP, port and protocol against the Citect port definition |
| Connects, then every read fails | Frame or transport mismatch on a live link | Confirm TCP at both ends and test one device address the driver documents |
| Low addresses read, higher ones fail | 16-bit address ceiling in the old driver | Compare the failing device number against 65,535 |
| Small test works, full project stumbles | Polling load or request grouping | Re-add tag groups in stages and watch read errors |
Get the failing evidence before you change anything: whether the channel never opens, opens and times out, or errors only on particular addresses. A working single tag proves one request path, never the whole project.
How do I configure the SLMP connection module on the iQ-R side? #
In the Mitsubishi engineering software's Ethernet configuration, add an SLMP connection object, set the connection method to SLMP, choose TCP, and give it the port number you will reuse in Citect — that module is the listener your driver talks to.
- Open the Ethernet configuration for the CPU or Ethernet module the Citect machine will reach.
- Add the connection object the software lists as "SLMP Connection".
- Set the connection method to SLMP and the protocol to TCP.
- Assign a port number and write it down; 1024 in this article is an example value, not a default, and whatever you set here is what Citect must target.
- Write the configuration to the PLC with the software's documented transfer and activation steps, then confirm the connection is present in the resulting configuration.
Use TCP. It is the transport that makes a polled SCADA link behave predictably, and it is the one the working configuration below assumes.
What settings does the Citect MELSECQ port need? #
Select the MELSECQ protocol, define its port on TCP_BOARD, and set the special options to the PLC's IP address, the SLMP port number and the transport letter: -I10.10.10.1 -P1024 -T is the working TCP form, with -U in place of -T for UDP.
The two forms, with the IP address and port as example values only:
-I10.10.10.1 -P1024 -T
-I10.10.10.1 -P1024 -U
Run one transport at a time. Attach the I/O device to that port, add a single readable device using the syntax the installed driver documents, then compile and activate through your normal deployment path. Substitute the IP address you read from the PLC's Ethernet interface and the port you assigned to the SLMP module; a guessed port produces exactly the silent failure you are trying to eliminate.
Why does the channel still fail when the IP address is right? #
Because the transport and the service must match as well: a Citect TCP client cannot be answered by a connection module configured for UDP, and a ping proves only IP reachability, never that an SLMP listener exists on that port. TCP opens a connection before any request; UDP fires datagrams with no handshake, so each end must be built for the same one.
Check the two ends together, not in isolation:
- The connection module's protocol setting (TCP or UDP) must equal the letter in the Citect special options.
- The module's port number must equal the number after -P.
- Any firewall or router between the Citect computer and the PLC must pass that port in that direction, since a blocked port produces the same silence as a missing module.
Fix all of it to TCP and retest before you conclude anything about the driver.
Why do low addresses read while higher ones fail? #
Because the address field itself is the limit: the MELSEC Q protocol path in the old Citect driver carries 16 bits, 2 to the 16th power is 65,536 values, and 65,535 is therefore the highest device number that request can ever name. This is arithmetic, not opinion, and it survives every timeout change you make.
The worked example that decides it: a 16-bit field holds 65,536 distinct values, so expressible device numbers run from 0 to 65,535 (65,536 − 1 = 65,535). Take a project tag at D70000: 70,000 − 65,535 = 4,465 device numbers past the top of the field, so the request cannot name it. D1000 sits well inside the field and reads fine on a working link — same driver, same transport, same port; the address field is the only difference. Engineers who moved iQ-R projects off this driver report exactly this pattern, because iQ-R device spaces run well past 65,535 while the legacy request format cannot follow.
The decision rule follows from the number: export your variable list, find the largest device number for each device letter, and compare it to 65,535. At or below it everywhere, the direct MELSECQ path can carry the whole project and belongs in the sections above. One tag above it, and no Citect or Ethernet setting widens the field — go straight to the OPC UA path below.
How do I prove the link before loading the whole tag database? #
One live tag first: read a value that changes, compare it against the same device watched online in the PLC engineering software, and only then add groups in stages while you watch tag quality and read errors. A constant value hides staleness; a value you can see move in both places proves the read is live.
Check quality as well as value — a number on screen does not prove the latest read succeeded, and most drivers surface that only in tag quality and driver diagnostics. Load the production groups in stages so a polling problem shows up as a stage boundary, not a mystery.
Leave writes until last, on a device that cannot move the machine: a SCADA write is a real command to the process, not a simulation, so the machine must be in a state where a wrong value is harmless. Floating-point targets deserve a specific look, because a write can fail without an alarm — the failure mode covered in why a SCADA write to a PLC real address fails silently. Once the link carries the load, create a SCADA communication alarm for link loss so a dead connection announces itself instead of quietly freezing the screen.
When should I stop fixing the MELSEC Q driver and use OPC UA instead? #
Move when any device number in the project exceeds 65,535, or when a fully matched TCP link still errors on valid in-range addresses — those are architecture limits, not configuration faults, and the fix is Mitsubishi's OPC MX UA server with a Citect OPC client driver. OPC UA is standardized as IEC 62541, which defines the client/server model, the read, write and subscription services the Citect OPC client driver uses, and the certificate exchange that decides whether the server accepts the client at all.
The sequence that works: confirm in the MX UA documentation that your CPU, device ranges, operating environment and license are covered; configure the PLC connection inside the server and prove live values there before Citect is involved; then point the Citect OPC client driver at the server's endpoint. Before the first successful read, client and server must exchange and trust certificates — the same trust step shown for another controller brand in trusting the Citect OPC UA client certificate on a B&R PLC. If you run the endpoint unsecured while commissioning, troubleshooting OPC UA certificates with Security None explains what that setting does and does not relax. Host the server on an industrial mini PC mounted in the cabinet beside the controller, so the OPC UA path does not depend on a desk machine. Engineers who made this switch report that the server's own link to the PLC moves noticeably more data per transaction than the MELSEC Q driver path — reported experience, not a figure measured here.
The decision, case by case:
- Transport or port mismatch, or no SLMP module: fix the PLC connection object and the port options; stay on MELSECQ.
- Every device number at or below 65,535: the direct driver can carry the project; finish staged testing and load.
- Any device number above 65,535: stop configuring — the 16-bit field cannot be widened; OPC MX UA server plus Citect OPC client driver is the path.
- In-range addresses still failing on a matched TCP link: verify the device syntax against the installed driver help once, and if it still fails, treat it as the previous case.
Questions asked
What does SLMP actually stand for?
Seamless Message Protocol: Mitsubishi's Ethernet application protocol for reading and writing devices in an SLMP-compatible controller, carried over TCP or UDP. The SLMP connection module you configure on the iQ-R is the listener that accepts those requests on the port you assign; the Citect MELSECQ driver over TCP_BOARD is the client that generates them.
Will this same setup work on an FX5U?
The Citect side is identical — MELSECQ on TCP_BOARD with matching IP, port and transport — but FX5-class CPUs add a step: one OPC server vendor's setup guide requires enabling external device access in the global label settings and using a port above 1024 before an Ethernet client can reach devices. Confirm the exact switch names in your CPU's manual, since menu paths differ by generation.
Is UDP ever the better choice for the Citect link?
No, not for polled SCADA reads. TCP gives you delivery and ordering, so a lost frame retries instead of leaving a stale value on screen; UDP saves handshake overhead but drops show up as silent staleness. Choose UDP only when a specific driver or architecture calls for it, and then set the connection module, the -U option and any firewall rules to match.
Do I still need an SLMP connection module if I use the OPC MX UA server?
Not for the Citect leg. Citect talks OPC UA to the MX UA server, and the server reaches the PLC through Mitsubishi's own internal path, which engineers report carries more data per transaction than SLMP does. The SLMP module matters only for direct MELSEC Q driver connections; keep one only if another client also polls the PLC directly.