Thanks for reply.

When I use UaExpert, connection works fine. But when I use PROSYS UA OPC Client, this app writes ConnectionFault too as compiled Prosys UA OPC Java Client SDK (SampleConsoleClient).

From the UaExpert:
Node – Root/Objects/Server/ServerStatus with id 2256 and his child State has id 2259 (value: 0 (Running) ).

Please … Whats next?

I compiled original source code with only 3 changes:

in func initialize() – client = new UaClient(promptServerUri()); -> changed on -> client = new UaClient(serverUri); where serverUri is string of address
and in func discover() – discoveryClient.setUri(url); -> changed on -> discoveryClient.setUri(“opc.tcp://172.18.14.82:4870”); because with this doesnt throw exception about bad endpoints.
in func connect() – EndpointDescription[] endpoints = client.discoverEndpoints();
client.setEndpoint(endpoints[1]);
println(“Endpoint———-: ” + client.getEndpoint());
println(“name: “+client.getServerName());

why is the client.getServerName() null or empty? (because of communicationFault ?)

when I run this Sample:
**********************************
Select the security mode to use.
(n=None,s=Sign,e=SignAndEncrypt)
n
Connecting to opc.tcp://172.18.14.82:4870
* Prosys OPC UA Java SDK v2.3.2-781
* (c) Prosys PMS Ltd.

* Running in EVALUATION mode
* Connections will close after 120 minutes

log4j:WARN No appenders could be found for logger (com.prosysopc.ua.UaApplication).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Using SecurityPolicy http://opcfoundation.org/UA/SecurityPolicy#None
Endpoint———-: EndpointDescription: EndpointDescription
EndpointUrl=opc.tcp://172.18.14.82:4870
Server=ApplicationDescription
ApplicationUri=urn:Siemens:Automation:WinCC:PanelRT
ProductUri=urn:Siemens:Automation:WinCC:PanelRT
ApplicationName=Siemens OPC UA Server for WinCC Panel RT
ApplicationType=ApplicationType
name=Server
ordinal=0
GatewayServerUri=null
DiscoveryProfileUri=null
DiscoveryUrls=class java.lang.String[1]
[0]=opc.tcp://HMIasrtp:4870
ServerCertificate=[793] 0x308203153082027ea0030201020204b64d0000300d06092a864886f70d0101050500306531133011060355040a160a5369656d656e73204147311f301d060355040b161657696e43432052756e74696d6520416476616e6365643112301006035504031609484d495f50616e656c31193017060a0992268993f22c6401191609484d495f50616e656c301e170d3039303130373231313032325a170d3139303130373231313032325a306531133011060355040a160a5369656d656e73204147311f301d060355040b161657696e43432052756e74696d6520416476616e6365643112301006035504031609484d495f50616e656c31193017060a0992268993f22c6401191609484d495f50616e656c30819f300d06092a864886f70d010101050003818d0030818902818100e803c7b245cf66368de50e7e3a8153a23152db6bf6d0e9578559f8601e1015eeac296306cd87324d0531806b7bcdf80329cf41757fb2ffa4c7b6e3031a3ebdc9a8c3ffa67afab920578d453cdec10c0e4d604e6ba399dfff561b4db2002128019e76bbc319b86c82b0197912f38f6a2777c08b412a1b48a8fabdfa877ab1cd750203010001a381d13081ce30280603551d23010100041e301c8014a8c6af1d80c93a2484ed8a09068a4c79c964dce48204b64d000030200603551d0e01010004160414a8c6af1d80c93a2484ed8a09068a4c79c964dce4300f0603551d130101ff04053003010100300e0603551d0f0101ff0404030201f630200603551d250101ff0416301406082b0601050507030206082b06010505070301303d0603551d11010100043330318209484d495f50616e656c862475726e3a5369656d656e733a4175746f6d6174696f6e3a57696e43433a50616e656c5254300d06092a864886f70d0101050500038181007ffcdb090a7e70d8df8aacb903f5ec0e5dba13fd6e5244281fa3ce1cc846e4b3b585b2bb8ca30b4b1f15b8b3f4dc7dd3d45b2aa80e50f08e7934964ec172be4af7e3c17d890d9cbc653dde4129a1ee914cddd0816dfea5a8e03732439d4e95cfe7fac326a303c88dc410be93c6bca563dbd9183c75d81dc9527ce3b3a5a4d96a
SecurityMode=MessageSecurityMode
name=None
ordinal=1
SecurityPolicyUri=http://opcfoundation.org/UA/SecurityPolicy#None
UserIdentityTokens=class org.opcfoundation.ua.core.UserTokenPolicy[2]
[0]=UserTokenPolicy
PolicyId=Anonymous
TokenType=UserTokenType
name=Anonymous
ordinal=0
IssuedTokenType=null
IssuerEndpointUrl=null
SecurityPolicyUri=http://opcfoundation.org/UA/SecurityPolicy#None
[1]=UserTokenPolicy
PolicyId=http://opcfoundation.org/UA/SecurityPolicy#Basic128Rsa15
TokenType=UserTokenType
name=UserName
ordinal=1
IssuedTokenType=null
IssuerEndpointUrl=null
SecurityPolicyUri=http://opcfoundation.org/UA/SecurityPolicy#Basic128Rsa15
TransportProfileUri=http://opcfoundation.org/UA-Profile/Transport/uatcp-uasc-uabinary
SecurityLevel=0

name:
ServerState changed from Unknown to CommunicationFault
ServerStatus: null

*** NOT connected to: opc.tcp://172.18.14.82:4870
——————————————————-
– Enter x to close client
——————————————————-
– Enter 0 to start discovery –
– Enter 1 to connect to server –
– Enter 2 to disconnect from server –
– Enter 3 to browse the server address space –
– Enter 4 to read values –
– Enter 5 to write values –
– Enter 6 to register nodes –
– Enter 7 to unregister nodes –
– Enter 8 to create a subscription –
– Enter 9 to call a method –
– Enter 10 to read history –
——————————————————-

Done, whats next now? In console no change … Is there any logfile? And what to do with this:

log4j:WARN No appenders could be found for logger (com.prosysopc.ua.UaApplication).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4…..l#noconfig for more info.

??

Im very demotivated :/ Im sure it is only one line wrong. Or wrong configured OPC UA server?

Hi Bjarne,

now path is OK and loging runs 🙂
But the output text is so huge … output is here -> http://mck-pw.szm.com/log.txt