Log In
Register
Topic RSS
12:22, EEST
July 11, 2017
Offline
Sample Code Provided as SimpleClient in “OPC UA Java Client SDK”, initiates close to 127 calls to the OPC UA server. These calls are like CreatSession, ActivateSession, bunch of Read and Browse requests and finally CloseSession.
This SimpleClient is only reading value for Server_ServerStatus_State. Looks like UaClient.client() method sending requests for many other NodeIds. Why this simple code needs to send so many calls to Server ?
Will it always be the case if Client SDK by ProSys going to be used ?
-Sumit
13:40, EEST
December 21, 2011
Offline
Yes, I would expect so.
OPC UA is not a simple protocol. On the other hand, the UaClient Java “component” tries to make it as simple to use as possible. Therefore it is initialising some stuff that it needs later on to communicate properly with the server.
We are using a UaNode-object based approach on the client side, which helps the application development very much. But, due to the nature of OPC UA, initialisation of these objects typically takes several browse and read requests to the server.
The SimpleClient is not the simplest possible OPC UA client application – it is the simplest example of a “full blown” client application just to show what phases it requires to establish the basic level of communication. Real applications typically do a lot more communication with the server.
1 Guest(s)
