Professional OPC
Development Tools

logos

Connecting to remote Machines via CODE

More
18 May 2017 07:13 #5159 by support
You are welcome. It is recommended that you put a 'using' directive at the top of your code file, in order to make it easier to reference QuickOPC objects. There are multiple namespaces needed, but you can start with
using OpcLabs.EasyOpc;
using OpcLabs.EasyOpc.DataAccess;
You can then simply write
EasyDAClient.SharedParameters.ClientParameters.UseCustomSecurity = false;
and also many other statements will become shorter.

Best regards

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

More
18 May 2017 06:03 - 18 May 2017 07:11 #5158 by bonsai112
Thank you for your fast response!
After tinkering around I finally found the right line of code I had to use in my MainForm_Load:
OpcLabs.EasyOpc.DataAccess.EasyDAClient.SharedParameters.ClientParameters.UseCustomSecurity = false;

is doing the trick. Now I can finally test and evaluate QuickOPC.

Again, thank you for you great support!
Last edit: 18 May 2017 07:11 by support.

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

More
17 May 2017 19:20 - 17 May 2017 19:20 #5157 by support
Yes indeed, EasyDAClient does not contain ClientParameters. If you look carefully at preceding posts, you will find that EasyDAClient contains SharedParameters which in turn contain ClientParameters.

In addition, be aware that SharedParameters is a *static* property on the EasyDAClient class itself. That it, you need to use the type name (easyDAClient) itself (EasyDAClient.SharedParameters.ClientParameters), and *not* the variable that holds your instance of the EasyDAClient type.
Last edit: 17 May 2017 19:20 by support.

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

More
17 May 2017 17:50 #5156 by bonsai112
where exactly do you add these additional codelines?
I am having a hard time figuring that out...

I always get the error that EasyDAClient does not contain definitions of Clientparameters.

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

More
11 May 2016 14:32 #4035 by support
Great - thanks for letting me know.

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

More
11 May 2016 13:41 #4033 by bojan
We started trying the combinatinations and the line
EasyDAClient.SharedParameters.Client.UseCustomSecurity = false;
Worked for us too.

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

More
17 Aug 2013 22:56 - 06 Mar 2015 07:19 #1394 by arahming
Awesome used this line
OpcLabs.EasyOpc.DataAccess.EasyDAClient.ClientParameters.UseCustomSecurity  = false;
Last edit: 06 Mar 2015 07:19 by support. Reason: code formatting

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

More
17 Aug 2013 15:48 - 06 Mar 2015 07:20 #1392 by support
Can you please try to assign different combinations to following static properties - in the code, before the very first OPC operation is attempted:
EasyDAClient.ClientParameters.UseCustomSecurity 
EasyDAClient.ClientParameters.TurnOffActivationSecurity 
EasyDAClient.ClientParameters.TurnOffCallSecurity

[ADDED LATER: TurnOffCallSecurity only has any influence when UseCustomSecurity == true.]
Last edit: 06 Mar 2015 07:20 by support. Reason: code formatting
The following user(s) said Thank You: arahming

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

More
15 Aug 2013 03:03 #1390 by arahming
Another update I found Interop.OPCAutomation.dll out in the internet and just to check I tested an OPC client with this and it also works.

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

More
14 Aug 2013 20:54 #1388 by arahming
it is a WinForm application
Attachments:

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

Moderators: support
Time to create page: 0.199 seconds

      

 Recommend this on Google