WinCC OA UI 3.15.7, Android, Connection not possible ...

Discussions about product bugs & problems!
Note: This is no replacement for the Official ETM Support!
4 posts • Page 1 of 1
roell.f
Posts:4
Joined: Tue Oct 23, 2012 3:18 pm

WinCC OA UI 3.15.7, Android, Connection not possible ...

Post by roell.f »

dear forum,

when trying to connect to the web-client "webclient_http.ctl" on the windows 7 host "my-host" (IP: 192.168.248.149) we get the error message:

Code: Select all

Connection not possible, WCCILdata. Address family not supported by protocol
and then a sequence of:

Code: Select all

WCCOAui (202), 2017.12.05 10:40.04.133, SYS INFO, 101, Connection to (SYS: 0 Data -num 0 CONN: 1) @ my-host: 5191 failed, new attempt in 1 secs
...
where "5191" is the port of the data-manager on "my-host".

the error shows on the following smartphones:
[ol][*]samsung galaxy s3 (GT-I9300)
android version 4.3[*][*]samsung galaxy s5 (SM-G900F)
android version 6.0.1
[*][/ol]app:
  • WinCC OA UI 3.15.7
for connection parameters:
  • IP: 192.168.248.149
  • HTTPS: yes
  • port: 443
  • http-username: "" (none)
  • http-password: "" (none)
we can execute the client "WinCC OA Desktop UI 3.15.007" on a windows 7 PC (instead of an android device) with the same parameters without problems.

well, the smartphones are connected to "my-host" via WLAN (192.168.248.0/24) and the windows 7 client is connected via LAN (10.49.36.0/24). in both cases the clients can connect to "my-host".

what can we do?

best regards

frank

mkoller
Posts:741
Joined: Fri Sep 17, 2010 9:03 am

Re: WinCC OA UI 3.15.7, Android, Connection not possible ...

Post by mkoller »

Try using the IP address (not the host name) in the config file for data and event entries.
I assume you do not have a DNS server in your network which can resolve "my-host" to an IP address the mobile phone can use.

roell.f
Posts:4
Joined: Tue Oct 23, 2012 3:18 pm

Re: WinCC OA UI 3.15.7, Android, Connection not possible ...

Post by roell.f »

using the IP address (not the host name) worked. thank you martin koller.

however that is not the "whole truth".

summary:
we wanted to use the Desktop UI (windows + android) and the ULC UX (windows only). we found the following preconditions for execution of these clients:
  • for multihomed servers (e.g. servers that can be reached via LAN and WLAN): event / data server network interface and Desktop UI client are in the same network.
  • if the client can't resolve server hostname, then server must reply numeric IP addresses:

    Code: Select all

    [general]
    noReverseLookup = 1
  • server runs MX proxy (WCCILproxy).
  • server runs HTTP server (WCCOActrl webclient_http.ctl).
  • client has unfiltered (firewall) access to server ports:
    • data
    • event
    • http / https
  • Desktop UI: server specifies (non default) root panel to load:

    Code: Select all

    [webClient]
    rootPanel = "my-panel.pnl"
    mobileRootPanel = "my-panel.pnl"
  • ULC UX: server specifies (non default) UI arguments:

    Code: Select all

    [httpServer]
    uiArguments = "-m vision -iconBar -menuBar -p my-panel.pnl -user {my-user}:{my-password}"
according to my opinion it is strange to specify the server host (IP or hostname) and http(s) ports in the configuration dialog of the Desktop UI and than the Desktop UI communicates aside these parameters (directly using the data and event port).

in principle the Desktop UI knows enough (hostname and http(s) port) in order to communicate with the server, provided there is some multiplexing service on the server side, which multiplexes data and event signals through the http(s) channel.

maybe, that's something for the ETM developer team :)

best greetings

frank

Gertjan van Schijndel
Posts:634
Joined: Mon Aug 02, 2010 10:37 am

Re: WinCC OA UI 3.15.7, Android, Connection not possible ...

Post by Gertjan van Schijndel »

The Desktop UI does not need direct access to the data and event if the mx proxy (default port: 5678) is reachable.

4 posts • Page 1 of 1