Professional OPC
Development Tools

logos

OPC operation failure

More
20 Sep 2018 07:22 #6694 by KAMIN
Replied by KAMIN on topic OPC operation failure
1a. In your test, is the client on the same computer as the server, or is it remote? Same computer
1b. What precisely is in the localAddress? IP
2. Have you tried reading too? Can you do that? What were the results? Yes. It was ok.
3. Have you tried writing using some other OPC client? Can you do that? What are the results? Not yet.
4. You are writing a string. What is the data type of the OPC item you are writing to? Writing object not string. Conversion should be done auto.

Please Log in or Create an account to join the conversation.

More
20 Sep 2018 06:44 #6693 by support
Replied by support on topic OPC operation failure
Thank you, the error number is now clear. Unfortunately, it is the dreaded E_FAIL code, which can mean just about anything. We avoid this code as much as possible on our (client) side, and it is therefore likely that it comes from the OPC server (or the infrastructure).

So, I'll try to narrow it down by some questions:

1a. In your test, is the client on the same computer as the server, or is it remote?
1b. What precisely is in the localAddress?
2. Have you tried reading too? Can you do that? What were the results?
3. Have you tried writing using some other OPC client? Can you do that? What are the results?
4. You are writing a string. What is the data type of the OPC item you are writing to? Normally the OPC "Classic" server is supposed to do conversions, but you never know :-)

Thank you

Please Log in or Create an account to join the conversation.

More
20 Sep 2018 05:51 - 20 Sep 2018 06:39 #6692 by KAMIN
Replied by KAMIN on topic OPC operation failure
I am sorry, it is 2147467259 (0x80004005), when trying to communicate with the server and write a value
private void btnZastoj_Click(object sender, EventArgs e)
        {
            opc.SpremeniRezim("2");
 
            Proizvodnja.FormZastoj frm = new Proizvodnja.FormZastoj();
            frm.ShowDialog();
        }
 
public void SpremeniRezim(string command)
        {
            object value = command;
            opcDaClient.WriteItemValue(localAddress.ToString(), serverName, "S7-1200 test.Device1.Rezim dela", value);
        }
Last edit: 20 Sep 2018 06:39 by support.

Please Log in or Create an account to join the conversation.

More
19 Sep 2018 20:51 #6689 by support
Replied by support on topic OPC operation failure
I think you have mistyped both the decimal and the hexadecimal form of the error number. In both cases, one digit seems to be missing. This makes it impossible for me to determine what the error actually is.

Please re-type the error number correctly.

Also, state from which method this is returned.

Best regards

Please Log in or Create an account to join the conversation.

More
19 Sep 2018 20:16 #6688 by KAMIN
OPC operation failure was created by KAMIN
We get this error code An OPC operation failure with error code -214746729 (0x8000400) occurred, originating from 'OpcLabs.EasyOpcRaw.DataAccess.RawEasyDAClient'.

We are connectiong to the KepServerEx 6.5.

What seems to be a problem? We jsut need to write 10 params and read 4 and the app is for one SRV with one client.


Are there any other solutions for Visual studio 2017, .net 4.5 and C#?

Please Log in or Create an account to join the conversation.

Moderators: support
Time to create page: 0.179 seconds

      

 Recommend this on Google