[OpcUaClient Fixed in 2025.4] Doesn't work with Anybus

Hello,
We test the OpcUaClient to connect a simulated B&R PLC with a virtual controller.
We see that using “841-1 EtherNet/IP Scanner/Adapter” works fine but using “840-1 EtherNet/IP Anybus Adapter” failed with error:
Bad result writing OPC UA data for node ::AsGlobalPV:RobotOutputs (status: 2155085824).

Device received the good data (input) but can’t send them to PLC (output).

Does anybody have this error too?

UP

UP

UP

Denis, please reach out to your local ABB with this issue and report it as a potential bug.

Thanks.

Post update for RS 2023.4.1:
Test creating an EthernetIP_Anybus with 128I/128O:


And an EthernetIP with 128I/128O too:

I’ve start OPC UA Client Configuration and add Controller Device I/O mapping:
Imgur

With EthernetIP it works fine:
Imgur

Still here in 2024.1

Still presents in 2024.2.1

Still present in 2025.2

Hi Denis,

Did you report this via Local ABB? :slight_smile:

Hello,
Yes

@DenisFR can you PM me the case number/work item number please?

Still present in 2025.3

Fixed in 2025.4

Still have bug when writing:
Bad result writing OPC UA data for node ::AsGlobalPV:gRobotList[1].MapIn (status: 2155085824).

BadTypeMismatch 0x80740000 2155085824 The value supplied for the attribute is not of the same type as the attribute’s value

Works fine with UaExpert.

@DenisFR I’m glad to hear that the initial bug was fixed in 25.4

For the new one, please report it via Local ABB.

Thanks!