Iginition tag browser lags/hangs/doesn't work when there are tags whose OPCUA path is not found

Ignition
,
1

So I need to read data from some SunSpec devices. Sunspec doesnt provide a modbus register list to create the tags from the normal modbus driver.

In order to read with these devices I have written a module that after connecting to the SunSpec device it registers the found modbus data points as OPCUA tags.

After this in the designer I import the tags using the "Browse Devices..." in tag broswer. (By import in the designer I mean I add them to a tag provider, default tag provider in this case)

Since the OPCUA tags are created after connecting to the device this means that if a device is offline the designer will have tags that reference OPC paths that are not existing.

This makes the tag browser not work.

I click browse devices, the button gets stuck and the popup to import tags doesn't show up.
image

I think this could be the reason it hangs because the UPC UA server browser works fine (shown in picture below after I click to edit a tag and browse OPC path from there), the quick client also works fine. Therfore my suspicion is that this causes an issue with displaying the tags imported in the designer.
image

2

Unfortunately I think the answer is going to lie somewhere in your Driver/Device implementation... I can't reproduce this with any of our own drivers when taking them offline.

Maybe if you did a Wireshark capture of the OPC UA traffic on localhost (after turning security for the loopback connection off) you will see something like a particular browse or read request go unanswered.

If you can provide some reproduction steps that don't involve a custom module let me know.

side note: SunSpec has been on my radar for a long time, I still get their emails, just never heard of anybody using it until now.

1 Like
3

I made a couple of changes to my module and now it is working as it should. There were a few lines I thought I had commented out but apparently did not.

If somehow I have this issue again, I will try to reproduce it with one of the Ignition drivers.

Thanks for pointing me to the right direction!