feat(plc4j/eip): Report the information if the tag address is invalid

[andvasp]

Hi @chrisdutz!

This is a simple PR to report tag INVALID_ADDRESS.

I discover this when analysing a problem where I am trying to read a valid tag address but the PLC does not recognize it. I am investigating it and probability I will create an issue.

[andvasp]

HI @chrisdutz.

Do you believe it can be merged before release 1.0.0?

[Copilot]

Pull request overview

Updates EIP read handling to report invalid tag addresses more accurately.

Changes:

• Centralizes CIP read-response conversion.
• Maps relevant CIP errors to INVALID_ADDRESS.
• Reuses response extraction for unconnected reads.

Suppressed comments (1)

plc4j/drivers/eip/src/main/java/org/apache/plc4x/java/eip/base/EipTcpConnection.java:1110

• The new status translation is the core behavior of this PR, but none of the EIP unit or driver tests exercises these error statuses. Add regression cases for 0x03, 0x04, and 0x05, including the forced-unconnected CipConnectedResponse shape and a normal CipReadResponse; this would catch the response-type regression above.

        if (status == CIPStatus.PathDestinationUnknown.getValue() ||
            status == CIPStatus.PathSegmentError.getValue() ||
            status == CIPStatus.InvalidParameterValue.getValue()) {
            return PlcResponseCode.INVALID_ADDRESS;

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[andvasp]

Hi @chrisdutz !

What about this PR. Can you review it?

[chrisdutz]

I'll look into this as soon as I manage to free a few seconds of time ... I'm sort of working my butt off in preparing PLC4X for 1.0.0 and the release ... your PRs always claim to be simple, but when looking at them the reformatting you keep on doing makes them all but simple to spot the changes.