feherz said
I am trying to read/write a ‘value’-attribute from my OPC Server.

When I try to read the value I get the following errormessage:

attribute: Value
com.prosysopc.ua.StatusException: Bad_NoCommunication (0x80310000) “Communication with the data source is defined, but not established, and there is no last known value available.” StatusCode=Bad_NoCommunication (0x80310000) “Communication with the data source is defined, but not established, and there is no last known value available.”

This status code comes from the server, so you have a working connection to the server established, but the server does not have a working connection to the device that is providing the Value for the variable.

StatusException in general is related to operational errors, whereas ServiceException is related to the service call errors. If the service call succeeds, there may still be bad quality values coming from the server for individual operations, such as the read operation in this case.

It might be due to the client doesn’t seem to use my Endpoint.
06/30/2015 16:17:47.034 INFO Using an alternate endpoint URL ‘opc.tcp://ibhlinkua_001211:48010’ instead of the requested ‘opc.tcp://192.168.3.200:48010’

The client first makes a connection to ‘opc.tcp://192.168.3.200:48010’ to discover the endpoints of the server: among these, it does not find an exact match, but decides to use ‘opc.tcp://ibhlinkua_001211:48010’ instead. The client is then connecting to this endpoint to establish the actual connection. However, it is still using the original address ‘192.168.3.200:48010’ to initialise the socket connection. So this message is more informative and can usually be ignored.