Production returns when the Productivity scanner requests the same EtherNet/IP connection sizes that the CLICK adapter exposes. The key diagnostic is the complete message Invalid Originator to Target Network Connection Size; the shortened text INVALID ORIGINATOR TO TARGET NET. hides the field that directs the repair.
Reject the usual quick fixes
Start with the fault that is actually present. MSG1.con.ONLINE = 0 reports that the I/O connection never reached the online state; it does not identify why. Repeatedly cycling power, recreating the message, or changing IP settings will not correct a connection-size mismatch.
| Observed condition | What it means | Next action |
|---|---|---|
MSG1.STATUS.DESC ends at INVALID ORIGINATOR TO TARGET NET.
|
The description field is too short to show the useful end of the diagnostic. | Increase its displayed or stored length to 128 characters. |
Full text says Invalid Originator to Target Network Connection Size
|
The target rejected the requested cyclic I/O connection because its byte count does not match the configured target data. | Compare both directional sizes. |
MSG1.con.ONLINE = 0 |
No active I/O connection exists. | Use the status description to find the rejection reason. |
| No complete size error appears | A different failure may be blocking the connection. | Check addressing, reachability, adapter state, and connection configuration before editing sizes. |
Do not treat an offline connection as proof of a cable or address fault. A device can answer network traffic and still reject an EtherNet/IP I/O connection during establishment. The scanner proposes connection attributes; the adapter validates them before cyclic data exchange starts.
Read the complete status description
- Open the message diagnostics for
MSG1. - Increase
MSG1.STATUS.DESCto 128 characters, following help topicP260for the relevant display or string handling. - Trigger or retry the connection once.
- Read the entire description rather than diagnosing from the truncated prefix.
If the complete message is Invalid Originator to Target Network Connection Size, move directly to the size comparison. If it reports another condition, stop changing connection sizes and follow that diagnostic instead.
The terms originator and target describe roles. The Productivity scanner is the originator because it opens the connection. The CLICK adapter is the target because it accepts or rejects the requested connection. “Originator to target” therefore identifies the output-data direction from the scanner toward the adapter. It does not mean that the IP route itself is invalid.
Compare the requested connection sizes
Read the configured originator-to-target byte count in the Productivity scanner and the corresponding consumed-output size on the CLICK adapter. Compare byte counts, not the number of visible tags, registers, or logical I/O points.
- Record the scanner’s configured originator-to-target connection size.
- Record the adapter’s configured size for data received from the scanner.
- Confirm that both values use the same unit. Convert words or other elements to bytes before comparing them.
- If the counts differ, correct the scanner request or the adapter mapping so they match.
- Check the reverse target-to-originator direction at the same time. A second mismatch can appear after the first one is removed.
A connection size covers the complete cyclic payload defined by the endpoint configuration. It can include mapped data that is not obvious from an I/O screen. Count every transmitted element according to its storage width and include any required status or control fields shown in the product configuration. Do not add padding by guesswork; use the byte total reported by each configuration.
Trace the I/O layout before editing it
If the byte totals are not obvious, build a short map from the actual configuration. This prevents the common repair where the connection comes online but fields land at the wrong offsets.
| Check | Reading to take | Decision |
|---|---|---|
| Direction | Whether the data travels from originator to target or from target to originator | Compare only equivalent directions. |
| Element width | Bytes occupied by each configured item | Sum storage bytes, not point count. |
| Order | Starting offset of every field | Keep the scanner and adapter maps aligned. |
| Total payload | Last occupied byte plus its field width | Use this total as the connection size when the device configuration calls for the full mapped payload. |
If one side expresses the map in words while the other requests bytes, convert the configured element count using the documented width of that element type. Do not assume every value occupies the same width. Read the data-type or mapping display for the actual storage size.
Stop here if changing the size would overwrite a known production mapping or if the displayed data layout cannot be reconciled with the configured byte count. Preserve the current values and obtain the project owner’s mapping before proceeding.
Correct the resolving branch
- Place the affected process in a state where loss or remapping of remote I/O cannot command motion or energize equipment unexpectedly.
- Save the current scanner and adapter configurations.
- Edit the originator-to-target size so the Productivity request exactly matches the CLICK adapter’s receive layout.
- Confirm the reverse-direction size against the adapter’s produced layout.
- Verify field order and byte offsets on both sides; a matching total alone does not prove that the data map is correct.
- Apply the configuration using the normal download or update method for each device.
- Retry the EtherNet/IP connection and reopen the
MSG1diagnostics.
Change one mapping variable at a time. If the connection remains offline, capture the new complete status description before another edit. The rejection may advance to a different configuration problem after the first mismatch is repaired.
Verify the connection and exchanged I/O
First confirm that MSG1.con.ONLINE changes from 0 to the online state used by the project. Then verify the data itself in both directions. An online indication proves that the connection opened; it does not prove that every byte maps to the intended signal.
- Observe a safe test value generated by the Productivity side and confirm that it reaches the intended CLICK-side location.
- Change a safe CLICK-side test value and confirm that the expected Productivity location updates.
- Check several fields across the beginning and end of each payload. This exposes shifted offsets and incorrect element widths.
- Confirm that the values remain stable through normal connection retries or permitted equipment restarts.
- Record the final directional byte counts and mapping revision with the machine configuration.
If MSG1.con.ONLINE remains 0, read the full current description again. Continue size work only if it still identifies a connection-size error.
FAQ
Can I fix MSG1.con.ONLINE = 0 by cycling power?
A power cycle can retry the connection but cannot reconcile mismatched payload sizes. Expand MSG1.STATUS.DESC to 128 characters, read the complete fault, and correct the directional byte count.
Does Invalid Originator to Target Network Connection Size mean the IP address is wrong?
No. It means the target rejected the originator-to-target I/O connection size requested by the scanner. Compare the Productivity output byte count with the CLICK adapter’s corresponding receive layout.
Can I increase the connection size until the CLICK adapter accepts it?
No. Match the configured payload exactly and verify every offset in both directions. Stop and escalate to official manufacturer support if the documented maps match but the full size error remains, or if the mapping cannot be changed without risking unintended outputs; provide the complete status text, both directional byte counts, and the saved configurations.