Hello,
thanks for the additional info.

For items that the server does not expose through browsing, you can use the following trick in Connectivity Explorer:

1. Navigate so that you can select some items from your server in the list view (right pane) of the "Browse" tab of the "Point Editor", and select some item.
2. Switch to the "Inspect" tab.
3. Expand Misc -> Item Descriptor, and in the "Item ID" row, enter the full desired Item ID of the item you want to work with.
4. Do Live -> Add Row from the main menu.

It is not, however, clear to me why you have brought this issue here, as apparently, the items in question can be accessed without this procedure anyway, as you have confirmed in your answer #3. It just sidetracks the discussion and possibly confuses me. Stay focused to the problem. If you have unrelated problems, start a new forum thread (and link to other thread(s) if needed).

The main points of my current understanding can now be summarized like this:

1. You get 0xC004D002 error when writing an item with QuickOPC 5.21.
2. If you use the current Connectivity Explorer (5.71), you can write the same value into the same item without problems.

The Connectivity Explorer, leaving aside all the fancy user interface, in the end just calls the EasyDAClient.WriteItemValue method (or equivalent), the same as your code does. If my summary understanding above is correct, I recommend to rebuild your project with current QuickOPC version (trial license is OK), because it should then start behaving like the Connectivity Explorer 5.71 does. Note that your version is very and there might be code breaking changes, although all principles remained in place and if there are changes, they should be easy to do (and we can help). kb.opclabs.com/Versions

Best regards

Hello,
thank you for additional details.

I do not understand what you mean by saying that you are not able to add some tags. What precisely happens? My guess: You need to select the parent level (Device1 maybe) in the tree view (left side), Only then are the items displayed in the list view (right side), and can be selected and "added".

I still have some questions, in order to get a clearer picture:

1. You wrote "The failed error messages in the other screenshot (from System Management Console) were from the earlier time when the write command from the VB application failed." . Does it mean that now you can write to your OPC server, using MatrikonOPC (or other client) without errors, to the same items and using the same values, that fail with you QuickOPC application?

2. Does your QuickOPC application do with the OPC server anything else besides the Write-s? E.g. some browse, read, or establishing a subscription? If so, does that work correctly?

3. Can you please test the writing using Connectivity Explorer? To do so, first "add" the live data row Then, click in the cell under the Value columns, and enter a new value. Then press Ctrl+W (or use the Write command from the context menu). Does it write the value? Does it show something in the Error Message column?

Thank you

Hello,

I have asked you to use Connectivity Explorer from us, not the MatrikonOPCExplorer.

But anyway. You are getting an error in another OPC client (MatrikonOPCExplorer) when trying to make the writes. Why do you think the same should work from QuickOPC, if it it does not work from other OPC client(s) either?

Regards

Hello,

I have searched through source code of QuickOPC version 5.21, and 0xC004D002 is not an error from that version either. It is therefore an error that is just reported by QuickOPC, but does not originate in it. It might come from the OPC server itself.

Do you have some other OPC client application at hand that can be used to verify whether it is possible to connect to your OPC server and operate items in it? If so, have you tried that and what were the results?

If not, please download our Connectivity Explorer (kb.opclabs.com/Tool_Downloads#Connectivity_Explorer ) and try to connect to your OPC server and see if you can browse it, read, write, etc.

One important question: Is you client application (with QuickOPC) on the same computer as the OPC server, or is it on a different computer, and connecting remotely?

Best regards

Hello.

QuickOPC is a library, not an application. It has its own settings, but you need to configure them from inside your own code, programatically. Since you have not indicated that anybody has changed the code to modify the settings, and the application has worked and is no longer working, trying to make it work by changing the settings does not seem reasonable, because it is something *else* that has changed and caused the issue, not the QuickOPC settings.

The error code 0xC004D002 could be one of own QuickOPC errors, but it does *not* appear in current QuickOPC version. It could be that it was an error code used in some earlier version, I need to check that. Please let me know which QuickOPC version you are using. The most reliable way to figure it out is to find one of OpcLabs.* assembly DLLs in your compiled application, and in the WIndows File Explorer, right-click the file, select Properties, and on Details tab, there should be the version(s).

Thank you