Welcome to the OptoForums! I’m sorry you’re having trouble with groov. To answer your specific question, the version of the OPC-UA client can change from version to version of groov, but groov 3.0 (the current version as I type this) uses Prosys Java client version 2.1.0-436.
However, getting to the actual problem you’re trying to solve, I know our engineering team would like to sort that out, especially since other OPC-UA clients work fine. A few thoughts:
- You mentioned UDT (User Data Types, yes?) which could complicate things. Were you able use any other data types successfully? Are there other variations of your data types you could try (perhaps a single element if you're using an array, or an array of 1 if you're using a single element)? All this extra info would help our groov team narrow down the real issue.
- Are you familiar with Wireshark (or some other packet-sniffing tool)? Since you have a client that works, a packet sniff of "working" vs. "non-working" could also be very helpful.
- Does your AB device communicate via any other protocols, e.g. Modbus? If so, you might be able to skip the extra OPC-UA layer(s) by having groov communicate directly.
In any case, we’d like to get to the bottom of that “unknown reason”! Also remember our product support is free (best to contact them via email: support @ opto22.com).