What are people using as a modern day replacement for wwClient?

 As far as I know WWClient ended life at 7,11,0,0306 with a limitation on the item name that could be advised.  It can be worked around by configuring a device item with the long name as the item reference, but who loves doing that each time?  Just wondered what everyone was using these days.    If the source were available, I'd.....

  • Hey, i would like to know what you are using WWClient for ? I use the free Intouch Dev environment for this now but would like a lite version of it

  • To verify resulting references, I use the IO Device and Mapping tools in the IDE.

  • Hi,

    The departure of wwClient did leave a gap, and we are (finally) considering how to address that. We want to provide direct feedback on connection state as well as easy access to validation tools for IO references. Some of this may start to appear in releases during 2025.

    I commonly see people using an OPC Client as substitute for wwClient but that has its own challenges of course.

  • Hi Joel,

    I can also feel the pain of not having wwClient available in newer versions, and in some cases I still use it.

    It is a very simple tool to verify device connection (and especially when testing out item names), without the need of any other tools available or proper things in place, such as a deployed galaxy or a running InTouch application.

    As mentioned there are other ways of verifying connection or 'quickly' test out item names against a datasource, but none as simple as wwClient

    In most cases I do have a galaxy and as soon as I have a DDESuitelink object deployed, configured to use my communication driver i can use Object Viewer to manually enter and test various items, without the need for the more time consuming procedure in creating attributes and assigning io references.

    syntax: <CommunicationObject>.<DeviceGroup>.Itemtotest

    I have found this as the most reliable way of 'testing' communication and item naming.

    As mentioned by others, since most Aveva drivers provide a OPC Interface as well it can be possible to use any OPC Client software to manually enter some item names for testing, but since OPC and Suitelink addressing is not identical it can be some extra steps required to transfer the result to System Platform using suitelink.

    So I am happy to see Rickards comment that Aveva acknowledge the gap and are planning for some additional features related to this in future versions.