IMDTouchKnowledge BaseShop main store

Troubleshooting

Fixing C-more CM5 timeout 1026 to a CLICK PLC

HMI and touchscreens Published 6 min read

Short answer

Timeout 1026 on a C-more CM5 to CLICK link is almost always the CLICK Ethernet port on its out-of-box settings: the panel sent a Modbus TCP request and nothing answered. Select Use the following IP address with 192.168.0.10 and mask 255.255.255.0, enable the Modbus TCP server on port 502, put the panel at 192.168.0.20, then settle the one-register tag offset with a 1-2-3 write-and-read test.

On this page
  1. What the 1026 code is telling you
  2. The four checks that clear almost every case
  3. Take the CLICK off the default IP
  4. Enable the Modbus TCP server
  5. Line up the panel side
  6. Prove the link
  7. Settle the register offset with a 1-2-3 test
  8. When it still times out
  9. Questions asked

Timeout 1026 on a C-more CM5 connected to a CLICK PLC means the panel sent its Modbus TCP request and nothing answered before the timeout expired. On a newly wired pair the fault is almost never the display — it is the CLICK Ethernet port sitting on its out-of-box settings. Select Use the following IP address on the CLICK, give it 192.168.0.10 with mask 255.255.255.0, enable the Modbus TCP server on port 502, set the panel to 192.168.0.20, download both projects, and the error stops. What remains afterwards is usually the one-register offset between panel and PLC addressing, which a 1-2-3 write-and-read test settles in minutes.

What the 1026 code is telling you #

The vendor's error-code reference describes Connection Timeout 1026 as a timeout that occurs after the request has been sent to the PLC: the panel asked, nothing replied, and the retry budget ran out. Nothing in that points at the screen or the touch controller — it is the request/reply path only. The panel's timeout setting is simply how long it waits for a reply before it resends and then errors, so a working link clears the code and a dead one raises it no matter how long the wait. If your link is RS-232 or RS-485 rather than Ethernet, the same symptom has a different checklist, and fixing an HMI PLC communication timeout over serial is where that path starts.

The four checks that clear almost every case #

  1. The CLICK is still on Use default IP. The port sits at its factory settings and the setup you believe you entered was never written that way. Selecting Use the following IP address and writing the setup is what puts your address, mask and server settings into the CPU.
  2. The Modbus TCP server is disabled. A C-more panel speaks Modbus TCP to a CLICK. EtherNet/IP is a different protocol that shares only the cable and the IP stack, so the server on the CLICK's Ethernet port 1 must be enabled, on TCP port 502.
  3. The subnet masks disagree. With 192.168.0.10 and 192.168.0.20 the first three octets match, so both devices need 255.255.255.0. One side on a broader mask breaks direct delivery between them.
  4. The tag base is off by one register. Panel numbering and CLICK numbering can differ by one — panel 40000 against CLICK 40001 for the same location — which reads the wrong value or errors once the link itself is up.

Take the CLICK off the default IP #

In the CLICK programming software, open Setup → Ethernet Port 1 and select the Use the following IP address option — the radio button, not the default setting beside it. Enter 192.168.0.10 and 255.255.255.0, then write the setup to the PLC. Until that write happens the CPU keeps whatever it already held, which explains plenty of installs that "should work". Note that the factory default address is also 192.168.0.10: the number on the screen proves nothing, the selected mode is what changes.

Enable the Modbus TCP server #

On the same Setup → Ethernet Port 1 pages, check Enable Modbus TCP Server, set the TCP port to 502 — the registered Modbus TCP port — and leave the unit ID at 1. Write the project to the CLICK again. When the CLICK answers but rejects the request you will see a Modbus exception, not silence; what an illegal function reply means is a different fault class from 1026, and seeing one actually proves the port is reachable and the server is on.

Line up the panel side #

In the C-more project, set the panel's own address under Project → Panel → Panel Information to 192.168.0.20 with mask 255.255.255.0; that address travels with the project, and where to save C-more panel IP settings in the project covers the detail. Under Project → Panel → PLC Connection, add the controller with the AutomationDirect CLICK (Modbus TCP) driver, pointed at the CLICK address on port 502 with the matching unit ID, and set the timeout to 3000 ms. Download the project to the panel. First three octets equal, masks equal: one network, no router in the path.

  • Ping both addresses from a laptop on the same switch. With the PC, panel and CLICK on one switch, ping 192.168.0.10 and 192.168.0.20; both should answer, typically at or under a millisecond on a bench switch.
  • Confirm both downloads happened. The CLICK setup was written to the CPU and the panel project downloaded to the panel — files saved on the PC mean nothing to the devices.
  • Watch the panel's PLC error screen. The 1026 count stops climbing the moment the server answers. If one screen runs clean while another errors, the link is fine and a screen object's tag is at fault.
  • Verify the hardware you actually have. Only CLICK CPUs with an Ethernet port can do any of this, and the cable must be true Ethernet: the phone-style programming connector on CPUs without Ethernet is not an RJ-45 network port.

Settle the register offset with a 1-2-3 test #

Run this with the machine idle or on registers nothing uses — a test write into a register that drives an output moves the machine.

Write three known values into consecutive CLICK registers: DF1 = 1, DF2 = 2, DF3 = 3. Put a numeric display on the panel aimed at what you intend as DF1, panel address 40001, and read it:

  • Shows 1: no offset. Your tags are correct as written.
  • Shows 2: panel 40001 is reaching DF2. Shift every tag down one register.
  • Shows 3: shift every tag down two registers.

Worked example: the display shows 2. Panel 40001 reaches DF2, so one step up in panel address reaches the next CLICK register and one step down reaches the previous one. DF1 = 40001 − 1 = 40000, and DF3 = 40001 + 1 = 40002. As a rule, DFn then answers at panel address 40000 + (n − 1); check it against the observation: DF2 = 40000 + (2 − 1) = 40001, exactly the address that returned the 2. Re-point every tag by that rule and the values line up.

For 32-bit data the base is only half the story: prove it with single-register values first, then treat a float that reads wildly wrong as word order inside the pair — how to swap words on a C-More 32-bit Modbus tag is that separate fix.

When it still times out #

With pings passing and port 502 enabled, work the short list:

  1. Set the connection timeout to 3000 ms if it is lower. The wait buys patience on a busy network; it never revives a port that does not answer.
  2. Audit every screen object's tag. One object aimed at an address the CLICK cannot map can hold the connection in error.
  3. Swap cable, then switch, then panel port — one piece at a time. A link that still times out against a CLICK that pings has a hardware suspect, not a configuration problem.
  4. For a CLICK that is deliberately offline part of the time, configure that one connection not to report its timeout, so a real failure on the main controller still alarms.

The decision path, one line each: ping fails — fix addressing and cabling before touching tags; ping passes but 1026 continues — the Modbus TCP server or the port; link up with wrong values — the register offset; error only on some screens — a screen object's tag.

Questions asked

Which CLICK CPUs can talk Modbus TCP to a CM5?

Only the CLICK CPUs with built-in Ethernet — the E-series models such as C0-02DRE-D and C0-03DRE-D — can serve Modbus TCP. A CLICK without an Ethernet port stays on Modbus RTU over its serial port, so the panel must be wired and driver-configured for serial instead.

Is timeout 1026 a fault inside the panel itself?

Almost never on this pair. The code comes from the communications driver when a request goes unanswered, and every cause worth checking sits in configuration. Treat the panel as suspect only after the CLICK pings, port 502 is open, tags are offset-checked and the error survives a second cable and switch — then test the panel on another port.

What timeout value should the CM5 connection use?

3000 ms is right for a small dedicated LAN. The timeout only sets how long the panel waits before it resends or raises the error, so a longer wait cannot revive a port that never answered — fix the address and server first, and treat the timeout value as polish for busier networks.

Can I stop the 1026 pop-up for a PLC that is deliberately offline?

Yes. When the CLICK is optional equipment that is sometimes powered down, configure that single PLC connection not to report its timeout instead of silencing alarms panel-wide, so a genuine failure on the main controller still announces itself on the screen.

Does the 1-2-3 offset test work on 32-bit values?

Prove the base address with single-register integers first, because a 32-bit value spans two registers and adds word order on top of any offset. Once the base is proven, a float that reads wildly wrong is a word-order problem inside the pair, not an addressing one.

Keep reading

  • How-to

    How to Swap Words on a C-More 32-Bit Modbus Tag

    Yes. In the C-more programming software, open Panel Manager, select the Modbus protocol, and enable Word Swap in its Setup dialog — add Byte Swap if each register's bytes are also reversed. The setting applies to every tag on that protocol instance, reaches the panel only with a full project transfer, and should be verified against a known reference value such as 0x12345678 (305419896 decimal).

    HMI and touchscreens

  • How-to

    Connecting an XBTGT HMI to an M241 PLC over Modbus TCP

    Delete the Generic Modbus TCP slave from the M241 device tree and activate the Modbus server on the controller's Ethernet interface instead — that slave makes the M241 a client, so both devices poll and neither answers. Then map Vijeo Designer driver address 40001 to PLC word %MW0, keep TCP port 502 open between panel and controller, and shift the address map by one word if a test read lands one register off.

    HMI and touchscreens

  • Selection guide

    Choosing a PC-based HMI runtime for a Modbus TCP PLC

    No — C-more projects deploy to C-more panel hardware, so a PC-only interface needs a PC runtime instead. Run AdvancedHMI, a PyQt5 front end with pymodbus, or an Excel VBA socket client as the Modbus TCP client, with the PLC acting as the server on TCP port 502.

    HMI and touchscreens