Field fix / guideProcedureVendor-agnosticPLC Connectivityindustrial-automation

Connection Diagnostics — Engineering Guide

Shared by TSIMEREZIVO Team · 4 Oct 2026 · 46 views

# Connection Diagnostics When a PLC connection fails, a systematic diagnostic approach gets you back online fast. This guide walks through the offline troubleshooting decision tree, protocol-specific checks, Wireshark capture techniques, and the complete TSIMEREZIVO error code reference. 18 min ## Offline Troubleshooting Decision Tree | q | yes | no | isStart | |---|---|---|---| | Is the TSIMEREZIVO connection status RED (OFFLINE)? | Continue → | Check quality codes (STALE/BAD) | true | | Can you ping the PLC IP address from your machine? | Network OK → skip to Step 4 | → Network problem | false | | Is the PLC in RUN/REMOTE mode (not PROGRAM mode)? | Continue → | → Change PLC to RUN mode | false | | Is the protocol port open? (EIP: 44818, Modbus: 502) | Continue → | → Firewall rule blocking port | false | | Does TSIMEREZIVO show the correct IP and slot/unit ID? | Continue → | → Edit connection settings and retry | false | | Is any other client already connected? (S7 max 1–4) | Disconnect other clients first | → Check TSIMEREZIVO bridge logs | false | ## Network Ping Test ### Step 1 — Ping the PLC IP Address TSIMEREZIVO includes a built-in network test at **Connections → [PLC] → Diagnostics → Ping**. This sends 4 ICMP echo requests to the PLC IP and shows round-trip times. Alternatively, from your terminal: ```bash # macOS / Linux ping -c 4 192.168.1.10 # Windows ping -n 4 192.168.1.10 # Expected result (healthy connection): 64 bytes from 192.168.1.10: icmp_seq=0 ttl=128 time=0.8 ms 64 bytes from 192.168.1.10: icmp_seq=1 ttl=128 time=0.9 ms # Bad result — packet loss: Request timeout for icmp_seq 0 → Check: Ethernet cable, switch port, PLC IP settings ``` ### Step 2 — Check TCP Port Connectivity Ping succeeds but TSIMEREZIVO still cannot connect? Check if the protocol port is open: ```bash # EtherNet/IP (ControlLogix, CompactLogix) nc -zv 192.168.1.10 44818 # Modbus TCP nc -zv 192.168.1.10 502 # Siemens S7comm nc -zv 192.168.1.10 102 # OPC-UA nc -zv 192.168.1.10 4840 # Expected result: Connection succeeded! # If failed: port is closed — check PLC firewall or IT network rules ``` ## Protocol-Specific Diagnostics | proto | tips | limit | CompactLogix | |---|---|---|---| | EtherNet/IP (Allen-Bradley) | [ 'Verify slot number — ControlLogix CPU is typically slot 0. Wrong slot = connection refused.' | 500 bytes per request. Very wide tag arrays may need to be split.' | IP is on the CPU itself | | Siemens S7comm (S7-300/400/1200/1500) | [ 'S7-1200/1500: You MUST enable "PUT/GET communication" in TIA Portal → PLC Properties → Protection. Default is disabled.' | | | | Modbus TCP | [ 'Unit ID (slave ID) must match the device configuration. Default is usually 1 or 255.' | | | | OPC-UA | [ 'Security policy: TSIMEREZIVO supports None | | | ))} ## Wireshark Protocol Capture ### Step 1 — Capture Filter by Protocol ```wireshark # EtherNet/IP tcp port 44818 # Modbus TCP tcp port 502 # Siemens S7 tcp port 102 # OPC-UA tcp port 4840 ``` ### Step 2 — What to Look For - **TCP RST (Reset)**: The PLC is refusing the connection — port closed or firewall - **TCP SYN with no SYN-ACK**: No response from PLC — check network route - **Modbus Exception Code 01**: Illegal function — FC not supported by device - **Modbus Exception Code 02**: Illegal data address — register address out of range - **S7 Error 0x8104**: PUT/GET not enabled — enable in TIA Portal - **EIP Error 0x08**: Connection refused — another exclusive owner connected ## TSIMEREZIVO Error Code Reference | code | meaning | resolution | |---|---|---| | CONN_TIMEOUT | TCP connection timed out after 10 seconds | Check network route, IP address, firewall rules. Try ping first. | | CONN_REFUSED | PLC actively rejected the TCP connection | Check port is open. Check PLC is in RUN mode. Check max connections not exceeded. | | AUTH_FAILED | OPC-UA session authentication rejected | Check username/password in connection settings. Import certificate if security mode is Basic256. | | BAD_CONFIG | Connection parameters invalid | Review slot number (EIP), unit ID (Modbus), TSAP (S7), or endpoint URL (OPC-UA). | | TAG_NOT_FOUND | Tag address does not exist in PLC | Verify tag name spelling and data type match PLC program. Check tag is not a local variable. | | STALE_DATA | Last successful read > 2 polling cycles ago | PLC connection may be intermittent. Check network for high packet loss. | | WRITE_BLOCKED | Write command blocked — safety tag | Tag has _ES, _STO, or _SIL suffix. Safety tags cannot be written via TSIMEREZIVO (RULE-P2). | | POLL_TOO_FAST | Requested poll interval ### Related Guides | href | label | desc | |---|---|---| | /dashboard/docs/controller-setup | Controller Setup | Initial connection wizard for all protocols | | /dashboard/docs/live-connection | Live Tag Monitor | Quality codes: GOOD, STALE, BAD explained | | /dashboard/docs/alarm-investigation | Alarm Investigation | STALE quality codes can cause false alarms |

More like this

Rate, comment, and get full access

Members can download files, rate contributions, and discuss fixes with the engineers who posted them — free.

Join the library